WO2011105771A2

WO2011105771A2 - Method and apparatus for controlling session interrupt in a home network system

Info

Publication number: WO2011105771A2
Application number: PCT/KR2011/001212
Authority: WO
Inventors: 이민수; 김진호; 전범진
Original assignee: 엘지전자 주식회사
Priority date: 2010-02-23
Filing date: 2011-02-23
Publication date: 2011-09-01
Also published as: WO2011105771A3

Abstract

The present invention relates to a home network system, and discloses methods for interrupting sessions formed in a home network, and apparatuses for supporting same. In one embodiment of the present invention, a method for controlling session interrupt in an HDBaseT network may comprise the steps of: a source device receiving, from an initial object, a session initiation request message, which includes a first session interrupt indicator field and requests the formation of a session between the source device and a sink device; and the source device transmitting, to the initial object and in response to the session initiation request message, a session initiation response message including a second session interrupt indicator field.

Description

Method and device for controlling session blocking in home network system

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. In order to use televisions (TVs), computers (PCs), and audio, which are currently used in homes or offices, a large number of various cables must be used.

Some of the high-definition (HD) transmission cable technologies currently in use today have limited transmission speeds and limited transmission capacity. Therefore, there is a problem in that it is not possible to process the increasing amount of content at high speed. In addition, the current HD transmission technology does not support uncompressed video, it is difficult to connect each device even if the video equipment is only a few meters away, and it is not possible to provide HD multimedia integrated content throughout the home and / or office.

In addition, since the existing home appliances are all present separately HD TV cable, audio cable, video cable, Internet LAN line and power supply line, the wiring is complicated and aesthetic problems are not good.

Among the cables currently used are HDMI (High Definition Multimedia Interface) cables. The HDMI cable uses uncompressed transmission, so there is no need to embed a compressed decoder or decoding software. In addition, 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.

However, in the case of 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. In addition, in the case of HDMI technology, it is difficult to effectively apply an environment in which a plurality of multimedia sources are supported together. For example, 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.

In addition, 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.

In addition, 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. A session defines a communication network path and schedules the appropriate services to be included in it.

However, currently disclosed technologies do not have a clear definition of how to manage the control information of each user when multiple users exist in the HDBaseT system. In addition, when one user occupies one session, the problem of whether the other user can use the session and the problem of whether the user can use the session without the restriction of the other user need to be solved. There is. For example, when a large number of users use the HDBaseT network, there is a need for a method in which a specific user can use the content and / or the HDBaseT device without being restricted to other users.

Accordingly, 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.

It is yet another object of the present invention to provide a method for managing sessions on an HDBaseT network.

Technical objects to be achieved in the present invention are not limited to the above-mentioned matters, and other technical problems which are not mentioned are those skilled in the art from the embodiments of the present invention to be described below. Can be considered.

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.

In one embodiment of the present invention, 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.

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. In addition, 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.

In the first embodiment, 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.

In a method for controlling session blocking in an HDBaseT network as a second embodiment of the present invention, 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. In this case, the first priority indicator field may indicate one of high, medium, and low priority of the session. In addition, the second priority indicator field may indicate one of high, medium, and low priority of the session.

In the second embodiment, 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.

In the second embodiment, 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.

As a third embodiment of the present invention, 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.

In the third embodiment, 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.

In this case, 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. In addition, the second session block indicator field may include information about a device blocked in the session.

In the third embodiment, when at least one of the view blocking field, the control blocking field, and the screen blocking field is set, the source device may block a session control message related to a session received from another initiating entity.

In another aspect of the third embodiment, 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. In response, the session initiation response message including the second priority indicator field may be transmitted to the initiation entity. In this case, the first priority indicator field may indicate one of high, medium, and low priority of the session. In addition, the second priority indicator field may indicate one of high, medium, and low priority of the session.

In this case, 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.

In the third embodiment, 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 above aspects of the present invention are only some of the preferred embodiments of the present invention, and various embodiments in which the technical features of the present invention are reflected will be described in detail below by those skilled in the art. Can be derived and understood.

According to embodiments of the present invention has the following effects.

First, communication can be efficiently performed in a home network system.

