JP6662444B2 - Apparatus, method and program - Google Patents

Description

  The present disclosure relates to an apparatus, a method, and a program.

  As one of the measures to alleviate the depletion of future frequency resources, discussion on secondary use of frequency is underway. The secondary use of the frequency means that some or all of the frequency channels that are preferentially allocated to a certain system are used secondarily by another system. Generally, a system to which a frequency channel is preferentially assigned is called a primary system (Primary System), and a system that uses the frequency channel secondary is called a secondary system (Secondary System).

  TV white space is an example of a frequency channel whose secondary use is being discussed. The TV white space refers to a channel that is not used by the TV broadcasting system according to a region, among frequency channels allocated to the TV broadcasting system as a primary system. By opening this TV white space to the secondary system, efficient utilization of frequency resources can be realized. For example, IEEE 802.22, IEEE 802.11af, and ECMA (European Computer Manufacturer Association) -392 (for example, as a specification of a wireless access system of a physical layer (PHY) and a MAC layer for enabling secondary use of TV white space. CogNea).

  The IEEE 802.19 working group is studying for the purpose of smoothly coexisting a plurality of secondary systems using different radio access schemes. For example, in the IEEE 802.19 working group, various functions required for coexistence of a secondary system are classified into three functions: CM (Coexistence Manager), CE (Coexistence Enabler), and CDIS (Coexistence Discovery and Information Server). Grouped into entities. The CM is a functional entity that mainly performs decision-making for coexistence. The CE is a functional entity serving as an interface that mediates command transmission and information exchange between the CM and the secondary usage node. CDIS is a functional entity that serves as a server that centrally manages information of a plurality of secondary systems. CDIS also has a Neighbor Discovery function that detects neighboring secondary systems that may interfere with each other.

  Regarding such a functional entity, Patent Literature 1 below discloses a technique in which a plurality of functional entities perform proximity detection in cooperation with each other to avoid concentration of a load generated in CDIS due to proximity detection.

International Publication No. WO 2012/132804

  However, the technology for coexistence of the secondary system proposed in Patent Document 1 and the like has not been developed yet, and the technology for realizing smooth coexistence in various aspects has been sufficiently proposed. It is hard to say that it is. For example, a technique for exchanging information between secondary systems so that a plurality of secondary systems coexist is one of those that have not been sufficiently proposed.

  Thus, the present disclosure proposes a new and improved device, method, and program that can smoothly exchange information between a plurality of wireless systems.

  According to the present disclosure, a discovery unit that acquires information indicating a detection result of a communication node managed by the second frequency use control system related to the first frequency use control system, and the first frequency use control system A first sharable generated from the first frequency usage information related to the communication node managed by the first frequency usage control system and held by the included first database or the first communication control determination unit. An information sharing unit that notifies information to a second communication control determination unit included in the second frequency use control system is provided.

  Further, according to the present disclosure, acquiring information indicating a detection result of a communication node managed by a second frequency use control system related to the first frequency use control system; The first sharable generated from the first frequency usage information related to the communication node managed by the first frequency usage control system and held by the first database or the first communication control determination unit included in Notification to a second communication control determining unit included in the second frequency use control system of the second frequency use control system.

  Also, according to the present disclosure, a discovery unit that acquires information indicating a detection result of a communication node managed by a second frequency use control system related to the first frequency use control system, A first database or a first communication control determination unit, which is included in the frequency use control system and holds a first frequency use information generated from first frequency use information related to a communication node managed by the first frequency use control system. A program is provided for functioning as an information sharing unit that notifies the second sharable information to a second communication control determining unit included in the second frequency use control system.

  As described above, according to the present disclosure, it is possible to smoothly exchange information between a plurality of wireless systems. Note that the above effects are not necessarily limited, and any of the effects shown in the present specification or other effects that can be grasped from the present specification are used together with or in place of the above effects. May be played.

FIG. 1 is an explanatory diagram for describing an overview of a communication system according to an embodiment of the present disclosure. It is explanatory drawing which shows the correlation of three functional entities for coexistence support. FIG. 9 is a diagram for describing an architecture according to a comparative example. FIG. 2 is a diagram for describing an architecture according to the embodiment. It is a block diagram showing an example of composition of a communication control device concerning this embodiment. FIG. 3 is a diagram illustrating an example of a reference model of a CoE interface. FIG. 3 is a diagram illustrating an example of a reference model of a CoE interface. FIG. 4 is an explanatory diagram for explaining a Neighbor discovery request procedure. FIG. 4 is an explanatory diagram for describing a CoE discovery procedure. FIG. 4 is an explanatory diagram for describing a CoE discovery procedure. FIG. 4 is an explanatory diagram for describing a Share data request procedure. FIG. 4 is an explanatory diagram for describing an Inter-CoE data exchange request procedure. FIG. 4 is an explanatory diagram for describing an Inter-CoE data indication procedure. FIG. 4 is an explanatory diagram for explaining a Spectrum usage information request procedure. FIG. 4 is an explanatory diagram for describing a Spectrum usage information indication procedure. FIG. 4 is a sequence diagram for explaining an example of the overall flow of a procedure according to the embodiment. FIG. 6 is a sequence diagram for explaining a flow of a discovery process according to the embodiment. It is a sequence diagram for explaining an example of the flow of the information exchange process according to the present embodiment. It is a sequence diagram for explaining an example of the flow of the information exchange process according to the present embodiment. FIG. 3 is a diagram for describing coexistence of each sub-channel in a shared frequency band. FIG. 3 is a diagram for describing coexistence of each sub-channel in a shared frequency band. FIG. 3 is a diagram for describing coexistence of each sub-channel in a shared frequency band. FIG. 4 is an explanatory diagram for describing an Inter-CoE Priority-based Information request procedure. FIG. 4 is an explanatory diagram for describing an Inter-CoE Priority-based Information indication procedure. FIG. 9 is a diagram for describing an architecture according to a first modification. FIG. 14 is a diagram for describing an architecture according to a second modification. FIG. 11 is an explanatory diagram for describing a procedure for an external device according to the present modification. FIG. 11 is an explanatory diagram for describing a procedure for an external device according to the present modification. FIG. 14 is a diagram for describing an architecture according to a third modification. FIG. 4 is an explanatory diagram for describing a use case of the architecture according to the present embodiment. FIG. 4 is an explanatory diagram for describing a use case of the architecture according to the present embodiment. FIG. 4 is an explanatory diagram for describing a use case of the architecture according to the present embodiment. FIG. 4 is an explanatory diagram for describing a use case of the architecture according to the present embodiment. FIG. 4 is an explanatory diagram for describing a use case of the architecture according to the present embodiment. FIG. 3 is a block diagram illustrating an example of a schematic configuration of a server.

  Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In the specification and the drawings, components having substantially the same functional configuration are denoted by the same reference numerals, and redundant description is omitted.

  Further, in the present specification and the drawings, elements having substantially the same function and configuration may be distinguished from each other by adding different alphabets to the same reference numerals. For example, a plurality of elements having substantially the same functional configuration are distinguished as needed, such as the communication control devices 10A and 10B. However, when it is not necessary to particularly distinguish each of a plurality of elements having substantially the same functional configuration, only the same reference numeral is assigned. For example, when there is no need to particularly distinguish the communication control devices 10A and 10B, they are simply referred to as the communication control device 10.

The description will be made in the following order.
1. Overview 1.1. Overall configuration of system 1.2. Explanation of license 1.3. Description of functional entity 1.4. Technical issues 2. First embodiment 2.1. Architecture 2.2. Configuration example of CoE 2.3. Technical features of CoE 2.4. Procedure Modified example 4. Use case 5. Application example 6. Conclusion

