WO2014185667A1 - Method for operating object in coexistence management system - Google Patents

Method for operating object in coexistence management system Download PDF

Info

Publication number
WO2014185667A1
WO2014185667A1 PCT/KR2014/004183 KR2014004183W WO2014185667A1 WO 2014185667 A1 WO2014185667 A1 WO 2014185667A1 KR 2014004183 W KR2014004183 W KR 2014004183W WO 2014185667 A1 WO2014185667 A1 WO 2014185667A1
Authority
WO
WIPO (PCT)
Prior art keywords
state
request
cdis
information
wso
Prior art date
Application number
PCT/KR2014/004183
Other languages
French (fr)
Korean (ko)
Inventor
강현덕
고광진
송명선
Original Assignee
한국전자통신연구원
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to KR20130053977 priority Critical
Priority to KR10-2013-0053977 priority
Priority to KR20140054253A priority patent/KR20140134606A/en
Priority to KR10-2014-0054253 priority
Application filed by 한국전자통신연구원 filed Critical 한국전자통신연구원
Priority claimed from US14/890,946 external-priority patent/US10039007B2/en
Publication of WO2014185667A1 publication Critical patent/WO2014185667A1/en

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W16/00Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/14Spectrum sharing arrangements between different networks

Abstract

The present invention relates to a method for operating individual devices in a coexistence management system for managing a plurality of frequency-sharing devices. To operate each of the objects (CE, CM, and CDIS), the status of an object status machine is defined to inactive, active, waiting engagement, engaged, request sent, and request received.

Description

How Objects Work in a Coexistence Management System

The present invention relates to a system for coexistence, and more particularly, to a method of operating individual entities in a system for managing a plurality of frequency sharing devices.

Coexistence technology allows wireless devices using different communication protocols to coexist without harmful interference at the core frequency (30MHz ~ 10Hz) where various dynamic spectrum access (DSA) technologies are expected to emerge. Spectrum management technology. DSA technologies, such as underlay and overlay, are contrary to current static spectrum management technology and use frequency by dynamically managing spectrum according to the surrounding radio environment of wireless devices. Wireless connection and management technology that maximizes flexibility and efficiency. In preparation for various frequency sharing technologies such as IEEE 802 and SCC 41, various technologies are being developed to derive mutual coexistence standards for comprehensive management of multiple sharing technologies in terms of spectrum management.

In Korea, research on integrated coexistence conditions of various sharing technologies has not been conducted systematically to secure optimal frequency efficiency among various WSOs in a crowded radio environment such as frequency auction system, sharing of licensed and unlicensed bands. have. IEEE 802.19, the International Organization for Standardization, is a wireless coexistence working group that addresses coexistence issues between 802 standards. Coexistence scenarios, coexistence analysis, and mutual coexistence between frequency-sharing wireless systems in licensed and unlicensed bands. Technical issues such as sharing mechanisms for coexistence are being discussed.

An object of the present invention is to propose an object operation method for avoiding interference and efficient resource management in an inter-existence management system for managing a plurality of frequency sharing devices.

In order to achieve the above object, according to an embodiment of the present invention, a coexistence enabler (CE), a coexistence manager (CM) and a coexistence identification and information server (Coexistence Discovery and Information Server) Provided are a method of operating a CM in an inter-existence management system including a CDIS. The method includes the CM transitioning to a Waiting Engagement state after sending a connection request to the CDIS or another CM in an active state; Switching to an interworking state when a connection response is received within a predetermined time in the standby state; Transitioning to a Request Received state upon receiving an information request from one of CE, CDIS, and another CM in the interoperation state; Transmitting the requested information to one of the CE, CDIS and another CM in response to the request in the request receiving state and returning to the interoperation state; Requesting information from one of CE, CDIS, and another CM in the interworking state and transitioning to a Request sent state; And returning to the interoperation state upon receiving the requested information from one of the CE, CDIS and another CM in the request transmission state.

In one embodiment, the method may further include returning to the active state if a connection response is not received within a predetermined time from the connection request transmission target CDIS or another CM in the interaction waiting state.

In one embodiment, the method sends a disconnect request to the CDIS or another CM in the interoperation state, receives a disconnect request from the CDIS or another CM, or maintains interoperability from a CE or other CM. Terminating a connection with the CDIS or another CM if it does not periodically receive a being engagement request; And switching to an active state when there is no CE provided with the mutual coexistence service by the CM.

In one embodiment, the method may further comprise transmitting the event information to the CE or another CM when an event designated by a CE or another CM occurs in the interoperation state.

In one embodiment, the method may further comprise receiving the event information from the CE or another CM when an event designated by the CM in the interoperation state occurs by a CE or another CM.

In one embodiment, the method wherein the information requested from one of the CE, CDIS and other CM in the interoperation state may be channel classification information or co-existence report.

In one embodiment, the method, the information requesting one of the CE, CDIS and other CM in the interworking state may be available channel list, channel classification information, measurement results or coexistence configuration information.

According to an embodiment of the present invention there is provided a method of operation of a CE in a coexistence management system including CE, CM and CDIS. The method includes the CE transitioning to a Waiting Engagement state after sending an access request to a CM in an active state; Transitioning to an interactive state when a connection response is received from the CM within a predetermined time in the interactive standby state; Transitioning to a Request Received state when receiving an information request from a WSO or CM associated with the interworking state; Transmitting the requested information to the WSO or CM in response to the request in the request reception state and returning to the interoperation state; Requesting information from a WSO or CM associated with the information in the interaction state and transitioning to a request sent state; And returning to the interoperation state upon receiving the requested information from the WSO or CM in the request transmission state.

In one embodiment, the method may further comprise returning to the active state if a connection response is not received within a predetermined time from the CM in the interoperation standby state.

In one embodiment, the method further comprises terminating the connection with the WSO or CM when sending a disconnect request to the WSO or CM in the interoperation state or when receiving a disconnect request from the CM; And converting to the active state.

In one embodiment, the method further comprises the CE maintaining the interworking state by periodically sending a being-engagement request to the CM. .

According to an embodiment of the present invention, a method of operating a CDIS in an inter-existence management system including a CE, a CM, and a CDIS is provided. The method includes the CDIS sending a connection response to the CM and transitioning to an interactive state upon receiving a connection request from the CM in an active state; Transitioning to a request receiving state when receiving information from the CM in the interactive state; Transmitting the requested information to the CM and returning to an interactive state; Requesting information from the CM in the interaction state and transitioning to a request transmission state; And returning to the interactive state when receiving the information requested by the CM from the CM.

