KR101900075B1 - System and method for managing resource in communication system - Google Patents

Abstract

The present invention relates to a resource management system and method for managing a plurality of frequency resources to be shared in a communication system including a plurality of systems that do not have usage rights for a first frequency band, A coexistence information gathering procedure, a coexistence determination gathering procedure, and a coexistence determination procedure for coexistence and frequency sharing of the plurality of systems in the usable frequency band, A coexistence decision making procedure, a reconfiguration procedure, a measurement procedure, and an event procedure, respectively.

Description

[0001] The present invention relates to a resource management system and method in a communication system,

The present invention relates to a communication system, and more particularly, to a resource management system and method for managing a plurality of frequency resources to be shared in a communication system.

BACKGROUND ART [0002] In the current communication system, active research is being conducted to provide various quality of service (QoS) services having a high transmission rate to users. In such a communication system, studies are actively conducted to provide a large-capacity service having a variety of QoS using limited resources such as frequency resources. Particularly, due to the development of radio communication technology and the emergence of new wireless communication services, there is a need to use finite frequency resources more efficiently.

In order to increase the utilization efficiency of the limited frequency resources in the communication system, it is desirable to optimize the performance of the communication system, for example, to maximize the spectrum efficiency through multiple access, coding, modulation, information compression, In addition, a frequency sharing scheme has been proposed to increase the use efficiency of frequency resources by using available frequency bands in a frequency band already in use, such as a TV band.

Here, the frequency sharing in a frequency band that can be used in a frequency band that is already in use, such as the above-described TV band, is a frequency that can be used without interfering with a primary license having incumbent usage right for the TV band It is important to detect the usable frequency band by checking whether the frequency band of the first licensee is used in the TV band. In addition, when there are a plurality of different systems to use the usable frequency band detected in the TV band, due to the difference in the communication system between the plurality of different systems, for example, the radio access system, There is a problem in coexistence to use the band.

In other words, in the present communication system, when there are a plurality of different systems to use the usable frequency band detected in the TV band as described above, the plurality of different systems can efficiently detect the usable frequency band There is no specific resource management scheme for using the frequency resources, and in particular, there is no way to efficiently use frequency resources by coexisting systems of different communication systems to use the available frequency band.

Therefore, after a usable frequency band is detected in a frequency band already in use, such as a TV band in a communication system, a plurality of different systems, for example, systems of different communication systems coexist and the detected usable frequency band is efficiently There is a need for a resource management plan for use as a resource.

It is therefore an object of the present invention to provide a resource management system and method in a communication system.

It is another object of the present invention to provide a resource management system and method for efficiently using a plurality of systems coexistence frequency bands available in a frequency band already used in a communication system.

It is another object of the present invention to provide a system and method for managing frequency resources such that a plurality of systems coexist in a communication system to use a frequency band usable in a TV band.

It is another object of the present invention to provide a system and method for managing frequency resources such that a plurality of systems in a communication system use an available frequency band through effective coexistence and frequency sharing in a usable frequency band of a TV band have.

According to an aspect of the present invention, there is provided a resource management system in a communication system including a plurality of systems that do not have usage rights for a first frequency band, A coexistence manager (CM) for managing the plurality of systems for coexistence and frequency sharing of the plurality of systems in the usable frequency band when a usable frequency band is found; A coexistence enabler (CE) for transmitting and receiving the information of the plurality of systems and information of the coexistence manager; And a Coexistence Discovery and Information Server (CDIS) supporting control of the coexistence manager for the plurality of systems; Wherein the coexistence manager includes a plurality of coexistence managers corresponding to the plurality of systems, respectively; Wherein the coexistence discovery and information server, the plurality of coexistence managers, and the coexistence enabler are configured to transmit and receive predetermined messages, respectively, to perform registration procedures, A coexistence information gathering procedure, a coexistence decision making procedure, a reconfiguration procedure, a measurement procedure, and an event procedure, respectively.

According to another aspect of the present invention, there is provided a method for managing resources of a first frequency band in a communication system including a plurality of systems having no usage right for a first frequency band, (CDIS) in a registration procedure for coexistence and frequency sharing of the plurality of systems in the usable frequency band when a frequency band in which the plurality of systems are usable in the frequency band is found, Transmitting and receiving a registration request message and a registration response message between a coexistence discovery and information server, a plurality of coexistence managers, and a coexistence enabler; In a coexistence information gathering procedure for coexistence and frequency sharing of the plurality of systems, a coexistence information request message is provided between the coexistence discovery and information server, the plurality of coexistence managers, and the coexistence enabler, Transmitting and receiving a coexistence information response message; In order to coexist and frequency-share the plurality of systems, a coexistence decision making procedure transmits and receives a command request message and a command response message, and a negotiation request message and a negotiation response message between the coexistence managers in a coexistence decision making procedure The coexistence enabler transmitting and receiving a channel classification request message and a channel classification response message; Transmitting and receiving a reconfiguration request message and a reconfiguration response message from the plurality of coexistence managers and the coexistence enabler in a reconfiguration procedure for coexistence and frequency sharing of the plurality of systems; Transmitting and receiving a management request message and a management response message by the plurality of coexistence managers and the coexistence enabler in a measurement procedure for coexistence and frequency sharing of the plurality of systems; And an event indication message and an event acknowledgment message between the coexistence discovery and information server, the plurality of coexistence managers, and the coexistence enabler in an event procedure for coexistence and frequency sharing of the plurality of systems And transmitting and receiving data.

The present invention manages frequency resources such that a plurality of systems in a communication system use an available frequency band in a frequency band already in use, such as a TV band, through coexistence and frequency sharing, The utilization efficiency of frequency resources can be improved.

BRIEF DESCRIPTION OF THE DRAWINGS Fig. 1 is a diagram schematically illustrating the structure of a resource management system in a communication system according to an embodiment of the present invention; Fig.
2 is a schematic diagram illustrating a registration procedure of a resource management system in a communication system according to an embodiment of the present invention;
3 schematically shows a deregistration procedure of a resource management system in a communication system according to an embodiment of the present invention;
Figures 4A and 4B schematically illustrate a registration procedure in each topology of a resource management system in a communication system according to an embodiment of the present invention.
5A and 5B are diagrams schematically illustrating a deregistration procedure in each topology of a resource management system in a communication system according to an embodiment of the present invention.
6 to 8 are views schematically showing a coexistence information gathering procedure of a resource management system in a communication system according to an embodiment of the present invention.
9 to 14 are diagrams schematically illustrating a coexistence decision making procedure of a resource management system in a communication system according to an embodiment of the present invention.
15 and 16 are diagrams schematically illustrating a reconfiguration procedure of a resource management system in a communication system according to an embodiment of the present invention.
17 schematically shows a measurement procedure of a resource management system in a communication system according to an embodiment of the present invention.
FIG. 18 schematically illustrates an event procedure of a resource management system in a communication system according to an embodiment of the present invention; FIG.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. In the following description, only parts necessary for understanding the operation according to the present invention will be described, and the description of other parts will be omitted so as not to disturb the gist of the present invention.

The present invention can be applied to a frequency band that is already in use, such as in a communication system, such as a cognitive radio (CR) system, an IEEE 802.19 based system, or an IEEE 802.22 based system, A resource management system and method for detecting and using a usable frequency band, e.g., an unused frequency band (WS), is proposed. Although the CR system and the IEEE 802.19 and IEEE 802.22 based systems are described as an example in the embodiment of the present invention, the resource management scheme proposed in the present invention can be applied to other communication systems.

In addition, the embodiment of the present invention proposes a resource management system and method for efficiently using a frequency band usable in a TV band by coexistence of a plurality of different systems in a communication system. Here, in the embodiment of the present invention, each object of the resource management system for sharing a frequency band usable in the communication system coexists and a plurality of different systems, in particular, different communication systems, for example, So as to share a usable frequency band in a frequency band already in use as in the TV band, thereby improving the use efficiency of the frequency resource.

That is, in the embodiment of the present invention, a resource management system for coexistence and frequency sharing among a plurality of different systems in a communication system shares a usable frequency band to improve usage efficiency of limited frequency resources. Herein, in the embodiment of the present invention, a frequency in a usable frequency band is shared in a frequency band that is already in use, such as a TV band, and a primary license having an exclusive use right for the TV band Since it is necessary to use the usable frequency band without interference, it is possible to detect a usable frequency band by checking whether the frequency band of the first licensee is used in the TV band, and to use the usable frequency band detected in the TV band A plurality of different systems selecting and using an operating channel in the detected usable frequency band through coexistence and frequency sharing. In other words, in the embodiment of the present invention, a resource management system for coexistence and frequency sharing among a plurality of different systems in a communication system selects an operation channel in WS for effective coexistence, To effectively select a channel, the available channels in the WS are classified and allocated channels.

Here, the resource management system performs a message transmission / reception procedure for efficient coexistence and frequency sharing among a plurality of systems different from each other in a band available in the TV band, i.e. TVWS. In other words, the resource management system transmits and receives messages among the objects of the resource management system for effective coexistence and frequency sharing of the plurality of systems using the TVWS, in particular, registration, coexistence information collection coexistence information gathering, coexistence decision making, reconfiguration, measurement, and event, so that the coexistence and frequency sharing efficiency of the plurality of systems in the TVWS .

That is, in the resource management system according to the embodiment of the present invention for effective coexistence and frequency sharing of a plurality of systems in the TVWS, a registration procedure and a message in the registration procedure are defined, a coexistence information gathering procedure, and a message in the coexistence information collection procedure. In the resource management system, a message in the coexistence decision making procedure and the coexistence decision making procedure is defined, a reconfiguration procedure and a message in the reconfiguration procedure are defined, and a management procedure a measurement procedure, a message in the management procedure, an event procedure, and a message in the event procedure, respectively. That is, for effective coexistence and frequency sharing in the TVWS of the plurality of systems, each defined message is transmitted and received between the respective objects of the resource management system as described above to perform each of the defined procedures, Thereby improving the coexistence and frequency sharing efficiency of the plurality of systems. Hereinafter, the resource management system in the communication system according to the embodiment of the present invention will be described in more detail with reference to FIG.

1 is a diagram schematically illustrating a structure of a resource management system in a communication system according to an embodiment of the present invention.

1, when a plurality of systems having different usable frequency bands, i.e., TVWS, are used by a plurality of systems, such as a TV band, For example, a TV band device (TVBD) 1 140 and a TVBD 2 160, which are intended to use the usable frequency band through sharing, A CM1 120 and a CM2 130 for managing the TVBDs 140 and 160 to improve the frequency sharing efficiency between the CMDs 140 and 160, A coexistence enabler (CE) is included in the TVBDs 140 and 160, or independently located, and serves as a channel between the TVBDs 140 and 160 and the CMs 120 and 130. [ ) For example, CE1 140 and CE2 170, a server supporting the control of the TVBs 140 and 160 of the CMs 120 and 130, for example, a coexistence discovery and information server (CDIS) And a TVWS DB (TVWS DB) 180 for providing channel information for the TVWS, which can be used in the TV band, do. Here, the resource management system includes CE, CM, CDIS, and TVWS DB as objects for coexistence and frequency sharing in TVWS of a plurality of systems, i.e., TVBDs.

As described above, the TVBDs 140 and 160 may be configured so that a primary licensee (hereinafter, referred to as a 'Primary System') having a preferential usage right for the TV band already has a predetermined When a frequency band is not used, another user (hereinafter, referred to as a 'secondary system') not having a preferential right to use the TV band is allowed to use a frequency band capable of using a predetermined frequency band in the TV band Quot; refers to a plurality of different systems, that is, sub-systems devices, which are to be detected and used in a band. Here, the TVBDs 140 and 160 share the predetermined frequency band through coexistence and frequency sharing in order to more efficiently use the limited frequency resources. That is, the TVBDs 140 and 160 receive channels through the TVWS and transmit and receive data.