<< 1. Overview >>
<1.1. Overall configuration of the system>
FIG. 1 is an explanatory diagram for describing an overview of a communication system according to an embodiment of the present disclosure.

  Referring to FIG. 1, a plurality of secondary usage nodes 30A constituting a secondary system A and a plurality of secondary usage nodes 30B constituting a secondary system B are shown. As shown in FIG. 1, the secondary usage node 30 is typically a transmitting station such as a base station or an access point. The secondary usage node 30A, which is the transmitting station, provides the service of the secondary system A to the receiving station located inside the service area 40A. Similarly, the secondary usage node 30B, which is the transmitting station, provides the service of the secondary system B to the receiving station located inside the service area 40B. Hereinafter, the transmitting station and the receiving station constituting the secondary system may be collectively referred to as a secondary usage node.

  Secondary usage nodes 30A and 30B are connected to communication control devices 10A and 10B, respectively. The communication control device 10 is a device that is introduced to control coexistence between a plurality of secondary systems using a frequency channel assigned to the primary system. The communication control devices 10A and 10B are connected to a geo-location information DB (GLDB: Geo-location Database) 20. The GLDB 20 has a function of notifying a list of available frequencies and / or transmission power to each of the secondary systems, and typically performs incumbent protection of the primary system. For example, the communication control device 10 obtains a secondary available frequency band from the GLDB 20 among the frequency bands allocated to the primary system, and manages and / or controls the target (hereinafter, also simply referred to as under management). Of the secondary system.

  The primary system includes, for example, a TV broadcast system, PMSE (Program Making and Special Events), radar (military, onboard, weather, etc.), fixed satellite service (FSS: Fixed Satellite Service), and earth exploration satellite (EESS: Earth). Exploration Satellite Service).

  Here, the service areas 40 (that is, 40A and 40B) of a plurality of secondary systems may geographically overlap and use frequency bands may overlap. As a specific example, for example, it is conceivable that the provision area of the LTE (Long Term Evolution) service operated by different operators and the provision area of the Wi-Fi service overlap.

  In the present embodiment, in such a situation, it is assumed that one or more secondary systems cooperate and secondary use some or all of the frequency band allocated to the primary system. For that purpose, it is desirable that the information can be smoothly exchanged between a plurality of secondary systems.

<1.2. Explanation of license>
Generally, a license for use of a frequency (License) is given by a frequency management organization or the like in each country. An example of a license form is shown in Table 1 below.

  Table 1 above shows “CEPT,“ ECC Report 132: Light Licensing, License-Exempt and Commons ”, Moscow, June, 2009.” <URL: http://www.erodocdb.dk/docs/doc98/official/Pdf /ECCRep132.pdf>. “Individual License” is a mechanism generally called “Licensed”, and requires a license. For example, the primary system is licensed according to this mechanism. For example, this mechanism is applied to a mobile communication service provider, a broadcast service provider, and the like. On the other hand, “Licence-Exempt” is a mechanism generally called “Unlicensed”, and does not require a license. For example, typical Wireless Local Area Network (WLAN) devices and Bluetooth® devices are used in this scheme. “Light-licensing” is a mechanism in which a non-exclusive license is typically given.

  The present embodiment is directed to a wireless system operating under “General authorization”. Devices that can be included in a wireless system that operates under “General authorization” include, for example, devices specified in “47 C.F.R. Part 15”. As such devices, for example, Intentional Radiators (900 MHz, 2.4 GHz and 5.8 GHz bands) in Subpart C, Unlicensed National Information Infrastructure devices (5 GHz bands) in Subpart E, and Television Band devices in Subpart H are defined. Other devices that can be included in a wireless system operating under “General authorization” include, for example, devices specified in “47 C.F.R. Part 96”. As such a device, for example, Citizens Broadband Radio Service Device (CBSD) is being defined. "47 C.F.R. Part 96" is an FCC rule (3.5 GHz SAS) under development and can be referred to from <URL: http://apps.fcc.gov/ecfs/comment/view?id=60001029680>. Devices that may be included in a wireless system operating under “General authorization” may be devices that are added or defined in the above rules in the future. That is, all devices that are recognized as being included in the framework of “General authorization” are targets of the technology according to the present embodiment.

  The secondary use of the frequency is provided in, for example, a mechanism of “Light-licensing”. In the present specification, a description will be given focusing on the coexistence of a plurality of secondary systems that perform secondary use of frequency in a mechanism of “Light-licensing”, which is a wireless system operating under “General authorization”. Of course, the technology according to the present embodiment is also applicable to a wireless system that operates under “General authorization” and operates according to the “Licence-Exempt” mechanism.

<1.3. Description of functional entity>
FIG. 2 is an explanatory diagram showing a correlation between three functional entities for coexistence support. As shown in FIG. 2, in IEEE 802.19.1, functions for supporting coexistence of secondary systems are grouped into three functional entities: CM, CE, and CDIS.

(1) CM (Coexistence Manager)
The CM is a functional entity that performs decision-making for coexistence. The CM acquires information about the primary system, information about available channels, and information about the secondary system. Sources of information obtained by the CM include CDIS, other CMs, and secondary usage nodes (accessed via the CE). The CM determines on which frequency channel the secondary usage node under its control should operate the secondary system based on the information. The CM may further determine, for each secondary usage node, additional control parameters such as a maximum transmission power, a recommended radio access scheme, and a location data update cycle. Then, the CM causes each secondary usage node to operate the secondary system or reconfigure the secondary system according to the determined parameters.

(2) CE (Coexistence Enabler)
The CE is a functional entity serving as an interface that mediates command transmission and information exchange between the CM and the secondary usage node. For example, the CE converts information possessed by the secondary usage node into a format usable by the CM, and transmits the converted information to the CM. Further, the CE converts an instruction from the CM regarding coexistence of the secondary system into a format that can be executed by the secondary usage node, and transmits the converted instruction to the secondary usage node.

(3) CDIS (Coexistence Discovery and Information Server)
CDIS is a functional entity that becomes a server that manages information of a plurality of secondary systems. For example, CDIS collects information about the secondary system from each secondary usage node via CE and CM. The CDIS also collects information about the primary system and information about available channels from the GLDB 20. CDIS stores the collected information in a database. The information accumulated by the CDIS is used when making decisions for coexistence by the CM. The CDIS may select a master CM (a CM that supervises a plurality of CMs and performs intensive decision-making) from a plurality of CMs. CDIS also has a neighbor detection function that detects nearby secondary systems that may interfere with each other.

  At least one of the three types of functional entities described above is implemented in each of the communication control devices 10 illustrated in FIG. Note that some functional entities may be implemented in individual secondary usage nodes 30. Further, some functional entities may be mounted on the same device as the GLDB 20.

  Note that the above three types of functional entities may be collectively referred to as a coexistence system. A coexistence system supports the coexistence of managed secondary systems.

(4) WSO (White Space Object)
WSO is one of the secondary usage nodes. In IEEE Std 802.19.1-2014, WSO represents a TV white space (TVWS) device or a network of TVWS devices. In the present embodiment, WSO is not limited to a TVWS device and a network of TVWS devices, but refers to a secondary usage node or a network of secondary systems in general. The WSO connects to the CM via the CE to receive a coexistence service, which is a service for coexistence of the secondary system. Note that WSO is a type of communication node.

(5) RLSS (Registered Location Secure Server)
The RLSS is a local server for preventing interference between terminals. The WSO connects to the GLDB 20 via the RLSS. The RLSS is defined by IEEE Std 802.11af, which is one of the standards for providing a wireless access scheme for TVWS. In IEEE Std 802.19.1-2014, the RLSS stores information organized using geographical location and accesses a database that holds operating parameters and locations for one or more basic service sets. , The entity to manage.

  The contents of each of the functional entities have been described above. Each of the functional entities may exchange information with each other using the interface. As shown in FIG. 2, the CE and the WSO / RLSS can exchange information via the interface A. The CM and the CE can exchange information via the interface B1. CM and CDIS can exchange information via the interface B2. CMs can exchange information via the interface B3. The CM and the Whitespace Database can exchange information via the interface C.