In one embodiment, the method may further include maintaining the interaction state upon receiving a being-engagement request periodically from the CM in the interaction state.

In one embodiment, if the method receives a disconnect request from the CM in the interworking state, periodically does not receive an interaction request from the CM, or transmits a disconnect request to the CM, the method disconnects from the CM. Terminating; And converting to the active state.

Through the CM, CE, CDIS individual operation method of the mutual coexistence management system proposed in the present invention to facilitate the interference avoidance and resource management between a plurality of heterogeneous frequency sharing devices, thereby improving the frequency sharing efficiency between heterogeneous frequency sharing devices Makes it possible.

1 is a diagram illustrating a configuration of a mutual coexistence management system.

2 shows a state machine diagram defined for the operation of a CM in a coexistence management system in accordance with one embodiment of the present invention.

3 to 9 are flowcharts illustrating a CM operation in a mutual coexistence management system according to an embodiment of the present invention.

10 illustrates a state machine diagram defined for the operation of a CE in an inter-existence management system in accordance with an embodiment of the present invention.

11 to 13 are flowcharts illustrating a CE operation in a mutual coexistence management system according to an embodiment of the present invention.

Figure 14 shows a state machine diagram defined for the operation of CDIS in a coexistence management system in accordance with an embodiment of the present invention.

15 and 16 are flowcharts illustrating a CDIS operation in a mutual coexistence management system according to an embodiment of the present invention.

17 is a block diagram illustrating a structure of an entity for mutual coexistence management system according to an embodiment of the present invention.

The present invention may be variously modified and have various embodiments, and specific embodiments are illustrated in the drawings and described in detail with reference to the accompanying drawings. However, this is not intended to limit the present invention to specific embodiments, it should be understood to include all modifications, equivalents, and substitutes included in the spirit and scope of the present invention.

In describing the present invention, when it is determined that the detailed description of the related known technology may unnecessarily obscure the subject matter of the present invention, the detailed description thereof will be omitted.

Also, the singular forms used in the specification and claims are to be interpreted as generally meaning "one or more", unless stated otherwise.

1 is a diagram illustrating a configuration of a mutual coexistence management system.

As shown, the coexistence management system includes three entities: Coexistence Enabler ("CE") 110a, 110b, Coexistence Manager ("CM"), 120a, 120b. ) And a coexistence discovery and information server ("CDIS") 130, and a shared channel information DB 140. 1 shows two frequency sharing devices and two CEs and two CMs associated therewith, which is for convenience of description and is not limited to a configuration of a specific number of CEs and CMs. Do.

