Method, device and computer readable medium for binding and unbinding adjacent devices

Abstract

Methods, apparatuses, and computer-readable media for binding neighboring devices are disclosed. An example apparatus may include at least one processor and at least one memory. The at least one memory may include computer program code, and the at least one memory and computer program code may be configured to, using at least one processor, cause the apparatus to execute sending a binding request to a management entity for binding with at least one neighboring device, and receiving a binding response to the binding request from the management entity.

Description

Technical Field

[0001] Various embodiments are directed to methods, devices, and computer-readable media for binding and unbinding neighboring devices. Background Art

[0002] Most of the time, goods with hypertags are always transported or stacked together. These grouped goods are located in the same space, and their hypertags will measure the same or very similar results about location-related information (such as position, speed, acceleration, etc.) and environmental perception-related information (such as atmospheric pressure, temperature, humidity, etc.). Summary of the invention

[0003] The following provides a brief summary of exemplary embodiments to provide a basic understanding of some aspects of various embodiments. It should be noted that this summary is not intended to identify key features of essential elements or define the scope of the embodiments, and its sole purpose is to introduce some concepts in a simplified form as a prelude to the more detailed description provided below.

[0004] In a first aspect, an apparatus is disclosed. The apparatus may include at least one processor and at least one memory. The at least one memory may include computer program code, and the at least one memory and the computer program code may be configured to, using the at least one processor, cause the apparatus to execute transmitting a binding request for binding with at least one neighboring apparatus to a management entity, and receiving a binding response to the binding request from the management entity.

[0005] In some embodiments, transmitting the bind request to the management entity for binding with at least one neighboring device may be triggered by a predetermined event.

[0006] In some embodiments, the binding request may include at least one of an indicator of the binding request, at least one identification of at least one neighboring device, at least one binding information type, and at least one binding reason.

[0007] In some embodiments, the binding response may include at least one of an acknowledgement or a negative acknowledgement of the binding request, at least one binding information type, and at least one identification of the at least one neighboring device.

[0008] In some embodiments, the at least one memory and the computer program code may be further configured to use the at least one processor to cause the device to further perform searching for the at least one neighboring device and obtaining at least one identification of the at least one neighboring device.

[0009] In some embodiments, the at least one memory and the computer program code may be further configured to utilize the at least one processor to cause the device to further execute transmitting a binding release request to the management entity for unbinding from the at least one adjacent device, and receiving a binding release response to the binding release request from the management entity.

[0010] In some embodiments, the binding release request may include at least one of an indicator of the binding release request, at least one binding information type to be released, and at least one binding release reason.

[0011] In some embodiments, the binding release response may include at least one of an acknowledgement of the binding release request and at least one released binding information type.

[0012] In a second aspect, an apparatus is disclosed. The apparatus may include at least one processor and at least one memory. The at least one memory may include computer program code, and the at least one memory and the computer program code may be configured to, with the at least one processor, cause the apparatus to perform receiving a capacity request for binding capacity with a neighboring device from a management entity, and transmitting a capacity response to the capacity request to the management entity.

[0013] In some embodiments, a capacity request may include at least one binding information type.

[0014] In some embodiments, the capacity response may include at least one of at least one supported binding information type, at least one rejected binding information category, and at least one rejection reason.

[0015] In some embodiments, the at least one memory and the computer program code may be further configured to, with the at least one processor, cause the apparatus to further perform receiving binding information from the management entity.

[0016] In some embodiments, the binding information may include at least one of an identification of the neighboring device and at least one binding information type.

[0017] In some embodiments, the at least one memory and the computer program code may be further configured to utilize the at least one processor to cause the device to further execute transmitting a binding release request to the management entity for unbinding from the neighboring device, and receiving a binding release response to the binding release request from the management entity.

[0018] In some embodiments, the binding release request may include at least one of an indicator of the binding release request, an identification of the neighboring device, at least one binding information type to be released, and at least one binding release reason.

[0019] In some embodiments, the binding release response may include at least one of an acknowledgement of the binding release request and at least one binding information type to be released.

[0020] In a third aspect, a device is disclosed. The device may include at least one processor and at least one memory. The at least one memory may include computer program code, and the at least one memory and the computer program code may be configured to use the at least one processor to cause the device to perform receiving a binding request from a first device for binding with at least one neighboring device of the first device; in response to the binding request, transmitting a first capacity request for binding capacity of the second device to a second device in the at least one neighboring device; receiving a first capacity response to the first capacity request from the second device; binding the first device and the second device based on the first capacity response; transmitting a binding response to the binding request to the first device.

[0021] In some embodiments, the binding request may include at least one of an indicator of the binding request, at least one identification of the at least one neighboring device, at least one binding information type, and at least one binding reason.

[0022] In some embodiments, the binding response may include at least one of an acknowledgement or a negative acknowledgement of the binding request, at least one binding information type, and an identification of the second device.

[0023] In some embodiments, the at least one memory and the computer program code may be further configured to utilize the at least one processor to cause the device to further execute receiving an access request to first measurement information of the first device, transmitting the access request to the second device, receiving second measurement information of the second device, and determining the first measurement information based on the second measurement information and calibration parameters.

[0024] In some embodiments, binding the first device and the second device based on the first capacity response may include establishing an association between at least one of an identification of the first device and the second device, a binding information type, a calibration parameter, and a binding establishment time.

[0025] In some embodiments, the at least one memory and the computer program code may be further configured to utilize the at least one processor to cause the device to further execute transmitting first binding information to the second device, and the first binding information may include an identifier of the first device and at least one of at least one binding information type.

[0026] In some embodiments, the at least one memory and the computer program code may be further configured to utilize the at least one processor to cause the device to further execute receiving a binding release request for unbinding the first device and the second device from one of the first device and the second device; based on the binding release request, deleting the association between at least one of the identification, binding information type, calibration parameters and binding establishment time of the first device and the second device; transmitting a binding release response to the binding release request to the one of the first device and the second device; and transmitting binding release information or binding update information to the other of the first device and the second device.

[0027] In some embodiments, the binding release request may include at least one of an indicator of the binding release request, an identification of the first device, at least one binding information type to be released, and at least one binding release reason.

[0028] In some embodiments, the binding release response may include at least one of an acknowledgement of the binding release request and at least one released binding information type.

[0029] In some embodiments, the binding release information may include at least one released binding information type.

[0030] In some embodiments, the at least one memory and the computer program code may be further configured to utilize the at least one processor to cause the device to further execute transmitting a second capacity request for binding capacity of a third device among the at least one adjacent device; receiving a second capacity response to the second capacity request from the third device in response to a binding release request from the second device, and binding the first device and the third device based on the second capacity response.

[0031] In some embodiments, the binding update information may include at least one of at least one binding information type and an identification of the third device.

[0032] In some embodiments, the at least one memory and the computer program code may be further configured to utilize the at least one processor to cause the device to further execute transmitting second binding information to the third device, and the second binding information may include an identifier of the first device and at least one of at least one binding information type.

[0033] In some embodiments, the first capacity request or the second capacity request may include at least one binding information type.

[0034] In some embodiments, the first capacity response or the second capacity response may include at least one of at least one supported binding information type, at least one rejected binding information category, and at least one rejection reason.

[0035] In a fourth aspect, a method is disclosed. The method may include transmitting a binding request for binding with at least one neighboring device to a management entity, and receiving a binding response to the binding request from the management entity.

[0036] In some embodiments, transmitting the bind request to the management entity for binding with at least one neighboring device may be triggered by a predetermined event.

[0037] In some embodiments, the binding request may include at least one of an indicator of the binding request, at least one identification of at least one neighboring device, at least one binding information type, and at least one binding reason.

[0038] In some embodiments, the binding response may include at least one of an acknowledgement or a negative acknowledgement of the binding request, at least one binding information type, and at least one identification of at least one neighboring device.

[0039] In some embodiments, the method may further include searching for the at least one neighboring device and obtaining at least one identification of the at least one neighboring device.

[0040] In some embodiments, the method may further include transmitting a binding release request for unbinding from at least one neighboring device to the management entity, and receiving a binding release response to the binding release request from the management entity.

[0041] In some embodiments, the binding release request may include at least one of an indicator of the binding release request, at least one binding information type to be released, and at least one binding release reason.

[0042] In some embodiments, the binding release response may include at least one of an acknowledgement of the binding release request and at least one released binding information type.

[0043] In a fifth aspect, a method is disclosed. The method may include receiving a capacity request for binding capacity with a neighboring device from a management entity, and transmitting a capacity response to the capacity request to the management entity.

[0044] In some embodiments, a capacity request may include at least one binding information type.

[0045] In some embodiments, the capacity response may include at least one of at least one supported binding information type, at least one rejected binding information category, and at least one rejection reason.

[0046] In some embodiments, the method may further include receiving binding information from a management entity.

[0047] In some embodiments, the binding information may include at least one of an identification of the neighboring device and at least one binding information type.

[0048] In some embodiments, the method may further include transmitting a binding release request for unbinding with the neighboring device to the management entity, and receiving a binding release response to the binding release request from the management entity.

[0049] In some embodiments, the binding release request may include at least one of an indicator of the binding release request, an identification of the neighboring device, at least one binding information type to be released, and at least one binding release reason.

[0050] In some embodiments, the binding release response may include at least one of an acknowledgment of the binding release request and at least one binding information type to be released.

[0051] In a sixth aspect, a method is disclosed. The method may include: receiving a binding request from a first device for binding with at least one neighboring device of the first device; transmitting a first capacity request for binding capacity of the second device to a second device of the at least one neighboring device in response to the binding request; receiving a first capacity response to the first capacity request from the second device; binding the first device and the second device based on the first capacity response; and transmitting a binding response to the binding request to the first device.

[0052] In some embodiments, the binding request may include at least one of an indicator of the binding request, at least one identification of at least one neighboring device, at least one binding information type, and at least one binding reason.

[0053] In some embodiments, the binding response may include at least one of an acknowledgment or a negative acknowledgment of the binding request, at least one binding information type, and an identification of the second device.

[0054] In some embodiments, the method may further include receiving an access request for first measurement information of the first device, transmitting the access request to the second device, receiving second measurement information of the second device, and determining the first measurement information based on the second measurement information and the calibration parameters.