<1.4. Technical Issues>
As a technique for enabling smooth information exchange between a plurality of secondary systems, coexistence systems that control and manage the secondary systems may exchange information. FIG. 3 shows an example of a possible architecture.

  FIG. 3 is a diagram for explaining an architecture according to a comparative example. In the comparative example illustrated in FIG. 3, CMs included in each of the coexistence systems having different management targets directly provide an interface. However, this architecture has the following concerns:

(1) Difference in Profile In IEEE Std 802.19.1-2014, three types of profiles having different procedures (Procedure) and / or messages (Message) are provided. Therefore, different coexistence systems may use different profiles. Further, an interface for connecting CMs included in each of the two coexistence systems illustrated in FIG. 3 may be similar to the interface B3. It is conceivable that an interface can be connected between CMs having different profiles, but information is not substantially exchanged for coexistence according to the standard. Therefore, it is difficult to allow a plurality of secondary systems to coexist by exchanging information between a plurality of coexisting systems, particularly, exchanging information and negotiating between CMs having different profiles.

(2) Information Security The manager (typically, operator) of the coexistence system is required to securely manage the information held by the manager. Since CDIS has a database function, it is assumed that the coexistence system administrator has CDIS independently and manages it. However, the CM does not have a function for performing secure communication. For this reason, if CMs included in each of the coexistence systems managed by different administrators are directly connected by the interface B3, there is a risk that information to be securely managed may be leaked.

  Accordingly, the architecture according to the embodiment of the present disclosure has been created with the above circumstances in mind. In IEEE Std 802.19.1-2014, only one CDIS was assumed, and only a case where a plurality of CMs were connected to one CDIS and an interface was provided between these CMs was assumed. However, in the case where a plurality of CMs are connected to different CDISs, the above-described concerns arise. Therefore, the present embodiment provides an appropriate interface between CMs in a case where a plurality of CMs are connected to different CDISs. As a result, for example, coexistence systems can exchange information while absorbing the difference in profiles and ensuring information security.

<< 2. First Embodiment >>
<2.1. Architecture>
FIG. 4 is a diagram for explaining the architecture according to the present embodiment. As shown in FIG. 4, in the architecture according to the present embodiment, a coordination enabler (CoE), which is a new functional entity, is introduced in the coexistence system. Also, an interface B4 for connecting CoE and CM and an interface D for connecting CoE and CoE are introduced. The CoE may be implemented in the communication control device 10 illustrated in FIG. 1, may be implemented in each of the secondary usage nodes 30, may be implemented in the same device as the GLDB 20, and may be other. It may be implemented in any device. Although omitted in FIG. 3, in the architecture according to the present embodiment, an interface may be provided between the GLDB and the CM as in FIG.

  In the present embodiment, the frequency use control system corresponds to a wireless system such as a coexistence system. The first frequency use control system corresponds to a first coexistence system (Coexistence System 1). The second frequency use control system corresponds to a second coexistence system (Coexistence System 2). The communication node corresponds to a communication node such as WSO. The communication control determining unit corresponds to a CM. The communication control unit corresponds to CE. The database corresponds to CDIS. The device corresponds to CoE. The first CM, the first CE, the first CDIS, and the first CoE indicate the CM, CE, CDIS, and CoE that constitute the first coexistence system. Similarly, the second CM, the second CE, the second CDIS, and the second CoE indicate the CM, CE, CDIS, and CoE that constitute the second coexistence system. Note that the correspondence between these terms is merely an example based on IEEE Std 802.19.1-2014. The following description focuses on the CoE constituting the first coexistence system.

<2.2. Configuration example of CoE>
Hereinafter, a configuration example of CoE will be described with reference to FIGS.

  FIG. 5 is a block diagram illustrating an example of a configuration of the communication control device 10 according to the present embodiment. The communication control device 10 illustrated in FIG. 5 is a device in which CoE is mounted. Although FIG. 5 illustrates components related to CoE, the communication control device 10 may include components related to CM, CE, and / or CDIS. As shown in FIG. 5, the communication control device 10 includes a first communication unit 110, a second communication unit 120, and a processing unit 130.

  The first communication unit 110 is a communication interface that mediates communication between the communication control device 10 and the secondary usage nodes 30 and the like. The first communication unit 110 supports an arbitrary wireless communication protocol or a wired communication protocol, and establishes a communication connection with one or more secondary usage nodes 30.

  The second communication unit 120 is a communication interface that mediates communication with another communication control device 10. The second communication unit 120 supports an arbitrary wireless communication protocol or a wired communication protocol, and establishes a communication connection with another communication control device 10 corresponding to CM, CE, or CDIS included in the same coexistence system. I do. In addition, the second communication unit 120 establishes a communication connection with another communication control device 10 corresponding to CoE included in a different coexistence system.

  The processing unit 130 provides various functions of the communication control device 10. The processing unit 130 includes a discovery unit 132 and an information sharing unit 134. Note that the processing unit 130 may further include other components other than these components. That is, the processing unit 130 can perform operations other than the operations of these components. The details of the function of the processing unit 130 will be described later in detail.

  FIG. 6 is a diagram illustrating an example of a reference model of the CoE interface. As shown in FIG. 6, the CoE may have one SAP including a CoE-SAP (Service Access Point) and a Com-SAP. The CoE-SAP is an SAP with an interface function (Interface Function), and the Com-SAP is an SAP with a communication function (Communication Function).

  FIG. 7 is a diagram illustrating an example of a reference model of the CoE interface. As shown in FIG. 7, the CoE may have two SAPs. Further, the CoE may have three or more SAPs.

<2.3. Technical features of CoE>
(1) Discovery Function The discovery unit 132 has a function of acquiring information indicating a detection result of a communication node (for example, a secondary usage node) managed by the second coexistence system related to the first coexistence system. That is, the discovery unit 132 provides a discovery function for another secondary system to be coexisted. Here, the second coexistence system related to the first coexistence system means that, with the first coexistence system, the secondary systems under management interfere with each other, may interfere with each other, or It refers to other coexistence systems such as overlapping service areas. This function can be realized by, for example, a CoE discovery procedure described later.

  More specifically, the discovery unit 132 notifies the second CM of a discovery signal based on a request signal from the first CM. Then, the discovery unit 132 notifies the first CM of information indicating the detection result of the neighboring node of the secondary usage node managed by the first coexistence system, which is detected by the second CM to which the discovery signal has been notified. I do. This function can be realized by, for example, a Neighbor discovery request procedure and a CoE discovery procedure described later. Here, the request signal from the first CM is transmitted based on a measurement result by the secondary usage node managed by the first coexistence system or a calculation result for controlling the secondary usage node by the first CM. Is done. For this reason, the CM can utilize the discovery function as necessary for coexistence.