The CEs 110a and 110b exist in the frequency sharing devices 150a and 150b and serve as a passage between the frequency sharing devices 150a and 150b and the CMs 120a and 120b. The context information (e.g., wireless access method, transmission power, spectrum sensing threshold value, location, etc.) related to the corresponding frequency sharing device (or WSO (white space object) 150a, 150b) requested by the CM is determined by the WSO 150a, 150b. Is extracted from the CM 120a and 120b and is transmitted to the CM 120a and 120b, and the event information (eg, the change of the WSO's context information) requested from the CM 120a and 120b is transmitted. It serves to reflect the reset to the WSOs 150a and 150b.

The CMs 120a and 120b are entities that make important decisions related to frequency sharing, such as operating frequency allocation, transmission power allocation, transmission time allocation, and the like, to improve frequency sharing efficiency among the plurality of WSOs 150a and 150b. The CMs 120a and 120b may collect channel measurement information and the like through the WSOs 150a and 150b.

In addition, the CMs 120a and 120b may exchange information directly or exchange information through the CDIS 130 when cooperation with other CMs controlling other frequency sharing devices is required. The CMs 120a and 120b may discover neighbor WSOs for the WSOs 150a and 150b belonging to the CMs 120a and 120b.

The CMs 120a and 120b may obtain channel information available for the WSOs 150a and 150b from the channel information DB 140.

The CDIS 130 is an entity to assist in the decisions related to the control of the WSOs 150a and 150b of the CMs 120a and 120b. The CDIS 130 obtains and stores necessary information from the plurality of CMs 120a and 120b and transmits the information required by the CMs 120a and 120b connected thereto. The CDIS 130 may discover a neighbor frequency sharing device for the WSO belonging to each CM 120a and 120b. In addition, the CDIS 130 may obtain channel information available for the frequency sharing devices 150a and 150b from the channel information DB 140.

The shared channel information DB 140 is a DB that provides channel information available for frequency sharing devices.

In detail, the CMs 120a and 120b may provide two types of coexistence services, that is, a management service and an information service, to the WSOs 150a and 150b. The management service is a service that reflects the component reset of the WSOs 150a and 150b indicated by the CMs 120a and 120b to the WSOs 150a and 150b. An information service is a service that delivers information related to mutual coexistence to the WSOs 150a and 150b through the CEs 110a and 110b so that the WSOs 150a and 150b can make important decisions regarding frequency sharing on their own. do.

The CMs 120a and 120b may operate under three topologies: autonomous centralized and distributed. While autonomous topologies exchange information for multiple coexistence among multiple CMs, decisions related to coexistence are made by themselves without negotiation with other CMs or assistance from the master CM. The central topology is a case where a plurality of slave CMs are connected to one master CM. In this case, the slave CMs are controlled by the master CM to solve the coexistence problem of the WSOs 150a and 150b. On the other hand, the distributed topology solves the coexistence problem of the WSOs 150a and 150b through negotiation between the CM and neighboring CMs.

Discovery of neighboring frequency sharing devices that can cause co-channel interference between WSOs is very important for co-existence between WSOs. Discovery of such neighboring frequency sharing devices may be performed in the CMs 120a and 120b and / or the CDIS 130. First, the neighbor frequency sharing apparatus may be classified into the following two types.

Intra-CM WSO neighbor discovery between WSOs registered in the same CM

Inter-CM WSO neighbor discovery between WSOs registered to different CMs

The neighbor CM refers to a case of neighboring frequency sharing devices between frequency sharing devices registered in different CMs. Based on this, CDIS of the mutual coexistence management system provides the following two discovery services to the CM. The first is Inter-CM discovery service. In this case, the CM discovers an Intra-CM neighbor and the CDIS discovers an Inter-CM neighbor. Second is intra-CM and inter-CM discovery service. In this case, all neighbor discovery takes place only in the CDIS.

In one embodiment, to perform the aforementioned operations of each entity CE, CM, CDIS, the entity's state machine may be defined as follows.

Inactive: A state prior to initialization that prevents interface setup with other objects.

─ Active: Ready to set up interface with other objects

Waiting engagement: Waiting for a response from the partner after requesting an interface setup from the partner.

─ Engaged: A state where the interface setup with the counterpart is completed and messages can be exchanged with the counterpart.

Request sent: Sends a message related to the request to the counterpart and waits for a response from the counterpart.

Request received: Receives a message related to a request from a counterpart, and processes the request of the counterpart.

Hereinafter, the operation of each entity of the mutual coexistence management system, that is, CE, CM and CDIS, according to an embodiment of the present invention will be described with reference to FIGS. 2 to 17.

Figure 2 shows a state machine diagram defined for the operation of the CM in the mutual coexistence management system according to an embodiment of the present invention.

As shown, the state of the CM is Inactive (210), Active (220), Waiting engagement (230), Engaged (Interaction, 240), Request sent (250) and It may be defined as a Request received state.

The transition conditions between the states of the CM are as follows.

-The CM is converted to the active state 220 through the initialization process in the Inactive state 210

─ The CM sends a connection request from the Active state 220 to the CDIS / other CM and transitions to the Waiting engagement state 230.

─ The CM returns to the active state 220 when there is no connection response from the CDIS / other CM in the waiting engagement state 230 within a certain time.

─ The CM transitions to the Engaged state 240 when there is a connection response from the CDIS / other CM within the Waiting engagement 230 state within a certain time.

When the CM receives information from the CE / CDIS / other CM in the Engaged state 240, the CM transitions to the Request received state 260, sends the requested information to the CE / CDIS / other CM, and returns to the Engaged state 240.

When the CM has previously received an event request from the CE / other CM, the CM sends the corresponding event response to the CE / other CM in the Engaged state without receiving the event request from the CE / other CM.

If the CM previously sent an event request to the CE / other C, the CM receives the corresponding event response from the CE / other CM in the Engaged state 240 without sending the event request.

─ The CM requests information from the CE / CDIS / other CM in the Engaged state 240 and enters the Request sent state 250. When the CM receives the requested information from the CE / CDIS / other CM, the CM returns to the Engaged state 240.

The CM maintains the Engaged state 240 by periodically sending an Interaction Requisition to the CDIS / other CM in the Engaged state 240.

─ The CM transmits a disconnection request to the CDIS / other CM in the Engaged state 240, terminates the connection with the CDIS / other CM, and switches to the Active state 220.

If the CM receives a disconnect request from the CDIS / other CM in the Engaged state 240 or periodically receives an Interaction Request from the CE / other CM, the CM terminates the connection with the CDIS / other CM. And becomes active (220)

3 to 9 are flowcharts showing the operation of the CM in the mutual coexistence management system according to an embodiment of the present invention. Although the CM operation is shown sequentially in FIGS. 3 to 9, this is for convenience and it will be apparent to those skilled in the art that the operation is not necessarily performed in the order shown.

After the CM authentication is successfully completed in step S301, the CM performs the CM subscription procedure (S302) and enters the Engaged state, and incoming from the CE // CDIS / other CM. ) Check the message.

In one embodiment, after the CM generates and sends a SubscriptionRequest message to the CDIS, the CM may switch to the Engaged state upon receiving a SubscriptionResponse message from the CDIS. In this case, the subscription request message may include subscription service type information indicating whether a service to be subscribed to is an inter-CM inter-existence discovery service or an inter-CM and intra-CM inter-existence discovery service.

When the CM receives subscription information from the CE (S303), the CM sequentially performs the WSO subscription procedure and the WSO registration procedure (S304, S305), and switches to the Engaged state.

In one embodiment, when a SubscriptionRequest message is received from the CE, the CM may switch to the Engaged state after generating and sending a SubscriptionResponse message to the CE. In this case, the subscription request message may include subscription service type information.

In one embodiment, if a CERegistrationRequest message is received from the CE, the CM may transition to the Engaged state after generating and sending a RegistrationResponse message to the CE. At this time, the CE registration request message includes the network identifier of the WSO, the wireless radio access technology information used by the WSO, the network type, discovery information of the WSO, information indicating whether the planned transmission is supported, available channel information, a list of supported channel numbers, and the WSO operation It may include at least one of a channel number list, required resource information required for WSO operation, and measurement capability information of the WSO.

In addition, the CM generates a CMRegistrationRequest message and sends it to the CDIS, and waits for a RegistrationResponse message from the CDIS.

When the CM receives an event indication from the CE (S306), the CM performs a sending event indication from CE to CM procedure (S307) and enters the Engaged state. . In one embodiment, upon receiving an EventIndication message from the CE, the CM may enter an Engaged state after generating and sending an EventConfirm message to the CE in response.

When the CM receives an event notification request from another CM (S308), the CM performs a sending event indication from CM to another CM procedure (S309) and is switched to the Engaged state. In one embodiment, the CM may generate an EventIndication message and transmit it to another CM, and then, when the EventConfirm message is received from the other CM, may be switched to the Engaged state. In one embodiment, the event included in the event notification message may include an event indicator (eg, an indicator indicating SINR threshold or QoS degradation).

If the CM needs an available channel list from the WSO (S310), the CM performs an obtaining available channel list from WSO procedure (S311), and enters the Engaged state. Is switched. In one embodiment, the CM generates an AvailableChannelsRequest message requesting the Available Channels list and sends it to the CE, and after receiving the AvailableChannelsResponse message from the CE, it is switched to the Engaged state. Can be.

When the CM receives a channel classification request from the CE (S312), the CM performs an obtaining channel classification information by CE procedure (S313) and enters the Engaged state. Is switched.

In one embodiment, upon receiving a ChannelClassificationRequest message requesting channel classification information from the CE, the CM generates and sends a ChannelClassificationResponse message including the channel classification information to the CE in response thereto. Can be switched to Engaged state

When the channel classification information of the WSO is updated (S314), the CM performs an announcecing channel classification information update to CE procedure to provide the channel classification update information to the WSO (S315), and Engaged. The state is switched. In one embodiment, the CM may be converted to an Engaged state after generating and transmitting a ChannelClassificationAnnouncement message including the updated channel classification information to the CE.

If the channel classification information of the CM is updated (S316), the CM performs an announce channel classification information update to CM procedure to provide the updated channel classification information to another CM (S317). , The state transitions to Engaged. In one embodiment, the CM may be converted to an Engaged state after generating and transmitting a ChannelClassificationAnnouncement message including updated channel information to another CM.

If the CM needs channel classification information of another CM (S318), the CM performs an obtaining channel classification information by CM procedure (CM319) by the CM (S319), and enters the Engaged state. In one embodiment, the CM generates a CMChannelClassificationRequest message and sends it to another CM, and in response, receives the CMChannelClassificationResponse message from the other CM and then transitions to the Engaged state. Can be. In one embodiment, the CM channel classification response message may include a network identifier and channel classification information of the other CM. In addition, the CM needs information of another CM (eg, SINR, required bandwidth, required QoS, interface level, fairness index, fairness threshold, subscribed service, etc.). In this case, the information acquisition procedure may be switched to the Engaged state after requesting information from another CM and receiving a response message thereto.

If the CM needs the measurement result of the WSO (S320), the CM performs a requesting measurement procedure (S321) to request measurement from the WSO, and is switched to the Engaged state. In one embodiment, the CM may transition to the Engaged state after generating and sending a MeasurementRequest message to the CE, after receiving a MeasurementConfirm message from the CE.

It is determined whether the CM has received the measurement result from the WSO requesting a one-time measurement (S323), and if so, the CM performs an one-time measurement procedure (obtaining one-time measurement procedure) (S324). , The state transitions to Engaged. On the other hand, if the CM receives the measurement results from the WSO requesting the scheduled measurement (scheduled measurement), the CM performs the scheduled measurement measurement procedure (obtaining scheduled measurement procedure) (S323), and is switched to the Engaged state.

If the CM needs information from another CM (S325), it performs an information acquisition procedure from another CM (S326).

It is determined whether the CM is subscribed to both the inter-CM coexistence discovery and the intra-CM coexistence discovery service in the CDIS (S327). If not, the CM performs coexistence discovery in the intra-CM domain (S328), and then performs obtaining coexistence set information (S329). On the other hand, if the CM is subscribed to the service for inter-CM and intra-CM co-existence discovery in the CDIS, the CM may perform the procedure for acquiring co-existence setting information without performing intra-CM co-existence discovery by itself.

In one embodiment, when picked coexistence configuration information procedure after the CM is to generate a coexistence configuration information request message (CoexistenceSetInformationRequest message) sent to CDIS, for receiving a coexistence configuration information reply message (CoexistnceSetInformationResponse message) from the CDIS Process may be included. At this time, the mutual coexistence setting information request message may include a list of network identifiers of the WSO for which the coexistence setting information is requested, and the response message may include neighbor CM information.

As a result of determining whether the WSO is subscribed to the information service (S330), if the subscriber is subscribed to the information service and the CM receives a coexistence report request from the CE (S331), the CM acquires the coexistence report. The procedure (obtaining coexistence report procedure) is performed (S332), and the state is switched to the Engaged state. In one embodiment, if the CE is sent to the CM generates the coexistence report request message (CoexistenceReportRequest message), CM is switched to Engaged state after sending the CE to generate a coexistence report response message (CoexistenceReportResponse message) in response thereto Can be. The coexistence report response message may include information on the coexistence configuration element of the WSO (neighbor network identifier, neighbor network description, neighbor operating channel number) and channel priority information.

When the CM receives the updated registration information from the CE (S333), the CM performs a WSO registration update procedure (S334), and switches to the Engaged state.

When the CM receives the WSO subscription renewal request from the CE (S335), the CM performs the WSO subscription renewal procedure (S336), and is switched to the Engaged state.

If the CM determines that a subscription change of the WSO is necessary (S337), the CM performs a WSO subscription change procedure (S338), and the state is switched to the Engaged state.

When the CM receives a deregistration request from the CE (S339), the CM performs the WSO registration update procedure (S340), and is switched to the Engaged state.

If the CM determines that a subscription change for the discovery service type provided by the CDIS is necessary (S341), the CM performs a CM subscription update procedure (S342), and is switched to the Engaged state.

When the CM receives new subscription information from the new CE (S343), the CM sequentially performs the WSO subscription procedure and the WSO registration procedure (S304, S305), and switches to the Engaged state.

If it is determined that no CE is provided with the mutual coexistence service from the CM (S344), it is switched to the active state.

On the other hand, if it is determined in step S330 that the subscription service of the WSO is a management service, the CM determines autonomous coexistence decision making, centralized coexistence decision making and distributed coexistence decision. It can be implemented by selecting one of the (distributed coexistence decision making).

If the CM makes an autonomous coexistence decision, it makes the decision independent of the neighboring CM.

If the CM makes a central coexistence decision, the master CM makes the decision about itself and the slave CM.

If the CM implements a distributed coexistence decision, the CM makes the decision through negotiations with neighboring CMs.

When the CM performs the central coexistence determination (ie, if it is determined that the master CM / slave CM is necessary) (S345), the CM performs a master / slave CM selection procedure (S346). In one embodiment, the master / slave CM selection procedure informs the CM that it wants to be a slave CM of another CM that receives the message by generating and sending a MasterCMRequest message to another CM. Wait for the MasterCMResponse message from the CM.

The success of the master / slave CM selection procedure is determined (S347), and if successful, the CM performs a master / slave CM configuration procedure (S348).

In one embodiment, a MasterSlaveCMConfigurationRequest message is generated and sent to the slave CM and transitioned to a Request sent state. In response to this, if a MasterSlaveCMConfigurationResponse message is received from the slave CM, the master slave CM configuration response message may be returned to the Engaged state. In one embodiment, the master slave CM configuration request message may include a list of CEs managed by the master CM, and the master slave CM configuration response message may include information on each of the CEs registered in the slave CM.

In one embodiment, it is determined whether the CM is selected as the master CM (S349). If it is selected as the master, and performs coexistence determination for the WSO of the slave CM and its registered WSOs (S351). Master CM may be sent to CM reconfiguration request (CMreconfigurationRequest) message, and switch to the request sent to the slave state CM (S352). In response, after receiving a CMreconfigurationResponse message from the slave CM, it may return to the Engaged state. In this case, the CM reconfiguration response message may include at least one of a CE to be reconfigured, an operation channel list of the WSO, a transmission power limit value, a flag indicating whether to share a frequency, a transmission schedule, and channel classification information for each CE registered in the CM. Can be.

The CM transitions to the Engaged state after performing the WSO reconfiguration procedure (S361, S362) until the mutual coexistence determination for registered WSOs is completed.

Meanwhile, if the corresponding CM is selected as the slave CM, it is determined whether a CM reconfiguration request is received from the master CM (S350), and in such a case, the state is switched to the request received state. Upon receiving the CM reconfiguration request, the slave CM generates a CM reconfiguration response message and responds to the master CM.

The CM performs the co-existence decision on the registered WSOs (S361), and after performing the WSO reconfiguration procedure (S362), is switched to the Engaged state.

In one embodiment, after the CM generates and sends a ReconfigurationRequest message to the CE, the CM may transition to the Engaged state when a ReconfigurationResponse message is received from the CE. In one embodiment, the reconfiguration request message may include a WSO operation channel list, a transmission power limit, whether to share a channel, a transmission schedule, and channel classification information.

On the other hand, if a central coexistence decision is not implemented or if a master / slave CM selection procedure fails, i.e., if a master CM and a slave CM are not specified, the CM can choose either a distributed coexistence decision or an autonomous coexistence decision. Determine whether to implement (S354, S355).

If the CM enforces distributed mutual decision (that is, negotiation between the CMs is necessary), the CM performs a negotiation procedure between the CMs (S356).

After determining whether the negotiation is successful (S357), and if the negotiation is successful, after executing the mutual coexistence decision for the registered WSOs (S360), and performing the WSO reconfiguration procedure (S361), Engaged state Is switched to. However, if the negotiation fails, it is determined whether to select the master / slave CM again (S358), and if not, an autonomous mutual coexistence decision is performed (S359). Next, after performing the co-existence determination for the registered WSOs (S360, S361), and after performing the WSO reconfiguration procedure (S362), it is switched to the Engaged state.

When the CM receives a reconfiguration failure response from the registered WSO (S363), the CM performs a WSO deregistration procedure (S364), and switches to the Engaged state.

Figure 10 shows a state machine diagram defined for the operation of the CE in an inter-existence management system in accordance with an embodiment of the present invention.

As shown, the state for the operation of the CE may be defined as Inactive (410), Active (420), Waiting engagement (430), Engaged (440), Request received (450) and Request sent (460), The transition condition between states is as follows.

─ The CE transitions from the Inactive state 410 to the Active state 420 through an initialization process.

The CE sends an access request from the active state 420 to the CM and transitions to the waiting engagement state 430

─ The CE returns to the active state 420 when there is no connection response within a certain time from the CM in the waiting engagement state 430.

─ The CE transitions to the Engaged state 440 when there is a connection response within a certain time from the CM in the Waiting engagement state 430.

When the CE receives information from the WSO / CM in the Engaged state (440), the CE transitions to the Request received state (450), sends the requested information to the WSO / CM, and returns to the Engaged state (440).

─ Even if there is no request from the CM in Engaged state 440, the CE transmits the event information to the CM when a specific event specified by the CM occurs in advance.

The CE receives the event information from the WSO when a specific event specified by the CE has occurred, even though the CE has not previously requested the WSO in the Engaged state (440).

The CE requests information from the WSO / CM in the Engaged state 440 and transitions to the Request sent state 460, and returns to the Engaged state 440 after receiving the requested information from the WSO / CM.

The CE maintains the Engaged state 440 by periodically sending a being-engagement request to the CM in the Engaged state 440.

The CE sends a disconnect request to the WSO / CM in the Engaged state (440), terminates the connection with the WSO / CM, and switches to the Active state (420).

When the CE receives the disconnect request from the CM in the Engaged state 44, the CE terminates the connection with the CM and enters the Active state 420.

11 to 13 are flowcharts illustrating the operation of the CE entity in the mutual coexistence management system according to an embodiment of the present invention. Although the CE operation is shown sequentially in FIGS. 11-13, this is for convenience and it is obvious to those skilled in the art that it is not necessarily performed in the order shown.

It is determined whether the WSO authentication is successfully completed (S501), and if so, the CE performs the WSO subscription procedure and registration procedure sequentially (S502, S503), enters the Engaged state, and the incoming message from the CM (incoming) messages) and whether or not to receive primitives from WSO.