[0055] In some embodiments, binding the first device and the second device based on the first capacity response may include establishing an association between at least one of an identification of the first device and the second device, a binding information type, a calibration parameter, and a binding establishment time.

[0056] In some embodiments, the method may further include transmitting the first binding information to the second device, and the first binding information may include at least one of an identification of the first device and at least one binding information type.

[0057] In some embodiments, the method may also include: receiving a binding release request for unbinding the first device and the second device from one of the first device and the second device; based on the binding release request, deleting the association between the first device and at least one of the second device identifiers, binding information types, calibration parameters, and binding establishment time; transmitting a binding release response to the binding release request to one of the first device and the second device; and transmitting binding release information or binding update information to the other of the first device and the second device.

[0058] In some embodiments, the binding release request may include at least one of an indicator of the binding release request, an identification of the first device, at least one binding information type to be released, and at least one binding release reason.

[0059] In some embodiments, the binding release response may include at least one of an acknowledgment of the binding release request and at least one released binding information type.

[0060] In some embodiments, the binding release information may include at least one released binding information type.

[0061] In some embodiments, the method may also include: in response to a binding release request from a second device, transmitting a second capacity request for the binding capacity of the third device to a third device among at least one adjacent device; receiving a second capacity response to the second capacity request from the third device; and binding the first device and the third device based on the second capacity response.

[0062] In some embodiments, the binding update information may include at least one of at least one binding information type and an identification of the third device.

[0063] In some embodiments, the method may further include transmitting second binding information to the third device, and the second binding message may include at least one of an identification of the first device and at least one binding information type.

[0064] In some embodiments, the first capacity request or the second capacity request may include at least one binding information type.

[0065] In some embodiments, the first capacity response or the second capacity response may include at least one of at least one supported binding information type, at least one rejected binding information category, and at least one rejection reason.

[0066] In a seventh aspect, an apparatus is disclosed. The apparatus may include means for transmitting a binding request for binding with at least one neighboring apparatus to a management entity, and means for receiving a binding response to the binding request from the management entity.

[0067] In some embodiments, transmitting the bind request to the management entity for binding with at least one neighboring device may be triggered by a predetermined event.

[0068] In some embodiments, the binding request may include at least one of an indicator of the binding request, at least one identification of at least one neighboring device, at least one binding information type, and at least one binding reason.

[0069] In some embodiments, the binding response may include at least one of an acknowledgement or a negative acknowledgement of the binding request, at least one binding information type, and at least one identification of at least one neighboring device.

[0070] In some embodiments, the apparatus may further include means for searching for at least one neighboring device, and means for obtaining at least one identification of the at least one neighboring device.

[0071] In some embodiments, the apparatus may further include means for transmitting a binding release request for unbinding from at least one neighboring device to the management entity, and means for receiving a binding release response to the binding release request from the management entity.

[0072] In some embodiments, the binding release request may include at least one of an indicator of the binding release request, at least one binding information type to be released, and at least one binding release reason.

[0073] In some embodiments, the binding release response may include at least one of an acknowledgment of the binding release request and at least one released binding information type.

[0074] In an eighth aspect, an apparatus is disclosed. The apparatus may include means for receiving a capacity request from a management entity for binding capacity with neighboring devices, and means for transmitting a capacity response to the capacity request to the management entity.

[0075] In some embodiments, a capacity request may include at least one binding information type.

[0076] In some embodiments, the capacity response may include at least one of at least one supported binding information type, at least one rejected binding information category, and at least one rejection reason.

[0077] In some embodiments, the apparatus may further include means for receiving binding information from a management entity.

[0078] In some embodiments, the binding information may include at least one of an identification of the neighboring device and at least one binding information type.

[0079] In some embodiments, the apparatus may further include means for transmitting a binding release request for unbinding with the neighboring device to the management entity, and means for receiving a binding release response to the binding release request from the management entity.

[0080] In some embodiments, the binding release request may include at least one of an indicator of the binding release request, an identification of the neighboring device, at least one binding information type to be released, and at least one binding release reason.

[0081] In some embodiments, the binding release response may include at least one of an acknowledgment of the binding release request and at least one binding information type to be released.

[0082] In a ninth aspect, an apparatus is disclosed. The apparatus may include means for receiving a binding request from a first device for binding with at least one neighboring device of the first device, means for transmitting a first capacity request for binding capacity of the second device to a second device of the at least one neighboring device in response to the binding request, means for receiving a first capacity response to the first capacity request from the second device, means for binding the first device and the second device based on the first capacity response, and means for transmitting a binding response to the binding request to the first device.

[0083] In some embodiments, the binding request may include at least one of an indicator of the binding request, at least one identification of at least one neighboring device, at least one binding information type, and at least one binding reason.

[0084] In some embodiments, the binding response may include at least one of an acknowledgment or a negative acknowledgment of the binding request, at least one binding information type, and an identification of the second device.

[0085] In some embodiments, the apparatus may also include a device for receiving an access request to first measurement information of the first device, a device for transmitting the access request to the second device, a device for receiving second measurement information of the second device, and a device for determining the first measurement information based on the third measurement information and a calibration parameter.

[0086] In some embodiments, binding the first device and the second device based on the first capacity response may include establishing an association between at least one of an identification of the first device and the second device, a binding information type, a calibration parameter, and a binding establishment time.

[0087] In some embodiments, the apparatus may further include means for transmitting the first binding information to the second device, and the first binding information may include at least one of an identification of the first device and at least one binding information type.

[0088] In some embodiments, the device may also include a device for receiving a binding release request for unbinding the first device and the second device from one of the first device and the second device; a device for deleting the association between the identification, binding information type, calibration parameters, and binding establishment time of the first device and the second device based on the binding release request; a device for transmitting a binding release response to the binding release request to the one of the first device and the second device; and a device for transmitting binding release information or binding update information to the other of the first device and the second device.

[0089] In some embodiments, the binding release request may include at least one of an indicator of the binding release request, an identification of the first device, at least one binding information type to be released, and at least one binding release reason.

[0090] In some embodiments, the binding release response may include at least one of an acknowledgment of the binding release request and at least one released binding information type.

[0091] In some embodiments, the binding release information may include at least one released binding information type.

[0092] In some embodiments, the device may also include: a device for transmitting a second capacity request for the binding capacity of the third device to a third device among at least one adjacent device in response to a binding release request from the second device; a device for receiving a second capacity response to the second capacity request from the third device; and a device for binding the first device and the third device based on the second capacity response.

[0093] In some embodiments, the binding update information may include at least one of at least one binding information type and an identification of the third device.

[0094] In some embodiments, the apparatus may further include means for transmitting second binding information to the third device, and the second binding message may include at least one of an identification of the first device and at least one binding information type.

[0095] In some embodiments, the first capacity request or the second capacity request may include at least one binding information type.

[0096] In some embodiments, the first capacity response or the second capacity response may include at least one of at least one supported binding information type, at least one rejected binding information category, and at least one rejection reason.

[0097] In a tenth aspect, a computer-readable medium is disclosed. The computer-readable medium may include instructions stored thereon for causing an apparatus to execute transmitting a binding request for binding with at least one neighboring apparatus to a management entity, and receiving a binding response to the binding request from the management entity.

[0098] In some embodiments, transmitting the bind request to the management entity for binding with at least one neighboring device may be triggered by a predetermined event.

[0099] In some embodiments, the binding request may include at least one of an indicator of the binding request, at least one identification of at least one neighboring device, at least one binding information type, and at least one binding reason.

[0100] In some embodiments, the binding response may include at least one of an acknowledgement or a negative acknowledgement of the binding request, at least one binding information type, and at least one identification of at least one neighboring device.

[0101] In some embodiments, the computer-readable medium may further include instructions stored thereon for causing the device to further perform searching for at least one neighboring device and obtaining at least one identification of the at least one neighboring device.

[0102] In some embodiments, the computer-readable medium may also include instructions stored thereon for causing the device to further execute transmitting a binding release request to the management entity for unbinding at least one neighboring device, and receiving a binding release response to the binding release request from the management entity.

[0103] In some embodiments, the binding release request may include at least one of an indicator of the binding release request, at least one binding information type to be released, and at least one binding release reason.

[0104] In some embodiments, the binding release response may include at least one of an acknowledgment of the binding release request and at least one released binding information type.

[0105] In an eleventh aspect, a computer-readable medium is disclosed. The computer-readable medium may include instructions stored thereon for causing a device to perform receiving a capacity request from a management entity for binding capacity with a neighboring device, and transmitting a capacity response to the capacity request to the management entity.

[0106] In some embodiments, a capacity request may include at least one binding information type.

[0107] In some embodiments, the capacity response may include at least one of at least one supported binding information type, at least one rejected binding information category, and at least one rejection reason.

[0108] In some embodiments, the computer-readable medium may further include instructions stored thereon for causing the apparatus to further perform receiving binding information from a management entity.

[0109] In some embodiments, the binding information may include at least one of an identification of the neighboring device and at least one binding information type.

[0110] In some embodiments, the computer-readable medium may further include instructions stored thereon for causing the device to further execute transmitting a binding release request for unbinding from a neighboring device to a management entity, and receiving a binding release response to the binding release request from the management entity.

[0111] In some embodiments, the binding release request may include at least one of an indicator of the binding release request, an identification of the neighboring device, at least one binding information type to be released, and at least one binding release reason.

[0112] In some embodiments, the binding release response may include at least one of an acknowledgment of the binding release request and at least one binding information type to be released.

[0113] In a twelfth aspect, a computer-readable medium is disclosed. The computer-readable medium may include instructions stored thereon, which are used to cause an apparatus to perform: receiving a binding request for binding with at least one neighboring apparatus of the first apparatus from a first apparatus; transmitting a first capacity request for binding capacity of the second apparatus to a second apparatus of the at least one neighboring apparatus; receiving a first capacity response to the first capacity request from the second apparatus in response to the binding request; binding the first apparatus and the second apparatus based on the first capacity response; and transmitting a binding response to the binding request to the first apparatus.

[0114] In some embodiments, the binding request may include at least one of an indicator of the binding request, at least one identification of at least one neighboring device, at least one binding information type, and at least one binding reason.