(2) Information Sharing Function The information sharing unit 134 has a first frequency associated with a communication node managed by the first coexistence system and held by the first CDIS or the first CM included in the first coexistence system. It has a function of notifying the first sharable information generated from the usage information to the second CM included in the second coexistence system. This function can be realized by, for example, a Share data request procedure, an Inter-CoE data indication procedure, and a Spectrum usage information indication procedure described later. Note that, of the first frequency usage information, information relating to the secondary usage of the frequency by the secondary usage node managed by the first coexistence system is also referred to as first frequency secondary usage information. The information sharing unit 134 may generate first sharable information from the first frequency secondary usage information.

  Further, the information sharing unit 134 is a second frequency use information related to the communication node indicated by the information acquired by the discovery unit 132 and held by the second CDIS or the second CM included in the second coexistence system. May be notified to the first CM. This function can be realized by, for example, a Spectrum usage information request procedure, an Inter-CoE data exchange request procedure, and a Share data request procedure described later. Note that, of the second frequency usage information, information relating to the secondary usage of the frequency by the secondary usage node managed by the second coexistence system is also referred to as second frequency secondary usage information. The second sharable information may be generated from the second frequency secondary usage information.

  The first sharable information is information shared from the first coexistence system to the second coexistence system. The second sharable information is information shared from the second coexistence system to the first coexistence system. Hereinafter, the first sharable information and the second sharable information are collectively referred to as sharable information unless it is particularly necessary to distinguish between them. Further, the first frequency secondary usage information is information of a secondary usage node managed by the first coexistence system, and the second frequency secondary usage information is information of a secondary usage node managed by the second coexistence system. This is information on the next usage node. In the following, the first frequency secondary usage information and the second frequency secondary usage information are collectively referred to as frequency secondary usage information unless it is particularly necessary to distinguish between them. The same applies to frequency usage information.

  The frequency secondary use information is typically information managed by CDIS or CM. Of the frequency secondary usage information, at least the geographic location (Geo-location), operating frequency (operating frequency, bandwidth, available frequency list) of the secondary system (or secondary usage node), and transmission power (Max EIRP, antenna gain) ), It is desirable that the information indicating the wireless access method can be shared. Furthermore, it is desirable that information on the total number of secondary systems (or secondary usage nodes) and the coverage can be shared. Note that the frequency usage information is typically information managed by CDIS or CM, and includes information such as geographical position and usage frequency regarding communication nodes other than the secondary usage node, in addition to the frequency secondary usage information. including.

  When notifying the sharable information, the information sharing unit 134 may notify information indicating a difference from the already notified information. As a result, the amount of communication is reduced. However, such a difference can be extracted by the CM from which the secondary frequency usage information is obtained. That is, the CoE need not have a storage unit.

  The information sharing unit 134 may generate the first sharable information based on the first frequency secondary usage information. The first sharable information is to select the first sharable information from the first frequency secondary usage information or to convert the first frequency secondary usage information into the first sharable information. Generated by Alternatively, the first sharable information may be generated by, for example, a first CM. The generation of sharable information can be performed, for example, in a Share data request procedure described later.

  The sharable information may be information corresponding to a profile used in the coexistence system of the notification destination. For example, when the profiles used in the coexistence system to which the CoE belongs and the coexistence system of the notification destination are different, the information sharing unit 134 selects information commonly used between different profiles as sharable information. I do. In addition, the information sharing unit 134 can share information by converting the information used in the profile of the coexistence system to which the CoE belongs to into a format usable in the profile used in the notification destination coexistence system. Information may be generated. As described above, information that absorbs the difference between the profiles is shared, so that information for coexistence can be exchanged even between coexistence systems using different profiles.

  Further, the sharable information may be information permitted to be disclosed to a coexistence system of a notification destination. For example, the information sharing unit 134 selects information permitted to be disclosed to another coexistence system as sharable information. In addition, the information sharing unit 134 may perform a conversion such as concealing or transforming a part or all of the information so as to be permitted to be disclosed to another coexistence system. In this way, only information whose information security is ensured is shared, so that secure exchange of information for coexistence is possible between coexistence systems managed by different managers.

  In addition, the sharable information may be, for example, information that cannot specify the privacy of one individual such as the owner of the wireless system. For example, with respect to location information, location information of an access point used privately by one individual is not sharable information because privacy of one individual can be specified. On the other hand, positional information of an access point (for example, an access point of a carrier Wi-Fi or a base station) installed for business is sharable information because privacy of one individual is not specified. As described above, it is determined whether sharing is possible or not depending on whether or not the privacy of one individual can be specified, so that information can be shared while protecting privacy.

  If there is a change in the license or priority assigned to at least a part of the frequency band used by the secondary usage node managed by the first coexistence system, the information sharing unit 134 Information about the license or the priority may be notified to the CM of the coexistence system. For example, when a secondary system managed by a coexistence system or a manager thereof receives a license for a part of a shared frequency band from an NRA (National Regulatory Authority), the CoE of another coexistence system using the band is used. Notify you of that. For example, if the NRA obtains a license for exclusive use of a part of the shared frequency band in a certain geographic area, this notification indicates to other coexistence systems that use in the same geographic area and the same band. Stop and request to use a different geographic area or a different band. Such notification realizes coexistence according to the granted license. The same applies to the priority. This function can be realized by, for example, an Inter-CoE Priority-based Information request procedure and an Inter-CoE Priority-based Information request procedure described later.

(3) Communication Function As shown in FIG. 4, the CoE may be included in each of the coexistence systems. In this case, the discovery unit 132 and the information sharing unit 134 communicate with a CM included in another coexistence system via another CoE included in another coexistence system. As a result, the CoE can function as an interface with the outside of the coexistence system.

  Further, as shown in FIG. 25 to be referred to later, the CoE is not included in any coexistence system, and may be provided independently of the coexistence system. In this case, the discovery unit 132 and the information sharing unit 134 communicate with the CM included in each coexistence system without passing through another CoE. As a result, the CoE can function as an external interface connecting the coexistence systems.

  In addition, as shown in FIG. 26 to be referred to later, an external device (External Entity) may be provided outside the coexistence system. In that case, the information sharing unit 134 may notify the external device of the sharable information. More specifically, the information sharing unit 134 may notify information that can be shared based on a request from an external device, or periodically or irregularly.

<2.4. Procedure>
Next, an example of a procedure introduced with the introduction of CoE will be described. Note that the names of procedures and messages to be transmitted / received used below are merely examples, and other arbitrary names may be used.

(1) Neighbor discovery request procedure
This procedure is for the CM to request the CoE to execute the discovery of another CoE via the interface D. This procedure is used in the same coexistence system.

  FIG. 8 is an explanatory diagram for explaining the Neighbor discovery request procedure. As shown in FIG. 8, the CM transmits a NeighborDiscoveryRequest to the CoE (Step S10). Next, the CoE transmits NeighborDiscoveryResponse to the CM (Step S12).

  NeighborDiscoveryRequest can include CM ID (IDentification information), IP address, port number, administrator ID (operator ID), target area information indicating a discovery target area, and the like.

  NeighborDiscoveryResponse may include an ID of CoE, an IP address, a port number, an information sharing enable / disable flag (True / False), an administrator ID (operator ID), and the like. The information sharing enable / disable flag is information indicating whether information on a communication node managed by the coexistence system can be shared by another coexistence system. According to the information sharing availability flag, it is determined whether information sharing is to be performed (for example, whether to request information sharing from another CoE). The CoE may transmit the information sharing enable / disable flag obtained from another CoE to the CM by using a CoE discovery procedure described later, in the NeighborDiscoveryResponse. Alternatively, the CoE may determine the information sharing enable / disable flag by itself and transmit it to the CM.

  This procedure can be used in a variety of situations. For example, the CM may use this procedure when it determines that interference from a nearby communication node is strong based on the measurement result of the managed communication node. In addition, when the CM determines that information on the WSO is necessary from a different coexistence system that manages a nearby WSO that is determined to have strong interference when performing calculations related to WSO control Alternatively, the procedure may be used.