In one embodiment, the CE creates and sends a GetServiceSubscriptionRequest primitive to the WSO to subscribe the WSO to the coexistence service, and then waits for a GetServiceSubscriptionResponse primitive from the WSO. After receiving the service subscription response primitive from the WSO, the CE generates and sends a SubscriptionRequest message to the CM and waits for a SubscriptionResponse message from the CM.

When the CE receives an event indication from the WSO (S504), the CE performs a sending event indication from CE to CM procedure (S505) and enters the Engaged state. .

In one embodiment, the CE creates a GetRegInfoRequest primitive for the WSO and sends it to the WSO to register the WSO with the CM, then waits for a GetRegInfoResponse primitive from the WSO. When a registration response response primitive ( GetRegInfoResponse primitive) is received from the WSO, the CE generates a CE registration request message and sends it to the CM, and waits for a RegistrationResponse message from the CM. After receiving the registration response message from the CM, the CE creates a GetRegInfoConfirm primitive and sends it to the WSO.

It is determined whether the WSO is subscribed to the information service and the management service provided by the CM (S506), and if it is subscribed to the information service, it is determined whether the CE has received a mutual coexistence report request from the WSO (S507). If so, the CE performs the co-existence report acquisition procedure (S508), and enters the Engaged state.

In one embodiment, the CE transitions to the Request Received state when a CoexistenceReportRequest primitive is received from the WSO. In response, CE is a coexistence report request message (CoexistenceReportRequest message) the generated and sent to the CM, coexistence report response message when receiving the (CoexistenceReportResponse message) coexist report response based on the coexistence report response message from the CM A primitive ( CoexistenceReportResponse primitive) is created and sent to the WSO and returned to the Engaged state.