Second, by blocking the session formed on the HDBaseT network, the first occupied user may not be disturbed by other users.

Third, by defining the priority of control messages used on the HDBaseT network, it is possible to block, share or control sessions between users.

Fourth, it is possible to efficiently manage sessions and HDBaseT devices on the HDBaseT network.

Fifth, 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.

Sixth, 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.

Effects obtained in the embodiments of the present invention are not limited to the above-mentioned effects, and other effects not mentioned above are usually described in the technical field to which the present invention pertains from the description of the embodiments of the present invention. Can be clearly derived and understood by those who have That is, unintended effects of practicing the present invention may also be derived from those skilled in the art from the embodiments of the present invention.

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.

2 is a view showing the structure and function of the HDBaseT adapter used in the embodiments of the present invention.

3 is a diagram illustrating an example of an HDBaseT network (T network) in which embodiments of the present invention are used.

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.

5 is a diagram illustrating an example of a session blocking control service according to an embodiment of the present invention.

6 is a diagram illustrating an example of a method for controlling a session blocking according to an embodiment of the present invention.

7 is a diagram illustrating an example of a session block indicator structure.

8 illustrates session initiation request message structures used in embodiments of the present invention.

9 illustrates structures of a session start response message used in embodiments of the present invention.

10 is a diagram illustrating a structure of a session block update request message used in embodiments of the present invention.

11 is a diagram illustrating a structure of a session block update response message used in embodiments of the present invention.

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.

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.

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.

18 illustrates an example of a session control message structure according to an embodiment of the present invention.

19 is a diagram illustrating devices used in embodiments of the present invention.

The following embodiments combine the components and features of the present invention in a predetermined form. 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. In addition, 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.

In the description of the drawings, procedures or steps which may obscure the gist of the present invention are not described, and procedures or steps that can be understood by those skilled in the art are not described.

In the present specification, embodiments of the present invention have been described based on data transmission / reception relations between a source device, a sink device, a switch, and / or a control point.

In the embodiments of the present invention, the term Downstream (DS) 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. In addition, the term "uplink stream" (US) 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.

In addition, 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.

In addition, the term 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.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. The detailed description, which will be given below with reference to the accompanying drawings, is intended to explain exemplary embodiments of the present invention and is not intended to represent the only embodiments in which the present invention may be practiced.

In addition, specific terms used in the embodiments of the present invention are provided to help the understanding of the present invention, and the use of the specific terms may be changed into other forms without departing from the technical spirit of the present invention. .

I. HD베이스T 네트워크I. HDBaseT Network

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.

It also supports existing devices / interfaces such as HDMI, Ethernet, USB, and S / PDIF (S / PDIF is the standard for transmitting digital audio signals, the origin of which is in AES / EBU) It is an object to provide a network for supporting network services.

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.

HDBaseT networks are based on the Open System Interconnection (OSI) reference model. However, 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.

Referring to FIG. 1, 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, and the sixth layer is an application layer.

In this case, 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.

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, Physical Addressing, Power Control and Power over Ethernet (PoE) to provide configuration information Etc.

The third layer provides a logical addressing function, a routing function for optimized transmission of data, an access control function, and the like.

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.

In the fifth layer, 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 devices used in embodiments of the present invention may transmit and receive data, streams, etc. based on the hierarchical model structure of FIG. 1.

II. HD베이스T 어댑터 (T-Adaptor)II. HD Base-T Adapter (T-Adaptor)

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.

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.

Referring to FIG. 2, 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. In addition, 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. In this case, 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.

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.

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. There is a port mapping function for selecting a port.

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.

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.

In embodiments of the present invention, 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.