(2) CoE discovery procedure
This procedure is for the CoE to find another CoE. This procedure is used between different coexistence systems, for example, between a first CoE and a second CoE.

  FIG. 9 is an explanatory diagram for explaining the CoE discovery procedure. The number at the end of the functional entity in the figure indicates the index of the coexistence system. For example, “CoE 1” is a first CoE constituting a first coexistence system, and “CoE 2” is a second CoE constituting a second coexistence system. The same applies to the following figures. As shown in FIG. 9, the first CoE transmits CoEDiscovery to the second CoE (step S20). Next, the second CoE transmits a CoEDiscoveryResponse to the first CoE (Step S28).

  CoEDiscovery is a discovery signal. The CoEDiscovery may include a CoE ID, an IP address, a port number, an administrator ID (operator ID), target area information indicating an area to be discovered, and the like. When the CoE specifies another target CoE, the CoE may transmit CoEDiscovery to the other CoE. Also, the CoE may broadcast CoEDiscovery when no other target CoE is specified.

  CoEDiscoveryResponse is a response to the discovery signal. The CoEDiscoveryResponse may include a CoE ID, an IP address, a port number, an information sharing enable / disable flag, an administrator ID (operator ID), and the like.

  The second CoE may determine the information sharing availability flag by itself. Alternatively, the second CoE may obtain an information sharing availability flag from the CM as shown in FIG.

  FIG. 10 is an explanatory diagram for explaining the CoE discovery procedure. FIG. 10 shows a flow until the second CoE receiving the CoEDiscovery in FIG. 9 returns a CoEDiscoveryResponse. As illustrated in FIG. 10, the second CoE that has received CoEDiscovery transmits a DiscoveryRequest to a CM configuring the same coexistence system (second coexistence system) (Step S22). Then, in the CM, a decision is made for neighbor detection (decision making for Neighbor Discovery), and an information sharing availability flag is determined (step S24). Next, the CM returns a DiscoveryResponse storing the determined information sharing availability flag to the second CoE (step S26).

  When the target area information is included in CoEDiscovery, the information sharing availability flag may be determined based on whether or not the target area includes a managed WSO. For example, the information sharing availability flag may be determined to be sharable (False) if WSO is not managed in the target area, and may be determined to be sharable (True) if it is included. In addition, the information sharing availability flag may be determined to be unsharable when a high priority WSO is included in the management. This is because the frequency assigned to the WSO having a higher priority is not typically used secondarily.

(3) Share data request procedure
This procedure is a procedure for acquiring information shared by CoE (hereinafter, also referred to as shared information). This procedure is used in the same coexistence system.

  FIG. 11 is an explanatory diagram for explaining the Share data request procedure. As shown in FIG. 11, first, the CoE transmits a ShareDataRequest to the CM (Step S30). Next, the CM generates shared information (Sharing data Generation) (Step S32). Next, the CM transmits a ShareDataResponse to the CoE (Step S34). Then, the CoE translates information as needed (Information translation if needed) (step S36).

  For example, the CoE generates sharable information, which is information that absorbs differences in profiles, assures information security, as translation of information as needed. The generation of such sharable information may be performed in the generation processing of the shared information by the CM, or may be performed by the translation processing by the CoE.

  When generating the shared information, the CM may obtain information from CDIS or another CM. For example, when there is a master / slave CM, the slave CM is not connected to the CoE, and the CoE needs frequency secondary usage information related to a secondary usage node managed by the slave CM, The CM acquires the frequency secondary usage information from the slave CM. Such a procedure may be referred to, for example, as a proxy information sharing procedure.

(4) Inter-CoE data exchange request procedure
This procedure is for the CoE to receive the provision of the secondary frequency usage information from another CoE. This procedure is used between different coexistence systems, for example, between a first CoE and a second CoE.

  FIG. 12 is an explanatory diagram for explaining the Inter-CoE data exchange request procedure. As shown in FIG. 12, the first CoE transmits a CxInfoRequest to the second CoE (Step S40). Next, the second CoE transmits CxInfoResponse to the first CoE (Step S42).

  The CxInfoRequest may include a CoE ID, profile information indicating a profile used in the coexistence system (first coexistence system), and target area information.

  CxInfoResponse includes frequency secondary usage information. Here, the secondary frequency usage information included in CxInfoResponse is sharable information generated or translated by the CM on the second CoE side or the second CoE in “(3) Share data request procedure”. The sharable information is generated or translated by, for example, selecting only WSO information in the neighborhood (Neighbor) of the WSO on the first CoE side, and excluding information that should be avoided in information security. Is also good. Further, when the profiles used in the first coexistence system and the second coexistence system are different, only the information commonly used regardless of the profiles may be selected, or the recalculation for absorbing the difference in the profiles may be performed. Etc. may be performed.

(5) Inter-CoE data indication procedure
This procedure is for the CoE to provide frequency secondary usage information to other CoEs. This procedure is used between different coexistence systems, for example, between a first CoE and a second CoE.

  FIG. 13 is an explanatory diagram for explaining the Inter-CoE data indication procedure. As shown in FIG. 13, first, the first CoE transmits CxInfoIndication to the second CoE (step S50). Next, the second CoE transmits CxInfoConfirm to the first CoE (Step S52).

  CxInfoIndication may include CoE ID, frequency secondary usage information, profile information, and the like. Here, the secondary frequency usage information included in CxInfoIndication may be generated or translated by the first CoE-side CM or the first CoE. The generation or translation here is the same as that described in “(4) Inter-CoE data exchange request procedure”.

(6) Spectrum usage information request procedure
This procedure is for the CM to notify the CoE of a request for secondary frequency usage information.

  FIG. 14 is an explanatory diagram for explaining the Spectrum usage information request procedure. As shown in FIG. 14, first, the CM transmits a SpectrumUsageInfoRequest to the CoE (Step S60). Next, the CoE transmits SpectrumUsageInfoResponse to the CM (Step S62).

  The SpectrumUsageInfoRequest may simply be a message requesting to provide any sharable information. Further, the SpectrumUsageInfoRequest may include information that specifically specifies information for which provision is requested.

  SpectrumUsageInfoResponse includes frequency secondary usage information acquired from another CoE. If there is an update from previously notified information, only the difference may be included.

(7) Spectrum usage information indication procedure
This procedure is a procedure for the CoE to notify the CM of the secondary frequency usage information acquired from another CoE.

  FIG. 15 is an explanatory diagram for explaining the Spectrum usage information indication procedure. As shown in FIG. 15, first, the CoE transmits SpectrumUsageInfoIndication to the CM (Step S70). Next, the CM transmits SpectrumUsageInfoConfirm to the CoE (Step S72).

  SpectrumUsageInfoIndication includes frequency secondary usage information obtained from another CoE. If there is an update from previously notified information, only the difference may be included.