On the other hand, when the WSO is subscribed to the management service, it is determined whether the CE has received the reconfiguration request from the CM (S509), and if so, the CE performs the WSO reconfiguration procedure (S510), and is switched to the Engaged state.

In one embodiment, when the CE receives the reconfiguration request message from the CM, it transitions to the request receiving state. The CE generates a PerformReconfigurationRequest primitive and sends it to the WSO, and waits for a PerformReconfigurationResponse primitive from the WSO. When the Reconfiguration Execution Response primitive is received from the WSO, the CE may generate a ReconfigurationResponse message and send it to the CM, and then switch to the Engaged state.

When the CE receives the deregistration request from the CM (S511), the CE performs a WSO deregistration procedure (S512), and finds a new CM to be provided with the coexistence service. After confirming the new CM, the CE sequentially performs the WSO subscription and registration procedure (S502, S503), and transitions to the Engaged state.

When the CE receives the update registration information from the WSO (S513), the CE performs the WSO registration update procedure (S514), and enters the Engaged state.

When the CE receives the channel classification information request from the WSO (S515), the CE performs an obtaining channel classification information by CE procedure (S516), and is switched to the Engaged state.

In one embodiment, when the CE receives a ChannelClassificationRequest primitive from the WSO, it generates and sends a ChannelClassificationRequest message to the CM and waits for a ChannelClassificationResponse message from the CM. After receiving the channel classification response message from the CM, the CE creates a ChannelClassification Response primitive and sends it to the WSO. In this case, the channel classification response primitive may include channel classification information.