As described above, the CEs 150 and 160 are independently located in the TVBDs 140 and 160, and transmit and receive information of the TVBDs 140 and 160 and information of the CMs 120 and 130, respectively. Although the CEs 150 and 160 are independently provided in the TVBDs 140 and 160 for convenience of description, the CEs 150 and 160 may include the TVBDs 140 and 160 Or may be included in the CMs 120 and 130. [

The CEs 150 and 160 may transmit context information related to the corresponding TVBDs 140 and 160 requested by the CMs 120 and 130 such as the radio access scheme, A threshold, and a position, from the TVBDs 140 and 160, and transmits the extracted information to the CMs 120 and 130. That is, the CEs 150 and 160 acquire communication-related information of each system as context information for different subsystems, and transmit the information to the CMs 120 and 130.

The CEs 150 and 160 receive a request of the CMs 120 and 130 for managing the TVBDs 140 and 160, for example, the context information and the configuration of the TVBDs 140 and 160 Updates the context information of the TVBDs 140 and 160 according to the request, and reconfigures or reconfigures the configuration of the TVBDs 140 and 160. In other words, the CEs 150 and 160 receive the changed information of the context information, that is, the event information of the TVBDs 140 and 160 in response to the context information of the TVBDs 140 and 160, And updates the context information of the TVBDs 140 and 160. The CEs 150 and 160 may also receive a component reset of the TVBDs 140 and 160 in response to a request for a configuration of the TVBDs 140 and 160 and may configure the components of the TVBDs 140 and 160 The element is reset, i.e., reconstructed.

The CMs 120 and 130 determine an operation frequency allocation, a transmission power allocation, and a transmission time allocation in order to improve frequency sharing efficiency between the TVBDs 140 and 160. In other words, the CMs 120 and 130 may be connected to the TVBs 140 and 160 in the available frequency band to improve the frequency sharing efficiency between the TVBDs 140 and 160 for the available frequency bands in the TV band described above. Performs operation frequency allocation, transmission power allocation, and transmission time allocation.

In order to further improve the frequency sharing efficiency between the TVBDs 140 and 160, the CMs 120 and 130 transmit and receive information to and from CMs of TVBDs that do not correspond to themselves, for example, neighboring CMs Transmits context information and event information of TVBDs, and performs operation frequency allocation, transmission power allocation, and transmission time allocation of the corresponding TVBD in the usable frequency band. At this time, the CMs 120 and 130 directly transmit and receive context information and event information of TVBDs that do not correspond to the CMs 120 and 130 with other CMs (for example, adjacent CMs) And acquires them. In addition, the CMs 120 and 130 may acquire information on spectrum use in the main system, that is, channel information about available channels in the TV band, through an external database, for example, the TVWS DB 180, To reset the components of their corresponding TVBDs.

The CDIS 110 supports control operations of the CMs 120 and 130 for frequency sharing of the TVBDs 140 and 160 with respect to frequency bands available in the TV band, as described above. That is, the CDIS 110 receives and stores the context information and the event information of the TVBDs 140 and 160 from the CMs 120 and 130. The CDIS 110 receives the context information and the event information of the TVBDs 140 and 160 from the CMs 120 and 130, To the CMs (120 and 130). In addition, the CDIS 110 acquires and stores information on spectrum use in the main system, that is, channel information on available channels in the TV band, through an external database, for example, the TVWS DB 180.

The TVWS DB 180 provides channel information on a channel available in the TVWS, that is, shared channel information, to the CMs 120 and 130. The channel information is registered in the TVWS DB 180, TVBD < / RTI >

The resource management system in the communication system according to this embodiment of the present invention uses a frequency band that can be used in a frequency band already used in a main system such as a TV band by sharing the sub-systems, that is, coexistence of the TVBDs 140 and 160 The CDIS 110, the CMs 120 and 130, and the CEs 140 and 160 for frequency sharing and frequency sharing. As described above, the TVBDs 140 and 160 are sub-systems devices for sharing and using the available frequency band. The TVBDs 140 and 160 include a base station (BS), an access point An access point (AP), a service access point (SAP), a terminal, and the like. In addition, the sub systems may be a plurality of systems different from each other in sharing available frequency bands as described above, and may be systems of different communication systems, such as an IEEE 802.19-based system and an IEEE 802.22-based system .

In addition, in the communication system according to the embodiment of the present invention, for the coexistence and frequency sharing of the TVBDs 140 and 160 with respect to the usable frequency band in the frequency band already in use, A coexistence information gathering procedure, a coexistence decision making procedure, a reconfiguration procedure, a management procedure, and an event (e.g., an event) in order to efficiently coexist and frequency-share a plurality of systems, e.g., the TVBDs 140 and 160, Perform the procedure. That is, the above-described procedures are performed through transmission and reception of a predetermined message between the respective objects of the resource management system, whereby a plurality of systems in the TVWS effectively improve frequency use efficiency through coexistence and frequency sharing.

At this time, the resource management system is operated in a management mode and an autonomous mode (or an information mode), and the setting and the configuration of the frequency sharing device indicated by the CM in the management mode, i.e., TVBD, And the CE is made to make coexistence and frequency sharing decisions on the basis of the coexistence and frequency sharing related information provided by the CM in the autonomous mode and the coexistence and frequency sharing decision is reset to the setting and configuration of the TVBD To the TBVD. In addition, the resource management system is operated in a centralized topology and a distributed topology, and in the centralized topology, a plurality of CMs are provided with a plurality of A slave CM is connected, and the slave CMs are under the control of the master CM for coexistence and frequency sharing among the TVBDs. In the distributed topology, a plurality of CMs perform coexistence and frequency sharing among TVBDs through negotiation between any one CM and adjacent CMs of the one CM. Hereinafter, a registration procedure of a resource management system in a communication system according to an embodiment of the present invention will be described with reference to FIGS. 2, 4A, and 4B. Referring to FIGS. 3, 5A and 5B, A deregistration procedure of the resource management system corresponding to the registration procedure will be described.

2 is a diagram schematically illustrating a registration procedure of a resource management system in a communication system according to an embodiment of the present invention. 2 is a diagram schematically illustrating a message transmission / reception procedure between respective objects of the resource management system in the registration procedure.

2, for the coexistence and frequency sharing in the TVWS, the TVBD 202 must register with the CM 206 and the TVBD 202 transmits a TVBD registration request (TVBD_REG_REQ: TVBD (Hereinafter referred to as " TVBD_REG_REQ ") message to the CE 204 (step 210). In step 212, the TVBD 202 receives a TVBD registration response (TVBD_REG_RSP) message from the CE 204 in response to the TVBD_REG_REQ message.

The CE 204 receives the TVBD_REG_REQ message from the TVBD 202 and confirms a registration request for coexistence and frequency sharing in the TVWS 202 of the TVBD 202, (CE_REG_REQ: CE_REG_REQ) message to the CM 206 for registration with the CM 206 (step 214). Here, the CE_REG_REQ message is a message requesting registration of the TVBD 202 to the CM 206 for coexistence and frequency sharing in the TVWS of the TVBD 202, as described above. Also, the CE_REG_REQ message is used in a centralized topology, a distributed topology, and an autonomous mode of the resource management system. Contents of the CE_REG_REQ message, that is, the header and the payload of the CE_REG_REQ message can be shown in Table 1.

Header Name Data Type Description SourceID CE ID Source identifier DestinationID CM ID Destination identifier Payload Name Data Type Description ServiceType BOOLEAN Service type, including
- Discovery service
- Management service

Also, in response to the CE_REG_REQ message, the CE 204 transmits a CE registration response (CE_REG_RSP: CE_REG_RSP) for notifying the registration result to the CM 206 of the TVBD 202 ) Message from the CM 206 (step 216). Here, the CE_REG_RSP message includes a response of the CE_REG_REQ message requesting registration of the TVBD 202 to the CM 206 for coexistence and frequency sharing in the TVWS of the TVBD 202, as described above A message that the CM 206 notifies the CE 204 of the registration result of the TVBD, i.e., the TVBD 202, as a message. The CE_REG_RSP message is used in a centralized topology, a distributed topology, and an autonomous mode of the resource management system. In addition, the contents of the CE_REG_RSP message, i.e., the header and the payload of the CE_REG_RSP message, can be represented as shown in Table 2 below.

Header Name Data Type Description SourceID CM ID Source identifier DestinationID CE ID Destination identifier Payload Name Data Type Description ServiceTypeStatus BOOLEAN Status of service type
- True: Subscription of the corresponding service type is succeeded.
- False: Subscription of the corresponding service type is failed.

In addition, the CM 206 transmits a CM Registration Request (CM_REG_REQ) message requesting registration of itself to the CMs adjacent to the CM 206, 208 (step 218). Here, the CM_REG_REQ message is a message for requesting registration of the CM 206 to the adjacent CM for coexistence and frequency sharing in the TVWS of the TVBD 202, in particular, in the distributed topology, 206 to the adjacent CM. The CM_REG_REQ message is used in the centralized topology, distributed topology, and autonomous mode of the resource management system. In addition, the contents of the CM_REG_REQ message, i.e., the header and the payload of the CM_REG_REQ message, can be represented as shown in Table 3 below.

Header Name Data Type Description SourceID CM ID Source identifier DestinationID CDIS ID / Neighbor CM ID Destination identifier Payload Name Data Type Description None

In response to the CM_REG_REQ message, the CM 206 transmits a CM Registration Response (CM_REG_RSP) message (hereinafter referred to as a CM_REG_RSP message) for notifying the neighboring CM of the CM 206 of the registration result From the CDIS 208 (step 220). Here, the CM_REG_RSP message is a response message of the CM_REG_REQ message requesting registration of the CM 206 to a neighboring CM for coexistence and frequency sharing in the TVWS of the TVBD 202 as described above, Is a message that the CDIS 208 sends to the CM 206 to notify the CM 206 of the registration result of the corresponding CM, that is, the CM 206 in the distributed topology. In addition, the CM_REG_RSP message is used in a centralized topology, a distributed topology, and an autonomous mode of the resource management system. In addition, the contents of the CM_REG_RSP message, i.e., the header and the payload of the CM_REG_RSP message,

Header Name Data Type Description SourceID CDIS ID / Neighbor CM ID Source identifier DestinationID CM ID Destination identifier Payload Name Data Type Description RegistrationStatus BOOLEAN Status of registration
- True: Registration of the corresponding CM is succeeded.
- False: Registration of the corresponding CM is failed.

The resource management system performs the registration procedure for the coexistence and frequency sharing of a plurality of systems, for example, TVBDs, by sending and receiving the messages as described above. Hereinafter, referring to FIG. 3, The registration release procedure of the resource management system in the communication system according to the example will be described in more detail.

3 is a diagram schematically illustrating a deregistration procedure of a resource management system in a communication system according to an embodiment of the present invention. 3 is a diagram schematically illustrating a message transmission / reception procedure between respective objects of the resource management system in the deregistration procedure.

3, in order to terminate the coexistence and frequency sharing in the TVWS, the TVBD 302 must unregister in the CM 306, and the TVBD 302, in order to unregister in the CM 306, And transmits a request (TVBD_DREG_REQ: TVBD_DREG_REQ) message to the CE 304 (step 310). The TVBD 302 receives a TVBD_DREG_RSP (TVBD_DREG_RSP) message from the CE 304 in response to the TVBD_DREG_REQ message (step 312) .

The CE 304 receives the TVBD_DREG_REQ message from the TVBD 302 and confirms a deregistration request for coexistence and frequency sharing termination in the TVWD 302 of the TVBD 302, To the CM 306, a CE release request (CE_DREG_REQ: CE_DREG_REQ) message to cancel the registration in the CM 306 (step 314). Here, the CE_DREG_REQ message is a message requesting the TVBD 302 to unregister in the CM 306 for coexistence and frequency sharing termination in the TVWS of the TVBD 302, as described above. Also, the CE_DREG_REQ message is used equally in a centralized topology, a distributed topology, and an autonomous mode of the resource management system. In addition, the contents of the CE_DREG_REQ message, that is, the header and the payload of the CE_DREG_REQ message, can be expressed as shown in Table 5 below.

Header Name Data Type Description SourceID CE ID Source identifier DestinationID CM ID Destination identifier Payload Name Data Type Description None

In addition, the CE 304 transmits a CE registration cancel response (CE_DREG_RSP: CE_DREG_RSP) to the TV 306 in response to the CE_DREG_REQ message, notifying the result of the registration cancel in the CM 306 of the TVBD 302 Message from the CM 306 (step 316). Here, the CE_DREG_RSP message includes the CE_DREG_REQ message requesting deregistration in the CM 306 of the TVBD 302 for coexistence and frequency sharing termination in the TVWS of the TVBD 302, The CM 306 informs the CE 304 of the result of the registration of the TVBD, i.e., the TVBD 302. [ The CE_DREG_RSP message is used in the centralized topology, distributed topology, and autonomous mode of the resource management system. In addition, the contents of the CE_DREG_RSP message, i.e., the header and the payload of the CE_DREG_RSP message, can be represented as shown in Table 6 below.

Header Name Data Type Description SourceID CM ID Source identifier DestinationID CE ID Destination identifier Payload Name Data Type Description DeregistrationStatus BOOLEAN Status of de-registration
- True: De-registration of the corresponding TVBD is succeeded.
- False: De-registration of the corresponding TVBD is failed.

Then, the CM 306 transmits a CM Deregistration Request (CM_DREG_REQ) requesting its own registration cancellation in order to cancel its registration in the CMs adjacent to the CM 306, Message to the CDIS 308 (step 318). Here, the CM_DREG_REQ message is a message for requesting the CM 306 to unregister in the adjacent CM for the coexistence and frequency sharing termination in the TVWS of the TVBD 302, as described above, in particular in a distributed topology Requesting the CM 306 to cancel the registration in the adjacent CM. Also, the CM_DREG_REQ message is used in a centralized topology, a distributed topology, and an autonomous mode of the resource management system. In addition, the contents of the CM_DREG_REQ message, that is, the header and the payload of the CM_DREG_REQ message, can be represented as shown in Table 7.

Header Name Data Type Description SourceID CM ID Source identifier DestinationID CDIS ID / Neighbor CM ID Destination identifier Payload Name Data Type Description None

In response to the CM_DREG_REQ message, the CM 306 transmits a CM registration cancel response (CM_DREG_RSP: CM_DREG_RSP, hereinafter referred to as "CM_DREG_RSP") indicating a result of deregistration in the adjacent CM of the CM 306 Message from the CDIS 308 (step 320). Herein, the CM_DREG_RSP message includes a response of the CM_DREG_REQ message requesting deregistration in the neighbor CM of the CM 306 to terminate coexistence and frequency sharing in the TVWS of the TVBD 302 as described above (308) to the CM 306 so that the neighboring CM informs the CM 306 of the result of the deregistration of the CM, that is, the CM 306, in a distributed topology, Message. In addition, the CM_DREG_RSP message is used in a centralized topology, a distributed topology, and an autonomous mode of the resource management system. The content of the CM_DREG_RSP message, i.e., the header and the payload of the CM_DREG_RSP message, can be represented as shown in Table 8 below.

Header Name Data Type Description SourceID CDIS ID / Neighbor CM ID Source identifier DestinationID CM ID Destination identifier Payload Name Data Type Description DeregistrationStatus BOOLEAN Status of de-registration
- True: De-registration of the corresponding CM is succeeded.
- False: De-registration of the corresponding CM is failed.

In this way, the resource management system performs the deregistration procedure for the coexistence of the plurality of systems, e.g., TVBDs and the frequency sharing end, by sending and receiving the messages as described above for each of the objects, and hereafter referring to Figs. 4A and 4B The registration procedure in each topology of the resource management system in the communication system according to the embodiment of the present invention will be described in more detail.

4A and 4B are diagrams schematically illustrating a registration procedure in each topology of a resource management system in a communication system according to an embodiment of the present invention. 4A is a diagram schematically illustrating a registration procedure of the resource management system in the centralized topology. In FIG. 4A, a procedure of sending and receiving messages in the registration procedure between each object of the resource management system, particularly, a master CM and a slave CM, Fig. 4B schematically shows a registration procedure of the resource management system in the distributed topology. In FIG. 4B, the procedure of transmitting and receiving messages in the registration process between the respective objects of the resource management system, Fig.

Referring to FIG. 4A, in the centralized topology, a slave CM (SCM) 402 (hereinafter referred to as "SCM") in a plurality of CMs managing a plurality of systems of the resource management system ) Registers an SCM registration request (SCM_REG_REQ: SCM_REG_REQ: SCM_REG_REQ: SCM_REG_REQ: SCM_REG_REQ: SCM_REG_REQ: SCM Registration Request (hereinafter, referred to as 'SCM_REG_REQ') message to the MCM 404 in operation 410. Here, the SCM_REG_REQ message is a message for requesting registration of the SCM 402 to the MCM 404 for coexistence and frequency sharing in the TVWS of the TVBD, as described above, and in particular for the SCM 402 in the centralized topology. To the MCM 404 of the mobile communication terminal. Also, the SCM_REG_REQ message is used in a centralized topology of the resource management system. In addition, the contents of the SCM_REG_REQ message, that is, the header and the payload of the SCM_REG_REQ message, can be represented as shown in Table 9.

Header Name Data Type Description SourceID Slave CM ID Source identifier DestinationID Master CM ID Destination identifier Payload Name Data Type Description RegisteredCEIDList SEQUENCE OF STRING Registered CE ID list including inter-CM neighbor TVBD

In response to the SCM_REG_REQ message, the SCM 402 transmits an SCM registration response (SCM_REG_RSP: SCM_REG_RSP) to the MCM 404 of the SCM 402, Message from the MCM 404 (step 412). Here, the SCM_REG_RSP message is a response message of the SCM_REG_REQ message requesting registration of the SCM 402 with the MCM 404 for coexistence and frequency sharing in the TVWS of the TVBD, as described above, In particular, the MCM 404 notifies the SCM 402 of the registration result of the corresponding SCM, that is, the SCM 402 in a centralized topology. Also, the SCM_REG_RSP message is used in a centralized topology of the resource management system. In addition, the contents of the SCM_REG_RSP message, i.e., the header and the payload of the SCM_REG_RSP message, can be represented as shown in Table 10 below.

Header Name Data Type Description SourceID Master CM ID Source identifier DestinationID Slave CM ID Destination identifier Payload Name Data Type Description RegisteredCEIDList SEQUENCE OF STRING Registered CE ID list including inter-CM neighbor TVBD The message contents below are repeated for each registered CE RegisteredCEID STRING Registered CE ID RegistrationStatus BOOLEAN Status of registration
- True: Registration of the corresponding CE is succeeded.
- False: Registration of the corresponding CE is failed.

4B, in the distributed topology, any one CM 452 in a plurality of CMs managing a plurality of systems of the resource management system may be configured so that, in the plurality of CMs, To the NCM 454, a CM_REG_REQ message requesting its registration to register in a neighbor CM (NCM) 454 (step 460). Here, the CM_REG_REQ message is a message requesting registration of the CM 452 with the NCM 454, particularly for the CM 452 in a distributed topology, for coexistence and frequency sharing in the TVWS of the TVBD, To the NCM 454, and is used in the distributed topology of the resource management system. The contents of the CM_REG_REQ message, that is, the header and the payload of the CM_REG_REQ message are as shown in Table 3.

The CM 452 receives a CM_REG_RSP message from the NCM 454 in response to the CM_REG_REQ message to the NCM 454 of the CM 452 in step 462. The CM_REG_RSP message includes a response message of the CM_REG_REQ message requesting registration of the CM 452 to the NCM 454 for coexistence and frequency sharing in the TVWS of the TVBD 202, Wherein the NCM 454 in a distributed topology notifies the CM 206 of a registration result of a corresponding CM, i.e., the CM 452, the CM_REG_RSP message being a distributed Used in topology. The contents of the CM_REG_RSP message, that is, the header and the payload of the CM_REG_RSP message are as shown in Table 4.

The resource management system thus performs the registration procedure for the coexistence and frequency sharing of a plurality of systems, e.g., TVBDs, by sending and receiving the messages as described above to each of the objects, particularly the SCM and MCM, and any CM and NCM Hereinafter, with reference to FIG. 5A and FIG. 5B, a procedure for unregistering a resource management system in a communication system according to an embodiment of the present invention will be described in more detail.

5A and 5B are diagrams schematically illustrating a deregistration procedure in each topology of a resource management system in a communication system according to an embodiment of the present invention. 5A is a diagram schematically illustrating a deregistration procedure of a resource management system in the centralized topology. In FIG. 5A, a procedure of sending and receiving messages in each of the objects of the resource management system, specifically, the MCM- Fig. FIG. 5B is a diagram schematically illustrating a deregistration procedure of the resource management system in the distributed topology, in which the procedures for sending and receiving messages in the deregistration procedures between the respective objects of the resource management system, in particular, the CM and the NCM, Fig.

5A, in the centralized topology, the SCM 502, at a plurality of CMs managing a plurality of systems of the resource management system, releases its registration at its MCM 504 (SCM_DREG_REQ) message to the MCM 504 in step 510. The SCM_DREG_REQ message is a response to the SCM_DREG_REQ message. Herein, the SCM_DREG_REQ message is a message for requesting deregistration in the MCM 504 of the SCM 502, particularly in a centralized topology, for the coexistence and frequency sharing end in the TVWS of the TVBD, And requests release of the registration in the MCM 504 of the mobile station 502. Also, the SCM_DREG_REQ message is used in a centralized topology of the resource management system. In addition, the contents of the SCM_DREG_REQ message, i.e., the header and the payload of the SCM_DREG_REQ message, can be represented as shown in Table 11.

Header Name Data Type Description SourceID Slave CM ID Source identifier DestinationID Master CM ID Destination identifier Payload Name Data Type Description RegisteredCEIDList SEQUENCE OF STRING Registered CE ID list The message contents below are repeated for each registered CE Registered CE ID SEQUENCE OF STRING Registered CE ID list None

In response to the SCM_DREG_REQ message, the SCM 502 transmits an SCM_DREG_RSP (SCM_DREG_RSP: SCM_DREG_RSP) to the MCM 504 of the SCM 502 Message from the MCM 504 (step 512). Herein, the SCM_DREG_RSP message includes a response message of the SCM_DREG_REQ message requesting deregistration in the MCM 504 of the SCM 502 to terminate coexistence and frequency sharing in the TVWS of the TVBD, as described above The MCM 504 notifies the SCM 502 of the release of the corresponding CM, that is, the SCM 502 in the distributed topology. Also, the SCM_DREG_RSP message is used in a centralized topology of the resource management system. In addition, the contents of the SCM_DREG_RSP message, i.e., the header and the payload of the SCM_DREG_RSP message, can be represented as shown in Table 12 below.

Header Name Data Type Description SourceID Master CM ID Source identifier DestinationID Slave CM ID Destination identifier Payload Name Data Type Description RegisteredCEIDList SEQUENCE OF STRING Registered CE ID list The message contents below are repeated for each registered CE RegisteredCEID STRING Registered CE ID DeregistrationStatus BOOLEAN Status of de-registration
- True: De-registration of the corresponding TVBD is succeeded.
- False: De-registration of the corresponding TVBD is failed.

5B, in the distributed topology, any one CM 552 in a plurality of CMs managing a plurality of systems of the resource management system may be configured so that, in the plurality of CMs, In step 510, the NCM 554 transmits a CM_DREG_REQ message to the NCM 554 to cancel its registration in order to cancel its registration. Here, the CM_DREG_REQ message is a message for requesting deregistration in the NCM 554 of the CM 552, particularly in the distributed topology, for the coexistence and frequency sharing termination in the TVWS of the TVBD, as described above. 552 in NCM 554 and is used in the distributed topology of the resource management system. Table 7 shows the contents of the CM_DREG_REQ message, that is, the header and the payload of the CM_DREG_REQ message.

The CM 552 receives a CM_DREG_RSP message from the NCM 554 in response to the CM_DREG_REQ message to inform the result of the deregistration in the NCM 554 of the CM 552 from the NCM 554 in operation 512. Here, the CM_DREG_RSP message includes a response message of the CM_DREG_REQ message requesting to cancel registration in the NCM 554 of the CM 552 to terminate coexistence and frequency sharing in the TVWS of the TVBD, as described above Is a message that the NCM (554) informs the CM (552) of the CM, that is, the result of deregistration of the CM (552) in a distributed topology, and the CM_DREG_RSP message is a message Used in a topology. At this time, the contents of the CM_DREG_RSP message, i.e., the header and the payload of the CM_DREG_RSP message are as shown in Table 8.

The resource management system thus allows each of the objects, particularly the SCM and the MCM, and any CM and NCM to send and receive messages as described above, to perform a deregistration procedure for coexistence and frequency sharing termination of a plurality of systems, Hereinafter, the coexistence information gathering procedure of the resource management system in the communication system according to the embodiment of the present invention will be described in more detail with reference to FIG. 6 to FIG.

6 to 8 are views schematically showing a coexistence information gathering procedure of a resource management system in a communication system according to an embodiment of the present invention. FIG. 6 is a diagram illustrating a coexistence information collection procedure in the CE of the resource management system, FIG. 7 is a diagram illustrating a coexistence information collection procedure in the CM of the resource management system, FIG. FIG. 4 is a view showing a coexistence information collection procedure in the CDIS of the management system. FIG. 6 to 8 illustrate a case where, after the registration procedure in the resource management system for coexistence and frequency sharing in a TVWS of a plurality of systems, for example, TVBDs, as described above, FIG. 2 is a diagram schematically showing a message transmission / reception procedure between objects of FIG.

6, in order to collect coexistence information after a registration procedure for coexistence and frequency sharing in a TVWS of a plurality of systems, e.g., TVBDs, the CE 604 transmits coexistence information of the TVBD 602, A TVBD coexistence information request (TVBD_CI_REQ: hereinafter referred to as TVBD_CI_REQ) message requesting context information of the TVBD 602 to the TVBD 602 in step 610. In response to the TVBD_CI_REQ message, the CE 604 transmits a TVBD coexistence information response (TVBD_CI_RSP: TVBD Coexistence Information Response) including the coexistence information of the TVBD 602, for example, the context information of the TVBD 602, (Hereinafter, referred to as 'TVBD_CI_RSP') message from the TVBD 602 (step 612).

Then, the CE 604 transmits a CM coexistence information request (CM_CI_REQ) message requesting the coexistence information of the CM corresponding thereto, that is, the CM 606 To the CM 606 (step 614). Here, the CM_CI_REQ message is a message requesting the coexistence information of the CM 606 to collect coexistence information for coexistence and frequency sharing in the TVWS of the TVBD 602, as described above. Also, the CM_CI_REQ message is used in the centralized topology, distributed topology, and autonomous mode of the resource management system. In addition, the contents of the CM_CI_REQ message, i.e., the header and the payload of the CM_CI_REQ message, can be represented as shown in Table 13 below. Here, the CM_CI_REQ message may be transmitted to the CM 606 so that the CDIS requests the coexistence information of the CM 606.

Header Name Data Type Description SourceID CDIS ID / CE ID Source identifier DestinationID CM ID Destination identifier Payload Name Data Type Description RegisteredCMInformationIDs COEX_CM_INFO_IDS Registered CM information IDs
- Registered CE ID list
- Registered CE information
- TVBD type
- Network type
- Antenna maximum gain
- Antenna height
- Geolocation
- Service duty cycle
- Service bandwidth
- Service coverage
- Interference range
- Operating channel list
- Channelization list
- TVWS DB channel list
- Reconfigurable TVWS channel list

In addition, the CE 604 transmits a CM Coexistence Information Response (CM_CI_RSP) message including the coexistence information of the CM 606 in response to the CM_CI_REQ message From the CM 606 (step 616). Here, the CM_CI_RSP message includes a response message of the CM_CI_REQ message requesting the coexistence information of the CM 606 for coexistence and frequency sharing in the TVWS of the TVBD 602, , And the CM 606 provides the coexistence information of the CM 606 to the CE 604. [ The CM_CI_RSP message is used in the centralized topology, the distributed topology, and the autonomous mode of the resource management system. In addition, the contents of the CM_CI_RSP message, i.e., the header and the payload of the CM_CI_RSP message, can be represented as shown in Table 14. Here, the CM_CI_RSP message may be transmitted to the CDIS in response to a request for coexistence information of the CM 606 in the CDIS as described above.

Header Name Data Type Description SourceID CM ID Source identifier DestinationID CDIS ID / CE ID Destination identifier Payload Name Data Type Description RegisteredCEIDList SEQUENCE OF STRING Registered CE ID list The message contents below are repeated for each registered CE RegisteredCEID STRING Registered CE ID RegisteredCETVBDType COEX_TVBD_TYPE TVBD type, categorized by
- Fixed device type
- Personal / portable mode I type
- Personal / portable mode II type RegisteredCENetworkType COEX_TVBD_NET_TYPE TVBD network type such as IEEE 802.11af, IEEE 802.22 and IEEE 802.16, etc. RegisteredCEAntennaMaxGain REAL TVBD antenna maximum gain RegisteredCEAntennaHeight REAL TVBD antenna height RegisteredCEGeolocation COEX_TVBD_GEOLOCATION TVBD geolocation, including
- Latitude
- Longitude
- Altitude RegisteredCEDutycycle REAL TVBD service duty cycle RegisteredCEBandwidth REAL TVBD service bandwidth RegisteredCECoverage REAL TVBD service coverage RegisteredCEInterferenceRange REAL TVBD interference range RegisteredCEOperatingChList SEQUENCE OF INTEGER TVBD operating channel list RegisteredCEChannelizationList SEQUENCE OF REAL TVBD channelization list RegisteredCETVWSDBChList COEX_TVBD_TVWS TVBD TVWS DB channel list, including
- Allowed TVWS channel list
- Channel use constraint

In this manner, the resource management system performs the coexistence information collection procedure at the CE after each object transmits and receives the messages as described above, and after the registration procedure for coexistence and frequency sharing of a plurality of systems, e.g., TVBDs, The coexistence information collection procedure in the CM of the resource management system in the communication system according to the embodiment of the present invention will be described in more detail with reference to FIG.

7, after a registration procedure for coexistence and frequency sharing in a TVWS of a plurality of systems, e.g., TVBDs, to collect coexistence information, CM 704 includes CDIS coexistence requesting coexistence information of adjacent CMs The CDIS 702 transmits a CDIS Co-Initiation Information Request (CDIS_CI_REQ) message to the CDIS 706 in step 710. Here, the CDIS_CI_REQ message may be transmitted to the CDIS 706 in order to allow the CM 704 to discover NCMs for coexistence and frequency sharing in the TVWS of the TVBD, as described above. Is a message requesting coexistence information of NCM. Also, the CDIS_CI_REQ message is used in a centralized topology, a distributed topology, and an autonomous mode of the resource management system. In addition, the contents of the CDIS_CI_REQ message, i.e., the header and the payload of the CDIS_CI_REQ message, can be expressed as shown in Table 15. [

Header Name Data Type Description SourceID  CM ID Source identifier DestinationID CDIS ID Destination identifier Payload Name Data Type Description NeighborCMIDlist SEQUENCE OF STRING Neighbor CM ID list NeighborCMInformationIDs COEX_CM_INFO_IDS Neighbor CM information IDs
- Neighbor CEs information

The CM 704 transmits a CDIS Coexistence Information Response (CDIS_CI_RSP) message including the coexistence information of the NCM to the CDIS_CI_RSP message in response to the CDIS_CI_REQ message, (Step 712). Here, the CDIS_CI_RSP message is a response message of the CDIS_CI_REQ message requesting the coexistence information of the NCM for collecting coexistence information for coexistence and frequency sharing in the TVWS of the TVBD, as described above, ) Provides the coexistence information of NCMs corresponding to the CM 704 to the CM 704. The CDIS_CI_RSP message is used in the centralized topology, the distributed topology, and the autonomous mode of the resource management system. In addition, the contents of the CDIS_CI_RSP message, that is, the header and the payload of the CDIS_CI_RSP message, can be represented as shown in Table 16 below.

Header Name Data Type Description SourceID CDIS ID Source identifier DestinationID CM ID Destination identifier Payload Name Data Type Description NeighborCMIDList SEQUENCE OF STRING Neighbor CM ID list The message contents below are repeated for each neighbor CM NeighborCMID STRING Neighbor CM ID NeighborCEIDList SEQUENCE OF STRING Neighbor CE ID list The message contents below are repeated for each neighbor CE NeighborCEID STRING Neighbor CE ID NeighborCETVBDType COEX_TVBD_TYPE TVBD type, categorized by
- Fixed device type
- Personal / portable mode I type
- Personal / portable mode II type NeighborCENetworkType COEX_TVBD_NET_TYPE TVBD network type such as IEEE 802.11af, IEEE 802.22 and IEEE 802.16, etc. NeighborCEAntennaMaxGain REAL TVBD antenna maximum gain NeighborCEAntennaHeight REAL TVBD antenna height NeighborCEGeolocation COEX_TVBD_GEOLOCATION TVBD geolocation, including
- Latitude
- Longitude
- Altitude NeighborCEDutycycle REAL TVBD service duty cycle NeighborCEBandwidth REAL TVBD service bandwidth NeighborCECoverage REAL TVBD service coverage NeighborCEInterferenceRange REAL TVBD interference range NeighborCEOperatingChList SEQUENCE OF INTEGER TVBD operating channel list NeighborCEChannelizationList SEQUENCE OF REAL TVBD channelization list NeighborCETVWSDBChList COEX_TVBD_TVWS TVBD TVWS DB channel list, including
- Allowed TVWS channel list
- Channel use constraint

The CM 704 transmits a CE Coexistence Information Request (CE_CI_REQ) message requesting coexistence information of the TVBD corresponding to the CE 702, for example, context information To the CE 702 (Step 714). Here, the CE_CI_REQ message is a message for requesting coexistence information of the TVBD in order to collect coexistence information for coexistence and frequency sharing in the TVWS of the TVBD, as described above. Also, the CE_CI_REQ message is used in the centralized topology, the distributed topology, and the autonomous mode of the resource management system. In addition, the contents of the CE_CI_REQ message, i.e., the header and the payload of the CE_CI_REQ message, can be represented as shown in Table 17.

Header Name Data Type Description SourceID CM ID Source identifier DestinationID CE ID Destination identifier Payload Name Data Type Description TVBDInformationIDs COEX_TVBD_INFO_IDS TVBD information IDs
- TVBD type
- TVBD network type
- TVBD antenna maximum gain
- TVBD antenna height
- TVBD geolocation
- TVBD service duty cycle
- TVBD service bandwidth
- TVBD service coverage
- TVBD interference range
- TVBD operating channel list
- TVBD channelization list
- TVBD TVWS DB channel list
- TVBD reconfigurable TVWS channel list

Also, the CM 704 transmits a CE coexistence information response (CE_CI_RSP) including the coexistence information of the TVBD, for example, the context information of the TVBD, in response to the CE_CI_REQ message ) Message from the CE 702 (step 716). Here, the CE_CI_RSP message is a response message of the CE_CI_REQ message requesting coexistence information of the TVBD for coexistence in the TVWS of the TVBD and coexistence information for frequency sharing, as described above, and the CE 702 ) Provides the coexistence information of the TVBD to the CM 704. The CE_CI_RSP message is used in a centralized topology, a distributed topology, and an autonomous mode of the resource management system. The contents of the CE_CI_RSP message, that is, the header and the payload of the CE_CI_RSP message, may be represented as shown in Table 18.

Header Name Data Type Description SourceID CE ID Source identifier DestinationID CM ID Destination identifier Payload Name Data Type Description RegisteredCEID STRING Registered CE ID RegisteredCETVBDType COEX_TVBD_TYPE TVBD type, categorized by
- Fixed device type
- Personal / portable mode I type
- Personal / portable mode II type RegisteredCENetworkType COEX_TVBD_NET_TYPE TVBD network type such as IEEE 802.11af, IEEE 802.22 and IEEE 802.16, etc. RegisteredCEAntennaMaxGain REAL TVBD antenna maximum gain RegisteredCEAntennaHeight REAL TVBD antenna height RegisteredCEGeolocation COEX_TVBD_GEOLOCATION TVBD geolocation, including
- Latitude
- Longitude
- Altitude RegisteredCEDutycycle REAL TVBD service duty cycle RegisteredCEBandwidth REAL TVBD service bandwidth RegisteredCECoverage REAL TVBD service coverage RegisteredCEInterferenceRange REAL TVBD interference range RegisteredCEOperatingChList SEQUENCE OF INTEGER TVBD operating channel list RegisteredCEChannelizationList SEQUENCE OF REAL TVBD channelization list RegisteredCETVWSDBChList COEX_TVBD_TVWS TVBD TVWS DB channel list, including
- Allowed TVWS channel list
- Channel use constraint

The CM 704 receives a NCM Coexistence Information Request (NCM_CI_REQ: NCM Coexistence Request) requesting coexistence information of the NCM 706 based on information on corresponding NCMs included in the CDIS_CI_RSP, (NCM_CI_REQ) message to the NCM 708 (step 718). Here, the NCM_CI_REQ message is a message for requesting coexistence information of the NCM 708 for coexistence and frequency sharing in the TVWS of the TVBD, as described above. Also, the NCM_CI_REQ message is used in the centralized topology, distributed topology, and autonomous mode of the resource management system. In addition, the contents of the NCM_CI_REQ message, that is, the header and the payload of the NCM_CI_REQ message, can be represented as shown in Table 19. Here, the NCM_CI_REQ message is transmitted to the NCMs or SCMs to request coexistence information of corresponding NCMs or SCMs.

Header Name Data Type Description SourceID CM ID / Master CM ID Source identifier DestinationID Neighbor CM ID / Slave CM ID Destination identifier Payload Name Data Type Description NeighborCEIDList SEQUENCE OF STRING Neighbor CE ID list to collect context information NeighborCEInformationIDs COEX_TVBD_INFO_IDS Neighbor CEs information
- TVBD type
- TVBD network type
- TVBD antenna maximum gain
- TVBD antenna height
- TVBD geolocation
- TVBD service duty cycle
- TVBD service bandwidth
- TVBD service coverage
- TVBD interference range
- TVBD operating channel list
- TVBD channelization list
- TVBD TVWS DB channel list
- TVBD reconfigurable TVWS channel list

Also, the CM 704 transmits a NCM Coexistence Information Response (NCM_CI_RSP) message including a coexistence information of the NCM 708 in response to the NCM_CI_REQ message From the NCM 708 (step 720). Here, the NCM_CI_RSP message is a response message of the NCM_CI_REQ message requesting coexistence information of the NCM 708 for coexistence and frequency sharing in the TVWS of the TVBD, as described above, And the NCM 708 provides the coexistence information of the NCM 708 to the CM 704. The NCM_CI_RSP message is used in the centralized topology, the distributed topology, and the autonomous mode of the resource management system. In addition, the contents of the NCM_CI_RSP message, i.e., the header and the payload of the CE_CI_RSP message, The NCM_CI_RSP message is a message for providing coexistence information of the corresponding NCMs or SCMs to the arbitrary CM or MCM in response to a coexistence information request of corresponding NCMs or SCMs of an arbitrary CM or MCM.

Header Name Data Type Description SourceID Neighbor CM ID / Slave CM ID Source identifier DestinationID CM ID / Master CM ID Destination identifier Payload Name Data Type Description NeighborCEIDList SEQUENCE OF STRING Neighbor CE ID list The message contents below are repeated for each neighbor CE NeighborCEID STRING Neighbor CE ID NeighborCETVBDType COEX_TVBD_TYPE TVBD type, categorized by
- Fixed device type
- Personal / portable mode I type
- Personal / portable mode II type NeighborCENetworkType COEX_TVBD_NET_TYPE TVBD network type such as IEEE 802.11af, IEEE 802.22 and IEEE 802.16, etc. NeighborCEAntennaMaxGain REAL TVBD antenna maximum gain NeighborCEAntennaHeight REAL TVBD antenna height NeighborCEGeolocation COEX_TVBD_GEOLOCATION TVBD geolocation, including
- Latitude
- Longitude
- Altitude NeighborCEDutycycle REAL TVBD service duty cycle NeighborCEBandwidth REAL TVBD service bandwidth NeighborCECoverage REAL TVBD service coverage NeighborCEInterferenceRange REAL TVBD interference range NeighborCEOperatingChList SEQUENCE OF INTEGER TVBD operating channel list NeighborCEChannelizationList SEQUENCE OF REAL TVBD channelization list NeighborCETVWSDBChList COEX_TVBD_TVWS TVBD TVWS DB channel list, including
- Allowed TVWS channel list
- Channel use constraint

In this manner, the resource management system performs the coexistence information collection procedure in the CM after each of the objects transmits and receives the messages as described above, and after the registration procedure for coexistence and frequency sharing of a plurality of systems, e.g., TVBDs, The coexistence information collection procedure in the CDIS of the resource management system in the communication system according to the embodiment of the present invention will be described in more detail with reference to FIG.

8, in order to collect coexistence information after registration procedures for coexistence and frequency sharing in TVWS of a plurality of systems, e.g., TVBDs, CDIS 804 requests coexistence information of CM 802 CM_CI_REQ message to the CM 802 (step 810). Here, the CM_CI_REQ message is a message for requesting the coexistence information of the CM 802 to collect coexistence information for coexistence and frequency sharing in the TVWS of the TVBD, as described above. Also, the CM_CI_REQ message is used in the centralized topology, distributed topology, and autonomous mode of the resource management system. Table 13 shows the contents of the CM_CI_REQ message, that is, the header and the payload of the CM_CI_REQ message.

In step 812, the CDIS 804 receives a CM_CI_RSP message including coexistence information of the CM 802 from the CM 802 in response to the CM_CI_REQ message. Here, as described above, the CM_CI_RSP message is a response message of the CM_CI_REQ message requesting the coexistence information of the CM 802 to collect coexistence information for coexistence and frequency sharing in the TVWS of the TVBD, And the CM 802 provides the coexistence information of the CM 802 to the CDIS 804. The CM_CI_RSP message is used in the centralized topology, the distributed topology, and the autonomous mode of the resource management system. Table 14 shows the contents of the CM_CI_RSP message, i.e., the header and the payload of the CM_CI_RSP message.

In this way, the resource management system transmits and receives the messages as described above in each of the objects, particularly, CE, CM, and CDIS, and performs a coexistence information collection procedure for coexistence and frequency sharing of a plurality of systems, Hereinafter, a coexistence decision making procedure of a resource management system in a communication system according to an embodiment of the present invention will be described in more detail with reference to FIG. 9 through FIG.

9 to 14 are views schematically showing a coexistence decision making procedure of a resource management system in a communication system according to an embodiment of the present invention. 9 and 10 are diagrams showing a coexistence decision making procedure in the MCM of the resource management system in a centralized topology, and FIGS. 11 and 12 are diagrams illustrating a procedure for making a decision on a random CM in the distributed resource management system FIG. 13 and FIG. 14 illustrate a coexistence decision making procedure in the CE of the resource management system in the autonomous mode. FIG. 9 to 14 illustrate a case where, as described above, after a registration procedure and a coexistence information collection procedure in a resource management system for coexistence and frequency sharing in a TVWS of a plurality of systems, for example, TVBDs, FIG. 2 is a diagram schematically illustrating a message transmission / reception procedure between respective objects of the resource management system in a procedure of FIG.

9, in the centralized topology, for a coexistence decision making process after a registration procedure and a coexistence information collection procedure for coexistence and frequency sharing in a TVWS of a plurality of systems, e.g. TVBDs, The arbitrary i-th SCM 902 and the MCM 904 complete the confirmation of their corresponding NCMs (steps 910 and 912).

After completing the channel classification in the TVWS (step 914), the MCM 904 transmits an NCM_CI_REQ message requesting the coexistence information of the NCM corresponding to the i-th SCM 902 to the i-th SCM 902, (Step 916). At this time, the MCM 904 collects coexistence information from all the SCMs corresponding to the MCM 904 (step 918). In step 920, the MCM 904 receives an NCM_CI_RSP message including NCM coexistence information of the i-th SCM 902 in response to the NCM_CI_REQ message.

Then, the MCM 904 performs coexistence decision making based on coexistence information of the SCMs acquired through the coexistence information collection, such as coexistence mode, operation channel selection, mutual channel sharing mechanism, etc. ).