HDBaseT networks (hereinafter, 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. For example, 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). In this case, the Tx adapter may be used in the same manner as the source adapter, and 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 (hereinafter, 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. The T stream may optionally contain different types of packets, respectively.

III. HD베이스T 개체 식별 방법III. How to identify HDBaseT objects

In the above, various HDBaseT devices and entities used in the HDBaseT network have been described. However, when transmitting a T-stream on a T-network, it is not clear how to transmit the T-stream through multiple devices, entities and multiple ports. In addition, even if transmitted to the same device, it is not clear how to distinguish the data or service according to the data and / or service provided. Therefore, hereinafter, a method of referring to and identifying HDbaseT entities in an HDbaseT network will be described in detail.

Referring to FIG. 4, one HDBaseT device may have one or more port devices, and each port device may have one or more T-Groups. In addition, each T-group may have one or more T-adapters. Hereinafter, a four-level hierarchical reference method for identifying entities of various HDBaseT networks will be described in detail.

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.

In embodiments of the present invention, a device ID is used to identify the HDBaseT device. In this case, 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 If the PDME is used as an Ethernet termination, the Ethernet MAC address may be used as a unique identifier. However, if the PDME is not used as an Ethernet termination, 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. In addition, 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. As the link partner, 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. In embodiments of the present invention, by using 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.

Referring to FIG. 4, it can be seen that a port identifier field is used to identify a port device and a T-G identifier field is used to identify a T-group. In this case, 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). In this case, 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. In addition, a non-zero T group index of 1 to 63 bits provides a unique reference to a specific T-group in the port device.

If the T group index in the TPG identifier is zero, 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.

Referring to FIG. 4, it can be seen that 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.

Table 1

Bit index	T-adapter type	Bit index	T-adapter type
0	HDMI source	8	S / PDIF Source
One	HDMI sink	9	S / PDIF Sink
2	Reserved	10	Reserved
3	Reserved	11	Reserved
4	USB host	12	IR Tx
5	USB device / hub	13	IR Rx
6	Reserved	14	UART
7	Reserved	15	Extension Bit

Referring to Table 1,

bit indexes

0 and 1 represent HDMI source devices and sink devices, bit indexes 4 and 5 represent USB hosts and USB devices / hubs, and bit indexes 8 and 9 represent S / PDIF source and sink devices, respectively. Indicates. In addition, bit indexes 12 and 13 indicate an IR transmitter (Infra-Red Tx) and an IR receiver (Infra-Red Rx), and bit index 14 indicates a UART (Universal Asynchronous Receiver / Transmitter).

If bit index 15 (b15) is set, it 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. In addition, 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. Thus, the type mask field may uniquely identify only a particular T-adapter instance within a T-group. In addition, 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.

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.

In addition, when signals or messages are transmitted and received within a specific HDBaseT device, the signals may be added or decreased for each field. For example, 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.

In embodiments of the present invention, 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. 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.

IV. 세션 (Session)IV. Session

1. 세션 라우팅 (Session Routing)Session Routing

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. In the embodiments of the present invention, 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. HDBaseT switches (hereinafter referred to as T-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. In embodiments of the present invention, 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.

2. HD베이스T 세션 차단 제어(Session Lock Control)2. HDBaseT Session Lock Control

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. Also, 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. In addition, 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.

One HDBaseT network can be used by multiple users, and FIG. 5 shows a case where three users use one HDBaseT network. The three users are Bob, John, and Alice.

In FIG. 5, 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. Also, 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.

By blocking the provision of the HDBaseT device and / or the content as shown in FIG. 5, Bob can be stably provided with the content. Hereinafter, the session blocking control service and the management entity of the HDBaseT device providing the same will be described in detail.

In the HDBaseT system, 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. Instead of the T-Adapter, 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.

(1) View Lock: 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.

(2) Control Lock: Control lock is to block other users from controlling the HDBaseT device.

(3) 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. In addition, the 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. In this case, 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, and 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. In addition, 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.

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.

(1) Step 1: The CPME may generate, maintain, and update the device blocking information table for each CP.

(2) Step 2: CPME may receive session control message from CPs.

(3) 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.

(4) 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 below shows an example of a device blocking information table format.

TABLE 2

CP ID	Session id	Source ID	Sink ID	Block view	Control block	Screen blocker
CP #
1 ID	One	One	2	block	block	block
CP #
2 ID	2	2	3	release	release	release
CP #
3 ID	3	3	One	release	release	release

Referring to Table 2 with reference to FIG. 5, Bob has established a session (session ID: 1) between BDP (source ID: 1) and TV1 (sink ID: 2). In this case, the CPME of the TV1 and the BDP may maintain and update the device blocking information table shown in Table 2 above.

FIG. 6 shows how users Bob and Elise control HDBaseT devices in one HDBaseT network. In FIG. 6, it is assumed that 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. For example, the control point may be provided in a smartphone, a mobile terminal and / or a remote controller.

Referring to FIG. 6, 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. In this case, 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).