[0115] In some embodiments, the binding response may include at least one of an acknowledgment or a negative acknowledgment of the binding request, at least one binding information type, and an identification of the second device.

[0116] In some embodiments, the computer-readable medium may also include instructions stored thereon for causing the device to further execute receiving a request to access first measurement information of a first device, transmitting the access request to a second device, receiving second measurement information of the second device, and determining the first measurement information based on the second measurement information and calibration parameters.

[0117] In some embodiments, binding the first device and the second device based on the first capacity response may include establishing an association between at least one of an identification of the first device and the second device, a binding information type, a calibration parameter, and a binding establishment time.

[0118] In some embodiments, the computer-readable medium may further include instructions stored thereon for causing the device to further execute transmitting first binding information to the second device, and the first binding information may include at least one of an identification of the first device and at least one binding information type.

[0119] In some embodiments, the computer-readable medium may also include instructions stored thereon, which are used to cause the device to further execute: receiving a binding release request for unbinding the first device from the second device from one of the first device and the second device; based on the binding release request, deleting the association between at least one of the identification, binding information type, calibration parameter and binding establishment time of the first device and the second device; transmitting a binding release response to the binding release request to the one of the first device and the second device; and transmitting binding release information or binding update information to the other of the first device and the second device.

[0120] In some embodiments, the binding release request may include at least one of an indicator of the binding release request, an identification of the first device, at least one binding information type to be released, and at least one binding release reason.

[0121] In some embodiments, the binding release response may include at least one of an acknowledgment of the binding release request and at least one released binding information type.

[0122] In some embodiments, the binding release information may include at least one released binding information type.

[0123] In some embodiments, the computer-readable medium may also include instructions stored thereon, which are used to cause the device to further execute: transmitting a second capacity request for the bound capacity of the third device to a third device among at least one neighboring device; receiving a second capacity response to the second capacity request from the third device in response to a binding release request from the second device; and binding the first device and the third device based on the second capacity response.

[0124] In some embodiments, the binding update information may include at least one of at least one binding information type and an identification of the third device.

[0125] In some embodiments, the computer-readable medium may further include instructions stored thereon for causing the device to further execute transmitting second binding information to a third device, and the second binding message may include at least one of an identification of the first device and at least one binding information type.

[0126] In some embodiments, the first capacity request or the second capacity request may include at least one binding information type.

[0127] In some embodiments, the first capacity response or the second capacity response may include at least one of at least one supported binding information type, at least one rejected binding information category, and at least one rejection reason.

[0128] Other features and advantages of exemplary embodiments of the present disclosure will also be apparent from the following description of specific embodiments when read in conjunction with the accompanying drawings, which illustrate, by way of example, the principles of exemplary embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0129] Some example embodiments will now be described, by way of non-limiting examples, with reference to the accompanying drawings.

[0130] Figure 1A and Figure 1B An example scenario is shown in which embodiments of the present disclosure may be implemented.

[0131] Figure 2 An exemplary sequence diagram of a device binding establishment process according to an embodiment of the present disclosure is shown.

[0132] Figure 3 An exemplary sequence diagram of a location and / or awareness information access process in an established binding according to an embodiment of the present disclosure is shown.

[0133] Figure 4 An exemplary sequence diagram of a device unbinding process according to an embodiment of the present disclosure is shown.

[0134] Figure 5 An exemplary sequence diagram of a device unbinding process according to another embodiment of the present disclosure is shown.

[0135] Figure 6 An exemplary sequence diagram of a device binding update process according to an embodiment of the present disclosure is shown.

[0136] Figure 7 A flow chart illustrating an example method for binding neighboring devices according to an embodiment of the present disclosure is shown.

[0137] Figure 8 A flow chart illustrating an example method for binding neighboring devices according to an embodiment of the present disclosure is shown.

[0138] Fig. 9 A flow chart illustrating an example method for binding neighboring devices according to an embodiment of the present disclosure is shown.

[0139] Fig.10 A block diagram illustrating an apparatus for binding and unbinding neighboring apparatuses according to an embodiment of the present disclosure is shown.

[0140] Fig.11 A block diagram illustrating an apparatus for binding and unbinding neighboring apparatuses according to an embodiment of the present disclosure is shown.

[0141] Fig.12 A block diagram illustrating an apparatus for binding and unbinding neighboring apparatuses according to an embodiment of the present disclosure is shown.

[0142] Fig.13 A block diagram illustrating an apparatus for binding neighboring devices according to an embodiment of the present disclosure is shown.

[0143] Fig.14 A block diagram illustrating an apparatus for binding neighboring devices according to an embodiment of the present disclosure is shown.

[0144] Fig.15 A block diagram illustrating an apparatus for binding neighboring devices according to an embodiment of the present disclosure is shown.

[0145] Throughout the drawings, the same or similar reference numerals denote the same or similar elements, and repeated description of the same elements will be omitted. DETAILED DESCRIPTION

[0146] Hereinafter, some example embodiments are described in detail with reference to the accompanying drawings. In order to provide a thorough understanding of various concepts, the following description includes specific details. However, it is obvious to those skilled in the art that these concepts can be practiced without these specific details. In some cases, well-known circuits, techniques, and components are shown in block diagram form to avoid obfuscation of the concepts and features described.

[0147] Figure 1A and Figure 1B An example scenario is shown in which embodiments of the present disclosure may be implemented. Figure 1A An example transport scenario is shown, in which a vehicle 100 carries a plurality of objects 110, 120, 130, and 140. Objects 110, 120, 130, and 140 are transported together and therefore belong to the same transport group. Figure 1BAn example stacking scenario is shown in which a plurality of objects 160, 170, 180, and 190 are stacked in a warehouse 150. Objects 160, 170, 180, and 190 are stacked together and thus belong to the same stacking group.

[0148] Objects 110, 120, 130, and 140 have devices 111, 121, 131, and 141, respectively, and objects 160, 170, 180, and 190 have devices 161, 171, 181, and 191, respectively. Devices 111, 121, 131, and 141 and devices 161, 171, 181, and 191 may measure position-related information such as position, velocity, acceleration, etc., and / or environmental perception-related information such as atmospheric pressure, temperature, humidity, etc., of objects 110, 120, 130, and 140, respectively.

[0149] For example, the devices 111, 121, 131, and 141 may measure the same or similar position-related information of the respective objects 110, 120, 130, and 140 in the same transport group, such as position, velocity, acceleration, etc. The devices 161, 171, 181, and 191 may, for example, measure the same or similar environmental perception-related information of the respective objects 160, 170, 180, and 190 in the same stacking group, such as atmospheric pressure, temperature, humidity, etc.

[0150] When a device suffers from low power, sensor failure, sensor loss, poor communication channel, etc., it may request a management entity (e.g., a location server or location management entity in a core network) to bind or connect to one or more other devices and utilize these other devices to perform positioning and awareness measurements. For example, such a request may be a non-access stratum message.

[0151] For example, if device 121 does not have enough power to measure the speed of object 120, it may request the management entity to bind to one or more devices on other objects in the same transport group, such as devices 111, 131, and 141. If the management entity binds device 121 to device 141 for speed, device 141 may measure the speed of object 140, and may determine the speed measurement information of object 120 based on the measured speed of object 140.

[0152] For example, if device 161 has a sensor failure and cannot measure the temperature and humidity of object 160, it may request the management entity to bind to one or more devices on other objects in the same stacking group, such as devices 171, 181, and 191. If the management entity binds device 161 to device 171 with respect to temperature and humidity, device 171 may measure the temperature and humidity of object 170, and the temperature and temperature measurement information of object 160 may be based on the measured temperature and humidity of object 170.

[0153] A device can be bound to different devices for different binding information types such as atmospheric pressure, temperature, humidity, etc. Figure 1B In the above example scenario, optionally, the management entity may bind device 161 to device 181 in terms of temperature, and bind device 161 to device 191 in terms of humidity, device 181 may measure the temperature of object 180 and device 191 may measure the humidity of object 190, and the temperature and humidity measurement information of object 160 may be based on the measured temperature of object 180 and the measured humidity of object 190.

[0154] In an embodiment, the object may be, for example, cargo or other items, such as a box, etc., and the device may be, for example, a tag device, such as a super tag. A device that cannot be measured and is bound to other devices, such as Figure 1A and Figure 1B The devices 121 and 161 in the above scenario may be, for example, lazy tags. The device bound to the lazy tag for measurement, for example Figure 1A and Figure 1B The device 141 and the devices 171, 181, and 191 in the above-mentioned scenario may be, for example, binding tags. The management entity may be, for example, a location management function (LMF), a perception management entity, or other Internet of Things (IoT) management functions. The vehicle 100 and the warehouse 150 are shown as examples, and it is understood that the example embodiments may be applicable to other carriers and platforms, such as ships, aircraft, workshops, etc. In addition, in Figure 1A or Figure 1B In the scenario of FIG. 1 , four devices attached to four objects are shown as examples, and it can be understood that the example embodiments may be applicable to more or fewer devices.

[0155] In some embodiments, the device of the object may communicate with the management entity via, for example, an access network (eg, including one or more base stations), and for the sake of brevity, descriptions regarding the access network are omitted.

[0156] Figure 2 An exemplary sequence diagram of a device binding establishment process according to an embodiment of the present disclosure is shown. Figure 2 , the device 210 may be, for example, referring to Figure 1A One of the devices 111, 121, 131 and 141 described above, or reference Figure 1B One of the devices 161, 171, 181 and 191 described.

[0157] The device binding establishment process may be initiated by the device 210 transmitting a binding request 214, which may be triggered by a predetermined event. The predetermined event may be, for example, low power being measured, failure of a positioning or some environmental sensing sensor, absence of a positioning or some environmental sensing sensor, lower quality of a communication channel, etc.

[0158] For example, device 210 may transmit a bind request 214 to management entity 220, which may be a reference Figure 1A or Figure 1B The binding request 214 may request the management entity 220 to bind the binding request 214 with at least one neighboring device.

[0159] For example, the binding request 214 may include at least one of an indicator of the binding request 214, at least one identifier of at least one neighboring device, at least one binding information type, and at least one binding reason. The at least one binding information type may be information of the corresponding object to be measured by the device 210, and includes position-related information such as position, speed, acceleration, and / or environmental perception-related information such as atmospheric pressure, temperature, humidity, and the like. At least one binding reason may be a reason why the device 210 cannot measure the corresponding object, and includes, for example, low power, poor channel quality, sensor failure, sensor loss, and the like.