Next, the MCM 904 transmits a SCM command request (SCM_COM_REQ) message requesting a reconfiguration command of the corresponding SCMs to the i-th SCM 902 (Step 924). At this time, the MCM 904 transmits the SCM_COM_REQ message to all SCMs corresponding to the MCM 904 (step 926). Here, the SCM_COM_REQ message is a message for requesting a reconfiguration command of the corresponding SCM to the corresponding SCMs in accordance with the coexistence decision making in the MCM 904, and the MCM 904 transmits the message to all the SCMs. Also, the SCM_COM_REQ message is used in a centralized topology of the resource management system. The contents of the SCM_COM_REQ message, that is, the header and the payload of the SCM_COM_REQ message, can be represented as shown in Table 21.

Header Name Data Type Description SourceID Master CM ID Source identifier DestinationID Slave CM ID Destination identifier Payload Name Data Type Description RegisteredCEIDList SEQUENCE OF STRING Registered CE ID list included in corresponding slave CM The message contents below are repeated for each registered CE RegisteredCEID STRING Registered CE ID included in corresponding slave CM CoexistenceMode COEX_MODE Coexistence mode such as
- Individual channel assignment mode
- Co-channel sharing mode ChannelClassificationList COEX_CH_CLASSIFICATION Channel classification list such as
- Available channel list
- Restricted channel list
- Operating channel list ServiceSchedule COEX_SER_SCHEDULE Service scheduling, including
- TBD