Referring to FIG. 7, an example of the structure of the session blocking indicator used in step S601 may be confirmed. 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. ) 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'.

Referring back to FIG. 6, it is assumed that Bob, a CP1 user, sets the view blocking field and the screen blocking field to '0' in the session blocking indicator in step S601.

Receiving the session start request message from the CP1, 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. In this case, the session blocking indicator may be included in the session route request and response message and transmitted and received (S602).

If the requested session is possible, since the view blocking field of the session blocking indicator is set to '0', 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.

If a session is established between the BDP and TV1 by the session initiation request, the BDP may provide HDMI session data, IR session data, and the like to TV1 through the formed session. At this time, 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. In other words, 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).

While a session is established between BDP and TV1 and the BDP is providing content to TV1, one of the users, Alice, wants to establish a session with BDP and TV2. Accordingly, 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).

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. To this end, Bob's CP1 may send a device block update request message including the session block indicator to the BDP. At this time, 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. In addition, 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). ).

After the view block of the BDP is released, a new session can be created between the BDP and other sink devices. In this case, Alice's CP2 may send a Session Initiation Request message to the BDP to establish a new session between BDP and TV2. In this case, 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. In this case, the session blocking indicator may be included and transmitted in the session route request and response message (S610).

If a session is established between the BDP and the TV2 in response to the session start request, the BDP may provide HDMI session data, IR session data, and the like to the TV2 through the formed session (S611).

In addition, 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).

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. In this case, the session initiation request message may be transmitted over an Ethernet (eg, an E-network) using an HD-CMP message.

8 (a) shows an example of a session initiation request message structure. Referring to FIG. 8 (a), 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). Field, Path Description Section (PDS) field, Network Path Availability (NPA) field indicating possible network paths, Session ID Query (SIQ) field, and HD-CMP payload-in operation It may include a Code Op_SNPM Body field.

In FIG. 8A, 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.

In embodiments of the present invention, 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. In addition, 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. For example, 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.

In FIG. 8A and the messages to be described below, the final target reference (FTR) field may be referred to as a final destination entity reference (FDER) field, and 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.

Referring to FIG. 8 (a), 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. (US Session Size) field, Source ID field indicating the identifier of the source device selected by the control point (CP), T-group and port of the source when the session is coupled with other sessions 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.

In addition, 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. And a sink T-Adapter Mask field indicating a T-adapter mask of the T-group of the sink device.

In this case, 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.

In addition, in the fields included in the Op Code U_SNPM body field, 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. .

That is, 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. In addition, 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.

When the session initiation request message of FIG. 8 (a) is used in FIG. 6, the final target reference field is used to identify the BDP, and the source reference field is used to identify the CP1 that sent the session initiation request message. In addition, 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. In addition, 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.

8 (b) shows another example of the session initiation request message structure. Referring to FIG. 8 (b), 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.

In this case, the sender identifier may be used to identify an initiating entity that transmits the session initiation request message, and 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.

In FIG. 8B, 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'. In addition, when the sink device supports session coupling, 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'. At this time, if the source group identifier and the sink group identifier is a value other than '0' and the source port identifier and the sink port identifier is a value other than '0', the session may be started.

In addition, 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. In addition, 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.

The session initiation response message may be sent by the session partners in response to the session initiation request message. Thus, a session initiation response message can also be sent over Ethernet using an HD-CMP message. In addition, 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.

9 (a) shows an example of a session start response message structure. In FIG. 9 (a), 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.

In FIG. 9 (a), the Final Target Reference (FTR) field is used to identify the initiator entity that sent the session initiation request message, and the Source Reference (RSR) field identifies the session partner management entity that transmitted the session initiation response message. Can be used for In this case, 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. In addition, 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.

In addition, 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.

In addition, 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.

In addition, 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.

Alternatively, 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. In addition, 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.

9 (b) is a diagram illustrating another structure of the session start response message. Referring to FIG. 9B, 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.