[0160] In order to obtain at least one identification of at least one neighboring device, in operation 212, the device 210 may search for at least one neighboring device from the same transport or stacking group to find the at least one identification by means of appropriate technology, such as Bluetooth, wireless fidelity (Wi-Fi), Zigbee, side link communication, etc. Alternatively or additionally, the device 210 may also be manually configured with at least one identification of the at least one neighboring device by the transport or stacking manager.

[0161] Upon receiving the binding request 214, the management entity 220 may transmit a first capacity request 222 for the binding capacity of the device 230 to the device 230 in the at least one neighboring device. The device 230 may be an example of one of the at least one neighboring device. The first capacity request 222 may include, for example, at least one binding information type in the binding request 214. With the help of the first capacity request 222, the management entity 220 may request the binding capacity of the device 230 in the form of polling based on at least one identification of at least one neighboring device in the binding request 214. The first capacity request 222 may indicate to the device 230 which location and / or perception information type is to be bound to the device 210. The binding capacity may include the power state and the working state of at least one location and / or perception sensor of the device 230 corresponding to the at least one binding information type. The binding capacity may also include allowing or prohibiting the device 230 from binding with the device 210, which may be set by, for example, the owner of the corresponding object of the device 230.

[0162] After receiving the first capacity request 222, the device 230 may make a first capacity response 232 to the first capacity request. The first capacity response 232 may indicate the binding capacity of the device 230 and may include at least one of at least one supported binding information type, at least one rejected binding information category, and at least one rejection reason.

[0163] For example, if the first capacity request 222 includes binding information types for temperature and humidity, and the device 230 has sufficient power and properly functioning sensors for the respective binding information types and is allowed to bind, the first capacity response 232 may include, for example, supported binding information types for temperature and humidity. If the device 230 has sufficient power and properly functioning sensors for temperature, but has a faulty sensor for humidity or is prohibited from binding to a binding information type for humidity, the first capacity response 232 may include a supported binding information type for temperature, a rejected binding information type for humidity, and a corresponding rejection reason, such as a sensor failure or disabling for the binding information type for humidity.

[0164] The device 230 may transmit the first capacity response 232 to the management entity 220. After collecting the first capacity response 232, in operation 224, the management entity 220 may bind the device 210 with the device 230 based on the first capacity response 232.

[0165] For example, management entity 220 may align binding request 214 from device 210 with first capacity response 232 from device 230. For a binding information type in binding request 214, if a first capacity response 232 supports binding request 214, management entity 220 may bind device 210 with device 230 for the binding information type.

[0166] In some examples, regarding the binding information type, management entity 220 may measure device 210 and device 230 in at least one neighboring device that satisfies binding request 214, compare the measurement information difference between device 210 and device 230 in the at least one neighboring device, and select device 230 with the smallest measurement information difference to bind to device 210.

[0167] Alternatively, the management entity 220 may select the device 230 to be bound to the device 210 based on other criteria, such as the device 230 with the greatest power, the device 230 with the closest distance to the device 210, and the like.

[0168] For example, in the event that more than one capacity response satisfies the binding request 214 regarding the binding information type, if the power of device 230 is higher than the power of other devices that make satisfactory capacity responses, or if device 230 is closer to device 210 than other devices that make satisfactory capacity responses, then the management entity 220 may select device 230 as the device to be bound to device 210.

[0169] In operation 224 , regarding the binding information type, the management entity 220 may obtain measurement information of the device 210 and the device 230 , and calculate a measurement information difference between the device 210 and the device 230 as a calibration parameter.

[0170] For example, regarding the binding information type of the location, the management entity 220 may calculate the location measurement information difference (Δx, Δy, Δz) between the device 210 and the device 230 as a calibration parameter for location calibration. For example, the management entity 220 may obtain the location (x1, y1, z1) of the device 210 and the location (x0, y0, z0) of the device 230, and calculate Δx=x1-x0, Δy=y1-y0, and Δz=z1-z0 as the calibration parameters of the location.

[0171] For example, regarding the binding information type of temperature, the management entity 220 may calculate the temperature measurement information difference (ΔT) between the device 210 and the device 230 as a calibration parameter for temperature calibration. For example, the management entity 220 may obtain the temperature T1 of the device 210 and the temperature T0 of the device 230, and calculate ΔT=T1-T0 as the calibration parameter for temperature.

[0172] Alternatively or additionally, the calibration parameters may be configured by, for example, a shipping or stacking manager. For example, a shipping or stacking manager may input calibration parameters for a corresponding binding information type based on a large amount of historical data.

[0173] Also in operation 224 , in establishing the binding between device 210 and device 230 , management entity 220 may establish an association between at least one of identifications of device 210 and device 230 , binding information types, calibration parameters, and binding establishment time.

[0174] The management entity 220 may make a binding response 226 corresponding to the binding request 214 and transmit the binding response 226 to the device 210. The binding response 226 may include at least one of a confirmation or a negative confirmation of the binding request 214, at least one binding information type, and an identification of the device 230. If the binding request 214 includes binding information types such as position and speed, and the management entity 220 binds the device 230 based on the position instead of the speed, the binding response 226 may include a confirmation of the binding request 214 for the position and the identification of the device 230, and a negative confirmation of the binding request 214 for the speed. It is understood that the binding response 226 may be in other forms based on different binding results.

[0175] The management entity 220 may further transmit first binding information 228 to the device 230. The first binding information 228 may include at least one of an identification of the device 210 and at least one binding information type. With the aid of the first binding information 228, the device 230 may be informed of, for example, the identification of the device 210 and at least one binding information type with which it is bound.

[0176] Figure 3 An exemplary sequence diagram of a location and / or awareness information access process in an established binding according to an embodiment of the present disclosure is shown.

[0177] refer to Figure 3 , assuming that application 310 wants to obtain measurement information 326 about the location, temperature, etc. of device 210, application 310 may transmit access request 312 to management entity 220, and access request 312 may include, for example, the identification of device 210 and the desired measurement information type. Application 310 may be, for example, a user-level application, such as an application for an owner of an object having device 210 or a transport or stack manager for monitoring the measurement information of device 210.

[0178] Upon receiving the access request 312, the management entity 220 may search the binding table 320 for a binding item that matches the access request 312. The binding table 320 may be established in operation 224 and maintained by the management entity 220. The binding table 320 may include a list of at least one binding item corresponding to the at least one association established by the management entity 220 in operation 224. For example, the binding item in the binding table 320 may include information such as an identification of the device 210, an identification of the device 230, a binding information type, a calibration parameter, a binding establishment time, etc. If the identification of the device 210 can be found in the binding item in the remapping operation 322 and the desired measurement information type matches the binding information type in the binding item, the management entity 220 may make an access request 314 based on the access request 312 and route the access request 314 to the device 230 instead of the device 210 based on the identification of the device 230 in the binding item. For example, the access address for the access request 312 may be the device 210, and the access address for the access request 314 may be changed to the device 230.

[0179] In response to the access request 314 routed from the management entity 220 , the device 230 may measure the binding information type and transmit the measurement information 332 to the management entity 220 .

[0180] Upon receiving the measurement information 332 of the device 230, the management entity 220 may make the measurement information 326 of the device 210 based on the measurement information 332 without calibration, and transmit the measurement information 326 to the application 310. Alternatively, the management entity 220 may determine the measurement information 326 of the device 210 based on the measurement information 332 of the device 230 and the calibration parameters, and transmit the measurement information 326 to the application 310.

[0181] For example, the management entity 220 may calibrate 324 the measurement information 332 based on corresponding calibration parameters, such as the position measurement information difference (Δx, Δy, Δz) or the temperature measurement information difference (ΔT) in the binding item to determine the measurement information 326 and transmit it to the application 310. For example, in the case where the measurement information is for position and the measurement information 332 is (x0', y0', z0'), the measurement information 326 may be (x0'+Δx, y0'+Δy, z0'+Δz). For example, in the case where the measurement information is for temperature and the measurement information 332 is T0', the measurement information 326 may be T0'+ΔT.

[0182] Remapping 322 may be transparent to application 310. For example, application 310 may not be aware that measurement information 326 is determined from measurement information 332 of device 230 and may assume that measurement information 326 comes from device 210, for example.

[0183] Figure 4 An exemplary sequence diagram of a device unbinding process according to an embodiment of the present disclosure is shown. After the binding between device 210 and device 230 is established, device 210 or device 230 may initiate an unbinding process to release the binding. Some events may trigger device 210 to initiate the unbinding process. The triggering event may be that the reason for requesting the binding is eliminated on device 210, such as power recovery, communication channel quality recovery, sensor failure recovery, etc. The triggering event may also be that the binding is no longer useful, for example, device 210 detects that the location of device 230 has changed, so that the measurement information of device 230 is no longer useful for determining the measurement information of device 210.

[0184] refer to Figure 4 , when the unbinding process is initiated by the device 210, the device 210 may transmit a binding release request 412 to the management entity 220 for unbinding with the device 230. The binding release request 412 may include at least one of an indicator 412 of the binding release request, at least one binding information type to be released, and at least one binding release reason.

[0185] Device 210 may indicate a complete binding release or a partial binding release to management entity 220. For example, if device 210 has bound to device 230 for a binding information type of atmospheric pressure, temperature, and humidity due to low power, and device 210 desires to release the binding for the binding information type of atmospheric pressure, temperature, and humidity with device 230 due to power restoration on device 210, binding release request 412 may include an indicator 412 of a binding release request, an identifier of the binding information type to be released including atmospheric pressure, temperature, and humidity, and a binding release reason for power restoration.

[0186] For example, if due to a sensor failure, device 210 has bound with device 230 for binding information types of atmospheric pressure, temperature, and humidity, and due to sensor failure recovery of temperature and humidity measurement, device 210 desires to release the binding of binding information types of temperature and humidity with device 230, and maintain the binding for atmospheric pressure because, for example, atmospheric pressure measurement is still erroneous, then the binding release request 412 may include an indicator 412 of the binding release request, the binding information types to be released including temperature and humidity, and the binding release reason of sensor failure recovery. It is understood that device 210 may also request to release the binding with a certain neighboring device and maintain the binding with a certain other neighboring device.