In response to the SCM_COM_REQ message, the MCM 904 transmits a SCM Command Response (SCM_CMD_RSP) message to all SCMs in response to the reconfiguration command of the corresponding SCM. th SCM 902 (step 928). Here, as described above, the SCM_CMD_RSP message is a response message of the SCM_COM_REQ message requesting a reconfiguration command of the SCM for making a coexistence decision for coexistence and frequency sharing in the TVWS of the TVBD, To the MCM 904 in response to the reconfiguration of the SCM. The SCM_CMD_RSP message is used in a centralized topology of the resource management system. The contents of the SCM_CMD_RSP message, that is, the header and the payload of the SCM_CMD_RSP message, can be represented as shown in Table 22.

Header Name Data Type Description SourceID Slave CM ID Source identifier DestinationID Master CM ID Destination identifier Payload Name Data Type Description RegisteredCEIDList SEQUENCE OF STRING Registered CE ID list included in corresponding slave CM The message contents below are repeated for each registered CE RegisteredCEID STRING Registered CE ID in corresponding slave CM ReconfigurationParameters COEX_RC_PARAMETERS The status information of reconfiguration parameters is provided with
- accepted values of parameters when reconfiguration is succeeded
- recommended values of parameters
when reconfiguration is failed

10, in the centralized topology, for a coexistence decision making process after a registration procedure and a coexistence information collection procedure for coexistence and frequency sharing in a TVWS of a plurality of systems, e.g. TVBDs, The arbitrary i-th SCM 1002 and the MCM 1004 at step S1010 complete the confirmation of their corresponding NCMs (steps 1010 and 1012).