When the CE receives the update channel classification information of the WSO (S517), the CE performs an announce- ing channel classification information update to CE procedure (S518), and enters the Engaged state.

When the CE receives an available channel list request from the CM (S519), the CE performs an available channel list acquisition procedure from the WSO (S520), and is switched to the Engaged state. In one embodiment, after the CE receives an Available Channel Request message from the CM, the CE creates an AvailableChannelListRequest primitive and sends it to the WSO, and sends an AvailableChannelListResponse primitive from the WSO. waiting. At this time, the available channel list response primitive includes the available channel list of the WSO. When the CE receives an Available Channel List Response primitive from the WSO, it generates an Available Channel Response message and sends it to the CM. Can be switched to Engaged state.

When the CE receives a measurement request from the CM (S521), the CE performs a requesting measurement procedure (S522) and is switched to the Engaged state.

The CE determines whether the CM has received the measurement result from the WSO requesting the one-time measurement (S523), and if so, the CE performs the one-time measurement result acquisition procedure (S525) and is switched to the Engaged state. . On the other hand, if the CE receives a measurement result from the WSO that the CM requested a scheduled measurement, the CE performs an obstructing scheduled measurement procedure (S524), and is switched to the Engaged state. .

When the CE receives a subscription update request from the WSO (S526), the CE performs a WSO subscription update procedure (S527), and enters the Engaged state.

When the CE receives a subscription change request from the CM (S528), the CE performs a WSO subscription change procedure (S529), and transitions to the Engaged state.

When the CE receives a deregistration request from the WSO (S530), the CE performs a WSO registration update procedure (S531), and then switches to the active state.

14 shows a state machine diagram defined for the operation of a CDIS entity in an inter-existence management system in accordance with one embodiment of the present invention.

As shown, the state for the operation of the CDIS may be defined as Inactive (610), Active (620), Engagement (630), Request received (640) and Request sent (650), the transition between each state (transition ) The conditions are as follows.

In the CDIS Inactive state 610, the process transitions to the Active state 620 through an initialization process.

─ When the CDIS receives the connection request from the CM in the active state 620, the CDIS transmits the connection response to the CM and transitions to the Engaged state 630.

─ When the CDIS receives information from the CM in the Engaged state (630), the CDIS transitions to the requested received state (640), transmits the requested information to the CM, and returns to the Engaged state (630).

─ Even if there is no request from the CM in the Engaged state (630), the CDIS sends the event information to the CM when a specific event specified by the CM occurs in advance.

─ CDIS receives the event information from the CM when a specific event specified by CDIS occurs, even if the request is not made to the CM in the Engaged state (630).

─ CDIS requests information from the CM in the Engaged state (630) and transitions to the request sent state (650), and returns to the Engaged state (630) upon receiving the requested information from the CM.

CDIS maintains the Engaged state (630) when it periodically receives a being-engagement request from the CM in the Engaged state (630).

─ If the CDIS receives the disconnect request from the CM in the Engaged state 630 or periodically does not receive the interaction request from the CM, the CDIS terminates the connection with the CM and switches to the Active state 620.

─ After the CDIS sends the disconnect request to the CM in the Engaged state (630), the CDIS terminates the connection with the CM and becomes Active (620).

15 and 16 are flowcharts illustrating CDIS entity operations in a mutual coexistence management system according to an embodiment of the present invention. Although the CDIS operation is shown sequentially in FIGS. 15 and 16, this is for convenience and it will be apparent to those skilled in the art that the operation is not necessarily performed in the order shown.

After successful CM authentication, the CDIS is switched to the Engaged state and checks for incoming messages from the CM.

When the CDIS receives the subscription request from the CM (S701), the CDIS performs a CM subscription procedure (S702), and is switched to the Engaged state.

When the CDIS receives a registration request from the CM (S703), the CDIS performs a WSO registration procedure (S704), and enters the Engaged state.

After WSO registration, it is determined whether the CM is subscribed only to the inter-CM coexistence discovery service in the CDIS (S705), and if so, the CDIS performs coexistence discovery in the inter-CM domain (S707). On the other hand, if the CM is subscribed to the inter-CM and intra-CM co-existence discovery service in the CDIS, the CDIS performs co-existence discovery in both the inter-CM and intra-CM domains.

When the CDIS receives the update registration information from the CM (S708), the CDIS performs the WSO registration update procedure (S709), and enters the Engaged state. After updating the WSO registration, the CDIS performs coexistence discovery according to the type of discovery service to which the CM subscribes to the CDIS.

When the CDIS receives the subscription request from the new CM (S710), the CDIS performs the CM subscription procedure (S702), and enters the Engaged state.

When the CDIS receives the coexistence set information request from the CM (S711), the CDIS obtains the coexistence coexistence setting information obtaining procedure according to the type of discovery service that the CM subscribes to the CDIS (obtaining coexistence). set information procedure) (S712), and is switched to the Engaged state.

In one embodiment, upon receiving the CoexistenceSetInformationRequest message from the CM, and transitions to the request occasional state. After the CDIS generates and transmits a CoexistenceSetInformationResponse message to the CM, the CDIS may be converted into an Engaged state. At this time, the mutual coexistence setting information response message may include a neighbor CM list.

When the CDIS receives a subscription change request for changing the type of the existing discovery service from the CM (S713), the CDIS performs a CM subscription update procedure (S714), and is switched to the Engaged state.

If no CM is provided with discovery service by the CDIS (S715), it is switched to the active state.

17 is a block diagram illustrating a structure of an entity for mutual coexistence management system according to an embodiment of the present invention. As illustrated in FIG. 17, each entity of the mutual coexistence management system, that is, CE, CM, and CDIS, may be one or more processors 810, a memory 820, and a storage unit 830, similar to a general computer system structure. , A user interface input unit 840, a user interface output unit 850, and a wireless transmitter / receiver 860 may include at least one or more elements, which may communicate with each other via a bus 870.

The processor 810 may be a CPU or a semiconductor device that executes processing instructions stored in the memory 820 and / or the storage 830. The memory 820 and the storage unit 830 may include various types of volatile / nonvolatile storage media. For example, the memory may include a ROM 824 and a RAM 825.

The object operating method according to the embodiment of the present invention described above is implemented in the form of computer executable instructions and stored in the memory 820 and / or storage 830, when the instructions are executed by a processor at least one of the present invention The object operation method according to the embodiment may be performed.