(8) Overall Flow FIG. 16 is a sequence diagram for explaining an example of the overall flow of the procedure according to the present embodiment. As shown in FIG. 16, a first CM, a first CoE, a second CoE, and a second CM are involved in this sequence. As shown in FIG. 16, first, a discovery process is performed (step S80). Next, an information exchange process (Step S82) is performed. Hereinafter, a detailed process flow of the discovery process will be described with reference to FIG.

  FIG. 17 is a sequence diagram for explaining the flow of the discovery process according to the present embodiment. As shown in FIG. 17, this sequence involves a first CM, a first CoE, a second CoE, and a second CM. First, the first CM transmits a NeighborDiscoveryRequest to the first CoE (Step S90), and the first CoE transmits CoEDiscovery to the second CoE (Step S91). Next, the second CoE transmits a DiscoveryRequest to the second CM (Step S92), and a decision for neighbor detection (decision making for Neighbor Discovery) is performed in the second CM (Step S93). DiscoveryResponse is returned to the second CoE (step S94). Then, the second CoE transmits CoEDiscoveryResponse to the first CoE (step S95), and the first CoE transmits NeighborDiscoveryResponse to the first CM (step S96).

  Subsequently, a detailed processing flow of the information exchange process will be described with reference to FIGS. Note that FIG. 18 shows a request-based (Request base) process, and FIG. 19 shows an instruction-based (Indication base) process. These processes may be used in combination, or any one of them may be used.

  FIG. 18 is a sequence diagram for explaining an example of the flow of the information exchange process according to the present embodiment. As shown in FIG. 18, a first CM, a first CoE, a second CoE, and a second CM are involved in this sequence. First, the first CM transmits SpectrumUsageInfoRequest to the first CoE (Step S100), and the first CoE transmits CxInfoRequest to the second CoE (Step S101). Next, the second CoE transmits a ShareDataRequest to the second CM (Step S102), and the second CM generates shared information (Sharing data Generation) (Step S103). Next, the second CM transmits ShareDataResponse to the second CoE (Step S104), and the second CoE translates information as needed (Information translation if needed) (Step S105). Next, the second CoE transmits CxInfoResponse to the first CoE (step S106), and the first CoE transmits SpectrumUsageInfoResponse to the first CM (step S107).

  FIG. 19 is a sequence diagram for explaining an example of the flow of the information exchange process according to the present embodiment. As shown in FIG. 19, this sequence involves a first CM, a first CoE, a second CoE, and a second CM. First, the first CoE transmits a ShareDataRequest to the first CM (Step S110), and the first CM generates sharing information (Sharing data Generation) (Step S111). Next, the first CM transmits ShareDataResponse to the first CoE (step S112), and the first CoE translates information as needed (Information translation if needed) (step S113). Next, the first CoE transmits CxInfoIndication to the second CoE (step S114), and the second CoE transmits SpectrumUsageInfoIndication to the second CM (step S115). Next, the second CM transmits SpectrumUsageInfoConfirm to the second CoE (Step S116), and the second CoE transmits CxInfoConfirm to the first CoE (Step S117).

  The various procedures described above may be appropriately combined. For example, the ShareDataResponse in step S104 in FIG. 18 may be transmitted together with the DiscoveryResponse in step S94 in FIG. In addition, the ShareDataRequest in step S110 in FIG. 19 may be transmitted along with the NeighborDiscoveryResponse in step S96 in FIG.

  The example of the overall flow of the procedure according to the present embodiment has been described above. Subsequently, a procedure introduced to realize coexistence for each sub-channel of the shared frequency band will be described. The procedure described below can be used when different types of licenses or secondary usage node priorities are provided for each sub-channel of the shared frequency band.

  20 to 22 are diagrams for explaining coexistence for each sub-channel of the shared frequency band. As shown in FIG. 20, it is assumed that shared frequency band 200 is divided into arbitrary N subchannels. One sub-channel is the smallest allocated channel unit.

  FIG. 21 shows an example in which a different license setting is permitted for each sub-channel. A PAL (Priority Access License) in the figure indicates a license that can use an exclusive frequency. A GAA (General Authorized Access) is a license that is essential to protect a secondary usage node that operates under a license that allows exclusive frequency use. In GAA, interference between GAA users may occur. When different licenses are defined as described above, sharing information on the license given to the secondary usage node between coexistence systems (for example, between operators) enables more advanced coexistence. For example, the coexistence system protects a secondary usage node that operates under a license that allows exclusive use of frequency, and also prevents interference from the secondary usage node (for example, intra-operator interference and inter-operator interference, etc.). ), Coexistence between secondary usage nodes operating under another license (for example, within an operator and between operators) can be implemented.

  FIG. 22 shows an example in which different priority settings are allowed for each sub-channel. For example, sub-channel # 0 is available only to high-priority secondary usage nodes, sub-channel # 1 is available to high-priority and low-priority secondary usage nodes, and sub-channel # 4 Is available only to low priority secondary usage nodes. When such different priorities are determined, higher-level coexistence can be implemented by sharing frequency secondary usage information including priority information of secondary usage nodes between coexistence systems (for example, between operators). Becomes The priority is set by, for example, QoS guarantee. A uniform index may be used between coexistence systems (for example, between operators).

(9) Inter-CoE Priority-based Information request procedure
This procedure is a procedure for requesting secondary frequency usage information including information on a license or priority in a shared frequency band. When the license or the priority in the shared frequency band changes, each coexistence system can use this procedure to perform the calculation for the control of the frequency secondary usage of the managed secondary usage node again. Become. This procedure is used between different coexistence systems, for example, between a first CoE and a second CoE.

  FIG. 23 is an explanatory diagram for describing the Inter-CoE Priority-based Information request procedure. As shown in FIG. 23, the first CoE transmits a PriorityInfoRequest to the second CoE (Step S120). Next, the second CoE transmits PriorityInfoResponse to the first CoE (Step S122).

  PriorityInfoResponse includes geolocation information (information indicating a valid license location, area, and location of a high-priority node, etc.), and information related to a band (center frequency, upper limit frequency, lower limit frequency, bandwidth, validity period, license And information indicating the priority type and the like).

(10) Inter-CoE Priority-based Information indication procedure
This procedure is a procedure for providing secondary frequency usage information including information on licenses or priorities in a shared frequency band.

  FIG. 24 is an explanatory diagram for describing the Inter-CoE Priority-based Information indication procedure. As shown in FIG. 24, the first CoE transmits PriorityInfoIndication to the second CoE (Step S130). Next, the second CoE transmits PriorityInfoConfirm to the first CoE (Step S132).

  PriorityInfoIndication includes geolocation information (information indicating a valid license location, area, and location of a high-priority node, etc.), and information related to a band (center frequency, upper limit frequency, lower limit frequency, bandwidth, validity period, license And information indicating the priority type and the like).

<< 3. Modifications >>
Hereinafter, a modification of the architecture according to the first embodiment will be described.

(1) Modification 1
FIG. 25 is a diagram for explaining an architecture according to the first modification. As shown in FIG. 25, in the architecture according to the present modification, CoE is introduced outside the coexistence system. In this modification, the CoE and each coexistence system are connected by an interface B4.

  In the architecture according to this modification, the interface D is omitted from the architecture shown in FIG. Therefore, in the architecture according to the present modification, it is possible to omit a procedure (a procedure whose name includes Inter-CoE) used between different coexistence systems.

(2) Modification 2
FIG. 26 is a diagram for explaining an architecture according to the second modification. As shown in FIG. 26, in the architecture according to this modification, an external device (External Entity) and an interface E for connecting the external device and CoE are introduced into the architecture shown in FIG. The external device may be, for example, a monitoring entity that monitors the usage status of the frequency, or may be a sensing entity that performs various types of sensing.

  The interface E is an interface between the external device and the CoE. For example, when the external device is a monitoring entity, it is possible for a regulator to check the frequency usage status and to use a frequency determined to be available to a system managed by the regulator. . Also, for example, when the external device is a sensing entity, more advanced coexistence control can be performed using the sensing result.

  In this modification, as shown in FIGS. 27 and 28, the external device can use CxInfoRequest and CxInfoResponse, or CxInfoIndication and CxInfoConfirm, to know the frequency usage status.

  FIG. 27 is an explanatory diagram for describing a procedure for an external device according to the present modification. As shown in FIG. 27, first, the external device transmits a CxInfoRequest to the CoE (Step S140). Next, the CoE transmits CxInfoResponse to the external device (Step S142).

  FIG. 28 is an explanatory diagram for describing a procedure for an external device according to the present modification. As shown in FIG. 28, first, the CoE transmits CxInfoIndication to an external device (Step S150). Next, the external device transmits CxInfoConfirm to the CoE (Step S152).

(3) Modification 3
FIG. 29 is a diagram for describing an architecture according to the third modification. As shown in FIG. 29, in the architecture according to the present modification, an external device and a CoE are introduced in addition to the coexistence system. In this architecture, the CoE included in the coexistence system and the external CoE are connected by an interface D.

<< 4. Use Case >>
Hereinafter, use cases in which the above-described architectures are implemented will be described.