After the i-th SCM 1002 and the MCM 1004 complete the channel classification in the TVWS (steps 1014 and 1016), the MCM 1004 acquires the information of the i-th SCM 1002 SCM 1002 to the i-th SCM 1002 in response to the InfoAcquiring_Request message (Step 1018), and transmits the InfoAcquiring_Request (hereinafter, referred to as 'Info Acquiring_Request' From the i-th SCM 1002, an information acquisition response (InfoAcquiring_Response, hereinafter referred to as "InfoAcquiring_Response") containing information of the information 1002 in step 1020.

The MCM 1004 performs coexistence decision making based on the information of the i-th SCM 1002 included in the InfoAcquiring_Response message, for example, information on a coexistence mode, an operation channel selection, a mutual channel sharing mechanism, and the like Step 1022).

Next, the MCM 1004 transmits a SCM_ReconfigurationCommand_Request (SCM_ReconfigurationCommand_Request) message requesting a reconfiguration command of the SCM to the i-th SCM 1002 (Step 1024) At this time, the MCM 1004 transmits the SCM_ReconfigurationCommand_Request message to all the SCMs corresponding to the MCM 1004 (Step 1026). Here, the SCM_ReconfigurationCommand_Request message is a message for requesting a reconfiguration command of the corresponding SCM to all the corresponding SCMs in accordance with the coexistence decision making in the MCM 1004, and the MCM 1004 transmits the message to all the SCMs. Also, the SCM_ReconfigurationCommand_Request message is used in a centralized topology of the resource management system. Table 23 shows the contents of the SCM_ReconfigurationCommand_Request message, that is, the header and the payload of the SCM_ReconfigurationCommand_Request message.

Header Information element Data type Description sourceIdentifier = CM_ID CX_ID Source identifier destinationIdentifier = CE_ID CX_ID Destination identifier ACKPolicy BOOLEAN Request to send an acknowledgment of reception Payload Information element Data type Description Note: Information elements below are repeated for each TVBD network or device. reconfigurationRequest ReconfigurationRequest Reconfiguration request description chClassInfo ChClassInfo Channel classification information of the CE timeSharingUnitInfo TimeSharingUnitInfo General time sharing unit information

In response to the SCM_ReconfigurationCommand_Request message, the MCM 1004 transmits a SCM_ReconfigurationCommand_Response (SCM_ReconfigurationCommand_Response) message to all the SCMs in response to the reconfiguration command of the corresponding SCM, (Step 1028). Here, the SCM_ReconfigurationCommand_Response message is a response message of the SCM_ReconfigurationCommand_Request message requesting a reconfiguration command of the SCM for making a coexistence decision for coexistence and frequency sharing in the TVWS of the TVBD, as described above, To the MCM 1004 in response to the reconfiguration of the SCM. The SCM_ReconfigurationCommand_Response message is used in a centralized topology of the resource management system. Table 24 shows the contents of the SCM_ReconfigurationCommand_Response message, i.e., the header and the payload of the SCM_ReconfigurationCommand_Response message.

Header Information element Data type Description sourceIdentifier = CE_ID CX_ID Source identifier destinationIdentifier = CM_ID CX_ID Destination identifier ACKPolicy BOOLEAN Request to send an acknowledgment of reception Payload Information element Data type Description status BOOLEAN Status: successful or not failedParameters FailedParameters Failed reconfiguration parameters with recommended values of parameters if reconfiguration request from slave CM to TVBD is failed

In this manner, the resource management system performs the coexistence determination making procedure for coexistence and frequency sharing of a plurality of systems, e.g., TVBDs, by sending and receiving the messages as described above in the centralized topology of each object, in particular, MCM and SCM Hereinafter, the coexistence determination making procedure in the distributed topology of the resource management system in the communication system according to the embodiment of the present invention will be described in more detail with reference to FIG. 11 and FIG.

11, in a distributed topology, for a coexistence decision making process after a registration procedure and a coexistence information collection procedure for coexistence and frequency sharing in a TVWS of a plurality of systems, e.g. TVBDs, The arbitrary i-th CM 1102 and the j-th CM 1104 complete the confirmation of their corresponding NCMs (steps 1110 and 1112).

After the i-th CM 1102 and the j-th CM 1104 complete the channel classification in the TVWS (steps 1114 and 1116), the i-th CM 1102 and the j-th CM 1104 , And the coexistence information collection as described above is completed (Step 1118). Here, the coexistence information collection procedure in the CM has been described in detail with reference to FIG. 7, and a detailed description thereof will be omitted here.

Then, the j-th CM 1104 transmits a CM Negotiation Request (CM_NEG_REQ) including a negotiation inforamtion of the CM adjacent thereto, for example, the i-th CM 1102, Message from the i-th CM 1102 (step 1120). Here, the CM_NEG_REQ message is a message to be transmitted to the NCM to provide negotiation information to an NCM when an arbitrary CM, for example, the i-th CM 1102 is adjacent to another CM, for example, the j-th CM 1104 , And transmits the negotiation information to the j-th CM 1104 in which the i-th CM 1102 is the NCM. Also, the CM_NEG_REQ message is used in a distributed topology of the resource management system. The contents of the CM_NEG_REQ message, that is, the header and the payload of the CM_NEG_REQ message, can be represented as shown in Table 25.

Header Name Data Type Description SourceID CM ID Source identifier DestinationID Neighbor CM ID Destination identifier Payload Name Data Type Description DialogToken INTEGER Identification of transaction NeogtiationStatus NEG_STATUS Negotiation status NegotiationInformation NEG_INFO Specific information
- Mode (Etiquette / Contention)
- Channel list
- General time sharing information
- Round-robin mode information
- Competition mode information

The j-th CM 1104 is configured to transmit the negotiation information included in the CM_NEG_REQ message and the coexistence information acquired through the coexistence information collection procedure, for example, information on coexistence mode, operation channel selection, mutual channel sharing mechanism, Coexistence determination making is performed (step 1122).