In addition, the apparatus and method according to the embodiment of the present invention may be implemented in the form of program instructions that can be executed by various computer means and recorded in a computer readable medium. Computer-readable media may include, alone or in combination with the program instructions, data files, data structures, and the like.

The program instructions recorded on the computer readable medium may be those specially designed and constructed for the present invention, or may be known and available to those skilled in the computer software arts. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tape, optical media such as CD-ROMs, DVDs, and magnetic disks, such as floppy disks. Hardware devices specially configured to store and execute program instructions such as magneto-optical media and ROM, RAM, flash memory and the like. In addition, the above-described medium may be a transmission medium such as an optical or metal wire, a waveguide, or the like including a carrier wave for transmitting a signal specifying a program command, a data structure, and the like. Examples of program instructions include not only machine code generated by a compiler, but also high-level language code that can be executed by a computer using an interpreter or the like.

So far, the present invention has been described with reference to the embodiments. Those skilled in the art will appreciate that the present invention can be implemented in a modified form without departing from the essential features of the present invention. Therefore, the disclosed embodiments should be considered in descriptive sense only and not for purposes of limitation. The scope of the present invention is shown in the claims rather than the foregoing description, and all differences within the scope will be construed as being included in the present invention.

Claims (20)

  1. The operation of CM in a coexistence management system including a coexistence enabler (CE), a coexistence manager (CM), and a coexistence discovery and information server (CDIS). In the method, the CM,
    Transitioning to a Waiting Engagement state after transmitting a connection request to the CDIS or another CM in an active state;
    Transitioning to an engaged state when a connection response is received within a predetermined time in the standby state;
    Transitioning to a Request Received state upon receiving an information request from one of CE, CDIS, and another CM in the interoperation state;
    Transmitting the requested information to one of the CE, CDIS and another CM in response to the request in the request receiving state and returning to the interoperation state;
    Requesting information from one of CE, CDIS, and another CM in the interworking state and transitioning to a Request sent state; And
    Returning to the interoperation state upon receiving the requested information from one of the CE, CDIS and another CM in the request transmission state.
    CM operation method in a mutual coexistence management system comprising a.
  2. The CM operation of the mutual coexistence management system according to claim 1, further comprising the step of returning to the active state if a connection response is not received within a predetermined time from the connection request transmission target CDIS or another CM in the interoperation waiting state. Way.
  3. The method of claim 1, wherein the CM sends a disconnect request to the CDIS or another CM in the interoperation state, receives a disconnect request from a CDIS or another CM, or interoperates from a CE or another CM. Terminating a connection with the CDIS or another CM if it does not periodically receive a being engagement request; And
    Transitioning to an active state when there is no CE provided with the coexistence service by the CM;
    CM operation method in a mutual coexistence management system further comprising.
  4. The method of claim 1, further comprising transmitting the event information to the CE or another CM when an event previously requested by a CE or another CM occurs in the interworking state. .
  5. The CM of the mutual coexistence management system according to claim 1, further comprising receiving the event information from the CE or another CM when an event previously requested by the CM in the interworking state occurs in a CE or another CM. How it works.
  6. The method of claim 1, wherein the information requested from one of the CE, the CDIS, and the other CM in the interworking state is channel classification information or a coexistence report.
  7. The method of claim 1, wherein the information requested to one of the CE, the CDIS, and the other CM in the interoperation state is available channel list, channel classification information, measurement result, or coexistence setting information.
  8. The method of claim 1, wherein the requesting information from one of the CE, the CDIS, and the other CM in the interworking state and transitioning to the Request sent state is performed by reconfiguring the CM to the slave CM when the CM is selected as the master CM. Sending a request message and transitioning to the request sending state,
    Receiving the requested information to one of the CE, CDIS and another CM in response to the request in the request transmission state and returning to the interworking state may be achieved when the CM reconfiguration response message is received from the slave CM. CM operation method of a coexistence management system comprising the step of returning to.
  9. The method of claim 1, wherein the receiving of the request for information from one of the CE, the CDIS, and the other CM in the interworking state switches to the Request Received state when the CM is selected as the slave CM. Receiving a CM reconfiguration request message and transitioning to the request receiving state,
    In response to the request in the request receiving state, transmitting the requested information to one of the CE, CDIS, and other CM and returning to the interoperation state, the slave CM generates a CM reconfiguration response message to the master CM. And returning to the interoperation state after transmitting to the CM.
  10. A method of operating a CE in a coexistence management system including a CE, a CM, and a CDIS, wherein the method comprises:
    Transitioning to a Waiting Engagement state after transmitting a connection request to the CM in an active state;
    Transitioning to an interactive state when a connection response is received from the CM within a predetermined time in the interactive standby state;
    Transitioning to a Request Received state when receiving an information request from a WSO or CM associated with the interworking state;
    Transmitting the requested information to the WSO or CM in response to the request in the request receiving state and returning to the Engaged state;
    Requesting information from a WSO or CM associated with the information in the interaction state and transitioning to a request sent state; And
    Returning to the interoperation state upon receiving the requested information from the WSO or CM in the request transmission state.
    CE operation method in a coexistence management system comprising a.
  11. 11. The method of claim 10, further comprising the step of returning to the active state if the connection response is not received within the predetermined time from the CM in the interoperation waiting state.
  12. 11. The method of claim 10, further comprising: terminating a connection with the WSO or CM when transmitting a disconnect request to the WSO or CM in the interoperation state or receiving a disconnect request from the CM; And
    Switching to the active state
    CE operation method in a coexistence management system further comprising.
  13. 11. The method of claim 10 further comprising the CE maintaining the interworking state by periodically sending a being-engagement request to the CM.
  14. The method of claim 10, wherein the transition from the WSO to the Request Received state upon receiving an information request from the WSO or CM associated with the interworking state comprises receiving a CoexistenceReportRequest primitive from the WSO. Transitioning to the request reception state;
    In the request receiving state, in response to the request, transmitting the requested information to the WSO or CM and returning to the interacted state, the CE generates a coexistence report request message ( CoexistenceReportRequest message). after the transmission and in response to coexist report response message (CoexistenceReportResponse message) is received from the CM to the interaction after generates the coexistence report response primitive (CoexistenceReportResponse primitive), based on the coexistence report response message transmitted to the WSO Return to status
    CE operation method in a coexistence management system comprising a.
  15. 11. The method of claim 10, wherein when the information request is received from the WSO or CM associated with the interworking state, the transitioning to the Request Received state comprises: receiving a reconfiguration request from the CM and transitioning to the request receiving state. Including,
    In the request receiving state, in response to the request, transmitting the requested information to the WSO or CM and returning to the interacted state, the CE generates a PerformReconfigurationRequest primitive to generate the self. sent to the WSO associated to and returning to the interaction state after when the reconfiguration performed response primitive (PerformReconfigurationResponse primitive) is received from the WSO to generate a reconstructed response message (ReconfigurationResponse message) on the basis of the reconfiguration performed response primitive transmitted to the CM CE operation method in a coexistence management system comprising the steps.
  16. In the method of operating CDIS in a mutual coexistence management system including CE, CM and CDIS, the method, the CDIS,
    In response to receiving a connection request from the CM in an active state, sending a connection response to the CM and transitioning to an interactive state;
    Transitioning to a request receiving state when receiving information from the CM in the interactive state;
    Transmitting the requested information to the CM in the request reception state and returning to an interoperation state;
    Requesting information from the CM in the interaction state and transitioning to a request transmission state; And
    Returning to the interoperation state when receiving the information requested by the CM from the request transmission state.
    CDIS operation method in a coexistence management system comprising a.
  17. 17. The method of claim 16, further comprising maintaining the interaction state upon receiving a being-engagement request periodically from the CM in the interaction state. .
  18. 17. The method of claim 16, wherein the connection with the CM is terminated when the connection request is received from the CM in the interworking state, the periodic request for interaction is not received from the CM, or the connection request is transmitted to the CM. step; And
    Switching to the active state
    CDIS operation method in a coexistence management system further comprising.
  19. 17. The method of claim 16, wherein when the information is requested from the CM in the interworking state, the step of switching to the request receiving state comprises receiving a CoexistenceSetInformationRequest message from the CM and switching to the request receiving state. And transmitting the requested information to the CM in the request reception state and returning to the interoperation state by generating a CoexistenceSetInformationResponse message and transmitting it to the CM and returning to the interoperation state. CDIS operating method in a mutual coexistence management system comprising the step of.
  20. 17. The method of claim 16, wherein the method further comprises transitioning to an active state when no CM is provided with discovery service by the CDIS.
