Page 345 - Big data - Concept and application for telecommunications
P. 345

Big data - Concept and application for telecommunications                       6

            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.





                                                                                          Application    337
   340   341   342   343   344   345   346   347   348   349   350