Next, the j-th CM 1104 transmits, in response to the CM_NEG_REQ message, a CM Negation Response (CM_NEG_RSP) including the negotiation information of the j-th CM 1104 itself Message to the i-th CM 1102 (step 1124). Here, the CM_NEG_RSP message is a message to be transmitted to the NCM to provide negotiation information to an NCM when an arbitrary CM, for example, the j-th CM 1104 is in a neighbor relationship with another CM, for example, the i-th CM 1102 , And transmits the negotiation information including the negotiation information to the i-th CM 1102 in which the j-th CM 1104 is an NCM. Also, the CM_NEG_RSP message is used in a distributed topology of the resource management system. In addition, the contents of the CM_NEG_RSP message, i.e., the header and the payload of the CM_NEG_RSP message, can be represented as shown in Table 26. [

Header Name Data Type Description SourceID CM ID Source identifier DestinationID Neighbor CM ID Destination identifier Payload Name Data Type Description DialogToken INTEGER Identification of transaction NeogtiationStatus NEG_STATUS Negotiation status NegotiationInformation NEG_INFO Specific information
- Mode (Etiquette / Contention)
- Channel list
- General time sharing information
- Round-robin mode information
- Competition mode information

After receiving the CM_NEG_REQ message (step 1126) and transmitting and receiving the CM_NEG_RSP message (step 1130) between the i-th CM 1102 and the j-th CM 1104 and receiving the CM_NEG_REQ message from the j-th CM 1104 The coexistence determination making (step 1128) is repeatedly performed.

When the NCMs of the j-th CM 1104 are in a competition mode, the i-th CM 1102 transmits a CM Negation Indication (CM_NEG_IND) To the NCMs, e.g., the jth CM 1104 (step 1132). Here, the CM_NEG_IND message is a message to be transmitted to the NCM to provide a negotiation result to the NCM when an arbitrary CM, for example, the i-th CM 1102 is adjacent to another CM, for example, the j-th CM 1104 And provides the negotiation result to the j-th CM 1104 in which the i-th CM 1102 is the NCM. Also, the CM_NEG_IND message is used in the distributed topology of the resource management system. The contents of the CM_NEG_IND message, that is, the header and the payload of the CM_NEG_IND message, can be represented as shown in Table 27.

Header Name Data Type Description SourceID CM ID Source identifier DestinationID Neighbor CM ID Destination identifier Payload Name Data Type Description DialogToken INTEGER Identification of transaction WinnderCMDIList SEQUENCE OF CM ID CM ID list SlotTimePositionList SEQUENCE OF REAL Slot time position list

12, in the distributed topology, for a coexistence decision making process, a registration procedure and a coexistence information collection procedure for coexistence and frequency sharing in a TVWS of a plurality of systems, e.g., TVBDs, The arbitrary i-th CM 1202 and the j-th CM 1204 in the step S124 respectively confirm the NCMs corresponding to the i-th CM 1202 and the j-th CM 1204, respectively (steps 1210 and 1212).

After the i-th CM 1202 and the j-th CM 1204 complete the channel classification in the TVWS (steps 1214 and 1216), the i-th CM 1202 and the j-th CM 1204 , Respectively, the information acquisition of the NCM is completed (Step 1218).

Then, the j-th CM 1204 transmits a CM_Negotiation_Request (hereinafter referred to as a CM_Negotiation_Request) message including negotiation information of a CM adjacent thereto, for example, the i-th CM 1202, From the CM 1202 (step 1220). Here, the CM_Negotiation_Request message is a message to be transmitted to the NCM in order to provide negotiation information to an NCM when an arbitrary CM, for example, the i-th CM 1202 is adjacent to another CM, for example, the j-th CM 1204 , And transmits the negotiation information including the negotiation information to the j-th CM 1204 in which the i-th CM 1202 is an NCM. Also, the CM_Negotiation_Request message is used in a distributed topology of the resource management system. In addition, the contents of the CM_Negotiation_Request message, i.e., the header and the payload of the CM_Negotiation_Request message, can be represented as shown in Table 28. [

Header Information element Data type Description sourceIdentifier = CM_ID CX_ID Source identifier destinationIdentifier = CM_ID CX_ID Destination identifier ACKPolicy BOOLEAN Request to send an acknowledgment of reception Payload Information element Data type Description dialogToken INTEGER Identification of transaction negotiationStatus NegotiationStatus Negotiation status negotiationInformation NegotiationInformation Negotiation information

The j-th CM 1204 performs coexistence decision making based on negotiation information included in the CM_Negotiation_Request message and information on the obtained NCM, for example, coexistence mode, operation channel selection, mutual channel sharing mechanism, and the like (Step 1222).

Next, the j-th CM 1204 transmits a CM_Negotiation_Response (CM_Negotiation_Response) message including the negotiation information of the j-th CM 1204 in response to the CM_Negotiation_Request message To the i-th CM 1202 (step 1224). Here, the CM_Negotiation_Response message is a message to be transmitted to the NCM to provide negotiation information to an NCM when an arbitrary CM, for example, the j-th CM 1204 is in a neighbor relationship with another CM, for example, the i-th CM 1202 , And transmits the negotiation information to the i-th CM 1202 in which the j-th CM 1204 is an NCM. In addition, the CM_Negotiation_Response message is used in a distributed topology of the resource management system. The contents of the CM_Negotiation_Response message, that is, the header and the payload of the CM_Negotiation_Response message can be shown in Table 29. [

Header Information element Data type Description sourceIdentifier = CM_ID CX_ID Source identifier destinationIdentifier = CM_ID CX_ID Destination identifier ACKPolicy BOOLEAN Request to send an acknowledgment of reception Payload Information element Data type Description dialogToken INTEGER Identification of transaction negotiationStatus NegotiationStatus Negotiation status negotiationInformation NegotiationInformation Negotiation information

The CM_Negotiation_Request message transmission and reception (step 1226) and the CM_Negotiation_Response message transmission / reception (step 1230) are performed between the i-th CM 1202 and the j-th CM 1204, and after receiving the CM_Negotiation_Request message from the j-th CM 1204 Performing coexistence decision making (step 1228) is repeatedly performed.

When the NCMs of the j-th CM 1204 are in a competition mode, the i-th CM 1202 transmits a CM_Negotiation_Announcement (CM_Negotiation_Announcement) message To the NCMs, e.g., the j th CM 1204 (step 1232). Here, the CM_Negotiation_Announcement message is a message to be transmitted to the NCM to provide a negotiation result to an NCM when an arbitrary CM, for example, the i-th CM 1202 is adjacent to another CM, for example, the j-th CM 1204 , And provides the negotiation result to the j-th CM 1204 in which the i-th CM 1202 is the NCM. Also, the CM_Negotiation_Announcement message is used in the distributed topology of the resource management system. In addition, the contents of the CM_Negotiation_Announcement message, that is, the header and payload of the CM_Negotiation_Announcement message, can be represented as shown in Table 30.

Header Information element Data type Description sourceIdentifier = CM_ID CX_ID Source identifier destinationIdentifier = CM_ID CX_ID Destination identifier ACKPolicy BOOLEAN Request to send an acknowledgment of reception Payload Information element Data type Description dialogToken INTEGER Identification of transaction listOfWinnerCMID ListOfWinnerCMID Winner CM ID list listOfSlotTimePosition ListOfSlotTimePosition Slot time position list

The resource management system thus allows each object, in particular any CM and NCM, to send and receive messages as described above in a distributed topology, and to perform coexistence decision making procedures for coexistence and frequency sharing of multiple systems, e.g. TVBDs Hereinafter, with reference to FIG. 13 and FIG. 14, a coexistence determination making procedure in an autonomous mode of a resource management system in a communication system according to an embodiment of the present invention will be described in more detail.

Referring to FIG. 13, in the autonomous mode, TVBD and CE (hereinafter referred to as " TVBD ") are registered for coexistence determination making after a registration procedure and a coexistence information collection procedure for coexistence and frequency sharing in a TVWS of a plurality of systems, ) 1304 completes the confirmation of adjacent TVBDs (step 1310), and the CM 1306 completes the channel classification of the TVWS (step 1312).

The TVBD / CE 1304 transmits a CM Channel Classification Request (CM_CC_REQ) message requesting channel classification information of the CM 1306 to the CM 1306 (Step 1314). In response to the CM_CC_REQ message, a CM channel classification response (CM_CC_RSP) including channel classification information of the CM 1306 is transmitted, Message from the CM 1306 (step 1316). At this time, the TVBD / CE 1304 completes the channel classification in the TVWS through the channel classification information included in the CM_CC_RSP message (step 1318).

Next, the TVBD / CE 1304 transmits a TVWS DB Channel Classification Request (TVWSDB_CC_REQ) message requesting channel classification information of the TVWS DB 1302 to the TVBD / TVWS DB Channel Classification Response (TVWS DB_CC_RSP: TVWS DB Channel Classification Response) including the channel classification information of the TVWS DB 1302 in response to the TVWSDB_CC_REQ message in step 1320, TVWSDB_CC_RSP 'message from the TVWS DB 1302 (step 1322).

In step 1324, the TVBD / CE 1304 performs co-existence decision making based on the operation channel selection corresponding to the received channel information.

14, in the autonomous mode, for a coexistence decision making process after a registration procedure and a coexistence information collection procedure for coexistence and frequency sharing in a TVWS of a plurality of systems, e.g., TVBDs, a TVBD / CE 1404 Completes the confirmation of the adjacent TVBDs (step 1410), and the CM 1406 completes the channel classification in the TVWS (step 1412).

The TVBD / CE 1404 transmits to the CM 1406 a Channel Classification_Request (ChannelClassification_Request) message requesting channel classification information of the CM 1406 (1414 From the CM 1406, a Channel Classification_Response (hereinafter, referred to as 'Channel Classification_Response') message including the channel classification information of the CM 1406 in response to the ChannelClassification_Request message (Step 1416) step).

Then, the TVBD / CE 1404 obtains a usable channel list from the TVWS DB 1402 (step 1418), and selects an operation channel corresponding to the channel classification information of the CM 1406 and an available channel list (Step 1420).

In this manner, the resource management system transmits and receives the above-mentioned messages in the respective objects, particularly TVBD and CE in the autonomous mode to perform a coexistence decision making procedure for coexistence and frequency sharing of a plurality of systems, e.g., TVBDs, Hereinafter, the reconfiguration procedure of the resource management system in the communication system according to the embodiment of the present invention will be described in more detail with reference to FIG. 15 and FIG.

15 and 16 are diagrams schematically illustrating a reconfiguration procedure of a resource management system in a communication system according to an embodiment of the present invention. Here, FIG. 15 is a diagram illustrating a reconfiguration procedure in the CM of the resource management system in the management mode, and FIG. 16 is a diagram illustrating a reconfiguration procedure in the CE of the resource management system in the autonomous mode. 15 and 16 are diagrams for explaining the procedure of registration and coexistence information collection in a resource management system for coexistence and frequency sharing in a TVWS of a plurality of systems, for example, TVBDs, And a message transmission / reception procedure between the objects of the resource management system in the reconfiguration procedure.

15, in the management mode, after a registration procedure and a coexistence information gathering procedure and a coexistence decision making procedure for coexistence and frequency sharing in a TVWS of a plurality of systems, e.g., TVBDs, (CE_RC_REQ) message (CE_RC_REQ) requesting reconfiguration of the CE 1504 after completing the coexistence decision making (step 1510), as described above, To the CE 1504 (step 1512). Here, the CE_RC_REQ message is a message for providing a reconfiguration command of the CE 1504 to reconfigure the configuration and settings of the CE 1504 for TVBD coexistence and frequency sharing according to the coexistence decision making. Also, the CE_RC_REQ message is used in a centralized topology and a distributed topology of the resource management system. The contents of the CE_RC_REQ message, that is, the header and the payload of the CE_RC_REQ message, can be represented as shown in Table 31.

Header Name Data Type Description SourceID CM ID Source identifier DestinationID CE ID Destination identifier Payload Name Data Type Description CoexistenceMode COEX_MODE Coexistence mode such as
- Individual channel assignment mode
- Co-channel sharing mode ChannelClassificationList COEX_CH_CLASSIFICATION Channel classification list such as
- Available channel list
- Restricted channel list
- Operating channel list ServiceSchedule COEX_START_END_TIME Service scheduling, including
- Start time
- End time ScheduleUnitInfo COEX_SCH_UNIT_INFO Service scheduling, including
- Reference time
- Window time
- Slot time

The CE 1504 confirms the reconfiguration command of the CE 1504 through the CE_RC_REQ message and provides a reconfiguration command of the CE 1504 to the TVBD 1502 to reconfigure A TVBD Reconfiguration Request (TVBD_RC_REQ) message requesting reconfiguration of the TVBD 1502 corresponding to the command is transmitted to the TVBD 1502 in step 1514. The TVBD_RC_REQ message, From the TVBD 1502, a reconfiguration response (TVBD_RC_RSP: TVBD_RC_RSP) message of the TVBD 1502 in response to the TVBD 1502 (step 1516).

Then, in response to the CE_RC_REQ message, the CE 1504 transmits a CE Reconfiguration Response (CE_RC_RSP) message to the CM 1506 (Step 1518). Here, the CE_RC_RSP message is a message for providing a response to the reconfiguration of the CE 1504 to the CM 1506. Also, the CE_RC_RSP message is used in a centralized topology and a distributed topology of the resource management system. In addition, the contents of the CE_RC_RSP message, i.e., the header and the payload of the CE_RC_RSP message, can be represented as shown in Table 32.

Header Name Data Type Description SourceID CE ID Source identifier DestinationID CM ID Destination identifier Payload Name Data Type Description ReconfigurationParameters COEX_RC_PARAMETERS The status information of reconfiguration parameters is provided with
- accepted values of parameters when reconfiguration is succeeded
- recommended values of parameters when reconfiguration is failed

In this way, the resource management system transmits and receives the messages as described above in the management mode of each of the objects, particularly the CM, and performs a reconfiguration procedure for coexistence and frequency sharing of a plurality of systems, e.g., TVBDs. The reconfiguration procedure in the autonomous mode of the resource management system in the communication system according to the embodiment of the present invention will be described in more detail.

16, in the autonomous mode, after the registration procedure and the coexistence information gathering procedure and the coexistence decision making procedure for coexistence and frequency sharing in the TVWS of a plurality of systems, e.g. TVBDs, the CE 1604 Sends a TVBD_RC_REQ message to the TVBD 1602 requesting reconfiguration of the TVBD 1602 corresponding to the reconfiguration command of the CE 1604 by confirming its reconfiguration command and providing its reconfiguration command to the TVBD 1602 (Step 1610), and receives a TVBD_RC_RSP message from the TVBD 1602 in response to the TVBD_RC_REQ message (step 1612).

The resource management system thus performs the reconfiguration procedure for coexistence and frequency sharing of a plurality of systems, e.g., TVBDs, by sending and receiving the messages as described above in the respective objects, particularly the CE in the autonomous mode, A measurement procedure of a resource management system in a communication system according to an embodiment of the present invention will be described in more detail with reference to FIG.

17 is a view schematically showing a measurement procedure of a resource management system in a communication system according to an embodiment of the present invention. Here, FIG. 17 is a flowchart illustrating a registration procedure and a coexistence information collection procedure, a coexistence determination making procedure, and a reconfiguration procedure in a resource management system for coexistence and frequency sharing in TVWS of a plurality of systems, e.g., TVBDs, FIG. 3 is a diagram schematically illustrating a message transmission / reception procedure in a management procedure between objects of the resource management system. FIG.

17, after a registration procedure and a coexistence information collection procedure for coexistence and frequency sharing in a TVWS of a plurality of systems, e.g., TVBDs, and a coexistence decision making and reconfiguration procedure, each object of the resource management system The CE 1704 transmits a TVBD_ME_REQ (TVBD_ME_REQ) message requesting management of the TVBD 1702 for management of the TVBD 1702 (TVBD_ME_RSP) message to the TVBD 1702 in response to the TVBD_ME_REQ message in step 1710. The TVBD_ME_RSP message is transmitted to the TVBD 1702 in response to the TVBD_ME_REQ message, 1702 (step 1712).

Also, the CM 1706 transmits a CE Measurement Request (CE_ME_REQ) message requesting the management of the CE 1704 to manage the CE 1704 CE 1704 (step 1714). Here, the CE_ME_REQ message is a message requesting management of the corresponding CE to manage the CE 1704. Also, the CE_ME_REQ message is used in a centralized topology and a distributed topology of the resource management system. In addition, the contents of the CE_ME_REQ message, that is, the header and payload of the CE_ME_REQ message, can be represented as shown in Table 33.

Header Name Data Type Description SourceID CM ID Source identifier DestinationID CE ID Destination identifier Payload Name Data Type Description MeasurementType COEX_ME_TYPE Measurement list such as
- TVBD QoS
- TVBD spectrum sensing ChannelNumberList SEQUENCE OF INTEGER Measuring channel number list MeasurementOptions COEX_ME_OPTIONS Measurement options such as
- Measurement duration
- Measurement frequency range

The CM 1706 receives a CE Response (CE_ME_RSP: CE_ME_RSP) message from the CE 1704 in response to the CE_ME_REQ message (Step 1716). Here, the CE_ME_RSP message is a message for providing the management result of the CE 1704 for the management request of the CE 1704 according to the CE_ME_REQ message. In addition, the CE_ME_RSP message is used in a centralized topology and a distributed topology of the resource management system. In addition, the contents of the CE_ME_RSP message, i.e., the header and the payload of the CE_ME_RSP message, can be represented as shown in Table 34.

Header Name Data Type Description SourceID CE ID Source identifier DestinationID CM ID Destination identifier Payload Name Data Type Description MeasurementType COEX_ME_TYPE Measurement type ChannelNumberList SEQUENCE OF INTEGER Measured channel number list MeasurementResults COEX_ME_RESULTS Measurement results MeasurementParameters COEX_ME_OPTIONS Actual measurement parameters such as
- Actual measurement duration
- Actual measurement frequency range

The CM 1706 also sends an NCM Management Request (NCM_ME_REQ: NCM_ME_REQ) message requesting management of the NCM 1708 to the NCM 1708 for management of the NCM 1708, (Step 1718). Here, the NCM_ME_REQ message is a message requesting management of the corresponding NCM for management of the NCM 1708, and the CM 1706 transmits the message to all the NCMs. In addition, the NCM_ME_REQ message is used in a centralized topology and a distributed topology of the resource management system. In the centralized topology, the MCM transmits to all the SCMs. In the distributed topology, a certain CM is transmitted to all the NCMs do. In addition, the contents of the NCM_ME_REQ message, that is, the header and payload of the NCM_ME_REQ message, can be represented as shown in Table 35.

Header Name Data Type Description SourceID CM ID / Master CM ID Source identifier DestinationID Neighbor CM ID / Slave CM ID Destination identifier Payload Name Data Type Description NeighborCEID STRING Neighbor CE ID MeasurementType COEX_ME_TYPE Measurement list such as
- TVBD QoS
- TVBD spectrum sensing ChannelNumberList SEQUENCE OF INTEGER Measuring channel number list MeasurementOptions COEX_ME_OPTIONS Measurement options such as
- Measurement duration
- Measurement frequency range

The CM 1706 receives a NCM Measurement Response (NCM_ME_RSP) message from the NCM 1708 in response to the NCM_ME_REQ message (Step 1720). Here, the NCM_ME_RSP message is a message for providing the management result of the NCM 1708 to the management request of the NCM 1708 according to the NCM_ME_RSP message. In addition, the NCM_ME_RSP message is used in a centralized topology and a distributed topology of the resource management system. In the centralized topology, all SCMs are transmitted to the MCM, and in the distributed topology, all the NCMs are transmitted to an arbitrary NCM. In addition, the contents of the NCM_ME_RSP message, that is, the header and the payload of the NCM_ME_RSP message, can be represented as shown in Table 36.

Header Name Data Type Description SourceID Neighbor CM ID / Slave CM ID Source identifier DestinationID CM ID / Master CM ID Destination identifier Payload Name Data Type Description NeighborCEID STRING Neighbor CE ID MeasurementType COEX_ME_TYPE Measurement type ChannelNumberList SEQUENCE OF INTEGER Measured channel number list MeasurementResults COEX_ME_RESULTS Measurement results MeasurementParameters COEX_ME_OPTIONS Actual measurement parameters such as
- Actual measurement duration
- Actual measurement frequency range

The resource management system transmits and receives the messages as described above between the respective objects and performs a management procedure for coexistence and frequency sharing of a plurality of systems, for example, TVBDs. Hereinafter, with reference to FIG. 18, The event procedure of the resource management system in the communication system according to the embodiment will be described in more detail.

18 is a diagram schematically illustrating an event procedure of a resource management system in a communication system according to an embodiment of the present invention. Here, FIG. 18 is a flowchart illustrating a registration procedure and a coexistence information collection procedure, a coexistence determination making procedure, and a reconfiguration procedure in a resource management system for coexistence and frequency sharing in TVWS of a plurality of systems, for example, TVBDs And FIG. 5 is a diagram schematically illustrating a message transmission / reception procedure in an event procedure between the objects of the resource management system.

18, after a registration procedure and a coexistence information collection procedure for coexistence and frequency sharing in TVWS of a plurality of systems, for example, TVBDs, and a coexistence decision making and reconfiguration procedure, each object of the resource management system CE 1804 sends an event request (TVBD_EV_REQ: TVBD_ME_REQ) message of TVBD 1802 requesting event detection of TVBD 1802 to the TVBD 1802 (TVBD_EV_RSP: TVBD_EV_RSP) to provide the detected event of the TVBD 1802 in response to the TVBD_EV_REQ message in step 1820, From the TVBD 1802 (step 1822).

The CM 1806 also receives the CM event of the CDIS 1808 for providing the CM event detected in the CDIS 1808 in correspondence with the event detection corresponding to the CM 1806 in the CDIS 1808 From the CDIS 1808, a CDIS CM event indication (CDIS_CM_EV_IND: CDIS CM Event Indication, hereinafter referred to as 'CDIS_CM_EV_IND') message. Here, the CDIS_CM_EV_IND message is a message for providing information on the detected event to the CM 1806 when the CDIS 1808 detects an event corresponding to the CM 1806. Also, the CDIS_CM_EV_IND message is used in the centralized topology and the distributed topology of the resource management system and in the autonomous mode. The contents of the CDIS_CM_EV_IND message, that is, the header and the payload of the CDIS_CM_IND message, may be shown in Table 37.

Header Name Data Type Description SourceID CDIS ID Source identifier DestinationID CM ID Destination identifier Payload Name Data Type Description RegisteredCEID STRING Registered CE ID TVWSChannelStatus COEX_TVWSCH_STATUS TVWS channel information event includes
- Allowed channel list change
- Use constraint change
This message conveys the detected event and updated information. NeighborInformationStatus COEX_NEI_CE_INFO_STATUS Neighbor information event includes
- Neighbor CE list change
- Channel classification change of neighbor CE
This message conveys the detected event and updated information.

In response to the CDIS_CM_EV_IND message, the CM 1806 transmits a CMIS Event Acknowledgment (CDIS_CM_EV_ACK) message to the CDIS 1808 (Step 1826). Here, the CDIS_CM_EV_ACK message is a message for confirming the CM event detected by the CDIS 1808 included in the CDIS_CM_EV_IND message, that is, for providing approval of information on the detected event. Also, the CDIS_CM_EV_ACK message is used in the centralized topology and the distributed topology of the resource management system and in the autonomous mode. In addition, the contents of the CDIS_CM_EV_ACK message, that is, the header and the payload of the CDIS_CM_EV_ACK message, can be shown in Table 38.

Header Name Data Type Description SourceID CM ID Source identifier DestinationID CDIS ID Destination identifier Payload Name Data Type Description EventAck BOOLEAN Acknowledgment of corresponding event as a receipt
- True: Event receipt is succeed
- False: Event receipt is failed

In addition, the CM 1806 may be configured to receive a CDIS event 1806 of the CM 1806 to provide a CDIS event detected in the CM 1806, corresponding to an event detection corresponding to the CDIS 1808 in the CM 1806. [ (CM_CDIS_EV_IND: CM_CDIS_EV_IND) message to the CDIS 1808 (step 1828). Here, the CM_CDIS_EV_IND message is a message for providing the CDIS 1808 with information on the detected event when the CM 1806 detects an event corresponding to the CDIS 1808. Also, the CM_CDIS_EV_IND message is used in the centralized topology and the distributed topology of the resource management system and the autonomous mode. In addition, the contents of the CM_CDIS_EV_IND message, that is, the header and the payload of the CM_CDIS_EV_IND message, may be shown in Table 39.

Header Name Data Type Description SourceID CM ID Source identifier DestinationID CDIS ID Destination identifier Payload Name Data Type Description RegisteredCMStatus COEX_REG_CM_STATUS Registered CM event includes
- Registered CE ID list change
- Information change of registered CE
This message conveys the detected event and updated information. ChannelClassificationStatus COEX_CH_CLASSIFICATION_STATUS Channel classification event includes
- Channel classification change of the registered CE
This message conveys the detected event and updated information.

In response to the CM_CDIS_EV_IND message, the CM 1806 transmits a CM_CDIS_EV_ACK (CM_CDIS_EV_ACK) message from the CDIS 1808 to the CM 1806 (Step 1830). Here, the CM_CDIS_EV_ACK message is a message that identifies the CDIS event detected by the CM 1806 included in the CM_CDIS_EV_IND message, that is, provides acknowledgment of information on the detected event. Also, the CM_CDIS_EV_ACK message is used in the centralized topology and distributed topology of the resource management system and in the autonomous mode. In addition, the contents of the CM_CDIS_EV_ACK message, that is, the header and the payload of the CM_CDIS_EV_ACK message can be represented as shown in Table 40.

Header Name Data Type Description SourceID CDIS ID Source identifier DestinationID CM ID Destination identifier Payload Name Data Type Description EventAck BOOLEAN Acknowledgment of corresponding event as a receipt
- True: Event receipt is succeed
- False: Event receipt is failed

Also, the CM 1806 may transmit the CM event of the CE 1804 to the CE 1804 in response to the event detection corresponding to the CM 1806 in the CE 1804, From the CE 1804, a CE CM event indication (CE_CM_EV_IND: CE_CM_EV_IND) message indicating the event (step 1832). Here, the CE_CM_EV_IND message is a message for providing the CM 1806 with information on the detected event when the CE 1804 detects an event corresponding to the CM 1806. Also, the CE_CM_EV_IND message is used in the centralized topology and the distributed topology of the resource management system and in the autonomous mode. The contents of the CE_CM_EV_IND message, that is, the header and the payload of the CE_CM_IND message, can be represented as shown in Table 41.

Header Name Data Type Description SourceID CE ID Source identifier DestinationID CM ID Destination identifier Payload Name Data Type Description RegisteredCEStatus COEX_REG_CE_STATUS Registered CE's event, subscribed to discovery service, includes
- TVBD geolocation change
- TVBD TVWS DB channel list change
- TVBD interference range change

Registered CE's event, subscribed to information service, includes
- CE's event of discovery service
- TVBD operating channel list change

Registered CE's event, subscribed to management service, includes
- CE's event of information service
- TVBD QoS change
- TVBD service duty cycle change
- TVBD service bandwidth change
- TVBD service coverage change
This message conveys the detected event and gives you updated information.

The CM 1806 transmits CE CME Event Acknowledgment (CE_CM_EV_ACK) message of the CE 1804 to the CE 1804 in response to the CE_CM_EV_IND message (Step 1834). Here, the CE_CM_EV_ACK message is a message for confirming the CM event detected by the CE 1804 included in the CE_CM_EV_IND message, that is, for providing approval of information on the detected event. Also, the CE_CM_EV_ACK message is used in the centralized topology and the distributed topology of the resource management system and the autonomous mode. In addition, the contents of the CE_CM_EV_ACK message, that is, the header and the payload of the CE_CM_EV_ACK message, can be represented as shown in Table 42.

Header Name Data Type Description SourceID CM ID Source identifier DestinationID CE ID Destination identifier Payload Name Data Type Description EventAck BOOLEAN Acknowledgment of corresponding event as a receipt
- True: Event receipt is succeed
- False: Event receipt is failed

In addition, the CM 1806 may detect a CE event of the CM 1806 to provide a CE event detected in the CM 1806, corresponding to the event detection corresponding to the CE 1804, (CM_CE_EV_IND: CM_CE_EV_IND) message to the CE 1804 (step 1836). Here, the CM_CE_EV_IND message is a message for providing the CE 1804 with information on the detected event when the CM 1806 detects an event corresponding to the CE 1804. Also, the CM_CE_EV_IND message is used in the centralized topology and the distributed topology of the resource management system and the autonomous mode. In addition, the contents of the CM_CE_EV_IND message, that is, the header and payload of the CM_CE_EV_IND message, can be represented as shown in Table 43.

Header Name Data Type Description SourceID CM ID Source identifier DestinationID CE ID Destination identifier Payload Name Data Type Description NDStatus COEX_ND_STATUS Registered CM event for discovery service, includes
- Neighbor discovery event such as
- Neighbor discovery done
- Neighbor CE list change

Registered CM event for information service, includes
- CM's event of discovery service
- TVBD information change of neighbor CE
- Channel classification change of neighbor CE

This message conveys the detected event and updated information.

The CM 1806 transmits a CM CE Event Acknowledgment (CM_CE_EV_ACK) message to the CE 1804 in response to the CM_CE_EV_IND message from the CE 1804 (Step 1838). Here, the CM_CE_EV_ACK message is a message for confirming the CE event detected by the CM 1806 included in the CM_CE_EV_IND message, that is, for providing approval of information on the detected event. Also, the CM_CE_EV_ACK message is used in the centralized topology and the distributed topology of the resource management system and in the autonomous mode. The contents of the CM_CE_EV_ACK message, that is, the header and the payload of the CM_CE_EV_ACK message, can be represented as shown in Table 44.

Header Name Data Type Description SourceID CE ID Source identifier DestinationID CM ID Destination identifier Payload Name Data Type Description EventAck BOOLEAN Acknowledgment of corresponding event as a receipt
- True: Event receipt is succeed
- False: Event receipt is failed

The CM 1806 also receives an NCM event of the CM 1806 for providing an NCM event detected in the CM 1806 in response to an event detection corresponding to the NCM 1810 in the CM 1806 (CM_NCM_EV_IND: CM_NCM_EV_IND) message to the NCM 1810 (Step 1840). Here, the CM_NCM_EV_IND message is a message for providing the NCM 1810 with information on the detected event when the CM 1806 detects an event corresponding to the NCM 1810. The CM_NCM_EV_IND message is used in a centralized topology and a distributed topology of the resource management system. In the centralized topology, the MCM detects an event corresponding to the SCM and provides the event information detected by the SCM The MCM transmits to the SCM, and in the distributed topology, any CM detects an event corresponding to the NCM and transmits the CM to the NCM to provide event information detected by the NCM. The contents of the CM_NCM_EV_IND message, that is, the header and the payload of the CM_NCM_EV_IND message, may be shown in Table 45.

Header Name Data Type Description SourceID CM ID / Slave CM ID Source identifier DestinationID Neighbor CM ID
/ Master CM ID Destination identifier Payload Name Data Type Description ChannelUseStatus COEX_CH_USE_STATUS Channel use status such as
- New TVBD
- TVBD information change
- Scheduled service time end

The CM 1806 receives a CM_NCM_EV_ACK message from the NCM 1810 in response to the CM_NCM_EV_IND message and transmits a CM_NCM_EV_ACK message to the CM 1806 (Step 1842). Here, the CM_NCM_EV_ACK message is a message for confirming the NCM event detected by the CM 1806 included in the CM_NCM_EV_IND message, that is, for providing information for the detected event. Also, the CM_NCM_EV_ACK message is used in a centralized topology and a distributed topology of the resource management system. In the centralized topology, the SCM sends the SCM to the MCM to provide acknowledgment of the event information. In the distributed topology, The NCM sends to any CM to provide acknowledgment of the event information. In addition, the contents of the CM_NCM_EV_ACK message, i.e., the header and the payload of the CM_NCM_EV_ACK message, can be represented as shown in Table 46.

Header Name Data Type Description SourceID Neighbor CM ID
/ Master CM ID Source identifier DestinationID CM ID / Slave CM ID Destination identifier Payload Name Data Type Description EventAck BOOLEAN Acknowledgment of corresponding event as a receipt
- True: Event receipt is succeed
- False: Event receipt is failed

When the resource management system detects an event for the corresponding objects in each of the objects, the resource management system transmits and receives the above-described messages between the respective objects, and transmits the messages for the coexistence and frequency sharing of a plurality of systems, Perform the procedure.

While the invention has been shown and described with reference to certain preferred embodiments thereof, it will be understood by those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the invention. Therefore, the scope of the present invention should not be limited by the described embodiments, but should be determined by the scope of the appended claims, as well as the appended claims.

Claims (20)

CLAIMS What is claimed is: 1. A resource management system in a communication system including a plurality of systems that do not have usage rights for a first frequency band,
A coexistence manager (CM) for managing the plurality of systems for coexistence and frequency sharing of the plurality of systems in the usable frequency band when a frequency band in which the plurality of systems are available in the first frequency band is found; );
A coexistence enabler (CE) for transmitting and receiving the information of the plurality of systems and information of the coexistence manager; And
And a coexistence discovery and information server (CDIS) supporting control of the coexistence manager for the plurality of systems;
Wherein the coexistence manager includes a plurality of coexistence managers corresponding to the plurality of systems, respectively;
Wherein the coexistence discovery and information server, the plurality of coexistence managers, and the coexistence enabler are configured to transmit and receive predetermined messages, respectively, to perform registration procedures, A coexistence information gathering procedure, a coexistence decision making procedure, a reconfiguration procedure, a measurement procedure, and an event procedure,
Wherein the coexistence manager sends a reconfiguration request message to the coexistence enabler and receives a reconfiguration response message from the coexistence enabler,
The reconfiguration request message includes:
Coexistence mode information having information indicating whether channels coexist, channel classification information indicating a classification type of the channel, and schedule information indicating information related to a data transmission schedule,
Wherein the reconfiguration response message comprises:
And information indicating whether reconfiguration has failed or not.
delete The method according to claim 1,
In the registration procedure, the coexistence discovery and the information server, the plurality of coexistence managers, and the coexistence enabler each transmit a registration request message and receive a registration response message in response to the registration request message, respectively The resource management system comprising:
The method of claim 3,
Wherein the plurality of coexistence managers,
A master coexistence manager and a slave coexistence manager,
Wherein the slave coexistence manager transmits the registration request message to the master coexistence manager and receives the registration response message from the master coexistence manager.
The method of claim 3,
Wherein any coexistence manager in the plurality of coexistence managers transmits the registration request message to a neighbor coexistence manager and receives the registration response message from the neighbor coexistence manager.
The method of claim 3,
After the registration procedure, in the deregistration procedure, the coexistence discovery and information server, the plurality of coexistence managers, and the coexistence enabler each send a deregistration request message, and the deregistration request And receives a registration release response message in response to the message.
The method according to claim 6,
Wherein the plurality of coexistence managers,
A master coexistence manager and a slave coexistence manager,
Wherein the slave coexistence manager transmits the registration cancellation request message to the master coexistence manager and receives the registration cancellation response message from the master coexistence manager.
The method according to claim 6,
Wherein any coexistence manager in the plurality of coexistence managers transmits the registration cancellation request message to a neighbor coexistence manager and receives the registration cancellation response message from the neighbor coexistence manager.
The method according to claim 1,
In the coexistence information collection procedure, the coexistence discovery and information server, the plurality of coexistence managers, and the coexistence enabler each transmit a coexistence information request message for requesting coexistence information, And receives a coexistence information response message including the coexistence information in response to the coexistence information response message.
10. The method of claim 9,
Wherein any coexistence manager in the plurality of coexistence managers transmits the coexistence information request message to a neighbor coexistence manager and receives the coexistence information response message from the neighbor coexistence manager.
11. The method of claim 10,
In the coexistence decision making procedure, the coexistence manager transmits the negotiation request message including negotiation inforamtion to the adjacent coexistence manager, and performs coexistence decision making based on the negotiation information and the coexistence information And receives a negotiation response message from the neighbor coexistence manager in response to the negotiation request message, and transmits a configuration indication message instructing the completion of the negotiation to the neighbor coexistence manager.
10. The method of claim 9,
Wherein the plurality of coexistence managers,
A master coexistence manager and a slave coexistence manager,
In the coexistence determination making procedure, the master coexistence manager transmits the coexistence information request message to the slave coexistence manager, receives the coexistence information response message from the slave coexistence manager, Transmits a command request message to the slave coexistence manager, and receives a command response message from the slave coexistence manager in response to the command request message.
10. The method of claim 9,
Wherein the coexistence information includes information on a coexistence mode, an operation channel selection, and a mutual channel sharing mechanism.
The method according to claim 1,
A TVWS DB (Data Base) (TVWS) for providing channel information of the usable frequency band;
In the coexistence decision making procedure, the coexistence enabler transmits a channel classification request message requesting the channel classification information to the TVWS database and the coexistence manager, respectively. In response to the channel classification request message, And receives a channel classification response message including classification information, and performs coexistence decision making based on operation channel selection in the channel classification information.
delete The method according to claim 1,
Wherein the plurality of coexistence managers and the coexistence enabler each transmit a management request message and receive a management response message in response to the management request message, respectively.
17. The method of claim 16,
Wherein any coexistence manager in the plurality of coexistence managers transmits the management request message to a neighbor coexistence manager and receives the management response message from the neighbor coexistence manager.
The method according to claim 1,
In the event procedure, an event indication message for instructing event detection is transmitted between the coexistence discovery and information server, the plurality of coexistence managers, and the coexistence enabler, and in response to the event indication message, And an acknowledgment message, respectively.
19. The method of claim 18,
Wherein any coexistence manager in the plurality of coexistence managers transmits the event indication message to a neighbor coexistence manager and receives the event approval message from the neighbor coexistence manager.
A method for managing resources of a first frequency band in a communication system including a plurality of systems that do not have usage rights for a first frequency band,
Wherein, when a frequency band in which the plurality of systems are usable in the first frequency band is found, in a registration procedure, for coexistence and frequency sharing of the plurality of systems in the usable frequency band, Transmitting and receiving a registration request message and a registration response message between a coexistence discovery and information server (CDIS), a plurality of coexistence managers (CM), and a coexistence enabler (CE)
In a coexistence information gathering procedure for coexistence and frequency sharing of the plurality of systems, a coexistence information request message is provided between the coexistence discovery and information server, the plurality of coexistence managers, and the coexistence enabler, Transmitting and receiving a coexistence information response message;
In order to coexist and frequency-share the plurality of systems, a coexistence decision making procedure transmits and receives a command request message and a command response message, and a negotiation request message and a negotiation response message between the coexistence managers in a coexistence decision making procedure The coexistence enabler transmitting and receiving a channel classification request message and a channel classification response message;
Transmitting and receiving a reconfiguration request message and a reconfiguration response message from the plurality of coexistence managers and the coexistence enabler in a reconfiguration procedure for coexistence and frequency sharing of the plurality of systems;
Transmitting and receiving a management request message and a management response message by the plurality of coexistence managers and the coexistence enabler in a measurement procedure for coexistence and frequency sharing of the plurality of systems; And
An event indication message and an event acceptance message are transmitted and received between the coexistence discovery and information server, the plurality of coexistence managers, and the coexisting enabler in an event procedure for coexistence and frequency sharing of the plurality of systems ; ≪ / RTI >
The reconfiguration request message includes:
Coexistence mode information having information indicating whether channels coexist, channel classification information indicating a classification type of the channel, and schedule information indicating information related to a data transmission schedule,
Wherein the reconfiguration response message comprises:
And information indicating whether reconfiguration has failed or not.

Images