[0187] In response to the binding release request 412, the management entity 220 may unbind the device 210 from the device 230 in operation 422. For example, based on the binding release request 412, the management entity 220 may Figure 3, wherein the binding item includes, for example, the binding information type to be released in the binding release request. For example, the association between at least one of the identification of the device 210 and the device 230, the binding information type, the calibration parameter, and the binding establishment time corresponding to the binding item can be deleted.

[0188] The management entity 220 may make a binding release response 424 corresponding to the binding release request 412 and transmit the binding release response 422 to the device 210. The binding release response 424 may include at least one of an acknowledgment of the binding release request 412 and at least one released binding information type.

[0189] The management entity 220 may further transmit binding release information 426 to the device 230. The binding release information 426 may include at least one released binding information type.

[0190] Figure 5 An exemplary sequence diagram of a device unbinding process according to another embodiment of the present disclosure is shown. Some events may trigger device 230 to initiate the unbinding process. The triggering event may be that device 230 cannot be bound to device 210. For example, the power or communication channel quality of device 230 is low, a sensor failure of device 230 occurs, etc. The triggering event may also be that device 230 is not allowed to bind to device 210 for certain binding information types, etc.

[0191] refer to Figure 5 , when the unbinding process is initiated by the device 230, the device 230 may transmit a binding release request 532 for unbinding from the device 210 to the management entity 220. The binding release request 532 may include at least one of an indicator of the binding release request 532, an identifier of the device 210, at least one binding information type to be released, and at least one binding release reason.

[0192] Similar to the binding release request 412 from the device 210, with the aid of the binding release request 532, the device 230 may instruct the management entity 220 to fully release or partially release the binding with the device 210. For example, assuming that the device 230 has been bound to the device 210 for the binding information type of position, speed and acceleration, the device 230 may request to unbind the device 210 for the binding information type of position, speed and acceleration due to, for example, low power of the device 230, or the device 230 may request to unbind the device 210 for the speed and acceleration due to, for example, sensor failure of the speed and acceleration measurement. It is understood that the device 230 may also request to release the binding with a certain neighboring device and maintain the binding with another neighboring device.

[0193] In response to the binding release request 532, the management entity 220 may unbind the device 230 from the device 210 in operation 522. Operation 522 is similar to operation 422. For example, the management entity 220 may Figure 3 The binding table 320 shown in FIG. 5 is deleted, including, for example, a binding entry of the type of binding information to be released in the binding release request 532, thereby deleting the association corresponding to the binding entry. The details of operation 522 may be referred to above regarding Figure 4 The description of operation 422 shown in FIG. 4 is provided above, and a repeated description thereof is omitted here.

[0194] The management entity 220 may make a binding release response 526 corresponding to the binding release request 532 and transmit the binding release response 522 to the device 230. The binding release response 526 may include at least one of an acknowledgement of the binding release request 532 and at least one released binding information type.

[0195] The management entity 220 may further transmit binding release information 524 to the device 210. The binding release information 524 may include at least one released binding information type.

[0196] Figure 6 An exemplary sequence diagram of a device binding update process according to an embodiment of the present disclosure is shown.

[0197] Return to reference Figure 5 In the case where the device 230 initiates the unbinding process, in response to the binding release request 532 from the device 230, in addition to operation 522, the management entity 220 may also try to find another neighboring device to bind with the device 210 for the binding information type released by the device 230. Return to Reference Figure 2 For example, in the case where the binding request 214 from the device 210 includes at least one identification of at least one neighboring device in addition to the identification of the device 230, reference Figure 6 , the management entity 220 may transmit a second capacity request 622 for the binding capacity of the device 610 to the device 610 in the at least one neighboring device identified in the binding request 214 .

[0198] Device 610 may be an example of one of at least one neighboring device other than device 230. Second capacity request 622 may include at least one binding information type to be released for device 230. With the aid of second capacity request 622, management entity 220 may request the binding capacity of device 610 in the form of polling based on at least one identification of at least one neighboring device in binding request 214.

[0199] The second capacity request 622 may be similar to the first capacity request 222, and the details of the second capacity request 622 may be referred to above with respect to Figure 2 The description of the first capacity requirement 222 shown in FIG. 2 is omitted here, and a repeated description thereof is omitted here.

[0200] Upon receiving the second capacity request 622, the device 610 may make a second capacity response 612 in response to the second capacity request 622. The second capacity response 612 may indicate the binding capacity of the device 610 and may include at least one of at least one supported binding information type, at least one rejected binding information category, and at least one rejection reason.

[0201] The second capacity request 622 may be similar to the first capacity request 222, and the details of the second capacity request 622 may be referred to above with respect to Figure 2 The description of the first capacity requirement 222 shown in FIG. 2 is omitted here, and a repeated description thereof is omitted here.

[0202] Device 610 may transmit second capacity response 612 to management entity 220. After collecting second capacity response 612, in operation 624, management entity 220 may bind device 210 with device 610 based on second capacity response 612.

[0203] Operation 624 may be similar to operation 224, and the details of operation 624 may refer to the above description of Figure 2 The description of operation 224 shown in FIG. 2 is omitted here, and a repeated description thereof is omitted here.

[0204] exist Figure 2 In the case where the binding request 214 shown in FIG. 2 does not include the identifier of the neighboring device other than the identifier of the device 230, the management entity 220 may not attempt to find another neighboring device to bind with the device 210 for the type of binding information released by the device 230, and thus the second capacity request 622, the second capacity response 612, and the related operations including the operation 624 may be omitted. In this case, the management entity 220 may directly transmit the second capacity request 622 to the device 210. Figure 5 Binding release information 524 shown in .

[0205] Alternatively, after collecting the second capacity response 612, if in operation 624 the management entity 220 finds that the binding information type in the second capacity request 622 is not supported according to the second capacity response 612, the management entity 220 may Figure 5 The binding release information 524 is shown transmitted to the device 210.

[0206] In operation 624, regardless of whether the management entity 220 can bind the device 210 to the device 610, the management entity 220 can make a binding release response 526 corresponding to the binding release request 532 and transmit the binding release response 526 to the device 230. The binding release response 526 may include an acknowledgment of the binding release request 532 and at least one of the at least one released binding information type.

[0207] In the case where the management entity 220 binds the device 210 with the device 610 in operation 624, the management entity 220 may transmit binding update information 626 to the device 210. The binding update information may include at least one of at least one binding information type and an identification of the device 610. The at least one binding information type may be a binding information type regarding releasing the binding from the device 230 in operation 522 and establishing the binding with the device 610 in operation 624.

[0208] The management entity 220 may further transmit second binding information 628 to the device 610. The second binding information 228 may include at least one of an identification of the device 210 and at least one binding information type. With the aid of the first binding information 228, the device 230 may be informed of, for example, the identification of the device 210 and at least one binding information type with which the device 230 is bound to the device 210.

[0209] In an embodiment, according to, for example, the Long Term Evolution (LTE) Positioning Protocol (LPP), the communication of requests, responses, information, etc. between the device 210, the management entity 220, the device 230, the device 610, etc. may be via, for example, one or more non-access stratum (NAS) messages. It is understood that the communication may be via other suitable protocols, such as a machine type communication (MTC) protocol, such as a cellular Internet of Things protocol.

[0210] Figure 7 A flow chart illustrating an example method 700 for binding neighboring devices according to an embodiment of the present disclosure is shown. The example method 700 may be performed at a device such as device 210, for example.

[0211] refer to Figure 7 , the example method 700 may include an operation 710 of transmitting a binding request for binding with at least one neighboring device to a management entity, and an operation 720 of receiving a binding response to the binding request from the management entity.

[0212] Operation 710 may be triggered by a predetermined event, such as low power being measured, failure of positioning or some environment perception sensors, loss of positioning or some environment perception sensors, lower quality of a communication channel, etc.

[0213] The management entity may be, for example, the management entity 220, the binding request may be, for example, the binding request 214, the binding response may be, for example, the binding response 226, and the at least one neighboring device may include, for example, the device 230. For details of operations 710 and 720, reference may be made to the above description of operations related to the binding request 214 and the binding response 226, and a repeated description thereof is omitted here.

[0214] In one embodiment, the binding request may include at least one of an indicator of the binding request, at least one identifier of at least one neighboring device, at least one binding information type, and at least one binding reason. For more details, reference may be made to the above description of the binding request 214, and a repeated description thereof will be omitted here.

[0215] In one embodiment, the binding response may include at least one of a confirmation or negative confirmation of the binding request, at least one binding information type, and at least one identifier of at least one neighboring device. For more details, refer to the above description of the binding response 226, and its repeated description will be omitted here.

[0216] In one embodiment, the exemplary method 700 may further include an operation of searching for at least one neighboring device and an operation of obtaining at least one identification of at least one neighboring device. For more details, reference may be made to the above description of operation 212, and a repeated description thereof will be omitted here.

[0217] In one embodiment, the example method 700 may also include an operation of transmitting a binding release request for unbinding from at least one neighboring device to a management entity, and an operation of receiving a binding release response to the binding release request from the management entity. The binding release request may be, for example, a binding release request 412, and the binding release response may be, for example, a binding release response 424. The details of the operation may refer to the above description of the operation related to the binding release request 412 and the binding release response 424, and its repeated description is omitted here.

[0218] In one embodiment, the binding release request may include at least one of an indicator of the binding release request, at least one binding information type to be released, and at least one binding release reason. For more details, refer to the above description of the binding release request 412, and its repeated description will be omitted here.

[0219] In one embodiment, the binding release response may include at least one of an acknowledgment of the binding release request and at least one type of released binding information. For more details, reference may be made to the above description of the binding release response 424, and its repeated description will be omitted here.

[0220] Figure 8A flow chart illustrating an example method 800 for binding neighboring devices according to an embodiment of the present disclosure is shown. The example method 800 may be performed at a device such as device 230, for example.

[0221] refer to Figure 8 , the example method 800 may include an operation 810 of receiving a capacity request for binding capacity with a neighboring device from a management entity, and an operation 820 of transmitting a capacity response to the capacity request to the management entity.