PCT/KR2014/004183 2013-05-13 2014-05-09 Method for operating object in coexistence management system WO2014185667A1 (en)

Priority Applications (4)

Application Number Priority Date Filing Date Title
KR20130053977 2013-05-13
KR10-2013-0053977 2013-05-13
KR20140054253A KR20140134606A (en) 2013-05-13 2014-05-07 Method of operating entities in Coexistence management system
KR10-2014-0054253 2014-05-07

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US14/890,946 US10039007B2 (en) 2013-05-13 2014-05-09 Method of operating entities in coexistence management system

Publications (1)

Publication Number Publication Date
WO2014185667A1 true WO2014185667A1 (en) 2014-11-20

Family

ID=51898598

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2014/004183 WO2014185667A1 (en) 2013-05-13 2014-05-09 Method for operating object in coexistence management system

Country Status (1)

Country Link
WO (1) WO2014185667A1 (en)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20080010907A (en) * 2006-07-28 2008-01-31 엘지전자 주식회사 Apparatus and method of allocating radio resource dynamically
KR20080076262A (en) * 2007-02-15 2008-08-20 삼성전자주식회사 Method and system for allocating resource in a communication system
KR20100041235A (en) * 2008-10-13 2010-04-22 삼성전자주식회사 A method for allocation channel in a wireless communication network and system thereof
WO2012030190A2 (en) * 2010-09-03 2012-03-08 한국전자통신연구원 System and method for managing resources in a communication system
WO2012057584A2 (en) * 2010-10-31 2012-05-03 엘지전자 주식회사 Method for acquiring information in a coexistence system, and apparatus using same

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20080010907A (en) * 2006-07-28 2008-01-31 엘지전자 주식회사 Apparatus and method of allocating radio resource dynamically
KR20080076262A (en) * 2007-02-15 2008-08-20 삼성전자주식회사 Method and system for allocating resource in a communication system
KR20100041235A (en) * 2008-10-13 2010-04-22 삼성전자주식회사 A method for allocation channel in a wireless communication network and system thereof
WO2012030190A2 (en) * 2010-09-03 2012-03-08 한국전자통신연구원 System and method for managing resources in a communication system
WO2012057584A2 (en) * 2010-10-31 2012-05-03 엘지전자 주식회사 Method for acquiring information in a coexistence system, and apparatus using same

Similar Documents

Publication Publication Date Title
JP6142465B2 (en) Wireless communication apparatus, wireless communication system, method, and computer program
JP4099149B2 (en) access point
KR20140058472A (en) Radiation imaging system, method for controlling a radiation imaging system, and computer-readable storage medium
JP4899643B2 (en) Network component
KR100516794B1 (en) Agent system
WO2013025085A2 (en) Apparatus and method for supporting family cloud in cloud computing system
WO2017176022A1 (en) Method and apparatus for managing beam in beamforming system
KR100501323B1 (en) Method and Apparatus for the realization of mobility by using WLAN Voice terminal at the ISDN switching system
JP4211529B2 (en) Channel selection method and radio station and program used therefor
EP2909919A1 (en) Wireless power receiver and method for setting sleep mode in wireless power receiver
CN102395170B (en) Systems and methods for handoff in wireless network
JP5821390B2 (en) Wireless communication apparatus, wireless communication program, and wireless communication method
WO2010044580A2 (en) Channel allocation method and apparatus for wireless communication networks
JP5945910B2 (en) Wireless communication device
WO2016043502A1 (en) Channel accessing method and device in wireless communication system
US20090147768A1 (en) Synchronizing wireless local area network access points
WO2014200240A1 (en) Method and apparatus for registering wireless device in wireless communication system
JP5887969B2 (en) Wireless communication equipment
JP2009049485A (en) Mobile communication system, host node device, base station device, mobile station device, and base station condition control method
JP2008022089A (en) Wireless communication system, system controller, wireless base station, wireless communication terminal, communication control method and communication control program
WO2012091418A2 (en) Device-to-device communication and terminal relay method
CN103369172A (en) Function executing device
EP2946586A1 (en) Method and device for measuring signal in beam forming system
JP2006060336A (en) Wireless lan system, wireless lan access point, wireless lan terminal, and actuation control method used therefor
ES2319630T3 (en) Procedure to make transfers in wireless networks.

Legal Events

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

Ref document number: 14798269

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase in:

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 14890946

Country of ref document: US

122 Ep: pct application non-entry in european phase

Ref document number: 14798269

Country of ref document: EP

Kind code of ref document: A1