(1) Use case 1
FIG. 30 is an explanatory diagram for describing a use case of the architecture according to the present embodiment. This use case is an implementation example of the architecture shown in FIG. The numbers at the end of the functional entities in the figure are the index of the coexistence system and the index of the same functional entity in the same coexistence system. For example, “CDIS 1” is a CDIS that configures a first coexistence system, and “CM 1-1” is a first CM that configures a first coexistence system. A solid line indicates an intra line, a double line indicates an Internet line, and functional entities of the same color are managed by the same administrator. The same applies to the following figures. An example of such an implementation is the coexistence of wireless LAN (eg, Operator-managed Wi-Fi) systems installed by different MNOs (Mobile Network Operators).

  In recent years, wireless LAN systems using MNOs have been increasingly installed for the purpose of offloading increasing traffic. However, in a wireless LAN system, unlike cellular, CSMA / CA (Carrier Sense Multiple Access / Collision Avoidance) is adopted as a multiple access method, and centric interference control or the like is not performed. Therefore, in a zone where communication is dense, such as a city center, a station, an apartment house, a commercial facility, and an event venue, usability of the wireless LAN may be reduced. Further, it is assumed that the MNO will introduce not only wireless LANs but also LTE-LAA (Licensed-Assisted Access using LTE), which is being studied in 3GPP, in the 5 GHz band (License-exempt band) in the future. Further, in the future, an LTE scheme that operates only in the license-exempt band may appear.

  Therefore, the usability is reduced not only in networks managed by the same MNO, but also between networks managed by different MNOs, and not only between the same RATs (Radio Access Technology) but also between different RATs. It is desirable to provide an appropriate coexistence scheme for prevention.

  However, if the IEEE 802.19.1 architecture is diverted to another band as it is, even though each MNO can manage CDIS and control the use of frequencies in its own network, it can be managed by different MNOs. No coexistence between networks is achieved.

  In this regard, according to the technology provided in the present embodiment, coexistence can be easily realized not only between networks managed by different MNOs, but also between different RATs as well as between the same RATs (Radio Access Technology). It is possible to In the architecture according to the present embodiment, CoE is introduced, which acts as an interface between networks managed by different MNOs, so that frequency secondary usage information can be appropriately exchanged between networks managed by different MNOs. That's why.

(2) Use case 2
FIG. 31 is an explanatory diagram for describing a use case of the architecture according to the present embodiment. This use case is an implementation example of the architecture shown in FIG. CoE may be shared between MNOs (a form of Infra-sharing). Further, a CoE operator may be separately provided.

(3) Use case 3
FIG. 32 is an explanatory diagram for describing a use case of the architecture according to the present embodiment. This use case is an implementation example when the architecture shown in FIG. 4 is implemented for an ETC (Electronic Toll Collection) system of a car. Double dashed lines in the figure indicate wireless communication paths. As shown in FIG. 32, under the first CDIS, an ETC system is managed (for example, Communication node 1-3). Further, under the second CDIS, a network using MNOs is deployed near an expressway (for example, Communication node 2-2). Even in such a use case, according to the architecture according to the present embodiment, coexistence can be easily realized.

(4) Use case 4
FIG. 33 is an explanatory diagram for describing a use case of the architecture according to the present embodiment. In the use case shown in FIG. 33, each of the small cell eNB and the AP (Access Point) of Wi-Fi includes CE, and each of the core network (Core network) and the enterprise server (Enterprise server) includes CM, CDIS and It has CoE.

  In LTE-LAA, implementation of carrier aggregation using a licensed frequency band (Licensed-spectrum) and a license-exempt frequency band (License-exempt spectrum) is being studied. In this regard, the operator manages and controls Wi-Fi using the same band, and performs detection of other unmanaged Wi-Fi networks by CoE, thereby enabling aggregation between different RATs. It is considered that the communication quality is further improved.

(5) Use case 5
FIG. 34 is an explanatory diagram for describing a use case of the architecture according to the present embodiment. In the use case shown in FIG. 34, on the floor of the shopping mall, a network managed by the shopping mall and a network managed by a company resident in the shopping mall are mixed. As described above, in an office building or the like, one or more companies are occupied, and in many cases, companies have built their own networks utilizing Wi-Fi. In such a case, it is conceivable that a company will set up its own server and centrally manage the network. In such a case, by providing each server with CoE in addition to CM and CDIS as shown in FIG. It becomes feasible.

<< 5. Application >>
The technology according to the present disclosure is applicable to various products. For example, the communication control device 10 may be realized as any type of server such as a tower server, a rack server, or a blade server. In addition, at least some of the components of the communication control device 10 are realized in a module mounted on a server (for example, an integrated circuit module configured with one die, or a card or a blade inserted into a slot of a blade server). May be done.

  FIG. 35 is a block diagram illustrating an example of a schematic configuration of a server 700 to which the technology according to the present disclosure may be applied. The server 700 includes a processor 701, a memory 702, a storage 703, a network interface 704, and a bus 706.

  The processor 701 may be, for example, a CPU (Central Processing Unit) or a DSP (Digital Signal Processor), and controls various functions of the server 700. The memory 702 includes a RAM (Random Access Memory) and a ROM (Read Only Memory), and stores programs executed by the processor 701 and data. The storage 703 may include a storage medium such as a semiconductor memory or a hard disk.

  The network interface 704 is a wired communication interface for connecting the server 700 to the wired communication network 705. The wired communication network 705 may be a core network such as an EPC (Evolved Packet Core) or a PDN (Packet Data Network) such as the Internet.

  The bus 706 connects the processor 701, the memory 702, the storage 703, and the network interface 704 to each other. The bus 706 may include two or more buses having different speeds (for example, a high speed bus and a low speed bus).

  In the server 700 illustrated in FIG. 35, the processing unit 130 described with reference to FIG. 5 may be implemented in the processor 701. As an example, a program for causing the processor to function as the processing unit 130 (in other words, a program for causing the processor to execute the operation of the processing unit 130) is installed in the server 700, and the processor 701 may execute the program. . As another example, the server 700 may include a module including the processor 701 and the memory 702, and the processing unit 130 may be mounted on the module. In this case, the module may store a program for causing the processor to function as the processing unit 130 in the memory 702, and execute the program by the processor 701. As described above, the server 700 or the above module may be provided as an apparatus including the processing unit 130, and the above program for causing a processor to function as the processing unit 130 may be provided. Further, a readable recording medium on which the program is recorded may be provided.

<< 6. Summary >>
The embodiment of the present disclosure has been described above in detail with reference to FIGS. 1 to 35. As described above, the CoE according to the present embodiment can acquire information indicating a detection result of a communication node managed by the second frequency usage control system related to the first frequency usage control system. Thus, for secondary use of frequency, the CMs of the coexistence system may have other coexistence, such as the managed secondary systems are interfering with each other, possibly interfering, or having overlapping service areas. It is possible to utilize the discovery function for the system. Further, the CoE according to the present embodiment uses the sharable information generated from the frequency usage information related to the communication node managed by the first frequency usage control system in the second frequency usage control system. Is notified to the communication control judgment unit. As a result, information necessary for coexistence is shared between coexistence systems. In this way, it is possible to smoothly exchange information between a plurality of secondary systems.

  Here, the sharable information may be information corresponding to a profile used in the coexistence system of the notification destination. As a result, information that absorbs the difference between the profiles is shared, so that information can be exchanged for coexistence even between coexistence systems using different profiles.

  Further, the sharable information may be information permitted to be disclosed to a coexistence system of a notification destination. As a result, only information for which information security is ensured is shared, so that secure exchange of information for coexistence is possible between coexistence systems managed by different administrators.

  In addition, the sharable information may be, for example, information that cannot specify the privacy of one individual such as the owner of the wireless system. This makes it possible to share information while protecting privacy.

  As described above, the preferred embodiments of the present disclosure have been described in detail with reference to the accompanying drawings, but the technical scope of the present disclosure is not limited to such examples. It is apparent that a person having ordinary knowledge in the technical field of the present disclosure can conceive various changes or modifications within the scope of the technical idea described in the claims. It is understood that also belongs to the technical scope of the present disclosure.

  In addition, a processor (e.g., a CPU, a DSP, or the like) provided in a device (e.g., a base station, a base station device, or a module for a base station device, or a terminal device or a module for a terminal device) of this specification is referred to as A computer program for causing the device to function as a component (for example, the processing unit 130) of the device (in other words, a computer program for causing the processor to execute the operation of the component of the device) can also be created. Further, a recording medium on which the computer program is recorded may be provided. Further, a device including a memory for storing the computer program and one or more processors capable of executing the computer program (for example, a base station, a module for a base station device or a base station device, or a terminal device or A module for a terminal device) may also be provided. In addition, a method including an operation of a component (for example, the processing unit 130) of the device is also included in the technology according to the present disclosure.

  Further, the processes described with reference to the flowcharts and the sequence diagrams in this specification do not necessarily have to be executed in the illustrated order. Some processing steps may be performed in parallel. Further, additional processing steps may be employed, and some processing steps may be omitted.

  Further, the effects described in this specification are merely illustrative or exemplary, and are not restrictive. That is, the technology according to the present disclosure can exhibit other effects that are obvious to those skilled in the art from the description in the present specification, in addition to or instead of the above effects.