In this case, 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 And a source group identifier indicating the number of group ports of the source when the session is coupled with other sessions, and a sink port identifier identifying the session sink port of the link device.

In addition, 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.

In embodiments of the present invention, a session coupled means that one session works in conjunction with another session. For example, it may mean that a session for transmitting an HDMI packet operates in conjunction with a session for transmitting an USB packet, or a session for transmitting an HDMI packet operates in conjunction with a session for transmitting an IR packet.

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). However, 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.

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). However, 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.

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.

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. For example, 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.

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. For example, 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.

12 illustrates a method of controlling a formed session based on priority. 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.

In the present invention, the session control method based on priorities may use three levels of priority. For example, the first level represents a low priority, the second level represents a priority normal, and the third level represents a priority high.

In the case of a method for controlling session blocking based on priority, each CP has a priority, and the CPME may allow or disallow a session control request according to the priority of each CP. For example, the CPME may only allow session control messages with high priority or the same priority. To this end, session control messages, session initiation request message and session initiation response message may include a Priority Level field.

In embodiments of the present invention, 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.

TABLE 3

CP ID	Priority	Session id	Source ID	Sink ID	Block view	Control block	Screen blocker
CP #
1	One	One	One	2	block	block	block
CP #
2	3	2	2	3	release	release	release
CP #
3	2	3	3	One	release	release	release

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.

Referring to FIG. 12, 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. At this time, since 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.

However, if the priority of the zone or Alice is higher than or equal to Bob, 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.

In the HDBaseT network of FIG. 13, users Bob and Ellis attempt to establish a session between BDP, TV1, and TV2 based on priorities. Each user has a unique identifier along with the session control priority. At this time, each user's CPME creates and manages an active session table as shown in Table 3. In FIG. 13, 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. In this case, 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).

Upon receiving the session initiation request, 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).

If a session between the BDP and the TV1 can be established, the CPME of the BDP and the TV1 updates the active session table they are creating and managing. In addition, the BDP may provide HDMI session data and / or IR session data to TV1 through the established session. In this case, 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. In this case, 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).

In FIG. 14, the priority indicator may be used to inform the session blocking information. Referring to FIG. 14, 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.

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.

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). However, the only difference is that the Session Control Priority field is used in the operation code U_SNPM body field and not the session block field. In addition, the session control priority field may include the priority indicator described with reference to FIG. 14.

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. In addition, the session control priority field may include the priority indicator described with reference to FIG. 14.

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.

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). However, the only difference is that the Session Control Priority field is used in the operation code U_SNPM body field and not the session block field. In addition, the session control priority field may include the priority indicator described with reference to FIG. 14.

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. In addition, 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.

In embodiments of the present invention, the session block indicator of FIG. 7 and the priority indicator of FIG. 14 may be used together in one management message. For example, it may be included in the session messages disclosed in FIGS. 8 to 11 and 15 to 16. In this case, each HDBaseT device can receive block control based on session priority as well as device block.

Referring to FIG. 17, when the CP1 starts a continuous control process to control multimedia devices, 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. In addition, the media switch may accommodate the control request of other users after the continuous control of the CP1 is completed.

Referring to FIG. 17, 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).

If a session control message is received from the CP1 and a session control process is being performed, the media switch may prevent session control from another user. Referring to FIG. 17, when the CP2 intends to initiate session control with the media switch (S1703), 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).

When the session control of the CP1, the device 1, and the device 2 is completed, the media switch may transmit a session end message to the notifier that the session control is completed to the CP1 (S1706).

When the session of CP1 ends, 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).

Therefore, 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).

Referring to FIG. 18, 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.

In addition, 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.

At this time, the priority information may indicate a level of priority as a size of one octet. For example, 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. For example, 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.

In addition, 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. In addition, the session control message described in FIG. 18 may be used in FIG. 17. In this case, 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.

Various HDBaseT devices and pure Ethernet devices can be used in the HDBaseT network. 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. Also, 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).

In embodiments of the present invention, 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.

In addition, 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.

In addition, 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.

In addition, 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.

In addition, the switch may optionally further include a CPME.

