{"id":347120,"date":"2024-10-20T00:24:37","date_gmt":"2024-10-20T00:24:37","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-iso-iec-29341-26-112017\/"},"modified":"2024-10-25T23:53:54","modified_gmt":"2024-10-25T23:53:54","slug":"bs-iso-iec-29341-26-112017","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-iso-iec-29341-26-112017\/","title":{"rendered":"BS ISO\/IEC 29341-26-11:2017"},"content":{"rendered":"
This service definition is compliant with [1]. It defines a service type referred to herein as the MediaManagement<\/span><\/i> service.<\/p>\n The MediaManagement<\/span><\/i> service enables the feature to set-up a media session on a Telephony Client (TC), under the control of a Telephony Control Point (TelCP). This service provides the following functions:<\/p>\n Set up a media session to send and\/or receive media streams between a TC and a TS. To set up a media session, The MediaManagement<\/span><\/i> service provides an interface for a TelCP to negotiate the media capabilities (e.g., codec types, IP address, port number etc.) between a TC and a TS. This ensures a TelCP to select a common set of the media capabilities to be used to send and\/or receive media streams between a TS and a TC. After the media session is established, the TC starts sending and\/or receiving media streams based on the media chapabilities negotiated between the TC and the TS.<\/p>\n<\/li>\n The mechanism to modify the media capabilities of an existing media session. For instance, if a media session is created for sending and receiving an audio media stream, it is possible to modify the media session for sending and receiving a video media stream.<\/p>\n<\/li>\n The mechanism to terminate a media session.<\/p>\n<\/li>\n<\/ul>\n Information technology. UPnP Device Architecture – Telephony device control protocol. Level 2. Media management service<\/b><\/p>\n\n
PDF Catalog<\/h4>\n
\n
\n PDF Pages<\/th>\n PDF Title<\/th>\n<\/tr>\n \n 2<\/td>\n National foreword <\/td>\n<\/tr>\n \n 7<\/td>\n Foreword <\/td>\n<\/tr>\n \n 14<\/td>\n 1 Scope
2 Normative references <\/td>\n<\/tr>\n\n 15<\/td>\n 3 Terms, definitions, symbols and abbreviated terms
3.1 Provisioning terms
3.2 Symbols
3.3 Terms <\/td>\n<\/tr>\n\n 16<\/td>\n 3.4 Abbreviated terms <\/td>\n<\/tr>\n \n 17<\/td>\n 4 Notations and conventions
4.1 Text conventions
4.2 Data Types
4.3 Vendor-defined Extensions
5 Service Modeling Definitions
5.1 Service Type
5.2 MediaManagement Service Architecture <\/td>\n<\/tr>\n\n 18<\/td>\n 5.3 State Variables
5.3.1 State Variable Overview
5.3.2.1 XML Schema Definition
5.3.2.2 Description of fields in the MediaSessionInfo structure <\/td>\n<\/tr>\n\n 20<\/td>\n 5.3.4.1 XML Schema Definition
5.3.4.2 Description of fields in the MediaCapabilityInfo structure <\/td>\n<\/tr>\n\n 21<\/td>\n 5.3.5.1 XML Schema Definition
5.3.5.2 Description of fields in the MediaSessionInfoList structure <\/td>\n<\/tr>\n\n 22<\/td>\n 5.4 Eventing and Moderation
5.4.1 Eventing of MediaSessionInfo
5.5 Actions
5.5.1.1 Arguments <\/td>\n<\/tr>\n\n 23<\/td>\n 5.5.1.2 Argument Descriptions
5.5.1.3 Service Requirements
5.5.1.4 Control Point Requirements When Calling The Action
5.5.1.5 Dependency on Device State
5.5.1.6 Effect on Device State
5.5.1.7 Errors <\/td>\n<\/tr>\n\n 24<\/td>\n 5.5.2.1 Arguments
5.5.2.2 Argument Descriptions
5.5.2.3 Service Requirements
5.5.2.4 Control Point Requirements When Calling The Action <\/td>\n<\/tr>\n\n 25<\/td>\n 5.5.2.5 Dependency on Device State
5.5.2.6 Effect on Device State
5.5.2.7 Errors
5.5.3.1 Arguments
5.5.3.2 Argument Descriptions
5.5.3.3 Service Requirements
5.5.3.4 Control Point Requirements When Calling The Action <\/td>\n<\/tr>\n\n 26<\/td>\n 5.5.3.5 Dependency on Device State
5.5.3.6 Effect on Device State
5.5.3.7 Errors
5.5.4.1 Arguments
5.5.4.2 Argument Descriptions <\/td>\n<\/tr>\n\n 27<\/td>\n 5.5.4.3 Service Requirements
5.5.4.4 Control Point Requirements When Calling The Action
5.5.4.5 Dependency on Device State
5.5.4.6 Effect on Device State
5.5.4.7 Errors <\/td>\n<\/tr>\n\n 28<\/td>\n 5.5.5.1 Arguments
5.5.5.2 Argument Descriptions
5.5.5.3 Service Requirements
5.5.5.4 Control Point Requirements When Calling The Action
5.5.5.5 Dependency on Device State
5.5.5.6 Effect on Device State
5.5.5.7 Errors <\/td>\n<\/tr>\n\n 29<\/td>\n 5.5.6 Error Code Summary
5.6 Service Behavioral Model
5.6.1 State Diagrams <\/td>\n<\/tr>\n\n 30<\/td>\n 6 XML Service Description <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" \n\n
\n Published By<\/td>\n Publication Date<\/td>\n Number of Pages<\/td>\n<\/tr>\n \n BSI<\/b><\/a><\/td>\n 2017<\/td>\n 200<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"featured_media":347129,"template":"","meta":{"rank_math_lock_modified_date":false,"ep_exclude_from_search":false},"product_cat":[2641],"product_tag":[],"class_list":{"0":"post-347120","1":"product","2":"type-product","3":"status-publish","4":"has-post-thumbnail","6":"product_cat-bsi","8":"first","9":"instock","10":"sold-individually","11":"shipping-taxable","12":"purchasable","13":"product-type-simple"},"_links":{"self":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product\/347120","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product"}],"about":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/types\/product"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/media\/347129"}],"wp:attachment":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/media?parent=347120"}],"wp:term":[{"taxonomy":"product_cat","embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product_cat?post=347120"},{"taxonomy":"product_tag","embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product_tag?post=347120"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}