WO2011105771A2 - Procédé et appareil pour commander une interruption de session dans un système de réseau domestique - Google Patents

Procédé et appareil pour commander une interruption de session dans un système de réseau domestique Download PDF

Info

Publication number
WO2011105771A2
WO2011105771A2 PCT/KR2011/001212 KR2011001212W WO2011105771A2 WO 2011105771 A2 WO2011105771 A2 WO 2011105771A2 KR 2011001212 W KR2011001212 W KR 2011001212W WO 2011105771 A2 WO2011105771 A2 WO 2011105771A2
Authority
WO
WIPO (PCT)
Prior art keywords
session
field
block
source device
control
Prior art date
Application number
PCT/KR2011/001212
Other languages
English (en)
Korean (ko)
Other versions
WO2011105771A3 (fr
Inventor
이민수
김진호
전범진
Original Assignee
엘지전자 주식회사
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 엘지전자 주식회사 filed Critical 엘지전자 주식회사
Publication of WO2011105771A2 publication Critical patent/WO2011105771A2/fr
Publication of WO2011105771A3 publication Critical patent/WO2011105771A3/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2803—Home automation networks
    • H04L12/2838—Distribution of signals within a home automation network, e.g. involving splitting/multiplexing signals to/from different paths
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management

Definitions

  • the present invention relates to a home network system, and more particularly, to methods of blocking sessions formed in a home network and devices for supporting the same.
  • the present invention relates to High Definition Base T (HD BaseT) technology.
  • HD BaseT High Definition Base T
  • TVs televisions
  • PCs computers
  • audio which are currently used in homes or offices, a large number of various cables must be used.
  • HD high-definition
  • HDMI High Definition Multimedia Interface
  • the HDMI cable uses uncompressed transmission, so there is no need to embed a compressed decoder or decoding software.
  • HDMI technology allows existing complex audio / video (AV) devices to be transmitted over a single cable using a format that combines video, audio and / or video signals into one digital interface. There is an advantage to simplify the connection wiring.
  • HDMI technology only one-way service from a multimedia source device to a display device is possible, and a cable length of only 15 meters can be supported.
  • HDMI technology it is difficult to effectively apply an environment in which a plurality of multimedia sources are supported together.
  • HDMI technology is limited in its use because it does not support USB, networking, and daisy chain.
  • the HDBaseT technology disclosed in the present invention provides 100Mbps Ethernet based on CAT5 / 6 (Category 5/6) cable and 100Mbps Ethernet for uncompressed high definition video and audio transmission using a single cable.
  • HDBaseT technology can be used in home theaters and digital video recorders (DVRs), Blu-Lay Disc Players (BDPs), game consoles, personal computers (PCs) and / or mobile products. You can also connect multiple displays to configure multiple screens.
  • DVRs digital video recorders
  • BDPs Blu-Lay Disc Players
  • PCs personal computers
  • HDBaseT technology can provide two-way communication, multiple streams, and even power over a single cable.
  • a session must be established in order to communicate between HDBaseT devices, such as HDBaseT adapters (hereinafter, T-adapters), on the HDBaseT network.
  • HDBaseT devices such as HDBaseT adapters (hereinafter, T-adapters)
  • T-adapters HDBaseT adapters
  • a session defines a communication network path and schedules the appropriate services to be included in it.
  • an object of the present invention is to provide an efficient communication method and a device supporting the same in a home network system.
  • Another object of the present invention is to provide a method for blocking a session formed on an HDBaseT network.
  • Another object of the present invention is to define a priority of control messages used on the HDBaseT network, and to provide a method of blocking, sharing or controlling sessions between users.
  • the present invention relates to a home network system, and to methods of blocking sessions formed in a home network and apparatuses for supporting the same.
  • a method for controlling session blocking in an HDBaseT network includes a first session blocking indicator field from a starting entity (terminal, control point (CP)) in a source device (eg Blu-ray Display) Receiving a session initiation request message for requesting to establish a session between a device and a sink device (eg TV) and receiving a session initiation response message including a second session block indicator field in response to the session initiation request message at the source device; And sending to the initiating entity.
  • CP control point
  • the first session block indicator indicates a view block field indicating whether to block output data of the source device in a formed session, a control block field indicating whether to block a remote control of the source device in the session, and a sink in the session. It may include a screen blocking field indicating whether to block the input data to the device.
  • the second session block indicator field may include information about a device blocked in the session.
  • the first embodiment includes the steps of: transmitting a session route request message to the sink device to confirm whether the session can be initiated by the session start request message; and receiving a session route response message indicating whether the session can be started. It may include.
  • the source device when at least one of the view blocking field, the control blocking field, and the screen blocking field is set to '0', the source device preferably blocks a session control message related to a session received from another initiating entity.
  • a session initiation request message including a first priority indicator field from an initiating entity in a source device and requesting the establishment of a session between the source device and the sink device And receiving the session initiation response message including the second priority indicator field in the response to the session initiation request message from the source device to the initiation entity.
  • the first priority indicator field may indicate one of high, medium, and low priority of the session.
  • the second priority indicator field may indicate one of high, medium, and low priority of the session.
  • the source device when the source device receives from the other initiation entity a session initiation request message indicating a priority lower than the priority indicated by the first priority indicator field, the source device ignores the session initiation request message received by the other initiation entity. It is desirable to.
  • the session initiation request message further includes a session block indicator field, wherein the session block indicator field is a view block field indicating whether to block output data of the source device in the formed session, and a remote to the source device in the session. And a screen blocking field indicating whether the input data to the sink device is blocked in the session.
  • the session block indicator field is a view block field indicating whether to block output data of the source device in the formed session, and a remote to the source device in the session.
  • a screen blocking field indicating whether the input data to the sink device is blocked in the session.
  • the source device supporting the method for controlling the session blocking in the HDBaseT network may control the operation of the source device in the control point management entity (CPME) and the HDBaseT network for supporting the method for controlling the session blocking. It may include a supporting port device management entity (PDME), a receiver for receiving a message, and a transmitter for transmitting a message.
  • CPME control point management entity
  • PDME port device management entity
  • the receiver receives from the initiating entity a session initiation request message that includes a first session block indicator field and requests to establish a session between the source device and the sink device, and the transmitter is in response to the session initiation request message.
  • the session initiation response message including the second session block indicator field may be transmitted to the initiation entity.
  • the first session blocking indicator may include a view blocking field indicating whether the output data of the source device is blocked in the formed session, a control blocking field indicating whether the remote control of the source device is blocked in the session, and a sink device in the session. It may include a screen blocking field indicating whether to block the input data.
  • the second session block indicator field may include information about a device blocked in the session.
  • the source device may block a session control message related to a session received from another initiating entity.
  • the receiver receives a session initiation request message from the initiating entity, the session initiation request message including a first priority indicator field and requesting the establishment of a session between the source device and the sink device.
  • the session initiation response message including the second priority indicator field may be transmitted to the initiation entity.
  • the first priority indicator field may indicate one of high, medium, and low priority of the session.
  • the second priority indicator field may indicate one of high, medium, and low priority of the session.
  • the source device when the source device receives from the other initiation entity a session initiation request message indicating a priority lower than the priority indicated by the first priority indicator field, the source device preferably ignores the session initiation request message received by the other initiation entity.
  • the session initiation request message further includes a session block indicator field, wherein the session block indicator field is a view block field indicating whether to block output data of the source device in the formed session, or the source device in the session.
  • the control block field indicating whether to block the remote control and the screen block field indicating whether or not to block the input data to the sink device in the session.
  • the first occupied user may not be disturbed by other users.
  • the HDBaseT technology disclosed in the present invention can perform high quality video / audio transmission, 3D video transmission, data communication (Internet), power supply and / or various control signals using a single cable. have. Thus, one cable can be used without having to use a large number of cables.
  • HDBaseT technology can greatly increase user convenience by supplying uncompressed HD multimedia contents, data, control signals, and power to multiple rooms simultaneously through a single cable.
  • FIG. 1 is a diagram illustrating an example of a hierarchical model of an HDBaseT network that can be used in embodiments of the present invention.
  • FIG. 2 is a view showing the structure and function of the HDBaseT adapter used in the embodiments of the present invention.
  • FIG. 3 is a diagram illustrating an example of an HDBaseT network (T network) in which embodiments of the present invention are used.
  • FIG. 4 is a diagram illustrating a four-level hierarchical reference method and identifier structure used to identify an HDBaseT entity as an embodiment of the present invention.
  • FIG. 5 is a diagram illustrating an example of a session blocking control service according to an embodiment of the present invention.
  • FIG. 6 is a diagram illustrating an example of a method for controlling a session blocking according to an embodiment of the present invention.
  • FIG. 7 is a diagram illustrating an example of a session block indicator structure.
  • FIG. 8 illustrates session initiation request message structures used in embodiments of the present invention.
  • FIG 9 illustrates structures of a session start response message used in embodiments of the present invention.
  • FIG. 10 is a diagram illustrating a structure of a session block update request message used in embodiments of the present invention.
  • FIG. 11 is a diagram illustrating a structure of a session block update response message used in embodiments of the present invention.
  • FIG. 12 is a diagram illustrating another example of a session blocking control service according to an embodiment of the present invention.
  • FIG. 13 is a diagram illustrating an example of a method for controlling session blocking using priority according to an embodiment of the present invention.
  • FIG. 14 is a diagram illustrating an example of a priority indicator structure used in embodiments of the present invention.
  • 15 is a diagram illustrating an example of a session initiation request message structure including priority information used in embodiments of the present invention.
  • FIG. 16 illustrates a session start response message structure including priority information used in embodiments of the present invention.
  • 17 is a diagram illustrating another example of a method for controlling session blocking using priority as an embodiment of the present invention.
  • FIG. 18 illustrates an example of a session control message structure according to an embodiment of the present invention.
  • FIG. 19 is a diagram illustrating devices used in embodiments of the present invention.
  • the present invention relates to a home network system, and to methods of blocking sessions formed in a home network and apparatuses for supporting the same.
  • each component or feature may be considered to be optional unless otherwise stated.
  • Each component or feature may be embodied in a form that is not combined with other components or features.
  • some components and / or features may be combined to form an embodiment of the present invention.
  • the order of the operations described in the embodiments of the present invention may be changed. Some components or features of one embodiment may be included in another embodiment or may be replaced with corresponding components or features of another embodiment.
  • Downstream refers to a flow of logical data or streams transmitted from a device providing content to a device receiving content, and is the same as the term downlink. Can be used in the sense.
  • uplink stream refers to the flow of logical data or streams in the opposite direction of the downstream, and may be used in the same meaning as the term uplink.
  • the source device provides contents such as a Blu-lay Disc Player (BDP), a digital video recorder (DVR), a computer, an Xbox, a laptop, and the like.
  • a sink device may refer to a home theater, a television, a monitor, and various display devices on which content is implemented.
  • the sink device may be referred to as a destination or destination entity of data and / or content.
  • end node refers to an entity located at both ends of the transmitting and receiving ends of the HDBaseT network.
  • the end node may be a source device, a sink device and / or a control point device.
  • Embodiments of the present invention may be supported by HDBaseT standard documents (especially HDBaseT Specification Draft Version 1.0 and / or version 1.4). That is, obvious steps or portions not described among the embodiments of the present invention may be described with reference to the above documents. In addition, all terms disclosed in the present document can be described by the above standard document.
  • the HDBaseT network in which the embodiments of the present invention are implemented is a parallel of real-time data streams and Ethernet data such as HDMI 1.4 streams, Sony / Philips Digital Interconnect Format (S / PDIF) streams, and Universal Serial Bus (USB) streams. It aims to provide high-end networking of home cable structure.
  • S / PDIF is the standard for transmitting digital audio signals, the origin of which is in AES / EBU
  • the HDBaseT Link operates to support four UTP (Unshielded Twisted Pair) / STP (Shielded Twist Pair) CAT5e / 6 / 6a cables, including 100m, point-to-point (PTP), and two middle RJ45 connectors. .
  • the downlink sublink supports 8 Gbps, 500 Msymboles / sec and PAM 16 symbols, and the uplink sublink supports 300 Mbps, 25 Msymboles / sec and PAM 16 symbols. It also supports bi-directional 200Mbps between USB 2.0, S / PDIF, IR and Universal Asynchronous Receiver / Transmitter (UART), and 100Mbps bidirectional Ethernet.
  • HDBaseT can support multiple streams simultaneously on a single link and can support at least eight HDMI 1.4 downlink streams, twelve USB or S / PDIF bidirectional streams, and eight IR and eight UART bidirectional streams.
  • FIG. 1 is a diagram illustrating an example of a hierarchical model of an HDBaseT network that can be used in embodiments of the present invention.
  • HDBaseT networks are based on the Open System Interconnection (OSI) reference model.
  • OSI Open System Interconnection
  • embodiments of the present invention are applied to the HDBaseT technology, and FIG. 1 discloses a new network hierarchy structure in which the HDBaseT technology is combined with the basic OSI reference model.
  • the HDBaseT network includes a physical layer (L1) as a first layer, a data link layer (L2) as a second layer, a network layer as a third layer,
  • the fourth layer is a transport layer
  • the fifth layer is a middleware layer
  • the sixth layer is an application layer.
  • the functions provided by the first layer include a physical coding function for transmitting a T-stream, an HDBaseT Stand By mode Interface (HDSBI) function, and the like.
  • HDSBI HDBaseT Stand By mode Interface
  • the functions provided by the second layer include the flow control function, the error control function, the access control function, the quality of service (QoS) function and the HDBaseT device.
  • HDBaseT Configuration Database HDCD
  • Framing Framing
  • Physical Addressing Power Control
  • PoE Power over Ethernet
  • the third layer provides a logical addressing function, a routing function for optimized transmission of data, an access control function, and the like.
  • the flow control function In the fourth layer, the flow control function, the error control function, the connection control function, the service point addressing function, and the partitioning and combining of higher data are used to control the flow of the service. Segmentation / Reassembly function is provided to support this.
  • the legacy device configuration function for providing legacy device information to support the legacy device, another network view for communicating with other networks, privacy for protecting data, and Provides functions (Privacy / Privilege) to prioritize data.
  • the sixth layer provides a function of HDBaseT Network Control Application (HDBaseT Network Control Application) for controlling communication through HDBaseT network and a function of showing multi-streamed video in picture in picture (PIP) method. can do.
  • HDBaseT Network Control Application HDBaseT Network Control Application
  • PIP picture in picture
  • HDBaseT devices used in embodiments of the present invention may transmit and receive data, streams, etc. based on the hierarchical model structure of FIG. 1.
  • the HDBaseT adapter (hereinafter, T-adapter) converts other types of protocol / interface / application data formats into the HDBaseT data format.
  • the T-Adapter uses a T-Network (network used by HDBaseT) service to communicate with other T-Adapters, and the target T-Adapter stream (hereinafter referred to as T-stream) of the converted HDBaseT system. Can be returned to its original format.
  • T-Network network used by HDBaseT
  • T-stream target T-Adapter stream
  • FIG. 2 is a view showing the structure and function of the HDBaseT adapter used in the embodiments of the present invention.
  • the T-adapter used in the HDBaseT system may include one or more of an end node (eg, dongle), an HDMI selector, and a USB selector.
  • an end node eg, dongle
  • an HDMI selector e.g., HDMI
  • USB selector e.g., USB 2.0
  • the T-adapter includes end nodes (eg dongle), and the function of the T-adapter includes a source discovery function and a device ID mapping (Device ID to HDMI / Ethernet / USB ports mapping). It also provides Tx Adapter control using HDMI-CEC, HDMI Selector and USB Selector.
  • the end node including the T-adapter may support HDCD (HDBaseT Configuration Database), Power over Ethernet function, Ethernet port, HDMI port, and USB (1.0 / 2.0 / 4.0) port.
  • the T-adapter may include one or more HDMI input ports.
  • the T-adapter can connect HDMI data from one source device to a sink device connected to another T-adapter (ie, a receiving adapter) using HDMI switching technology.
  • the HDMI selector may select one or more HDMI input ports by controlling the Consumer Electronics Control (HDMI-CEC) interface according to a user's designation. This is called HDMI selection.
  • HDMI-CEC Consumer Electronics Control
  • the T-adapter may also include one or more USB input ports.
  • the T-adapter can select one of the USB ports according to the user's specification, which can be performed by the USB selector included in the T-adapter.
  • a single stream T-adapter supports peer-to-peer connections of other adapters on an HDBaseT network.
  • the T-Adapter supports legacy networks such as Ethernet, USB and CEC, allowing Control Points (CPs) to use legacy networks and control HDMI switches.
  • CPs Control Points
  • T-Adapter used in HDBaseT systems
  • Key features of the T-Adapter used in HDBaseT systems include HDMI switching, Source Discovery to find source devices connected to the T-Adapter's HDMI port and / or USB port, and USB based on HDMI port selection.
  • Source discovery refers to the ability of the T-Adapter to discover what the actual source device is on its port.
  • the T-Adapter doesn't know what the actual device name is on the HDMI, Ethernet and USB ports. The device name is assigned directly by the user.
  • the T-Adapter obtains and configures HDBaseT Link Internal Controls (HLIC) acquisition / configuration processes that include a Device Description String to obtain and set the actual device name from the HDBaseT Configuration Database (HDCD) device entity. For example, you can use HLIC Get Transaction / HLIC Set Transaction.
  • HDCD HDBaseT Configuration Database
  • the port mapping function refers to a function of mapping device identifiers to HDMI ports, Ethernet ports, and USB ports.
  • the T-Adapter may select the corresponding HDMI / Ethernet / USB ports as a group of ports according to the source device identifier selection.
  • the USB Hub can be included in the receiving T-Adapter attached to the USB port.
  • the T-adapter may be included inside the source device, the sink device, and / or the switch, and may be independently implemented outside the HDBaseT devices according to a user's request.
  • FIG. 3 is a diagram illustrating an example of an HDBaseT network (T network) in which embodiments of the present invention are used.
  • T networks can provide predictable, stable, high efficiency and low latency services to support Ethernet services and real time communication streams.
  • the T-Adapter can provide the appropriate HDBaseT service through a connection group of Switch Devices and Daisy Chain Devices that support serial connectivity.
  • the T-adapter can select the appropriate T-service over the switch device and the daisy chain device according to the requirements of the native protocol / interface / application. At this time, the switch device and the daisy chain devices do not need to know the type of T-adapter and the message processing method.
  • the T-network indicates an area in which the HD baseT stream converted by the T-adapter is transmitted and means a communication area from the source T-adapter to the sink T-adapter.
  • the T-Adapter may be used as a Tx Adapter in Downstream (DS) and as a Rx Adapter in UpStream (US).
  • DS Downstream
  • US UpStream
  • the Tx adapter may be used in the same manner as the source adapter
  • the Rx adapter may be used in the same manner as the sink adapter. That is, one T-adapter may perform the functions of the Tx adapter and the Rx adapter according to the transmission form of the stream.
  • HD base T-stream means a set of HD base T packet streams corresponding to information belonging to one native session. All packets belonging to one T-stream contain the same Session ID (SID) tokens.
  • SID Session ID
  • the T stream may optionally contain different types of packets, respectively.
  • FIG. 4 is a diagram illustrating a four-level hierarchical reference method and identifier structure used to identify an HDBaseT entity as an embodiment of the present invention.
  • one HDBaseT device may have one or more port devices, and each port device may have one or more T-Groups.
  • each T-group may have one or more T-adapters.
  • the four-level hierarchical reference method includes a device MAC address for identifying management objects (ie, PDME, SDME, and CPME) included in the HDBaseT device, and a port identifier for identifying each port. ID), HD BaseT Group Identifier (TG ID) for identifying each HDBaseT group (hereinafter, T-Group), and Type Mask, which is a unique mask for identifying each T-Adapter. Can be.
  • a device ID is used to identify the HDBaseT device.
  • an Ethernet MAC address may be used as a device identifier, which is called a device MAC address.
  • the device MAC address is a unique identifier for identifying management entities included in the corresponding HDBaseT device.
  • Port Device Management Entity (PDME), Switching Device Management Entity (SDME) and Control Point Management Entity (CPME) preferably support Ethernet Termination
  • the Ethernet MAC address may be used as a unique identifier.
  • the PDME preferably communicates with the link partner SDME using HLIC processing.
  • the PDME can also borrow the identifier of the SDME by deriving the device identifier of the SDME.
  • the PDME may use the SDME MAC address as the device identifier of the PDME and use the port index of the SDME as the port index of the PDME.
  • the SDME must communicate all management processes to the PDME. If the link partner is not a switch that is a direct point of point-to-point, the PDME may not have a unique identifier.
  • Port Referencing (Device ID: Port ID) method is required to uniquely identify the PDME.
  • the Ethernet MAC address as the device identifier, it is possible to form a linkage between the T-network and the E-network, and manage the T-network and sessions using the Ethernet communication.
  • a port identifier field is used to identify a port device and a T-G identifier field is used to identify a T-group.
  • the port identifier field and the T-group field may be used together, and may be configured with a total size of 2 bytes (10 bits and 6 bits, respectively).
  • the port identifier and the T-G identifier may be referred to as a TPG identifier (or a group port identifier).
  • Two bytes of the TPG identifier field may carry a 10 bit index of the port device and a 6 bit T-group index within the port device.
  • the non-zero port index of 1 to 1023 provides a unique reference to the port device in the HDBaseT device.
  • a non-zero T group index of 1 to 63 bits provides a unique reference to a specific T-group in the port device.
  • the TPG identifier provides a unique reference for the port in the HDBaseT and may be referred to as the port identifier. If the port identifier is zero, the TPG identifier does not provide any meaningful value.
  • the type mask field is used to identify the T-adapter.
  • Each T-group may have a T-Adapter Type Mask field indicating what type of T-Adapter is associated with that group.
  • the basic type mask field is a 16-bit field (MSB is b15, LSB is b0), and each bit represents a specific type of T-adapter associated with the corresponding T-group.
  • Table 1 below shows an example of the bit index of the type mask field corresponding to the T-adapter type.
  • bit indexes 0 and 1 represent HDMI source devices and sink devices
  • bit indexes 4 and 5 represent USB hosts and USB devices / hubs
  • bit indexes 8 and 9 represent S / PDIF source and sink devices, respectively.
  • bit indexes 12 and 13 indicate an IR transmitter (Infra-Red Tx) and an IR receiver (Infra-Red Rx)
  • bit index 14 indicates a UART (Universal Asynchronous Receiver / Transmitter).
  • bit index 15 (b15) indicates that an additional extension field of 16 bits is further used to indicate a T-adapter type.
  • HDBaseT devices do not assume that index 15 is always set to zero.
  • HDBaseT devices can support up to three extended fields. For example, an HDBaseT device may support a type mask field up to 64 bits.
  • Each T-group may not be associated with multiple instances of a particular T-adapter type.
  • the type mask field may uniquely identify only a particular T-adapter instance within a T-group.
  • one or more T-adapter instances may be referenced from the T-adapter group associated with the T-group using the type mask reference of the present invention.
  • FIG. 4 illustrates a hierarchical reference method for identifying a T-adapter as a size of 10 bytes. That is, when transmitting a T-stream from a source T-adapter to a sink T-adapter, a message (or stream) including a 10-byte source T-adapter identifier and a 10-byte sink T-adapter identifier may be transmitted. have.
  • the signals may be added or decreased for each field.
  • the HDBaseT control & management protocol (HD-CMP) message used in the communication between the PDME of the HDBaseT end node and the SDME of the HDBaseT switch includes an 8-byte source identifier (eg, For example, a device identifier 6 bytes + TPG identifier 2 bytes) and an 8 byte sync identifier may be used.
  • a type mask is used to distinguish an interface of a port. For example, when one T-group port identifier (TPG ID) is included in an HDMI data packet, an IR data packet, and a USB data packet, a type mask is used to distinguish each interface.
  • TPG ID T-group port identifier
  • the type mask is also used when referring to a particular interface within the T-group port identifier at session establishment. For example, when establishing a session between two ports using HD-CMP messages, the type mask may also be used to specify the source and sink in the HD-CMP messages.
  • a session must be established for the T-adapter to communicate with other T-adapters on the T-network.
  • the session defines the path of the bidirectional communication and communication network and schedules the appropriate services contained therein.
  • the term session may be used interchangeably with the term Link.
  • Each activated session is identified by the SID token (ie session ID or stream ID) that accompanies each HDBaseT stream.
  • SID token ie session ID or stream ID
  • HDBaseT switches included in the network path switch packets according to SID tokens.
  • the initiation and initiation of a session is to configure and establish a communication network path of the session to exchange HDBaseT data. Termination of a session also means releasing the communication network path to stop data exchange.
  • methods for establishing a transmission / reception path of a data stream from a source device to a sink device may be referred to as session routing.
  • FIG. 5 is a diagram illustrating an example of a session blocking control service according to an embodiment of the present invention.
  • the HDBaseT network of FIG. 5 includes a BDP, a notebook PC and an XBOX as a source device, and a TV1 and TV2 as a sink device.
  • the HDBaseT network may be connected to a sink end node, a source end node, and a switch (or host) which is an HD baseT node.
  • the sink end node and the source end node are preferably T-adapters, and may convert HDMI data, USB data, and Ethernet data into HD baseT data and provide them between the two ends.
  • the sink end node and the source end node may be located inside or outside each source node or sink node.
  • a switch is an entity that connects and routes each source node and sink node in an HDBaseT network.
  • FIG. 5 shows a case where three users use one HDBaseT network.
  • the three users are Bob, John, and Alice.
  • Bob first establishes a session with TV1, a sink device, and BDP, a source device.
  • Bob has also blocked TV1 and BDP first.
  • Another user, John can BDP send a session control message to establish a session with BDP and TV2, but John's session control message is ignored because BDP is already blocked by Bob.
  • another user, Ellis attempts to establish a session with TV1 or a laptop computer with TV1, but Alice's request to start a session is ignored because TV1 is already blocked by Bob.
  • the session blocking control service means that a user of a control point (CP) allows and disallows control of a session through HDBaseT devices.
  • the user of the CP may block a user of a CP that is not allowed between HDBaseT devices by using the session blocking control.
  • Session blocking control may use an HD-CMP service to send and receive session blocking information with other HDBaseT devices.
  • the SDME or PDME may be responsible for initiating and terminating the session.
  • SDME, PDME and CPME can support HD-CMP service for controlling and managing sessions.
  • the session blocking control service provides three types of session blocking.
  • a view lock is to block other users from viewing the video content when the user is provided with the video content through the session.
  • Control lock is to block other users from controlling the HDBaseT device.
  • Display lock Screen lock is to prevent other users from providing different contents to the display of the session that the user is using.
  • Each CP may transmit a session control message including a session block indicator field, and a CP management entity (CPME) may allow or disallow a session control request of a CP according to device blocking information in a formed session.
  • CPME may allow or disallow the session control request of the CP according to the priority level information of the CP.
  • Device blocking information can be used interchangeably with session blocking information.
  • the session blocking information may be included as an indicator field of one octet (one byte) in the session control message.
  • the session blocking information may be referred to as a session lock indicator field, and may include a 1-bit viewing block field, a control block field, and a screen block field.
  • the Block View field can indicate block information to block the HDMI output of the source device in the session
  • the Control Block field can indicate block information to block remote control of the source device in the session. Blocking information may be indicated to block the HDMI input of the sink device of the session.
  • the CPME included in the HDBaseT device may have a device blocking control function to allow or disallow a session control message.
  • the CPME may manage device blocking information that allows or disallows control messages.
  • the CPME preferably indicates that sink and source devices are not blocked until the CPME allows processing of the CP control message. If one of the sink device and the source device is blocked, the CPME may ignore the CP control message.
  • the CPME can be included in any HDBaseT device.
  • the CPME may communicate using an HDBaseT network and an Ethernet network, and may communicate with one or more CPs.
  • the CPME may perform device blocking control in the following order.
  • Step 1 The CPME may generate, maintain, and update the device blocking information table for each CP.
  • Step 2 CPME may receive session control message from CPs.
  • Step 3 The CPME checks whether the display of the sink and the view of the source are blocked in the received session control message. If the display of the sink device and the view of the source device are not blocked, the CPME allows processing of the corresponding session control message. Otherwise, the CPME may ignore the session control message.
  • Step 4 The CPME may update the device blocking information table according to the session blocking information included in the session control message.
  • Table 2 shows an example of a device blocking information table format.
  • Bob has established a session (session ID: 1) between BDP (source ID: 1) and TV1 (sink ID: 2).
  • the CPME of the TV1 and the BDP may maintain and update the device blocking information table shown in Table 2 above.
  • FIG. 6 is a diagram illustrating an example of a method for controlling a session blocking according to an embodiment of the present invention.
  • FIG. 6 shows how users Bob and Elise control HDBaseT devices in one HDBaseT network.
  • Bob controls the first control point CP1 and Ellis controls the second control point CP2.
  • CP1 and CP2 may be provided in a mobile device or the like.
  • the control point may be provided in a smartphone, a mobile terminal and / or a remote controller.
  • the first control point CP1 may transmit a session start request message to the BDP to form a session between the Blu-ray display player BDP and TV1.
  • the session initiation request message may include fields indicating BDP as a source device and TV1 as a sink device, and may include a session block indicator for session blocking (S601).
  • the session block indicator includes a Display Lock field that indicates blocking information for the HDMI input to the sink device in a particular session, and a control lock that indicates whether or not to allow or control the source device by another user in a particular session.
  • a Display Lock field that indicates blocking information for the HDMI input to the sink device in a particular session
  • a control lock that indicates whether or not to allow or control the source device by another user in a particular session.
  • Field and a View Lock field indicating blocking information on the HDMI output of the source device in a specific session. At this time, each field indicates that the block is blocked when it is set to '0' and when the block is released when it is set to '1'.
  • the CPME of the BDP exchanges a session route request message and a session route response message with the TV1 and intermediate devices to confirm whether a session between the BDP and TV1 can be formed.
  • the session blocking indicator may be included in the session route request and response message and transmitted and received (S602).
  • the CPME of the BDP blocks the BDP in the formed session. That is, the content of the BDP is controlled and blocked by Bob's CP1, so it is provided only to TV1 and not to other users.
  • the BDP may provide HDMI session data, IR session data, and the like to TV1 through the formed session.
  • the CPME of the TV1 provides the screen of the TV1 only to Bob according to the screen blocking field included in the session blocking indicator, and blocks the other user.
  • the viewing block and the screen block are established in the session between the BDP and the TV1 (S603).
  • the CPME of the BDP sends a session start response message indicating that the session start request is successful to CP1 (S604).
  • the CP2 of the Alice may transmit a session start request message indicating that the source device is BDP and the sink device is TV2 (S605).
  • the CPME of the BDP Upon receiving the session start request message from CP2, the CPME of the BDP checks whether a session can be established between the BDP and TV2. However, the BDP ignores the session start request from the CP2 since the view blocking is already set by the CP1. Accordingly, the BDP indicates that the view of the BDP is blocked by the CP1, and transmits a session start response message to the CP2 including a NACK signal indicating that the session start request has failed (S606).
  • CP2 can show Alice the session blocking information of the BDP to show why the session initiation request of the CP was blocked.
  • Bob can unblock the view of the BDP.
  • Bob's CP1 may send a device block update request message including the session block indicator to the BDP.
  • the view blocking field and the screen blocking field of the session blocking indicator are set to '1' (S607).
  • the CPME of the BDP which confirms that the device blocking update request from CP1 is valid, releases the view blocking of the BDP.
  • the CPME of the BDP may set the view blocking field of the session blocking indicator to '1' to notify that the view blocking of the BDP has been released, and may transmit a device blocking update response message including the session blocking indicator to the CP1 (S608). ).
  • a new session can be created between the BDP and other sink devices.
  • Alice's CP2 may send a Session Initiation Request message to the BDP to establish a new session between BDP and TV2.
  • the source session start request message may indicate that the source device is BDP and the sink device is TV2 (S609).
  • the CPME of the BDP can confirm that the view of the BDP and the screen of the TV2 are not blocked. Accordingly, the CPME of the BDP receiving the session initiation request message from the CP2 exchanges the session route request message and the session route response message with the TV2 and the intermediate devices to confirm whether the session between the BDP and the TV2 can be formed. do.
  • the session blocking indicator may be included and transmitted in the session route request and response message (S610).
  • the BDP may provide HDMI session data, IR session data, and the like to the TV2 through the formed session (S611).
  • the CPME of the BDP may transmit a session start response message notifying that the new session between the BDP and the TV2 has been formed (S612).
  • FIG. 8 illustrates session initiation request message structures used in embodiments of the present invention.
  • the session initiation request message is sent from the initiating entity initiating the session to session partners (eg, the first partner or the second partner) that is the management entity to confirm their session initiation possibilities and the requirements of the session. do.
  • session partners eg, the first partner or the second partner
  • the session initiation request message may be transmitted over an Ethernet (eg, an E-network) using an HD-CMP message.
  • the session initiation request message may include an HD-CMP Msg OpCode (HD-CMP Msg OpCode) field, a final target reference (FTR) field, and a real source reference (RSR).
  • HD-CMP Msg OpCode HD-CMP Msg OpCode
  • FTR final target reference
  • RSR real source reference
  • Field Path Description Section (PDS) field
  • NPA Network Path Availability
  • SIQ Session ID Query
  • HD-CMP payload-in operation It may include a Code Op_SNPM Body field.
  • the HD-CMP Msg Op code field may include a Mod field indicating a method of transmitting a session start request message to another device and a Dir field indicating a direction in which the session start request message is transmitted.
  • the Mod field is two bits in size to deliver the message to all ports connected to the device (00), and to forward the message to designated ports for delivery to a routing path known by the device (01). For example, it may represent forwarding a message to a designated port 10 for forwarding on one optimal routing path, or forwarding a message 11 on a path defined in a PDS field.
  • the Dir field may indicate a forwarding direction of the message and may indicate downstream (DL) 01, upstream (US) 10, or bidirectional (Mixed Path) 11.
  • the final target reference (FTR) field is used to identify the session partner (eg, the managed entity of the final destination) to which the session initiation request message will be sent, and the source reference (RSR) field identifies the initiation entity that sends the session initiation request message. Used for.
  • the final target reference field may be 8 bytes in size, and may include a MAC address identifying the managed entity of the destination session partner and a TPG identifier identifying the session partner's port device, and the source reference (RSR) field may be It may be 8 bytes in size and include the MAC address of the management entity included in the initiator and the TPG identifier identifying the port device of the initiator.
  • the final target reference (FTR) field may be referred to as a final destination entity reference (FDER) field
  • the source reference field may be a source entity reference (RSER) Real. Source Entity Reference) field.
  • the PDS field is included in the payload of the HD-CMP message and includes information on PDS entities indicating an input port and an output port from the device.
  • the NPA field is included in the payload of the HD-CMP message and indicates the possible throughput and the accumulated number of packet streams.
  • the SIQ field is used to find the activated / already assigned session identifier in the network path.
  • an action code U_SNPM body field which is an HD-CMP payload includes a downstream session size (DS Session Size) field indicating a downstream session size and an upstream session size indicating an upstream session size.
  • DS Session Size downstream session size
  • US Session Size US Session Size
  • Source ID field indicating the identifier of the source device selected by the control point (CP)
  • a source T-Group field indicating a device and a Source T-Adapter Mask field indicating a T-adapter mask of the T-group of the source device may be included.
  • the operation code U_SNPM body field is a Sink ID field indicating an identifier of the sink device selected by the control point (CP), the T-group and the port device of the sink device when the session is coupled with other sessions.
  • a sink T-Adapter Mask field indicating a T-adapter mask of the T-group of the sink device.
  • the operation code U_SNPM body field of the session initiation request message of FIG. 8A may further include the session blocking indicator described in FIG. 7.
  • the source device represents a device providing content and the sink device represents a device to which content is provided. If the source device or the sink device couples between sessions, the source T-group identifier field or the sink T-group identifier field is set to a value other than '0', respectively. However, the Source T-Adapter Mask field is set to null if the source device supports intersession coupling and the source group token number is not '0', and the Sync T-Adapter Mask field is set to the session device If it supports filling and the sink T-group is not '0', it is set to null. In this case, when the source T-group identifier and the sink T-group identifier are not '0' and the source source T-adapter mask field and the sink T-adapter mask field are not '0', the session may be started. .
  • the source identifier field, the source T-group field, and the source T-adapter field may be used as a This Partner T-Adaptor Reference (TPTR) field indicating the T-adapter of the current session partner.
  • TPTR This Partner T-Adaptor Reference
  • the sink identifier field, the sink T-group field, and the sink T-adapter field may be used as another partner T-adapter reference (OPTR) field indicating the T-adapter of another session partner.
  • OPTR partner T-adapter reference
  • the final target reference field is used to identify the BDP
  • the source reference field is used to identify the CP1 that sent the session initiation request message.
  • the source identifier field, the source T-group identifier field, and the source T-adapter mask field of the operation code U_SNPM body field are used to identify the MAC address, port number, and T-adapter of the BDP which is the source device.
  • the sync identifier field, the sync T-group identifier field, and the sync T-adapter mask field are used to identify the MAC address, port number, and T-adapter of the TV which is the sink device.
  • the session initiation request message includes a sander identifier (Sender ID) field indicating an identifier of a control point device (that is, an initiating entity) that transmits the session initiation request message, and a session initiation request message is sent to A destination ID field identifying a management object that is a session partner of a destination and a message type field indicating a type of a corresponding message may be included.
  • Sender ID sander identifier
  • the sender identifier may be used to identify an initiating entity that transmits the session initiation request message
  • the destination identifier may be used to identify a management entity that is a session partner of the final destination in which the session initiation request message is transmitted.
  • the session initiation request message includes a source identifier identifying a source device selected by the control point, a source group identifier field indicating a group port number of the source when the current session is coupled with another session, a source Source Port ID field to identify the session source port of the device, Sink ID field to identify the sink device selected by the control point, group port of the sink if the current session is coupled with another session It may further include a sink group ID field indicating a number and a sink port ID field for identifying a session sink port of the sink device.
  • the source group identifier field may be set to a value other than '0' when the source device supports the session coupling.
  • the source port identifier field may be set to a null value when the source device supports session coupling and the source group identifier field is not '0'.
  • the sink group identifier field may be set to a value other than '0'.
  • the sink port identifier field may be set to a null value when the sink device supports session coupling and the sink group identifier is set to a value other than '0'.
  • the session initiation request message of FIG. 8B may further include a device lock field of one octet.
  • the device blocking field may include a view blocking field, a control blocking field, and a screen blocking field. In this case, the device blocking field may perform the same function as the session blocking indicator described with reference to FIG. 7.
  • the source identifier field, the source group field, and the source port field of FIG. 8B may be used as a This Partner T-Adaptor Reference (TPTR) field indicating the T-adapter of the current session partner.
  • TPTR This Partner T-Adaptor Reference
  • the sink identifier field, the sink group field, and the sink port field may be used as another partner T-adapter reference (OPTR) field indicating a T-adapter of another session partner.
  • OPTR partner T-adapter reference
  • FIG 9 illustrates structures of a session start response message used in embodiments of the present invention.
  • the session initiation response message may be sent by the session partners in response to the session initiation request message.
  • a session initiation response message can also be sent over Ethernet using an HD-CMP message.
  • the session initiation request message and the session initiation response message may be transmitted and received between two management entities in the HDBaseT subnetwork through a unicast SNPM message.
  • the HD-CMP Msg OpCode field has the same structure as the HD-CMP message action code field of FIG. 8 (a), but further includes a Response Code field. Include.
  • the Response Code field is 3 bits that indicates that the session initiation request was successful (Success), that the request was attempted from another device (Redirection), or that the request was not complete because the request was in error and the error is corrected. Indicates that an attempt could be made (Sender Error), the request could not be completed due to a recipient error, and the request could be retried to another device (Receiver Error), or the session initiation request failed May indicate Global Failure.
  • the Final Target Reference (FTR) field is used to identify the initiator entity that sent the session initiation request message
  • the Source Reference (RSR) field identifies the session partner management entity that transmitted the session initiation response message.
  • the final target reference field may include a MAC address for identifying a management entity included in the initiating entity and a TPG identifier for identifying a port device of the initiating entity.
  • the Source Reference (RSR) field may include a MAC address identifying the session entity's management entity and a TPG identifier identifying the session partner's port device.
  • the PDS field, the NPA field, and the SIQ field may perform the same function as the PDS field, the NPA field, and the SIQ fields included in the session initiation request message.
  • the Operation Code Per Op Code U_SNPM Body field of the Session Initiation Response message indicates the downstream data size of the session indicated by the Session ID field and the NPA field that uniquely identifies the session initiated at the source device. It may include an upstream session size (US Session Size) field indicating an upstream data size of the session indicated by the downstream session size (DS Session Size) field and the NPA field.
  • US Session Size upstream session size
  • DS Session Size downstream session size
  • the operation code U_SNPM Body field is a Source ID field indicating an identifier of a source device selected by a control point (CP), and the T- of the source when the session is coupled with another session.
  • the apparatus may further include a source T-group identifier field indicating a group identifier and a source T-adapter mask field indicating a T-adapter mask of the T-group of the source device.
  • the operation code U_SNPM body field is a Sink ID field indicating the identifier of the sink device selected by the control point (CP), the sink T- indicating the sink's T-group when the current session is coupled with other sessions. It may further include a Sink T-Group field and a Sink T-Adapter Mask field indicating a T-adapter mask of the T-group of the sink device.
  • the action code U_SNPM body field may further include a session lock field.
  • the session block field is a field into which the session block indicator described in FIG. 7 enters. At this time, the session blocking field of the session start response message indicates whether viewing, control and / or screen of the corresponding session is blocked.
  • the source identifier field, source T-group field and source T-adapter mask field in the action code U_SNPM body field are used to identify the adapter of the source device when the session is initiated, and the sink identifier field, sink T-group field and sink T
  • the adapter mask field may be used to identify the adapter of the sink device when the session is initiated.
  • the source identifier field, the source T-group field, and the source T-adapter mask field may be used as a This Partner T-Adaptor Reference (TPTR) field indicating the T-adapter of the current session partner.
  • TPTR This Partner T-Adaptor Reference
  • the sink identifier field, the sink T-group field, and the sink T-adapter field may be used as another partner T-adapter reference (OPTR) field indicating the T-adapter of another session partner.
  • OPTR partner T-adapter reference
  • a session initiation response message includes a sander identifier indicating an identifier for a device transmitting a session initiation response message, and a destination ID indicating a destination to which a session initiation response message is transmitted. It may include a message type field indicating the type of the message and an OP Code field indicating whether the session start is successful or failed.
  • the sender identifier may be used to identify a management entity that is a session partner that transmits the session initiation response message, and the destination identifier may be used to identify the initiation entity that transmitted the session initiation request message.
  • the session initiation response message includes a session ID indicating a session unique to the source device, a session type field indicating whether the type of session being initiated is HDMI, Ethernet, USB, or IR, and the source of the session.
  • Source ID identifying the device
  • Source group field indicating the number of group ports of the source when the session is coupled with other sessions
  • Source port ID indicating the port identifier of the session source port of the source device
  • a source group identifier indicating the number of group ports of the source when the session is coupled with other sessions
  • a sink port identifier identifying the session sink port of the link device.
  • the session initiation response message may further include a device blocking field.
  • the device blocking field is a field including the session blocking indicator described with reference to FIG. 7 and may indicate whether viewing, control, and / or screen are blocked in the formed session.
  • a session coupled means that one session works in conjunction with another session.
  • a session for transmitting an HDMI packet operates in conjunction with a session for transmitting an USB packet
  • a session for transmitting an HDMI packet operates in conjunction with a session for transmitting an IR packet.
  • FIG. 10 is a diagram illustrating a structure of a session block update request message used in embodiments of the present invention.
  • FIG. 10 (a) shows an example of a session block update request message structure.
  • the structure of the session block update request message of FIG. 10 (a) is the same as that of the session start request message of FIG. 8 (a).
  • the session block update request message may be used to block or unblock the view, control, and / or display of the source device and / or the sink device in the session in which the control point (CP) is formed. Used.
  • FIG. 10B Another example of the structure of the session block update request message shown in FIG. 10B is shown.
  • the structure of the session block update request message of FIG. 10 (b) is the same as that of the session start request message of FIG. 8 (b).
  • the session block update request message may be used to block or unblock the view, control, and / or display of the source device and / or the sink device in the session in which the control point (CP) is formed. Used.
  • FIG. 11 is a diagram illustrating a structure of a session block update response message used in embodiments of the present invention.
  • the session block update response message indicates whether the block or release of the session is completed in response to the session block update request message.
  • FIG. 11 (a) shows an example of a session block update response message structure.
  • the structure of FIG. 11 (a) is the same as that of the session block update request message of FIG. 10 (a), but each field is used for a session block update response.
  • the action code U_SNPM body field includes a session lock field indicating whether the view, control and / or screen of the session is blocked or unblocked.
  • FIG. 11 (b) shows another example of a session block update response message structure.
  • the structure of FIG. 11 (b) is the same as that of the session block update request message of FIG. 10 (b). However, each field is used for the session block update response.
  • the session block update response message includes a Device Lock field indicating whether the view, control and / or screen of the session is blocked or the block is released.
  • the session block indicator, session start request / response message, and session block update request / response messages disclosed in FIGS. 7 to 11 may be used in the embodiments disclosed in FIGS. 5 and 6.
  • FIG. 12 is a diagram illustrating another example of a session blocking control service according to an embodiment of the present invention.
  • Session control by priority means that a user of a CP allows or disallows control of a session according to the priority of each user. For example, if a large number of users exist in the HDBaseT network, session blocking control based on priority may protect a session of a user having a higher priority from session control of another user having a lower priority.
  • the session control method based on priorities may use three levels of priority.
  • the first level represents a low priority
  • the second level represents a priority normal
  • the third level represents a priority high.
  • each CP has a priority
  • the CPME may allow or disallow a session control request according to the priority of each CP.
  • the CPME may only allow session control messages with high priority or the same priority.
  • session control messages, session initiation request message and session initiation response message may include a Priority Level field.
  • the CPME may have a Device Lock Control Function to allow or disallow a session control message according to session control priority.
  • the CPME can create and manage an active session table that indicates device blocking information and session control priority information to allow or disallow session control messages.
  • Table 3 below shows an example of an active session table including device blocking information and priority information.
  • the CPME may process the session control message for the new session when the existing sessions formed between the source node and the sink node have the same or lower priority than the newly created session. If the source node and / or sink node are blocked, the CPME can ignore the session control message.
  • Session blocking control based on priority may use HD-CMP to transmit and receive session blocking information.
  • Bob establishes and controls a session between TV1 and BDP with a priority of the third level (High).
  • John wants to establish a session with BDP and TV2, but BDP is already occupied by Bob's CP.
  • the priority of the zone is the first level (Low) and lower than the priority of Bob, the session start request of the zone is blocked.
  • Alice attempts to establish a session between BDP and TV3, but Alice's priority is lower than Bob's priority at the second level, so Alice's request to start the session is blocked.
  • the session established by Bob may be released, and the session control request of zone or Alice may be performed. Accordingly, as shown in FIG. 12, the control of the session may be adaptively performed by using the priority in the session blocking control service.
  • FIG. 13 is a diagram illustrating an example of a method for controlling session blocking using priority according to an embodiment of the present invention.
  • each user has a unique identifier along with the session control priority.
  • each user's CPME creates and manages an active session table as shown in Table 3.
  • Table 3 it is assumed that CP1 of Bob has a priority of the third level and CP2 of Alice has a priority of the second level (S1310a and S1310b).
  • Bob's CP1 sends a session start request message with a third level of priority to the BDP to establish a session between the BDP and TV1.
  • the priority information may be indicated by a priority indicator of 1 octet, and the priority indicator may be included in the session start request message (S1320).
  • the CPME of the BDP may exchange a session route request / response message with the TV1 and / or intermediate devices to determine whether the requested session can be established between the BDP and TV1 ( S1330).
  • the CPME of the BDP and the TV1 updates the active session table they are creating and managing.
  • the BDP may provide HDMI session data and / or IR session data to TV1 through the established session.
  • the newly formed session has a third level of priority (S1340).
  • the CPME of the BDP may transmit a session start response message indicating whether the session establishment is successful to the CP1 (S1350).
  • Alice's CP2 sends a Session Initiation Request message with a second level of priority to the BDP to establish a session between the BDP and TV2.
  • the priority of the session initiation request message may be indicated by the priority indicator field (S1360).
  • the CPME of the BDP may compare the priority of the session initiation request message received in the CP2 with the session activity table managed by the BDP. If the priority of CP2 is higher than or equal to the priority of the session formed between CP1 and BDP, the existing session is released and the session start request of CP2 proceeds. However, the priority of CP2 is lower than the session priority of CP1 as the second level. Accordingly, the BDP may block the session initiation request of the CP2 and transmit a session initiation response message to the CP2 including session control priority information (e.g. priority indicator) and a NACK signal indicating the failure of the session initiation request (S1370).
  • session control priority information e.g. priority indicator
  • NACK signal indicating the failure of the session initiation request
  • FIG. 14 is a diagram illustrating an example of a priority indicator structure used in embodiments of the present invention.
  • the priority indicator may be used to inform the session blocking information.
  • priority information may be represented as a 2-bit priority field. For example, '00' indicates no priority, '01' indicates the priority of the first level, '10' indicates the priority of the second level, and '11' indicates the priority of the third level. Can be represented.
  • 15 is a diagram illustrating an example of a session initiation request message structure including priority information used in embodiments of the present invention.
  • the session initiation request message is used to initiate a session with session control priority.
  • the session initiation request message may be sent using DH-CMP.
  • FIG. 15 (a) illustrates an example of a session initiation request message structure including a priority indicator.
  • the structure of the session initiation request message of FIG. 15 (a) is almost the same as that of the session initiation request message of FIG. 8 (a).
  • the Session Control Priority field is used in the operation code U_SNPM body field and not the session block field.
  • the session control priority field may include the priority indicator described with reference to FIG. 14.
  • FIG. 15 (b) shows another example of a session initiation request message structure including a priority indicator.
  • the structure of the session initiation request message of FIG. 15B is almost identical to that of the session initiation request message of FIG. 8B. The only difference is that the Session Control Priority field is used rather than the Device Lock field.
  • the session control priority field may include the priority indicator described with reference to FIG. 14.
  • FIG. 16 illustrates a session start response message structure including priority information used in embodiments of the present invention.
  • the session initiation response message is used to inform whether the session establishment is success or failure based on the session control priority information.
  • the session initiation response message may be sent using DH-CMP.
  • FIG. 16 (a) shows an example of a session initiation response message structure including a priority indicator.
  • the structure of the session start response message of FIG. 16 (a) is almost the same as that of the session start response message of FIG. 8 (b).
  • the Session Control Priority field is used in the operation code U_SNPM body field and not the session block field.
  • the session control priority field may include the priority indicator described with reference to FIG. 14.
  • FIG. 16 (b) shows another example of a session start response message structure including a priority indicator.
  • the structure of the session start response message of FIG. 16 (b) is almost the same as that of the session start response message of FIG. 8 (b).
  • the only difference is that the Session Control Priority field is used rather than the Device Lock field.
  • the session control priority field may include the priority indicator described with reference to FIG. 14.
  • the session priority indicator, the session start request message, and the session start response message disclosed in FIGS. 14 to 16 may be used in FIGS. 12 and 13.
  • the session block indicator of FIG. 7 and the priority indicator of FIG. 14 may be used together in one management message.
  • it may be included in the session messages disclosed in FIGS. 8 to 11 and 15 to 16.
  • each HDBaseT device can receive block control based on session priority as well as device block.
  • 17 is a diagram illustrating another example of a method for controlling session blocking using priority as an embodiment of the present invention.
  • the media switch may automatically block control from other users (e. G. CP2) on the multimedia devices. That is, when there is a session started first, the media switch can block another user's session initiation by transmitting a busy signal to other users.
  • the media switch may accommodate the control request of other users after the continuous control of the CP1 is completed.
  • the CP1 may initiate session control using a media switch and multiple commands for HDBaseT service between the first HDBaseT device (Device 1) and the second HDBaseT device (Device 2). There is (S1701).
  • the CP1 transmits a session control message to the media switch, and the media switch transmits the session control message to the device 1 (S1702).
  • the media switch may prevent session control from another user.
  • the media switch may block control commands input from the CP2 by transmitting a busy signal to the CP2 (S1704).
  • CP1 may continuously transmit the session control message to the media switch for session control, and the media switch may transmit the session control message to device 2 (S1705).
  • the media switch may transmit a session end message to the notifier that the session control is completed to the CP1 (S1706).
  • the media switch may allow session initiation from another user. Therefore, when session control is started from CP2 after the session of CP1 is terminated, the media switch allows session control initiation of CP2 (S1707).
  • the media switch upon receiving the session control message from the CP2, the media switch can transmit the session control message to the device 1 and / or the device 2 (S1708).
  • FIG. 18 illustrates an example of a session control message structure according to an embodiment of the present invention.
  • a session control message includes a message type field indicating a type of a corresponding message, a control type field indicating a type of session control, a control point identifier field identifying a control point transmitting a control message, and a destination of the control message.
  • a destination identifier field that indicates, a stream identifier field that identifies the stream from the source node in the session, a source identifier field that identifies the source node that provides the content of the session, and a sink identifier that identifies the sink node that receives the content of the session. May contain fields.
  • the session control message includes a data type field indicating the data type of the corresponding session, a data size field indicating the size and / or data rate of the corresponding data, and an input port indicating the number of the input port of the switch for the corresponding stream. It may further include a number field and an output port number field indicating the number of the output port of the switch for the stream.
  • the session control message may further include a priority field indicating priority information of the corresponding control message and a device blocking information field indicating whether the HDBaseT device is blocked.
  • the priority information may indicate a level of priority as a size of one octet.
  • the priority information may indicate a first level (Low) indicating a low priority, a second level (Normal) indicating a normal priority, and a third level (High) indicating a high priority. .
  • the device blocking information field may be 1 octet in size and indicate whether a corresponding device is blocked.
  • the device blocking information may include a screen blocking field indicating whether a display of a device is blocked, a control blocking field indicating whether a control of a corresponding session is blocked, and whether a view of the device is blocked. It may include a view blocking field indicating whether or not.
  • the session control message may further include a reserved bit field and a CRC field according to a user's request.
  • the session control message described in FIG. 18 may be used for session initiation request / response messages, session termination request / response messages, session notification request / response messages, and / or session block update request / response messages.
  • the session control message described in FIG. 18 may be used in FIG. 17.
  • the media switch may allow or disallow session control of the users CP1 and CP2 using the priority information and the device blocking information included in the session control message.
  • FIG. 19 is a diagram illustrating devices used in embodiments of the present invention.
  • the HDBaseT device includes a source device providing content, a sink device receiving content, a switch for switching data between the source device and the sink device, and an adapter converting original data into HDBaseT.
  • a pure Ethernet device may include a terminal, and the terminal may be called a mobile station (MS), a user equipment (UE), or a subscriber station (SS).
  • the source device and the sink device may be called a source node, a sink node, or an end node, respectively.
  • Source and sink devices are transmitters for transmitting and receiving T-Adapter, HDBaseT data, or original data that mutually convert original data (e.g., HDMI data, USB data, and / or Ethernet data) to HDBaseT data. And a receiver.
  • the source device and the sink device may further include a PDME for discovering and managing a knowledge base about all other T-adapters located in the proper direction of the same sub-network.
  • the PDME can use the periodic SNPM sent by the switch's edge SDME to form a knowledge base related to the performance, status and directional connectivity of the other T-adapters.
  • the PDME may be provided in the source device and the sink device to perform functions for providing or receiving content.
  • the source device and sink device may optionally include a CPME that discovers and manages a knowledge base of all T-adapters and their associated devices (edge SDME including PDMEs and embedded T-adapters). Can be.
  • CPME is a management entity that manages CP. That is, the CPME may control the CP to start, manage, and terminate the session.
  • the switch includes a transmitter and a receiver capable of transmitting and receiving HDbaseT data and original data.
  • the switch also includes an E-switching entity for switching Ethernet data and a T-switching entity for switching HDBaseT data.
  • the switch discovers and maintains a knowledge base and their directional connectivity to all T-adapters located in the same subnetwork and their associated devices (eg, edge SDMEs including PDMEs and embedded T-adapters). May include an SDME.
  • the SDME may detect an output port that targets a particular T-adapter / end node in the appropriate direction.
  • the switch may optionally further include a CPME.
  • the terminal is a pure Ethernet device, and may include a transmitter for transmitting Ethernet data and a receiver for receiving Ethernet data.
  • the terminal may be provided with a CPME for controlling the CP and CP. That is, the user can start, control and end the session by using the CPME of the terminal.
  • the terminal may include a Routing Processor Entity (RPE).
  • RPE Routing Processor Entity
  • the source device / sink device and the switch constitute an HDBaseT network. That is, the source device, the switch, and the sink device can transmit and receive HDBaseT data and process Ethernet data according to user requirements.
  • the terminal can transmit and receive control messages on the source device / sink device and / or switch and the Ethernet network.
  • the present invention can be applied to various home networks and home entertainment industries, and particularly to the HDBaseT system.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Automation & Control Theory (AREA)
  • Computer And Data Communications (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente invention porte sur un système de réseau domestique, et divulgue des procédés pour interrompre des sessions formées dans un réseau domestique, et des appareils pour supporter ceux-ci. Dans un mode de réalisation de la présente invention, un procédé de commande d'interruption de session dans un réseau HDBaseT peut comprendre les étapes consistant à : recevoir, par un dispositif source, à partir d'un objet initial, un message de demande d'initiation de session, qui comprend un premier champ indicateur d'interruption de session et demande la formation d'une session entre le dispositif source et un dispositif récepteur ; et la transmission par le dispositif source, à l'objet initial et en réponse au message de demande d'initiation de session, d'un message de réponse d'initiation de session comprenant un second champ indicateur d'interruption de session.
PCT/KR2011/001212 2010-02-23 2011-02-23 Procédé et appareil pour commander une interruption de session dans un système de réseau domestique WO2011105771A2 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US30695710P 2010-02-23 2010-02-23
US61/306,957 2010-02-23
US32772810P 2010-04-26 2010-04-26
US61/327,728 2010-04-26

Publications (2)

Publication Number Publication Date
WO2011105771A2 true WO2011105771A2 (fr) 2011-09-01
WO2011105771A3 WO2011105771A3 (fr) 2011-12-29

Family

ID=44507391

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2011/001212 WO2011105771A2 (fr) 2010-02-23 2011-02-23 Procédé et appareil pour commander une interruption de session dans un système de réseau domestique

Country Status (1)

Country Link
WO (1) WO2011105771A2 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014123394A1 (fr) * 2013-02-07 2014-08-14 엘지전자(주) Procédé et appareil de commande de session entre des dispositifs sur un réseau comprenant plusieurs dispositifs

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040218599A1 (en) * 2003-05-01 2004-11-04 Genesis Microchip Inc. Packet based video display interface and methods of use thereof
US20050091302A1 (en) * 2003-10-24 2005-04-28 Microsoft Corporation Systems and methods for projecting content from computing devices
KR20070040280A (ko) * 2005-10-11 2007-04-16 엘지전자 주식회사 Ｓｉｐ 기반 서비스 방법

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040218599A1 (en) * 2003-05-01 2004-11-04 Genesis Microchip Inc. Packet based video display interface and methods of use thereof
US20050091302A1 (en) * 2003-10-24 2005-04-28 Microsoft Corporation Systems and methods for projecting content from computing devices
KR20070040280A (ko) * 2005-10-11 2007-04-16 엘지전자 주식회사 Ｓｉｐ 기반 서비스 방법

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014123394A1 (fr) * 2013-02-07 2014-08-14 엘지전자(주) Procédé et appareil de commande de session entre des dispositifs sur un réseau comprenant plusieurs dispositifs
JP2016514293A (ja) * 2013-02-07 2016-05-19 エルジー エレクトロニクス インコーポレイティド 複数個のデバイスを含むネットワーク上におけるデバイス間セッションを制御する方法及び装置
KR101734739B1 (ko) 2013-02-07 2017-05-11 엘지전자 주식회사 복수개의 디바이스를 포함하는 네트워크 상에서 디바이스 간 세션을 제어하는 방법 및 장치
US10341392B2 (en) 2013-02-07 2019-07-02 Lg Electronics Inc. Method and apparatus for controlling session between devices on network including multiple devices

Also Published As

Publication number Publication date
WO2011105771A3 (fr) 2011-12-29

Similar Documents

Publication Publication Date Title
WO2011105815A2 (fr) Procédé et appareil pour routage de session dans un système à réseau familial
WO2011105780A2 (fr) Procédé et appareil pour lancer une session dans un système de réseau domestique
WO2011105770A2 (fr) Procédé et appareil de transmission de messages dans un réseau domestique
JP3906394B2 (ja) Ｍｐｅｇ信号のクロックの修復のための方法と装置
KR100418303B1 (ko) 멀티미디어네트워크를위한크로스바/허브설비
WO2010128827A2 (fr) Système et procédé de fourniture de services liés au téléphone à des dispositifs utilisant upnp sur un réseau domestique
WO2010019022A2 (fr) Système et procédé d'émission et de réception d'un appel sur un réseau domestique
WO2020076110A1 (fr) Dispositif électronique pour déterminer un canal opérationnel p2p et procédé associé
WO2013048008A1 (fr) Procédé et appareil d'enregistrement d'un dispositif auprès d'un serveur
WO2012099378A2 (fr) Procédé et appareil pour commander l'émission et la réception de contenu
WO2011155762A2 (fr) Procédé pour la communication avec d'autres dispositifs, et dispositif de communication
WO2015190880A1 (fr) Procédé et appareil de transmission et de réception de données via une interface hdmi
WO2022124870A1 (fr) Procédé d'émission et de réception de données et dispositif destiné audit procédé dans un système de communication sans fil à courte portée
KR100656487B1 (ko) Ｉｐ 디지털 방송 시스템에서의 ｉｇｍｐ 네트워크 장비 및그 신호 처리 제어방법
WO2011136538A2 (fr) Procédé et appareil de transmission de données ethernet par l'intermédiaire d'une interface audio/vidéo
WO2021091241A1 (fr) Procédé, appareil et programme informatique de définition de clé de chiffrement dans un système de communication sans fil, et support d'enregistrement associé
WO2011105771A2 (fr) Procédé et appareil pour commander une interruption de session dans un système de réseau domestique
WO2011136581A2 (fr) Procédé de réglage de réseau et récepteur iptv utilisant le procédé
WO2020246767A1 (fr) Procédé, dispositif et programme informatique pour commander des données audio dans un système de communication sans fil, et support d'enregistrement associé
WO2020262926A1 (fr) Procédé, dispositif et programme informatique permettant de réguler et de gérer l'état d'un dispositif périphérique dans un système de communication sans fil et support d'enregistrement associé
KR20060121233A (ko) Ｉｐ 및 비-ｉｐ 신호들을 분배하기 위한 이더넷 기반네트워크
WO2019203580A1 (fr) Procédé et dispositif permettant de fournir un service de diffusion en continu audio à l'aide de la technologie bluetooth à faible énergie
WO2015010252A1 (fr) Procédé, dispositif et système de fourniture de services dans un système de câble coaxial
WO2011145896A2 (fr) Procédé et appareil de détermination d'un coordinateur
WO2021215776A1 (fr) Procédé, dispositif et programme informatique pour choisir un canal dans un système de communication sans fil, et support d'enregistrement s'y rapportant

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11747661

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase in:

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11747661

Country of ref document: EP

Kind code of ref document: A2