In FIG. 19, the terminal is a pure Ethernet device, and may include a transmitter for transmitting Ethernet data and a receiver for receiving Ethernet data. In addition, 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. In addition, the terminal may include a Routing Processor Entity (RPE).

In Fig. 19, 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. In addition, the terminal can transmit and receive control messages on the source device / sink device and / or switch and the Ethernet network.

The invention can be embodied in other specific forms without departing from the spirit and essential features of the invention. Accordingly, the above detailed description should not be construed as limiting in all aspects and should be considered as illustrative. The scope of the invention should be determined by reasonable interpretation of the appended claims, and all changes within the equivalent scope of the invention are included in the scope of the invention. In addition, the claims may be incorporated into claims that do not have an explicit citation relationship in the claims, or may be incorporated into new claims by post-application correction.

The present invention can be applied to various home networks and home entertainment industries, and particularly to the HDBaseT system.

Claims

In the method of controlling session blocking in HDBaseT network,

Receiving a session initiation request message from the initiating entity at the source device, the session initiation request field including a first session block indicator field and requesting to establish a session between the source device and the sink device; And

Sending, by the source device, a session initiation response message including a second session block indicator field to the initiation entity in response to the session initiation request message;

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. And a screen blocking field indicating whether the input data to the device is blocked.
The method of claim 1,

And the second session block indicator field includes information about a device blocked in the session.
The method of claim 1,

Sending 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 initiated.
The method of claim 1,

And if one or more of the view blocking field, the control blocking field and the screen blocking field are set, the source device blocks a session control message associated with the session received from another initiating entity.
In the method of controlling session blocking in HDBaseT network,

Receiving a session initiation request message from the initiating entity at the source device, the session initiation request message including a first priority indicator field and requesting to establish a session between the source device and the sink device; And

Sending, by the source device, a session initiation response message including a second priority indicator field to the initiation entity in response to the session initiation request message;

And the first priority indicator field indicates one of high, medium, and low priority of the session.
The method of claim 5,

And the second priority indicator field indicates one of high, medium, and low priority of the session.
The method of claim 5,

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. Control method.
The method of claim 5,

The session initiation request message further includes a session block indicator field,

The session block indicator field may include a view block field indicating whether the output data of the source device is blocked in the formed session, a control block field indicating whether to block the remote control of the source device in the session, and a sink in the session. And a screen block field indicating whether or not to block input data to the device.
In the source device that supports the session block control method in the HDBaseT network,

The source device includes a control point management entity (CPME) for supporting the session blocking control method;

A port device management entity (PDME) for supporting the operation of the source device in the HDBaseT network;

A receiver for receiving a message; And

Including a transmitter for transmitting a message,

The receiver receiving from the initiating entity a session initiation request message including a first session block indicator field and requesting to establish a session between the source device and the sink device,

The transmitter sends a session initiation response message including a second session block indicator field to the initiation entity in response to the session initiation request message;

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. And a screen block field indicating whether or not to block input data to the device.
The method of claim 9,

The second session block indicator field includes information about a device blocked in the session.
The method of claim 9,

And if one or more of the view blocking field, the control blocking field and the screen blocking field is set, the source device blocks a session control message associated with the session received from another initiating entity.
In the source device that supports the session block control method in the HDBaseT network,

The source device includes a control point management entity (CPME) for supporting the session blocking control method;

A port device management entity (PDME) for supporting the operation of the source device in the HDBaseT network;

A receiver for receiving a message; And

Including a transmitter for transmitting a message,

The receiver receiving from the initiating entity a 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 transmitter sends a session initiation response message including a second priority indicator field to the initiation entity in response to the session initiation request message,

And the first priority indicator field indicates one of high, medium, and low priority of the session.
The method of claim 12,

And the second priority indicator field indicates one of high, medium, and low priority of the session.
The method of claim 12,

The source device disregarding the session initiation request message received at another initiation entity upon receiving a session initiation request message from another initiation entity that indicates a priority lower than the priority indicated by the first priority indicator field. .
The method of claim 12,

The session initiation request message further includes a session block indicator field,

The session block indicator field may include a view block field indicating whether to block output data of the source device in the formed session, a control block field indicating whether to block the remote control of the source device in the session, and a sink in the session. And a screen block field indicating whether or not to block input data to the device.