[0222] The management entity may be, for example, the management entity 220, the capacity request may be, for example, the first capacity request 222, the capacity response may be, for example, the first capacity response 232, and the neighboring device may be, for example, the device 210. For details of operations 810 and 820, reference may be made to the above description of operations related to the first capacity request 222 and the first capacity response 232, and a repeated description thereof is omitted here.

[0223] In one embodiment, the capacity request may include at least one binding information type. For more details, reference may be made to the above description of the first capacity request 222, and a repeated description thereof will be omitted here.

[0224] In one embodiment, the capacity response may include at least one supported binding information type, at least one rejected binding information category, and at least one rejection reason. For more details, refer to the description of the first capacity response 232 above, and the repeated description thereof will be omitted here.

[0225] In one embodiment, the exemplary method 800 may further include an operation of receiving binding information from a management entity. The binding information may be, for example, the first binding information 228. The details of the operation may refer to the above description of the operation related to the first binding information 228, and its repeated description is omitted here.

[0226] In one embodiment, the binding information may include at least one of an identifier of the neighboring device and at least one binding information type. For more details, reference may be made to the above description of the first binding information 228, and a repeated description thereof will be omitted here.

[0227] In one embodiment, the example method 800 may also include an operation of transmitting a binding release request for unbinding from a neighboring device to a management entity, and an operation of receiving a binding release response to the binding release request from the management entity. The binding release request may be, for example, a binding release request 532, and the binding release response may be, for example, a binding release response 526. The details of the operation may refer to the above description of the operation related to the binding release request 532 and the binding release response 526, and its repeated description is omitted here.

[0228] In one embodiment, the binding release request may include an indicator of the binding release request, an identifier of the neighboring device, at least one binding information type to be released, and at least one binding release reason. For more details, reference may be made to the above description of the binding release request 532, and its repeated description will be omitted here.

[0229] In one embodiment, the binding release response may include at least one of an acknowledgement of the binding release request and at least one binding information type to be released. For more details, reference may be made to the above description of the binding release response 526, and its repeated description will be omitted here.

[0230] Fig. 9 A flow chart illustrating an example method 900 for binding neighboring devices according to an embodiment of the present disclosure is shown. The example method 900 may be performed at a device such as the management entity 220, for example.

[0231] refer to Fig. 9 , example method 900 may include: operation 910, receiving a binding request from a first device for binding with at least one neighboring device of the first device; operation 920, transmitting a first capacity request for binding capacity of the second device to a second device of the at least one neighboring device in response to the binding request; operation 930, receiving a first capacity response to the first capacity request from the second device; operation 940, binding the first device and the second device based on the first capacity response; and operation 950, transmitting a binding response to the binding request to the first device.

[0232] The first device may be, for example, device 210, the second device may be, for example, device 230, the binding request may be, for example, binding request 214, the first capacity request may be, for example, first capacity request 222, the first capacity response may be, for example, first capacity response 232, and the binding response may be, for example, binding response 226.

[0233] For details of operation 910, refer to the above description of the operation of binding request 214, for details of operation 920, refer to the above description of the operation of first capacity request 222, and for details of operation 930, refer to the above description of the operation related to first capacity response 232, for details of operation 940, refer to the above description of operation 224, and for details of operation 950, refer to the above description of the operation related to binding response 226, and repeated descriptions thereof are omitted here.

[0234] In one embodiment, the binding request may include at least one of an indicator of the binding request, at least one identifier of at least one neighboring device, at least one binding information type, and at least one binding reason. For more details, reference may be made to the above description of the binding request 214, and a repeated description thereof will be omitted here.

[0235] In one embodiment, the binding response may include at least one of a confirmation or negative confirmation of the binding request, at least one binding information type, and an identification of the second device. For more details, refer to the above description of the binding response 226, and its repeated description will be omitted here.

[0236] In one embodiment, the example method 900 may further include an operation of receiving an access request for first measurement information of a first device, an operation of transmitting the access request to a second device, an operation of receiving second measurement information of the second device, and an operation of determining the first measurement information based on the second measurement information and the calibration parameter. The access request may be, for example, the access request 312, the first measurement information may be, for example, the measurement information 326, and the second measurement information may be, for example, the measurement information 332. The details of the operation may refer to the above description of the operation related to the access request 312, the measurement information 326, the measurement information 332, the binding table 320, the remapping 322, and the calibration 324, and the repeated description thereof is omitted here.

[0237] In one embodiment, binding the first device and the second device based on the first capacity response may include establishing an association between at least one of an identifier of the first device and the second device, a binding information type, a calibration parameter, and a binding establishment time. For more details, refer to the above description of operation 224, and a repeated description thereof will be omitted here.

[0238] In one embodiment, the example method 900 may further include an operation of transmitting first binding information to the second device, and the first binding information may include at least one of an identifier of the first device and at least one binding information type. The first binding information may be the first binding information 228. For more details, refer to the above description of the first binding information 228, and its repeated description will be omitted here.

[0239] In one embodiment, the example method 900 may also include: an operation of receiving a binding release request for unbinding the first device from the second device from one of the first device and the second device; based on the binding release request, deleting an association between at least one of an identification, a binding information type, a calibration parameter, and a binding establishment time of the first device and the second device; an operation of transmitting a binding release response to the binding release request to the one of the first device and the second device; and an operation of sending binding release information or binding update information to the other of the first device and the second device.

[0240] The binding release request may be, for example, the binding release request 412 or the binding release request 532, the binding release response may be, for example, the binding release response 424 or the binding release response 526, the binding release information may be, for example, the binding release information 426 or the binding release information 524, and the binding update information may be, for example, the binding update information 626. For details of the operation, reference may be made to the above description of the operations related to the binding release request 412, the binding release request 532, the binding release response 424, the binding release response 526, the binding release information 426, the binding release information 524, the binding update information 626, and the operation 522, and a repeated description thereof will be omitted here.

[0241] In one embodiment, the binding release request may include an indicator of the binding release request, an identifier of the first device, at least one binding information type to be released, and at least one binding release reason. For more details, reference may be made to the above description of the binding release request 412 or the binding release request 532, and its repeated description will be omitted here.

[0242] In one embodiment, the binding release response may include at least one of the confirmation of the binding release request and at least one of the released binding information types. For more details, reference may be made to the description of the binding release response 424 or the binding release response 526 above, and its repeated description will be omitted here.

[0243] In one embodiment, the binding release information may include at least one type of released binding information. For more details, reference may be made to the above description of the binding release information 426 or the binding release information 524, and a repeated description thereof will be omitted here.

[0244] In one embodiment, the example method 900 may also include: in response to a binding release request from a second device, transmitting a second capacity request for the binding capacity of the third device to a third device among at least one adjacent device; receiving a second capacity response to the second capacity request from the third device; and binding the first device and the third device based on the second capacity response.

[0245] The third device may be, for example, device 610, the second capacity request may be, for example, second capacity requirement 622, the binding release request may be, for example, binding release requirement 532, and the second capacity response may be, for example, second capacity response 612. For details of the operation, reference may be made to the above description of the operations related to the second capacity request 622, the binding release request 532, and the second capacity response 612, and operation 624, and a repeated description thereof will be omitted here.

[0246] In one embodiment, the binding update information may include at least one of at least one binding information type and an identifier of the third device. For more details, reference may be made to the above description of the binding update information 626, and a repeated description thereof will be omitted here.

[0247] In one embodiment, the example method 900 may further include an operation of transmitting second binding information to a third device, and the second binding message includes at least one of an identifier of the first device and at least one binding information type. The second binding information may be a second binding message 628. For more details, reference may be made to the above description of the second binding information 628, and its repeated description will be omitted here.

[0248] In one embodiment, the first capacity request or the second capacity request may include at least one binding information type. For more details, reference may be made to the above description of the first capacity request 222 or the second capacity request 622, and a repeated description thereof will be omitted here.

[0249] In one embodiment, the first capacity response or the second capacity response includes at least one supported binding information type, at least one rejected binding information category, and at least one rejection reason. For more details, refer to the above description of the first capacity response 232 or the second capacity response 612, and the repeated description thereof will be omitted here.

[0250] Fig.10 A block diagram showing an apparatus for binding and unbinding neighboring apparatuses according to an embodiment of the present disclosure is shown. For example, the apparatus may be at least a part of the apparatus 210 in the above example.

[0251] like Fig.10 As shown in FIG. 1 , the example apparatus 1000 may include at least one processor 1010 and at least one memory 1020 that may include computer program code 1030. The at least one memory 1020 and the computer program code 1030 may be configured to use the at least one processor 1010 to cause the apparatus 1000 to at least perform the above-described example method 700.

[0252] In various example embodiments, at least one processor 1010 in the example device 1000 may include, but is not limited to, at least one hardware processor, including at least one microprocessor such as a central processing unit (CPU), a portion of at least one hardware processor, and any other suitable special-purpose processor, such as a special-purpose processor developed based on, for example, a field programmable gate array (FPGA) and an application-specific integrated circuit (ASIC). In addition, the at least one processor 1010 may also include Fig.10 At least one other circuit or element not shown.

[0253] In various example embodiments, at least one memory 1020 in the example device 1000 may include at least one storage medium in various forms, such as volatile memory and / or non-volatile memory. Volatile memory may include, but is not limited to, for example, random access memory (RAM), cache, etc. Non-volatile storage may include, but is not limited to, for example, read-only memory (ROM), hard disk, flash memory, etc. In addition, at least the memory 820 may include, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or devices, or any combination of the above.

[0254] Furthermore, in various example embodiments, the example apparatus 1000 may further include at least one other circuit, element, and interface, such as at least one I / O interface, at least one antenna element, and the like.

[0255] In various example embodiments, the circuits, components, elements, and interfaces in the example device 1000 including at least one processor 1010 and at least one memory 1020 may be connected in any suitable manner, such as electrically, magnetically, optically, electromagnetically, etc., via any suitable connection including, but not limited to, buses, crossbar switches, wiring, and / or wireless lines.

[0256] It is understood that the device structure on the device 210 side is not limited to the above-described example device 1000 .

[0257] Fig.11 A block diagram showing an apparatus for binding and unbinding neighboring apparatuses according to an embodiment of the present disclosure is shown. For example, the apparatus may be at least a part of the apparatus 230 in the above example.