The following configuration also belongs to the technical scope of the present disclosure.
(1)
A discovery unit that acquires information indicating a detection result of a communication node managed by the second frequency use control system related to the first frequency use control system;
From first frequency usage information related to a communication node managed by the first frequency usage control system and held by a first database or a first communication control determination unit included in the first frequency usage control system. An information sharing unit that notifies the generated first sharable information to a second communication control determination unit included in the second frequency use control system;
An apparatus comprising:
(2)
The information sharing unit may be a second database or a second communication control determination unit included in the second frequency use control system, the second communication control determination unit may include a second database related to a communication node indicated by the information acquired by the discovery unit. The device according to (1), wherein the second sharable information generated from the second frequency usage information is notified to the first communication control determination unit.
(3)
The device is included in each of the frequency use control systems,
The discovery unit and the information sharing unit communicate with a communication control determination unit included in another frequency use control system via another device included in another frequency use control system. Or the apparatus according to (2).
(4)
The device is not included in any frequency use control system,
The device according to (1) or (2), wherein the discovery unit and the information sharing unit communicate with a communication control determination unit included in each frequency use control system without passing through another device.
(5)
The device according to any one of (1) to (4), wherein the sharable information is information corresponding to a profile used in a frequency usage control system of a notification destination.
(6)
The device according to any one of (1) to (5), wherein the sharable information is information permitted to be disclosed to a frequency use control system of a notification destination.
(7)
The device according to any one of (1) to (6), wherein the information sharing unit generates the first sharable information based on the first frequency usage information.
(8)
The device according to any one of (1) to (6), wherein the first sharable information is generated by the first communication control determination unit.
(9)
The first sharable information selects the first sharable information from the first frequency usage information, or converts the first frequency usage information into the first sharable information. The device according to (7) or (8), which is generated by the above.
(10)
Any of the above (1) to (9), wherein the sharable information includes at least one of information indicating a geographical position of a communication node, information indicating a frequency, information indicating a transmission power, and information indicating a wireless system. An apparatus according to claim 1.
(11)
The apparatus according to (10), wherein the sharable information includes at least one of information indicating a total number of communication nodes and information indicating coverage.
(12)
The device according to any one of (1) to (11), wherein the information sharing unit notifies information indicating a difference from information already notified.
(13)
The discovery unit notifies the second communication control determination unit of a discovery signal based on a request signal from the first communication control determination unit, and the second communication control determination unit notified of the discovery signal Notifying the first communication control determining unit of information indicating a detection result of a neighboring node of a communication node managed by the first frequency use control system, detected by the first frequency usage control system, to any one of (1) to (12). An apparatus according to claim 1.
(14)
The request signal is transmitted based on a measurement result by a communication node managed by the first frequency use control system or a calculation result by the first communication control determination unit for controlling the communication node. Device according to 13).
(15)
The information sharing unit uses the frequency band when a license or a priority assigned to at least a part of a frequency band used by a communication node managed by the first frequency use control system changes. The apparatus according to any one of (1) to (14), which notifies the communication control determination unit of another frequency usage control system of the information on the license or the priority.
(16)
The device according to any one of (1) to (15), wherein the information sharing unit notifies the first sharable information to an external device that monitors a frequency usage state.
(17)
The device according to (16), wherein the information sharing unit notifies the first sharable information based on a request from the external device, or periodically or irregularly.
(18)
Obtaining information indicating a detection result of a communication node managed by the second frequency use control system related to the first frequency use control system;
From first frequency usage information related to a communication node managed by the first frequency usage control system and held by a first database or a first communication control determination unit included in the first frequency usage control system. Notifying the generated first sharable information to a second communication control determining unit included in the second frequency use control system;
A method performed by a processor comprising:
(19)
Computer
A discovery unit that acquires information indicating a detection result of a communication node managed by the second frequency use control system related to the first frequency use control system;
From first frequency usage information related to a communication node managed by the first frequency usage control system and held by a first database or a first communication control determination unit included in the first frequency usage control system. An information sharing unit that notifies the generated first sharable information to a second communication control determination unit included in the second frequency use control system;
Program to function as

Reference Signs List 1 communication system 10 communication control device 110 first communication unit 120 second communication unit 130 processing unit 132 discovery unit 134 information sharing unit 20 GLDB
30 Secondary usage node 40 Service area

Claims (20)

Receiving a discovery signal including area information from an external device,
Based on the discovery signal, generate sharable information from the frequency usage information related to the communication node managed by the frequency usage control system,
A processing unit that notifies the sharable information to the external device,
An apparatus comprising:   2. The sharable information according to claim 1, wherein the processing unit generates the sharable information by removing information not permitted to be disclosed to the external device from the frequency usage information related to the communication node. 3. Equipment.   The apparatus according to claim 1, wherein the area information includes target area information indicating an area targeted for discovery by the external device.   The device according to claim 1, wherein the discovery signal includes a device ID, profile information indicating a profile used in the coexistence system, and target area information.   The apparatus according to claim 1, wherein the sharable information includes information corresponding to a profile commonly used between coexistence systems in which different profiles are used.   The apparatus of claim 1, wherein the sharable information includes information about a total number of secondary systems and coverage of the secondary systems.   The apparatus of claim 1, wherein the sharable information includes information corresponding to a profile used in a coexistence system.   The apparatus of claim 1, wherein the sharable information does not include private access point location information.   The apparatus according to claim 1, wherein the sharable information includes position information of a business access point.   The apparatus according to claim 1, wherein the sharable information corresponds to a profile used in a second frequency usage control system notified of the sharable information.   The apparatus according to claim 1, wherein the sharable information is information permitted to be disclosed to a second frequency use control system to which the sharable information is notified.   2. The processing unit according to claim 1, wherein, among the frequency usage information, the sharable information is generated based on information related to a secondary usage of a frequency by a secondary system managed by the frequency usage control system. 3. The described device.   2. The sharable information according to claim 1, wherein the sharable information is generated by selecting sharable information among the frequency usage information or by converting the frequency usage information into sharable information. apparatus.   2. The sharable information according to claim 1, wherein the sharable information includes at least one of information indicating a geographical position of the communication node, information indicating a use frequency, information indicating a transmission power, and information indicating a wireless access scheme. 3. Equipment.   The apparatus according to claim 14, wherein the sharable information includes at least one of a total number report of the communication nodes and information on coverage.   The apparatus according to claim 1, wherein the processing unit notifies information indicating a difference from the sharable information that has been notified.   The device according to claim 1, wherein the processing unit notifies the external device of the sharable information when the external device monitors a frequency use situation. 18. The device according to claim 17, wherein the processing unit notifies the sharable information based on a request from the external device , or periodically or irregularly . Receiving a discovery signal including area information from an external device,
Based on the discovery signal, generating sharable information from the frequency usage information related to the communication node managed by the frequency usage control system,
Notifying the external device of the sharable information,
A method performed by a processor, comprising: Computer
Receiving a discovery signal including area information from an external device,
Based on the discovery signal, generate sharable information from the frequency usage information related to the communication node managed by the frequency usage control system,
A processing unit that notifies the sharable information to the external device,
A recording medium on which a program for functioning as a computer is recorded.

Images