[0258] like Fig.11 As shown in , the example apparatus 1100 may include at least one processor 1110 and at least one memory 1120 that may include computer program code 1130. The at least one memory 1120 and the computer program code 1130 may be configured to use the at least one processor 1110 to cause the apparatus 1100 to at least perform at least one of the above-mentioned example methods 800.

[0259] In various example embodiments, at least one processor 1110 in the example device 1100 may include, but is not limited to, at least one hardware processor, including at least one microprocessor such as a central processing unit (CPU), a portion of at least one hardware processor, and any other suitable special-purpose processor, such as a special-purpose processor developed based on, for example, a field programmable gate array (FPGA) and an application-specific integrated circuit (ASIC). In addition, the at least one processor 1110 may also include Fig.11 At least one other circuit or element not shown.

[0260] In various example embodiments, at least one memory 1120 in the example device 1100 may include at least one storage medium in various forms, such as volatile memory and / or non-volatile memory. Volatile memory may include, but is not limited to, for example, random access memory (RAM), cache, etc. Non-volatile memory may include, but is not limited to, for example, read-only memory (ROM), hard disk, flash memory, etc. In addition, at least the memory 1120 may include, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or devices, or any combination of the above.

[0261] Furthermore, in various example embodiments, the example apparatus 1100 may further include at least one other circuit, element, and interface, such as at least one I / O interface, at least one antenna element, and the like.

[0262] In various example embodiments, the circuits, components, elements, and interfaces in the example device 1100 including at least one processor 1110 and at least one memory 1120 may be connected in any suitable manner, such as electrically, magnetically, optically, electromagnetically, etc., via any suitable connection including but not limited to buses, crossbar switches, wiring, and / or wireless lines.

[0263] It is understandable that the device structure on the device 230 side is not limited to the above-mentioned example device 1100.

[0264] Fig.12 A block diagram showing an apparatus for binding and unbinding neighboring apparatuses according to an embodiment of the present disclosure is shown. For example, the apparatus may be at least a part of the management entity 220 in the above example.

[0265] like Fig.12 As shown in , the example apparatus 1200 may include at least one processor 1210 and at least one memory 1220 that may include computer program code 1230. The at least one memory 1220 and the computer program code 1230 may be configured to use the at least one processor 1210 to cause the apparatus 1200 to at least perform at least one of the above-mentioned example methods 900.

[0266] In various example embodiments, at least one processor 1210 in the example device 1200 may include, but is not limited to, at least one hardware processor, including at least one microprocessor such as a central processing unit (CPU), a portion of at least one hardware processor, and any other suitable special-purpose processor, such as a special-purpose processor developed based on, for example, a field programmable gate array (FPGA) and an application-specific integrated circuit (ASIC). In addition, the at least one processor 1210 may also include Fig.12 At least one other circuit or element not shown.

[0267] In various example embodiments, at least one memory 1220 in the example device 1200 may include at least one storage medium in various forms, such as volatile memory and / or non-volatile memory. Volatile memory may include, but is not limited to, for example, random access memory (RAM), cache, etc. Non-volatile memory may include, but is not limited to, for example, read-only memory (ROM), hard disk, flash memory, etc. In addition, at least the memory 1220 may include, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or devices, or any combination of the above.

[0268] Furthermore, in various example embodiments, the example apparatus 1200 may further include at least one other circuit, element, and interface, such as at least one I / O interface, at least one antenna element, and the like.

[0269] In various example embodiments, the circuits, components, elements, and interfaces in the example device 1200 including at least one processor 1210 and at least one memory 1220 may be coupled together in any suitable manner, such as electrically, magnetically, optically, electromagnetically, etc., via any suitable connection including, but not limited to, buses, crossbar switches, wiring, and / or wireless lines.

[0270] It should be understood that the structure of the device on the management entity 220 side is not limited to the above-mentioned example device 1200.

[0271] Fig.13 A block diagram showing an apparatus for binding neighboring devices according to an embodiment of the present disclosure is shown. For example, the apparatus may be at least a part of the apparatus 210 in the above example.

[0272] like Fig.13 As shown in , the example device 1300 may include means 1310 for performing operation 710 of the example method 700, and means 1320 for performing operation 720 of the example method 700. In one or more other example embodiments, at least one I / O interface, at least one antenna element, etc. may also be included in the example device 1300.

[0273] In some example embodiments, the examples of means in example device 1300 may include circuitry. For example, the examples of means 1310 may include circuitry configured to perform operation 710 of example method 700, and the examples of means 1320 may include circuitry configured to perform operation 720 of example method 700. In some example embodiments, the examples of means may also include software modules and any other suitable functional entities.

[0274] Fig.14 A block diagram showing a device for binding neighboring devices according to an embodiment of the present disclosure is shown. For example, the device may be at least a part of the device 230 in the above example.

[0275] like Fig.14 As shown in , the example device 1400 may include means 1410 for performing operation 810 of the example method 800, and means 1420 for performing operation 820 of the example method 800. In one or more other example embodiments, at least one I / O interface, at least one antenna element, etc. may also be included in the example device 1400.

[0276] In some example embodiments, the examples of means in example device 1400 may include circuitry. For example, the examples of means 1410 may include circuitry configured to perform the operations 810 of example method 800, and the examples of means 1420 may include circuitry configured to perform the operations 820 of example method 800. In some example embodiments, the examples of means may also include software modules and any other suitable functional entities.

[0277] Fig.15 A block diagram showing a device for binding neighboring devices according to an embodiment of the present disclosure is shown. For example, the device may be at least a part of the management entity 220 in the above example.

[0278] like Fig.15 As shown in , the example device 1500 may include means 1510 for performing operation 910 of the example method 900, means 1520 for performing operation 920 of the example method 900, means 1530 for performing operation 930 of the example method 900, means 1540 for performing operation 940 of the example method 900, and means 1550 for performing operation 950 of the example method 900. In one or more other example embodiments, at least one I / O interface, at least one antenna element, etc. may also be included in the example device 1500.

[0279] In some example embodiments, examples of means in example device 1500 may include circuitry. For example, examples of means 1510 may include circuitry configured to perform operation 910 of example method 900, examples of means 1520 may include circuitry configured to perform operation 920 of example method 900, examples of means 1530 may include circuitry configured to perform operation 930 of example method 900, examples of means 1540 may include circuitry configured to perform operation 940 of example method 900, and examples of means 1550 may include circuitry configured to perform operation 950 of example method 900. In some example embodiments, examples of means may also include software modules and any other suitable functional entities.

[0280] The term "circuitry" throughout this disclosure may refer to one or more or all of the following: (a) hardware-only implementations of the circuit (e.g., implementations in analog and / or digital circuitry only); (b) combinations of hardware circuitry and software, such as (i) combinations of analog and / or digital hardware circuitry and software / firmware, as applicable, and (ii) hardware processors and software (including digital signal processors), software, and any portion of memory that work together to enable a device such as a mobile phone or server to perform various functions); and (c) hardware circuitry and / or processors, such as microprocessors or portions of microprocessors, that require software (e.g., firmware) to operate, but where software is not required for operation, the software may not be present. This definition of circuitry applies to this disclosure, including one or all uses of the term in any claim. As a further example, as used in this disclosure, the term circuitry also encompasses implementations of hardware circuitry or a processor (or multiple processors) or portions of a hardware circuitry or processor and their (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the claimed element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in a server, cellular network device, or other computing or networking device.

[0281] Another example embodiment may involve computer program codes or instructions that may cause the apparatus to perform at least each of the above methods. Another example embodiment may involve a computer readable medium having such computer program codes or instructions stored thereon. In some embodiments, such a computer readable medium may include at least one storage medium in various forms, such as volatile memory and / or non-volatile memory. Volatile memory may include, but is not limited to, for example, RAM, cache, etc. Non-volatile memory may include, but is not limited to, ROM, hard disk, flash memory, etc. Non-volatile memory may also include, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices, or devices or any combination of the above.

[0282] Unless the context clearly requires otherwise, throughout the specification and claims, the words "comprise", "including", and the like are to be interpreted in an inclusive and not exclusive or exhaustive sense; that is, in the sense of "including but not limited to". As generally used herein, the word "coupled" refers to two or more elements that can be directly connected or connected through one or more intermediate elements. Similarly, as generally used herein, the word "connected" refers to two or more elements that can be directly connected or connected through one or more intermediate elements. In addition, the words "herein", "above", "below", and words of similar meaning as used in this application shall refer to the entirety of this application and not to any particular part of this application. Where the context permits, words used in the specification in the singular or plural may also include the plural or singular, respectively. The word "or" refers to a list of two or more items, and the word covers all of the following interpretations of the word: any item in the list, all items in the list, and any combination of items in the list.

[0283] Furthermore, conditional language used herein, such as "may," "could," "might," "may," "for example," "for example," "such as," and the like, unless specifically stated otherwise or otherwise understood in the context of use, is generally intended to convey that some embodiments include, while other embodiments do not include, certain features, elements, and / or states. Thus, such conditional language generally does not imply that features, elements, and / or states are in any way required by one or more embodiments, or that one or more embodiments necessarily include logic for determining, with or without author input or prompting, whether such features, elements, or states are included or will be performed in any particular embodiment.

[0284] Although some embodiments have been described, these embodiments are presented by way of example and are not intended to limit the scope of the present disclosure. In fact, the devices, methods, and systems described herein may be embodied in various other forms; in addition, without departing from the spirit of the present disclosure, various omissions, substitutions, and changes may be made to the forms of the methods and systems described herein. For example, although the blocks are presented in a given arrangement, alternative embodiments may utilize different components and / or circuit topologies to perform similar functions, and may delete, move, add, subdivide, combine, and / or modify some blocks. At least one of these blocks may be implemented in various different ways. The order of these blocks may also be changed. Any appropriate combination of the elements and actions of some of the above-described embodiments may be combined to provide further embodiments. The attached claims and their equivalents are intended to cover such forms or modifications that fall within the scope and spirit of the present disclosure.

Claims

1. A device for communication, comprising: at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code being configured to, with the at least one processor, cause the apparatus to perform: transmitting a binding request for binding with at least one neighboring device to a management entity; as well as receiving a binding response to the binding request from the management entity, wherein the device and the neighboring device have the same or similar measurement results regarding the binding information type, And wherein the binding of the device and the neighboring device comprises: establishing an association between at least one of an identification of the device and the neighboring device, a binding information type, a calibration parameter, and a binding establishment time.

2. The device according to claim 1, wherein: The transmitting of the binding request for binding with at least one neighboring device to the management entity is triggered by a predetermined event.

3. The device according to claim 1 or 2, wherein: The binding request includes at least one of an indicator of the binding request, at least one identification of the at least one neighboring device, at least one binding information type, and at least one binding reason; and The binding response includes at least one of a confirmation or a negative confirmation of the binding request, at least one binding information type, and at least one identifier of the at least one neighboring device.

4. A device for communication, comprising: at least one processor; as well as at least one memory including computer program code, the at least one memory and the computer program code being configured to, with the at least one processor, cause the apparatus to perform: receiving a capacity request from a management entity for binding capacity with a neighboring device; as well as transmitting a capacity response to the capacity request to the management entity, wherein the device and the neighboring device have the same or similar measurement results regarding the binding information type, And wherein the binding of the device and the neighboring device comprises: establishing an association between at least one of an identification of the neighboring device and the device, a binding information type, a calibration parameter, and a binding establishment time.

5. The device according to claim 4, wherein: The capacity request includes at least one binding information type; and The capacity response includes at least one of at least one supported binding information type, at least one rejected binding information category, and at least one rejection reason.

6. A device for communication, comprising: at least one processor; as well as at least one memory including computer program code, the at least one memory and the computer program code being configured to, with the at least one processor, cause the apparatus to perform: receiving, from a first device, a binding request for binding with at least one neighboring device of the first device; transmitting, in response to the binding request, to a second device of the at least one neighboring device, a first capacity request for binding capacity of the second device; receiving a first capacity response to the first capacity request from the second device; binding the first device and the second device based on the first capacity response; as well as transmitting a binding response to the binding request to the first device, wherein the first device and the neighboring device have the same or similar measurement results regarding the binding information type, And wherein binding the first device and the second device based on the first capacity response includes: An association is established between at least one of an identification of the first device and the second device, a binding information type, a calibration parameter, and a binding establishment time.

7. The device according to claim 6, wherein: The binding request includes at least one of an indicator of the binding request, at least one identification of the at least one neighboring device, at least one binding information type, and at least one binding reason; and The binding response includes at least one of a confirmation or a negative confirmation of the binding request, at least one binding information type, and an identifier of the second device.

8. The device according to claim 6 or 7, wherein: The at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to further perform: receiving a request for accessing first measurement information of the first device; transmitting the access request to the second device; receiving second measurement information of the second device; as well as The first measurement information is determined based on the second measurement information and a calibration parameter.

9. The device according to any one of claims 6 to 8, wherein: The at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to further perform: receiving, from one of the first device and the second device, a binding release request for unbinding the first device and the second device; Based on the binding release request, delete an association between at least one of an identifier, a binding information type, a calibration parameter, and a binding establishment time of the first device and the second device; transmitting a binding release response to the binding release request to one of the first device and the second device; as well as Binding release information or binding update information is transmitted to the other of the first device and the second device.

10. The device of claim 9, wherein: The at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to further perform: transmitting, in response to the binding release request from the second device, to a third device among the at least one neighboring device, a second capacity request for a binding capacity of the third device; receiving a second capacity response to the second capacity request from the third device; as well as The first device and the third device are bound based on the second capacity response.

11. The device of claim 10, wherein: The first capacity request or the second capacity request includes at least one binding information type; and The first capacity response or the second capacity response includes at least one of at least one supported binding information type, at least one rejected binding information category, and at least one rejection reason.

12. A method performed by an apparatus for communication, comprising: transmitting a binding request for binding with at least one neighboring device to a management entity; as well as receiving a binding response to the binding request from the management entity, wherein the device and the neighboring device have the same or similar measurement results regarding the binding information type, And wherein the binding of the device and the neighboring device comprises: establishing an association between at least one of an identification of the device and the neighboring device, a binding information type, a calibration parameter, and a binding establishment time.

13. The method of claim 12, wherein: The transmitting of the binding request for binding with at least one neighboring device to the management entity is triggered by a predetermined event.

14. The method according to claim 12 or 13, wherein: The binding request includes at least one of an indicator of the binding request, at least one identification of the at least one neighboring device, at least one binding information type, and at least one binding reason; and The binding response includes at least one of a confirmation or a negative confirmation of the binding request, at least one binding information type, and at least one identifier of the at least one neighboring device.

15. A method performed by an apparatus for communication, comprising: receiving a capacity request from a management entity for binding capacity with a neighboring device; as well as transmitting a capacity response to the capacity request to the management entity, wherein the device and the neighboring device have the same or similar measurement results regarding the binding information type, And wherein the binding of the device and the neighboring device comprises: establishing an association between at least one of an identification of the neighboring device and the device, a binding information type, a calibration parameter, and a binding establishment time.

16. The method of claim 15, wherein: The capacity request includes at least one binding information type; and The capacity response includes at least one of at least one supported binding information type, at least one rejected binding information category, and at least one rejection reason.

17. A method performed by a management entity for communications, comprising: receiving, from a first device, a binding request for binding with at least one neighboring device of the first device; transmitting, in response to the binding request, to a second device of the at least one neighboring device, a first capacity request for binding capacity of the second device; receiving a first capacity response to the first capacity request from the second device; binding the first device and the second device based on the first capacity response; as well as transmitting a binding response to the binding request to the first device, wherein the first device and the neighboring device have the same or similar measurement results regarding the binding information type, And wherein binding the first device and the second device based on the first capacity response includes: An association is established between at least one of an identification of the first device and the second device, a binding information type, a calibration parameter, and a binding establishment time.

18. The method of claim 17, wherein: The binding request includes at least one of an indicator of the binding request, at least one identification of the at least one neighboring device, at least one binding information type, and at least one binding reason; and The binding response includes at least one of a confirmation or a negative confirmation of the binding request, at least one binding information type, and an identifier of the second device.

19. The method of claim 17 or 18, further comprising: receiving a request for accessing first measurement information of the first device; transmitting the access request to the second device; receiving second measurement information of the second device; as well as The first measurement information is determined based on the second measurement information and a calibration parameter.

20. The method of any one of claims 17 to 19, further comprising: receiving, from one of the first device and the second device, a binding release request for unbinding the first device and the second device; Based on the binding release request, delete an association between at least one of an identifier, a binding information type, a calibration parameter, and a binding establishment time of the first device and the second device; transmitting a binding release response to the binding release request to one of the first device and the second device; as well as Binding release information or binding update information is transmitted to the other of the first device and the second device.

21. The method of claim 20, further comprising: transmitting, in response to the binding release request from the second device, to a third device among the at least one neighboring device, a second capacity request for a binding capacity of the third device; receiving a second capacity response to the second capacity request from the third device; as well as The first device and the third device are bound based on the second capacity response.

22. The method of claim 21, wherein: The first capacity request or the second capacity request includes at least one binding information type; and The first capacity response or the second capacity response includes at least one of at least one supported binding information type, at least one rejected binding information category, and at least one rejection reason.

23. A device for communication, comprising: means for transmitting to a management entity a binding request for binding with at least one neighboring device; as well as means for receiving a binding response to said binding request from said management entity, wherein the device and the neighboring apparatus have the same or similar measurement results regarding the binding information type, And wherein the binding of the device and the neighboring apparatus comprises: establishing an association between at least one of an identification of the device and the neighboring apparatus, a binding information type, a calibration parameter, and a binding establishment time.

24. A device for communication, comprising: means for receiving a capacity request from a management entity for binding capacity with a neighboring device; as well as means for transmitting a capacity response to said capacity request to said management entity, wherein the device and the neighboring apparatus have the same or similar measurement results regarding the binding information type, And wherein the binding of the device and the neighboring apparatus comprises: establishing an association between at least one of an identification of the neighboring apparatus and the device, a binding information type, a calibration parameter, and a binding establishment time.

25. A device for communication, comprising: means for receiving, from a first device, a binding request for binding with at least one neighboring device of the first device; means for transmitting, in response to the binding request, to a second device of the at least one neighboring device, a first capacity request for a binding capacity of the second device; means for receiving a first capacity response to the first capacity request from the second device; means for binding the first device and the second device based on the first capacity response; as well as means for transmitting a binding response to the binding request to the first device, wherein the first device and the neighboring device have the same or similar measurement results regarding the binding information type, And wherein binding the first device and the second device based on the first capacity response includes: An association is established between at least one of an identification of the first device and the second device, a binding information type, a calibration parameter, and a binding establishment time.

26. A computer readable medium comprising program instructions for causing an apparatus to: transmitting a binding request for binding with at least one neighboring device to a management entity; and receiving a binding response to the binding request from the management entity, in, The device and the neighboring device have the same or similar measurement results regarding the binding information type, And wherein the binding of the device and the neighboring device comprises: establishing an association between at least one of an identification of the device and the neighboring device, a binding information type, a calibration parameter, and a binding establishment time.

27. A computer readable medium comprising program instructions for causing an apparatus to: receiving a capacity request from a management entity for binding capacity with a neighboring device; and transmitting a capacity response to the capacity request to the management entity, in, The device and the neighboring device have the same or similar measurement results regarding the binding information type, And wherein the binding of the device and the neighboring device comprises: establishing an association between at least one of an identification of the neighboring device and the device, a binding information type, a calibration parameter, and a binding establishment time.

28. A computer readable medium comprising program instructions for causing an apparatus to: receiving, from a first device, a binding request for binding with at least one neighboring device of the first device; transmitting, in response to the binding request, to a second device of the at least one neighboring device, a first capacity request for binding capacity of the second device; receiving a first capacity response to the first capacity request from the second device; binding the first device and the second device based on the first capacity response; as well as transmitting a binding response to the binding request to the first device, wherein the first device and the neighboring device have the same or similar measurement results regarding the binding information type, And wherein binding the first device and the second device based on the first capacity response includes: An association is established between at least one of an identification of the first device and the second device, a binding information type, a calibration parameter, and a binding establishment time.

Images