(19)
(11)EP 3 384 716 B1

(12)EUROPEAN PATENT SPECIFICATION

(45)Mention of the grant of the patent:
13.10.2021 Bulletin 2021/41

(21)Application number: 16881053.9

(22)Date of filing:  21.12.2016
(51)International Patent Classification (IPC): 
H04W 68/02(2009.01)
(52)Cooperative Patent Classification (CPC):
H04W 68/02
(86)International application number:
PCT/CN2016/111337
(87)International publication number:
WO 2017/114264 (06.07.2017 Gazette  2017/27)

(54)

PAGING MECHANISM FOR WIRELESS NETWORKS

PAGING-MECHANISMUS FÜR DRAHTLOSE NETZWERKE

MÉCANISME DE RADIORECHERCHE POUR RÉSEAUX SANS FIL


(84)Designated Contracting States:
AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

(30)Priority: 31.12.2015 US 201514985991

(43)Date of publication of application:
10.10.2018 Bulletin 2018/41

(73)Proprietor: Huawei Technologies Co., Ltd.
Longgang District Shenzhen, Guangdong 518129 (CN)

(72)Inventors:
  • ZARIFI, Keyvan
    Kanata Ontario K2K 3J1 (CA)
  • BALIGH, Mohammadhadi
    Ottawa Ontario K2M 0B1 (CA)

(74)Representative: Goddar, Heinz J. 
Boehmert & Boehmert Anwaltspartnerschaft mbB Pettenkoferstrasse 22
80336 München
80336 München (DE)


(56)References cited: : 
EP-A1- 2 683 211
WO-A2-2009/148258
CN-A- 102 821 467
US-A1- 2015 141 002
WO-A1-2009/052733
CN-A- 101 009 927
US-A1- 2002 046 287
  
  • "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture enhancements for Cellular Internet of Things (Release 13)", 3GPP STANDARD; 3GPP TR 23.720, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. V1.1.0, 29 October 2015 (2015-10-29), pages 1-90, XP051046169, [retrieved on 2015-10-29]
  
Note: Within nine months from the publication of the mention of the grant of the European patent, any person may give notice to the European Patent Office of opposition to the European patent granted. Notice of opposition shall be filed in a written reasoned statement. It shall not be deemed to have been filed until the opposition fee has been paid. (Art. 99(1) European Patent Convention).


Description

TECHNICAL FIELD



[0001] The present invention relates to wireless communications, and, in particular embodiments, to a method for paging a device in a wireless communications network, a wireless device and a non-transitory computer-readable medium.

BACKGROUND



[0002] In current Long Term Evolution networks, a device may be assigned an identifier which is used by the network to send data to the device, while the device has a logical connection established with a particular base station or network node. The assigned identifier is temporary and its use is discontinued after the device has completed communications and entered a standby or idle mode of operation. If the network subsequently has data to send to the device, a paging mechanism is used to contact the device prior to sending data. The paging mechanism increases overhead in the network, particularly when the paging message is transmitted from multiple base stations within the known tracking area for the device. Paging messages may include a lengthy identifier associated with the device such as an International Mobile Equipment Identity (IMEI) or International Mobile Subscriber Identity (IMSI). A series of messages must also be exchanged in order for the device to re-establish a connection with a base station.

[0003] WO 2009/052733A1 discloses a paging method for a system including user equipment and a base station. The method includes the following steps: the base station sets the paging message, the message carries the paging multi-user equipment indication information; the base station sends the paging message to the user equipment, so that the user equipment exits the idle mode in accordance to the paging multi-user equipment indication information.

[0004] "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture enhancements for Cellular Internet of Things (Release 13)", 3GPP TR 23.720 V1.1.0 (2015-10) studies and evaluates the architecture enhancement to support ultra-low complexity, power constrained, and low data-rate 'Internet of Things' devices. It discloses a solution for UE state transition signalling reduction.

[0005] WO 2009/148258 A2 discloses a method for efficiently transmitting and receiving a paging message and system information from and in a mobile station of a broadband wireless access system. The method comprises receiving paging information from a serving base station, the paging information including paging sub group identifier (paging sub_group ID) indicating a paging sub group to which the mobile station belongs; and receiving the paging message for a predetermined paging interval of the paging sub group.

[0006] EP 2 683 211 A1 provides a method for the support of data transmission in a packet mobile network, for PDN connectivity over said packet mobile network between an User Equipment UE and an external Packet Data Network PDN. Said packet mobile network comprises a CN accessed by a RAN, said data transmission uses a tunnel over an interface between a serving RAN node and a serving user plane CN node.

SUMMARY



[0007] The present invention provides a method of claim 1 performed by a device in a wireless communications network, a wireless device of claim 7 and a non-transitory computer-readable medium of claim 13. Possible implementation manners are disclosed in the dependent claims.

[0008] According to another example, described herein is a method performed by a device in a wireless communications network, the method comprising: receiving and storing a device connection identifier while in an active state, wherein the device connection identifier of the device is a dedicated connection identifier, DCID, which is assigned to the device by a network controller of the wireless communications network, wherein the device has different operating states with different sets of functionality in each state, and wherein at least some degree of connectivity to the network is supported in each operating state, such that the device maintains its DCID and an always-on connection to the wireless communications network; transitioning to a standby state, wherein a reduced set of device functionality is supported in the standby state compared to the set of device functionality supported in the active state; periodically monitoring, while in the standby state, the wireless communications network for paging messages that include the device connection identifier; and periodically monitoring, while in the standby state, the wireless communications network for a paging message that includes a relay indicator, wherein the relay indicator is used to indicate that the paging message should be relayed or retransmitted in the wireless communications network for receipt by a target device, and retransmitting the received paging message based on the relay indicator.

[0009] According to another example, described herein is a wireless device comprising: a communications interface; a processor; and one or more non-transitory computer readable media having computer readable instructions stored thereon for transmitting and receiving data through the communications interface. The instructions, when executed by the processor, direct the wireless device to: receive and store a device connection identifier while in an active state wherein the device connection identifier of the device is a dedicated connection identifier, DCID, which is assigned to the device by a network controller of a wireless communications network, wherein the wireless device has different operating states with different sets of functionality in each state, and wherein at least some degree of connectivity to the network is supported in each operating state, such that the wireless device maintains its DCID and an always-on connection to the wireless communications network; transition to a standby state, wherein a reduced set of device functionality is supported in the standby state compared to the set of device functionality supported in the active state; periodically monitor, while in the standby state, the wireless communications network for paging messages that include the device connection identifier; and periodically monitor, while in the standby state, the wireless communications network for a paging message that includes a relay indicator, wherein the relay indicator is used to indicate that the paging message should be relayed or retransmitted in the wireless communications network for receipt by a target device, and retransmit received paging message based on the relay indicator.

BRIEF DESCRIPTION OF THE DRAWINGS



[0010] Reference will now be made, by way of example, to the accompanying drawings which show example embodiments of the present disclosure, and in which:

Figure 1 illustrates an example of a wireless communications network;

Figure 2 illustrates an example of a logical entity or hypercell of a network of Figure 1.

Figure 3 illustrates an example of a DCID associated with a user equipment device.

Figure 4A is a schematic flowchart diagram illustrating a paging method.

Figure 4B illustrates an example of a paging message used in the method of Figure 4A.

Figure 5A is a schematic flowchart diagram illustrating a paging method.

Figure 5B illustrates an example of a paging message used in the method of Figure 5A.

Figure 6A and Figure 6B are schematic flowchart diagrams illustrating a paging method according to example embodiments.

Figure 7 is a diagram of a concatenated paging message.

Figure 8 is a block diagram of a wirelessly-enabled device for implementing embodiments described herein.


DETAILED DESCRIPTION



[0011] The structure, manufacture and use of example embodiments are discussed in detail below. The specific examples discussed are merely illustrative of specific ways to make and use embodiments of the invention, and do not limit the scope of the invention.

[0012] Figure 1 illustrates a wireless communications network 100 to which the paging procedures described herein can be applied. The communications network 100 is a user equipment (UE)-centric network 100 which employs an air interface designed to support non-cellular based wireless communications. In example embodiments, network communications are organized around a connection identifier, which is a Dedicated Connection Identifier (DCID), which is assigned to a device or UE 104. The UE 104 has different operating states with different sets of functionality in each state. At least some degree of connectivity to the network 100 is supported in each operating state, such that the UE 104 maintains its DCID and its connection to the wireless communications network 100. As a result, if the network 100 has data to send to a particular target UE 104, a paging message containing the DCID of the target UE 104 is sent during a listening occasion of the target UE 104. Overhead in the network 100 is reduced because the UE 104 is not required to re-establish a connection to the network as part of the paging process. The DCID also may be shorter than other identifiers, such as an International Mobile Equipment Identity (IMEI) or International Mobile Subscriber Identity (IMSI), used in existing paging processes. In example embodiments not covered by the claimed invention, the location of the UE 104 relative to a number of transmission points may be tracked, and the paging message may be sent by a single transmission point 106 which is selected to serve the UE 104. Because a further exchanging of messages is not required to complete the paging process, in some embodiments, the paging message may also contain the data intended for the target UE 104.

[0013] In an example embodiment, the communications network 100 of Figure 1, which as such is not covered by the claimed invention, includes a plurality of transmission points (TPs) 106 and a cloud processor or controller 108 in communication with the TPs 106. The TPs 106 communicate with a plurality of UEs 104. The TPs 106 may include any component or network node capable of providing wireless access by establishing uplink and/or downlink connections with the UEs 104, such as a base transceiver station (BTS), a NodeB, an evolved NodeB (eNB), a femtocell node, a lower power node, or other wirelessly enabled devices. The UEs 104 may include any component capable of establishing a wireless connection with the TPs 106. In an embodiment, the UE 104 can be a mobile phone, a sensor, a smart phone, a tablet, a computer, a wireless transmit/receive unit (WTRU), or other wirelessly enabled device. The TPs 106 may be connected to controller 108 via a backhaul network (not shown). The backhaul network may be any component or collection of components that allow data to be exchanged between the TPs 106 and the controller 108 and/or a remote end (not shown). In some embodiments, the network 100 may include various other wireless devices, such as relays. The controller 108 may be any type of data processing system capable of performing the processes disclosed below and capable of communication with other devices. In some embodiments, one of the TPs 106 may operate as the network controller 108.

[0014] In the network 100, the TPs 106 are not associated with a conventional cell. Rather, the controller 108 organizes the TPs 106 into logical entities or hypercells 110. In one embodiment, each UE 104 is assigned to a hypercell 110 and is assigned a unique DCID. The UE 104 may move freely within an area serviced by a single logical entity without acquiring a new DCID. Each TP 106 monitors signal strengths for any UE 104 detectable by the TP 106 and sends this data to the controller 108. The controller 108 creates a logical entity or determines the identity of a logical entity to be assigned to serve each UE 104 according to the signal strengths measured by the TPs 106. This determination can be performed dynamically. In some examples, the controller 108 assigns a logical entity ID (also referred to as a hypercell ID) to the logical entity for the hypercell 110 and assigns a DCID to each UE 104.

[0015] In some examples, the controller 108 selects one of the TPs 106 in the hypercell 110 to serve and provide network access to a UE 104. In an embodiment not covered by the claimed invention, the controller 108 selects the TP 106 based on relative signal strengths of the UE 104 at each of the TPs 106 in the logical entity 110, or the loads of each TP 106 in the hypercell 110, or a combination of relative signal strengths and loads. In other embodiments, other selection criteria can be used. In an embodiment, the controller 108 dynamically reassigns a new TP 106 in the hypercell 110 to serve the UE 104 based on changes to the signal strength of the UE 104 at each TP 106 in the hypercell 110. The change in signal strength may be due to UE mobility or to other factors. In an embodiment, the controller 108 can enable or disable one or more TPs 106 within a hypercell 110 to reach a tradeoff between the service quality provided to all covered UEs 104 and energy saving criteria. In an embodiment, the TPs 106 assigned to a hypercell 110 may be changed dynamically by the controller 108 according to changes in network conditions. In networks 100 which support coordinated multi-point (CoMP) transmission, multiple TPs 106 in a hypercell 110 may operate jointly as a virtual transmission point for a UE 104.

[0016] Figure 2 illustrates a hypercell coverage area associated with hypercell 110 (depicted with an outlined circle). In at least some example embodiments not covered by the claimed invention, the TPs 106 (not shown in Figure 2) of hypercell 110 are associated with different zones 200, with at least some TPs 106 that do not have common coverage areas within a hypercell 110 being assigned to common zones. In this regard, Figure 2 illustrates hypercell 110 divided into zones 1-7; each zone includes multiple TPs 106 that are located in geographically separated regions or areas. Such a configuration can facilitate the reuse of resources in different areas of hypercell 110.

[0017] The network 100 is configured to support different operating states for the UE 104, with each operating state supporting different levels of UE functionality. According to the invention, the UE 104 is configured to transition between two different states, namely an "active" state and an energy economizing "ECO" or "standby" state. In example embodiments, the active state includes the UE 104 performing operations to send, receive, or send and receive data from the network 100 for one or more applications or services supported by the UE 104. A reduced set of UE functionality is supported in the standby state compared to the set of UE functionality supported in the active state. In at least some example embodiments, network resources used to support the UE 104 while it is operating in a standby state are less than the resources required when the UE 104 is in an active state. In both states, at least some degree of connectivity to the network 100 is supported. The UE 104 maintains an always-on connection to the wireless communications network 100, and in particular the UE 104 stores and retains the assigned DCID during different operating states including the standby state. As a result of retaining the DCID, the UE 104 may perform a number of actions in a standby operating state such as, but not limited to, receiving paging messages, receiving data, and sending acknowledgements, as described below. The UE 104 may also perform other actions to update location or synchronization information with the network 100. These actions permit the transition of the UE 104 from a standby operating state to an active operating state without having to obtain a new DCID identifier.

[0018] The DCID for a UE 104 may be assigned during an initial access procedure that is supported by UE 104 in the active state. In an example initial access procedure, the UE 104 searches for a synchronization signal associated with the logical entity for the hypercell 110; the UE 104 accesses the hypercell 110 of network 100 via a pre-defined default frame structure; the UE 104 obtains downlink (DL) synchronization via a sync channel; and the UE 104 uses Physical Random Access Channel (PRACH) for initial access. The network controller 108 authenticates the UE 104 and assigns a UE DCID. At the conclusion of the initial access procedure, the UE 104 is provided with a hypercell ID, a UE DCID, and a UE-specific sequence that is associated with the UE DCID (which may, for example, be a Zadoff-Chu sequence). In example embodiments, for uplink communications, a UE 104 can be identified by the network 100 based on the UE-specific sequence used by the UE 104 in an uplink communications channel and the DCID which is associated with or related to that UE- specific sequence. The DCID for the UE 104 may be used by multiple signaling, control and data channels including, for example, a tracking channel (TC) and a physical downlink control channel (PDCCH). Systems and methods for initial access procedures and for UE connection and identification in the network 100 are described in further detail in the applicant's co-pending application No. 62/141,483, filed April 1, 2015, and entitled System and Method for a Tracking Channel, and co-pending application No. 62/213,450, filed September 9, 2015, and entitled System and Method for Channel Security.

[0019] In example embodiments, the DCID assigned to a UE 104 within the hypercell 110 may contain multiple fields such as a zone identifier (zone ID), a UE type, and a UE identifier (UE ID). An example of such a multi-field DCID record 302 is illustrated in Figure 3. The UE type may identify or group the device according to the type of device, the type of data or traffic associated with the device, or both. For example, a stationary device which does not transmit or receive a large amount of data may be designated as a sensor type of device. The UE ID may consist of a number or other identifier assigned to or associated with the UE 104 to identify the UE 104 in the hypercell 110. The zone ID indicates the zone of the hypercell 110 to which the UE is assigned, as described above. In example embodiments, the DCID includes both a zone ID and a subzone ID as illustrated in Figure 3 by DCID record 304. The subzone ID may be used to indicate a smaller geographical area and subset of TPs 106 within a zone.

[0020] As noted above, once a UE 104 has initially accessed the network 100, the UE 104 may enter a standby state. Periodically during the standby state, the UE 104 may perform one or more tasks that require communication with the network 100. In example embodiments, at least some of the standby communications use tracking channel network resources assigned to the UE 104. In example embodiments not covered by the claimed invention, the UE 104 periodically transmits an identifying signal while in its standby state, which contains or is associated with the DCID which has been assigned to the UE 104. In some embodiments, the signal transmitted by the UE 104 includes the UE-specific sequence (for example a Zadoff-Chu sequence) which is associated with or related to the DCID, as described above, and is transmitted using the tracking channel resources assigned to the UE 104. The UE 104 may periodically transmit the signal to maintain or update synchronization or power control within the network 100, maintain or update authentication and security, or provide a status report to the network 100.

[0021] As a result, the network 100 may track the UE 104 even while the UE 104 is operating in its standby state and determine a serving TP 106 or a set of serving TPs 106 which are capable of serving the UE 104. The network 100 also may update a zone, a subzone, a type, or a combination of the zone, subzone and type for the UE 104 and a new DCID may be assigned. A new DCID may also be assigned to the UE 104 for security purposes either periodically or in response to other triggers or conditions. The assigned DCID is retained by the UE 104 during the standby operating state and during transitions between the standby state and other operational states, including transitions between the standby and active states. The DCID assigned to the UE 104 and the serving TP 106, or set of serving TPs 106, is also retained by the network 100 for as long as the network 100 is able to continue tracking the UE 104, regardless of whether the UE 104 remains in the active state. Thus, the UE 104 maintains the always-on connection to the wireless communications network 100. Accordingly, the assigned DCID is retained by the network 100 and the UE 104 for a period of time that includes at least one active state duration and a subsequent standby state duration of the UE 104.

[0022] Examples will now be described of how paging messages for a UE 104 are processed according to example embodiments. In example embodiments, paging messages are messages that can be sent to a UE 104 that is in a standby state to notify the UE 104 that the network 100 has downlink data to transmit to the UE 104. In some examples, the paging message includes network resource allocation information that instructs the UE 104 to receive data using the allocated network resources, which may require the UE to transition from its standby state to an active state. In some examples, the paging message includes appended data that the UE 104 can receive using the same network resources as the paging message without transitioning to an active state.

[0023] In this regard, Figure 4A is a signaling diagram that illustrates methods for processing paging messages as performed by target UE 104, a network node (TP 106) and network controller 108. In Figure 4A, UE 104 has transitioned to a standby state. While in the standby state, as previously discussed, UE 104 periodically sends an identifying signal (action 402) to a TP 106 of the network 100 using a tracking channel. In an example embodiment, the identifying signal is a sequence that is associated with the DCID previously assigned to the UE 104 by the network controller 108 during a prior active state of the UE 104. After the TP 106 receives the identifying signal, the TP 106 sends the network controller 108 a message that includes the indentifying signal (or other information that identifies the UE 104) as well as information that identifies the TP 106 and the network controller 108 uses this information to track the location of the UE 104.

[0024] While in the standby state, UE 104 listens for paging messages from the network 100 . In particular, the UE 104 periodically performs an operation referred to herein as a listening occasion (LO) 416 during which the UE 104 monitors, for a predetermined duration, predetermined network resources allocated to it for paging messages and other messages. The predetermined network resources may, for example, include a time/ frequency allocation associated with a tracking channel or other channel such as a dedicated paging channel. One or more of the actions 402, 416 may be performed by the UE 104 at the same time, or at different times. Each of the actions 402, 416 may be performed periodically with the same or different standby cycle time intervals 418.

[0025] In Figure 4A, a paging sequence starts when the network controller 108 receives an indication (action 405) that a data source connected to the network 100 has data to send to the target UE 104. The indication may include the DCID which has been assigned to the target UE 104, or the network controller 108 may alternatively determine the DCID of the target UE 104 in some other way. Based on the periodic identifying signals that the network 100 has been receiving from target UE 106, the network controller 108 tracks the current location of the UE 104 even while the UE 104 is in its standby state, thus allowing the network controller 108 to determine a serving TP 106 (Action 324) for the target UE 104. The serving TP 106 is a TP 106 which has been selected by the network 100 to send or receive data from the UE 104 based on various criteria such as, but not limited to, signal strengths and traffic loads. The serving TP 106 for a particular UE 104 may be selected or determined on a periodic basis either separate from, or as part of, the paging method of Figure 4. In one embodiment not covered by the claimed invention, the serving TP 106 may be determined based on the TP 106 with the best channel to the UE 104. The best channel may be determined based on the relative signal strengths of the target UE 104 at each of the TPs 106 in the logical entity 110 and/or the loads of each TP 106 in the hypercell 110. In example embodiments, the serving TP may be a virtual transmission point consisting of multiple TPs 106 in the network 100 which operate jointly to transmit data to the target UE 104.

[0026] Once a serving TP 106 has been determined, the network controller 108 generates and sends a UE data notification message to the serving TP 106 (Action 410) instructing the serving TP 106 to send a paging message to the target UE 104. In one example, the data notification message sent from the network controller 108 to the serving TP 106 includes: the DCID for the target UE 104; a wireless resource allocation (RA) or other scheduling information that is to be used by the serving TP 106 to send data to the target UE 104; and the data that is to be sent to the target UE 104 (or information that identifies the data so that the TP 106 can retrieve the data). In an example embodiment the network controller 108 starts a paging timer (action 412) for the paging process when it sends the data notification.

[0027] The data notification may be sent from the network controller 108 to the serving TP 106 through the backhaul network. If the serving TP 106 also operates as the network controller 108, the data notification is provided from a network controller function to a paging function within the serving TP 106. If the network controller 108 is part of one TP 106 which is not the serving TP 106, the data notification for the target UE 104 may be sent from one TP 106 to the second, serving TP 106.

[0028] Once the serving TP 106 receives the data notification (action 410) the serving TP 106 generates and sends a corresponding paging message (action 414) addressed to the target UE 104. Figure 4B illustrates an example paging message 450, which includes the DCID 302 of the target UE 104 and the resource allocation (RA) 452 that is going to be used to send the data associated with the paging message. The paging message 450 may be sent by the TP 106 (action 414) during paging intervals which coincide with the listening occasions (LO) 416 of the target UE 104. The paging interval may be an integer multiple of the listening occasion interval of the target UE 104, such that the paging interval coincides with at least one listening occasion for the UE 104. The paging intervals and listening occasion intervals may be predetermined for the network 100 and TPs 106 and configured for the UE 104 when the UE 104 initially accesses the network 100.

[0029] In the example paging message 450 shown in Figure 4A, the UE identifying information includes the entire DCID. However, in some embodiments, the paging message 450 may include only a portion of the DCID that contains sufficient information to identify the target UE 104 within the hypercell 110.

[0030] After receiving the paging message 450, the UE 104 processes the resource allocation information 450 that is included with the message to determine what network resources will be used to transfer data that is associated with the paging message, and then proceeds to receive the data, which is sent by the serving TP 106 (action 420) using the specified network resources. In some embodiments, the UE 104 may transition from the standby state to the active state to receive the data from the network 100 in association with the DCID. In one embodiment, the UE 104 only wakes up or operates sufficiently to perform one or more of the above actions (402, 414, 420) but the UE 104 does not necessarily transition from the standby state to the active state.

[0031] In example embodiments, the paging method of Figure 4A may further include a data reception confirmation message (action 422) that is sent from the target UE 104 to the serving TP 106 to confirm receipt of the paging message. The serving TP 106 may then confirm successful delivery of the paging message to the network 100 by sending a confirmation notification to the controller 108 (Action 424). Upon receipt of this confirmation notification, the network controller 108 stops the paging timer (action 426) to end the paging process.

[0032] Figure 5A illustrates another example method for processing a paging message which is similar to that shown in Figure 4A and described above with the exception of differences that will be apparent from the following description. As illustrated in Figure 5A, other embodiments may be suitable for use when only a small amount of data is intended for the target UE 104. Figure 5B illustrates a paging message 550 for use in the method of Figure 5. Similar to previously discussed paging message 450, the paging message 550 includes an identifier for the target UE 104 (for example DCID 302). However, instead of having resource allocation information, the paging message 550 includes the actual downlink data 552. Accordingly, in the method of Figure 5A, the paging message 550 sent by the TP 106 (action 510) includes the DCID (or shortened identifier) of the target UE 104 together with the data 552 at the same time-frequency (TF) resource. In some embodiments, such as for a short data packet as illustrated in the example of Figure 5A, the paging message with data may be received by the UE 104 while remaining in a standby state.

[0033] In some example embodiments, the network 100 is configured to support both the paging method of Figure 4A and the paging method of Figure 5. In such configurations, the network controller 108 may be configured to determine, based on one or more criteria, whether the data for a paging message is best sent using the same network resources as the paging message (as in Figure 5) or using different network resources (as in Figure 4). Such criteria could include, for example, the size of the data to be sent, the available network resources, and the UE type.

[0034] As illustrated in Figures 4 and 5, a paging interval timer may be started (action 412) in the network when a notification (action 410) is sent to a serving TP 106. In one embodiment, the timer is maintained by the controller 108. If the timer expires before confirmation of delivery is received for the paging message and data, further actions may be taken. In one embodiment, additional paging messages may be sent for the target UE 104 at subsequent paging intervals. In some embodiments, the paging message includes a relay flag and, after a failed paging attempt, the relay flag is turned on. The relay flag provides an indication to the UEs 104, other than the target UE 104, that the paging message should be relayed or retransmitted in the network 100. The relay flag may be included with the notification provided by the network 100 to the TP 106 and included with the paging message sent by the TP 106.

[0035] In this regard, Figures 6A and 6B illustrate paging methods in which one UE1 104 is used as an intermediate device to relay a paging message to a second UE2 104. The methods of Figures 6A and 6B are similar to those described above in respect of Figures 4 and 5 with the exception of differences that will be apparent from the following description. In the example of Figure 6A, network controller 108 has determined that a paging message is required to be sent to UE2 104, but has determined that the last transmission hop for the paging message will be a peer-to-peer relay from another user equipment device to UE2 104. The network controller 18 may, for example, make the determination that an intermediate relay is required as a result of a previously failed attempt to send a paging message to target UE2 104. Alternatively, the network controller 18 may make the determination without a previously failed paging attempt based on prior information that the network is tracking in respect of UE2 104. In an example embodiment, the network controller determines, based on tracked information in respect of UE2 104, a suitable TP 106 to use to deliver the paging message, and then sends a paging notification (action 610) to the TP 106. In an example embodiment, the paging notification includes the DCID for the target UE2 104, an indication of the data that is to be sent, resource allocation information for the data transfer if required, and a relay indicator such as a flag that indicates that the paging message is to be relayed by an intermediate device. Upon receiving the paging notification (action 610), the serving TP 106 generates a paging message as indicated by reference 650 in Figure 6A. The paging message 650 is similar to paging message 450 discussed above in that it includes the DCID 302 of the target UE2 104 and resource allocation information 442. However, the paging message 650 also includes a relay indicator 652, which may for example be a binary flag, that is set to indicate that the paging message 652 is intended to be relayed by an intermediate wireless communication device. The serving TP 106 then transmits the paging message 650 (action 612) over wireless network 100. In an example embodiment, paging message 650 is transmitted in a tracking channel or other channel such as paging channel that devices other than UE2 104 have access to.

[0036] In the example of Figure 6A, a wireless device UE1 104 monitoring the channel on which paging message 650 is sent receives the paging message 650 during a LO 416. After comparing the UE ID in the DCID 302 from the paging message 650, and determining that this UE ID does not correspond to its own UE ID, the UE1 104 checks the relay indicator 652. If this relay indicator 652 is "on" and thus indicates that the paging message 650 should be relayed, the UE1 104 retransmits the paging message 650 (action 614) for possible receipt by the target UE2 104. The paging message 650 may be received by the target UE2 104 during a LO 620 which occurs periodically during the standby cycle 622 of the target UE2 104. UE1 104 may use the network tracking channel for sending the paging message 650 or it may use a dedicated peer-to-peer channel.

[0037] Similar to the example paging method of Figure 4A, the paging message 650 can include resource allocation information 442 that instructs the target UE2 104 what resources will be used to transmit the data associated with the paging message 650. In some example embodiments, the intermediate device UE1 104 may also be used to relay such data; however in some embodiments the target UE2 104 may receive the data directly from TP 106. In some example embodiments, the paging message 650 itself includes data 552 (as in the example of Figure 5). The relay indicator 652 may thus be used to increase the success rate in paging and delivering data to the target UE 104. In some embodiments, the relay indicator may be turned on for the initial paging of the target UE 104. In some embodiments, the relay indicator may be turned on only after one or more attempts at paging the target UE 104 have failed.

[0038] In the example of Figure 6A, after receipt of the paging message 650 and data, the target UE2 104 sends a confirmation (action 624) to confirm receipt of the paging message to the intermediate UE1 104. The UE1 in turn sends a confirmation (action 626) to confirm receipt to serving TP 106. The TP 106 then sends a confirmation (action 628) to the network 100 to confirm successful delivery of the data and paging message, after which the timer may be stopped (action 426). In other embodiments, as illustrated in Figure 6B, the target UE2 sends a confirmation 640 directly to the TP 106 to confirm receipt.

[0039] In some embodiments, before relaying the paging message for the target UE2 104, the intermediate UE1 104 may determine whether the DCID 302 in the paging message 650 has the same zone, or the same zone and subzone, as UE1 104. If the zone or zone and subzone are the same, and the relay indicator is on, the UE1 retransmits the paging message 650. However, if the zone or zone and subzone do not match, or the relay indicator is off, UE1 104 ignores the message. In a further embodiment, the UE1 may determine whether to retransmit the paging message based on differences between the UE ID for the UE1 and the UE ID for the target UE2. In an example embodiment, the UE IDs which are assigned to the UEs 104 are configured so that a binary distance between the UE ID numbers indicates, e.g. is proportional to, a geographical or physical distance between the UEs 104. Thus, if UE1 and UE2 are stationary devices, such as sensor devices, the assigned UE IDs may represent a geographical distance between the UEs. The UE IDs may also be configured in this manner for UEs 104 which are stationary or moving within a small area, such as the mobile devices of users attending a concert or event. After the UE1 compares the UE ID in the DCID from the paging message intended for UE2, the UE1 may determine whether to relay the message based on the differences in the UE IDs. In one example, small differences in the UE IDs may indicate that there is a small relative distance between the UE1 and UE2. Based on this small difference and the relay flag being turned on, the UE1 relays or retransmits the paging message for a further chance of receipt by the UE2. In one embodiment, the differences in the UE IDs are compared to a predetermined threshold difference configured for or transmitted to the UE1. If the differences are below the threshold, and the relay flag is turned on, the first device UE1 relays or retransmits the paging message.

[0040] In any of the embodiments described above, it will be appreciated that the paging message may include information which is concatenated for multiple target UEs 104. The paging message may be concatenated for multiple target UEs 104 in a particular zone, as illustrated in Figure 7. The paging message may include the zone ID along with the type, UE ID and resource allocation or data for each target UE 104, 1 to n. The paging message may include a relay flag, as described above, which is determined and turned on or off independently for each target UE 104. As shown in Figure 7, the relay flag may be on for only selected UEs. Alternatively, the paging message may include one relay flag (not shown) for all target UEs 104 included within the paging message.

[0041] Figure 8 illustrates a device 800 adapted to execute embodiments described herein. The device 800 may be a network-side device such as, but not limited to, a TP 106, controller 108, base station, relay-station, or the like. The device 800 may be a user-side device such as, but not limited to, a user equipment (UE) 104. The device 800 may include one or more processing devices 802, such as a processor, a microprocessor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a dedicated logic circuitry, or combinations thereof. The device 800 may also include a memory 804, which may include a volatile or non-volatile memory (e.g., a flash memory, a random access memory (RAM), and/or a read-only memory (ROM)). The memory 804 may consist of a transitory computer readable media such as a RAM, a ROM, an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a flash memory, a CD-ROM, or other portable memory storage. The memory 804 may store instructions for execution by the processing device(s) 802, such as to carry out the present disclosure. The memory 804 may include other software instructions, such as for implementing an operating system and other applications/functions. In one embodiment, the device 800 may include a user interface 808 which may include various inputs/outputs 810 such as a display, keypads, buttons, speaker, microphones or other inputs or outputs.

[0042] The device 800 may include one or more network interfaces 820 for sending and receiving data over the network 100. The network interface(s) 820 may include a transmitter 822, a receiver 824 and any component or collection of components that allow the device 800 to interact and/or communicate with another device, component, or entity. In one embodiment, the device 800 is a network-side device, such as the network controller 108. The network interface 820 may include a wired backhaul interface that allows the network controller 108 to communicate with other network-side devices, e.g., transmission points, access points, gateways, and other network controllers 108. In one embodiment, the device 800 is a network-side device, such as the TP 106. The network interface 820 may include a wired backhaul interface that allows the TP 106 to communicate with other network-side devices, e.g., neighboring transmission points, access points, controllers, gateways, etc. The network interface 820 includes a wireless communications interface to support communications with UEs 104. In some embodiments not covered by the claimed invention, the device 800 is configured to operate as both a network controller 108 and as a TP 106. In another embodiment, the device 800 is a user-side device such as the UE 104. The network interface 820 allows a user or a second user device to interact and/or communicate wirelessly with the UE 104.

[0043] It will be appreciated that the functions of the network interface 820 and wireless communications interface may be carried out by different transceiver or modem components including multiple transmitter, receiver and antenna components or arrays. The one or more network interfaces 820 may be configured for wired or wireless communication with a network, such as but not limited to, an intranet, the Internet, a peer to peer (P2P) network, a wide area network (WAN), local area network (LAN) and/or a mobile communications network such as a 5G, 4G LTE or other network as noted above. The network interface(s) 820 may include wired links (e.g., Ethernet cable) and/or wireless links (e.g., one or more antennas) for intra-network and/or inter-network communications.

[0044] The device 800 may be configured to communicate in accordance with a standard wireless telecommunication protocol. In some embodiments, the device 800 communicates in accordance with a long-term evolution (LTE) protocol. In other embodiments, the device 800 communicates in accordance with another protocol, such as a Wi-Fi protocol defined by Institute of Electrical and Electronics Engineers (IEEE) technical standard 802.11-2012 or 802.11ac-2013.

[0045] Through the descriptions of the preceding embodiments, the present invention may be implemented by using hardware only, or by using software and a necessary universal hardware platform, or by a combination of hardware and software. Based on such understandings, the technical solution of the present invention may be embodied in the form of a software product. The software product may be stored in a non-volatile or non-transitory storage medium, which can be a compact disk read-only memory (CD-ROM), USB flash drive, or a hard disk. The software product includes a number of instructions that enable a computer device (personal computer, server, or network device) to execute the methods provided in the embodiments of the present invention.

[0046] The invention is defined by the appended claims.


Claims

1. A method performed by a device in a wireless communications network (100), comprising:

receiving and storing a device connection identifier of the device while in an active state, wherein the device connection identifier of the device is a dedicated connection identifier, DCID, which is assigned to the device by a network controller (108) of the wireless communications network (100), wherein the device (104) has different operating states with different sets of functionality in each state, and wherein at least some degree of connectivity to the network (100) is supported in each operating state, such that the device (104) maintains its DCID and an always-on connection to the wireless communications network (100);

transitioning from the active state to a standby state, wherein a reduced set of device functionality is supported in the standby state compared to the set of device functionality supported in the active state;

periodically monitoring, while in the standby state, the wireless communications network (100) for a paging message (414, 510) that includes the device connection identifier of the device; and

periodically monitoring, while in the standby state, the wireless communications network (100) for a paging message (612) that includes a relay indicator, wherein the relay indicator is used to indicate that the paging message (612) should be relayed or retransmitted in the wireless communications network (100) for receipt by a target device, and retransmitting (614) the received paging message (612) based on the relay indicator.


 
2. The method of claim 1 wherein the method further comprises receiving data associated with the paging message (414, 510, 612) that includes the device connection identifier.
 
3. The method of claim 2 further comprising transmitting confirmation of receipt of the paging message (414, 510, 612) and data, wherein receiving the data and transmitting the confirmation of receipt are performed by the device in the standby state.
 
4. The method of claim 1 wherein the received paging message (612) that includes the relay indicator further includes a target device identifier for the target device that specifies one or more of a target device zone and a target device type, and wherein the retransmitting (614) the received paging message is further based on one or more of the target device zone and the target device type.
 
5. The method of claim 1 wherein the device connection identifier of the device is associated with a relative geographic location, and wherein the received paging message (612) that includes the relay indicator further includes a device connection identifier for the target device that is associated with the relative geographic location, and the retransmitting (614) the paging message is further based on a physical distance between the device and the target device.
 
6. The method of claim 1, wherein the paging message (414, 510) that includes the device connection identifier of the device further includes resource allocation information for the device to receive data associated with the paging message (414, 510).
 
7. A wireless device (800), comprising:

a communications interface (820);

a processor (802); and

one or more non-transitory computer readable media having computer readable instructions stored thereon for transmitting and receiving data through the communications interface (820), the instructions, when executed by the processor (802), direct the wireless device (800) to:

receive and store a device connection identifier of the wireless device (800) while in an active state, wherein the device connection identifier of the wireless device (800) is a dedicated connection identifier, DCID, which is assigned to the wireless device (800) by a network controller (108) of a wireless communications network (100), wherein the wireless device (800) has different operating states with different sets of functionality in each state, and wherein at least some degree of connectivity to the network (100) is supported in each operating state, such that the wireless device (104) maintains its DCID and an always-on connection to the wireless communications network (100);

transition from the active state to a standby state, wherein a reduced set of device functionality is supported in the standby state compared to the set of device functionality supported in the active state;

periodically monitor, while in the standby state, the wireless communications network (100) for a paging message that includes the device connection identifier of the wireless device (800); and

periodically monitor, while in the standby state, the wireless communications network (100) for a paging message that includes a relay indicator, wherein the relay indicator is used to indicate that the paging message should be relayed or retransmitted in the wireless communications network (100) for receipt by a target device, and retransmit received paging message based on the relay indicator.


 
8. The wireless device (800) of claim 7 wherein the instructions, when executed by the processor (802), further direct the wireless device (800) to receive data associated with the paging message that include the device connection identifier.
 
9. The wireless device (800) of claim 8 wherein the instructions, when executed by the processor (802), further direct the wireless device (800) to transmit confirmation of receipt of the paging message and data, wherein the actions to receive the data and transmit the confirmation of receipt are performed by the wireless device (800) in the standby state.
 
10. The wireless device (800) of claim 7 wherein the received paging message that includes the relay indicator further includes a target device identifier for the target device that specifies one or more of a target device zone and a target device type, and wherein the instructions, when executed by the processor (802), further direct the wireless device (800) to retransmit the received paging message based on one or more of the target device zone and the target device type.
 
11. The wireless device (800) of claim 7 wherein the device connection identifier of the wireless device (800) is associated with a relative geographic location, and wherein the received paging message that includes the relay indicator further includes a device connection identifier for the target device that is associated with the relative geographic location, and the instructions, when executed by the processor (802), further direct the wireless device (800) to retransmit the paging message based on based on a physical distance between the wireless device (800) and the target device.
 
12. The wireless device (800) of claim 7, wherein the paging message that includes the device connection identifier of the wireless device (800) further includes resource allocation information for the wireless device (800) to receive data associated with the paging message.
 
13. A non-transitory computer-readable medium storing computer instructions, that when executed by one or more processors, cause the one or more processors to perform the method according to any one of claims 1-6.
 


Ansprüche

1. Verfahren, das von einem Gerät in einem Drahtloskommunikationsnetz (100) durchgeführt wird, umfassend:

Empfangen und Speichern einer Geräteverbindungskennung des Geräts, während es sich in einem aktiven Zustand befindet, wobei die Geräteverbindungskennung des Geräts eine "Dedicated Connection Identifier", DCID, ist, die dem Gerät von einer Netzwerksteuerung (108) des Drahtloskommunikationsnetzes (100) zugewiesen wird, wobei das Gerät (104) verschiedene Betriebszustände mit verschiedenen Sätzen von Funktionalität in jedem Zustand aufweist, und wobei zumindest ein gewisser Grad an Konnektivität mit dem Netzwerk (100) in jedem Betriebszustand unterstützt wird, derart, dass das Gerät (104) seine DCID und eine ständig aktive Verbindung mit dem Drahtloskommunikationsnetz (100) beibehält;

Übergehen vom aktiven Zustand in einen Bereitschaftszustand, wobei im Bereitschaftszustand ein reduzierter Satz von Gerätefunktionalität im Vergleich zu dem im aktiven Zustand unterstützten Satz von Gerätefunktionalität unterstützt wird;

periodisches Überwachen, während des Bereitschaftszustands, des Drahtloskommunikationsnetzes (100) auf eine Paging-Nachricht (414, 510), die die Geräteverbindungskennung des Geräts beinhaltet; und

periodisches Überwachen, während des Bereitschaftszustands, des Drahtloskommunikationsnetzes (100) auf eine Paging-Nachricht (612), die einen Relay-Indikator beinhaltet, wobei der Relay-Indikator zu der Angabe verwendet wird, dass die Paging-Nachricht (612) im Drahtloskommunikationsnetz (100) zum Empfang durch ein Zielgerät weitergeleitet oder erneut gesendet werden soll, und erneutes Senden (614) der empfangenen Paging-Nachricht (612) auf der Grundlage des Relay-Indikators.


 
2. Verfahren nach Anspruch 1, wobei das Verfahren ferner das Empfangen von Daten umfasst, die der Paging-Nachricht (414, 510, 612), die die Geräteverbindungskennung beinhaltet, zugeordnet sind.
 
3. Verfahren nach Anspruch 2, ferner umfassend das Senden einer Bestätigung des Empfangs der Paging-Nachricht (414, 510, 612) und der Daten, wobei das Empfangen der Daten und das Senden der Bestätigung des Empfangs vom Gerät im Bereitschaftszustand durchgeführt werden.
 
4. Verfahren nach Anspruch 1, wobei die empfangene Paging-Nachricht (612), die den Relay-Indikator beinhaltet, ferner eine Zielgerätekennung für das Zielgerät beinhaltet, die eines oder mehrere von einer Zielgerätezone und einem Zielgerätetyp spezifiziert, und wobei das erneute Senden (614) der empfangenen Paging-Nachricht ferner auf einem oder mehreren von der Zielgerätezone und dem Zielgerätetyp basiert.
 
5. Verfahren nach Anspruch 1, wobei die Geräteverbindungskennung des Geräts einem relativen geografischen Standort zugeordnet ist, und wobei die empfangene Paging-Nachricht (612), die den Relay-Indikator beinhaltet, ferner eine Geräteverbindungskennung für das Zielgerät beinhaltet, die dem relativen geografischen Standort zugeordnet ist, und das erneute Senden (614) der Paging-Nachricht ferner auf einer physischen Entfernung zwischen dem Gerät und dem Zielgerät basiert.
 
6. Verfahren nach Anspruch 1, wobei die Paging-Nachricht (414, 510), die die Geräteverbindungskennung des Geräts beinhaltet, ferner Ressourcenzuweisungsinformationen für das Gerät zum Empfangen von der Paging-Nachricht (414, 510) zugeordneten Daten beinhaltet.
 
7. Drahtlosgerät (800), umfassend:

eine Kommunikationsschnittstelle (820);

einen Prozessor (802); und

ein oder mehrere nicht-flüchtige computerlesbare Medien mit darauf gespeicherten computerlesbaren Anweisungen zum Senden und Empfangen von Daten über die Kommunikationsschnittstelle (820), wobei die Anweisungen, wenn sie vom Prozessor (802) ausgeführt werden, das Drahtlosgerät (800) zu folgenden Vorgängen anweisen:

Empfangen und Speichern einer Geräteverbindungskennung des Drahtlosgeräts (800), während es sich in einem aktiven Zustand befindet, wobei die Geräteverbindungskennung des Drahtlosgeräts (800) eine "Dedicated Connection Identifier", DCID, ist, die dem Drahtlosgerät (800) von einer Netzwerksteuerung (108) eines Drahtloskommunikationsnetzes (100) zugewiesen wird, wobei das Drahtlosgerät (800) verschiedene Betriebszustände mit verschiedenen Sätzen von Funktionalität in jedem Zustand aufweist, und wobei zumindest ein gewisser Grad an Konnektivität mit dem Netzwerk (100) in jedem Betriebszustand unterstützt wird, derart, dass das Drahtlosgerät (104) seine DCID und eine ständig aktive Verbindung mit dem Drahtloskommunikationsnetz (100) beibehält;

Übergehen vom aktiven Zustand in einen Bereitschaftszustand, wobei im Bereitschaftszustand ein reduzierter Satz von Gerätefunktionalität im Vergleich zu dem im aktiven Zustand unterstützten Satz von Gerätefunktionalität unterstützt wird;

periodisches Überwachen, während des Bereitschaftszustands, des Drahtloskommunikationsnetzes (100) auf eine Paging-Nachricht, die die Geräteverbindungskennung des Drahtlosgeräts (800) beinhaltet; und

periodisches Überwachen, während des Bereitschaftszustands, des Drahtloskommunikationsnetzes (100) auf eine Paging-Nachricht, die einen Relay-Indikator beinhaltet, wobei der Relay-Indikator zu der Angabe verwendet wird, dass die Paging-Nachricht im Drahtloskommunikationsnetz (100) zum Empfang durch ein Zielgerät weitergeleitet oder erneut gesendet werden soll, und erneutes Senden der empfangenen Paging-Nachricht auf der Grundlage des Relay-Indikators.


 
8. Drahtlosgerät (800) nach Anspruch 7, wobei die Anweisungen, wenn sie vom Prozessor (802) ausgeführt werden, das Drahtlosgerät (800) ferner anweisen, Daten zu empfangen, die der Paging-Nachricht, die die Geräteverbindungskennung beinhaltet, zugeordnet sind.
 
9. Drahtlosgerät (800) nach Anspruch 8, wobei die Anweisungen, wenn sie vom Prozessor (802) ausgeführt werden, das Drahtlosgerät (800) ferner anweisen, eine Bestätigung des Empfangs der Paging-Nachricht und der Daten zu senden, wobei die Aktionen zum Empfangen der Daten und zum Senden der Empfangsbestätigung vom Drahtlosgerät (800) im Bereitschaftszustand durchgeführt werden.
 
10. Drahtlosgerät (800) nach Anspruch 7, wobei die empfangene Paging-Nachricht, die den Relay-Indikator beinhaltet, ferner eine Zielgerätekennung für das Zielgerät beinhaltet, der eines oder mehrere von einer Zielgerätezone und einem Zielgerätetyp spezifiziert, und wobei die Anweisungen, wenn sie vom Prozessor (802) ausgeführt werden, ferner das drahtlose Gerät (800) anweisen, die empfangene Paging-Nachricht basierend auf einem oder mehreren von der Zielgerätezone und dem Zielgerätetyp erneut zu senden.
 
11. Drahtlosgerät (800) nach Anspruch 7, wobei die Geräteverbindungskennung des Drahtlosgeräts (800) einem relativen geografischen Standort zugeordnet ist, und wobei die empfangene Paging-Nachricht, die den Relay-Indikator beinhaltet, ferner eine Geräteverbindungskennung für das Zielgerät beinhaltet, die dem relativen geografischen Standort zugeordnet ist, und die Anweisungen, wenn sie vom Prozessor (802) ausgeführt werden, ferner das Drahtlosgerät (800) anweisen, die Paging-Nachricht auf der Grundlage einer physischen Entfernung zwischen dem Drahtlosgerät (800) und dem Zielgerät erneut zu senden.
 
12. Drahtlosgerät (800) nach Anspruch 7, wobei die Paging-Nachricht, die die Geräteverbindungskennung des Drahtlosgeräts (800) beinhaltet, ferner Ressourcenzuweisungsinformationen für das Drahtlosgerät (800) zum Empfangen von der Paging-Nachricht zugeordneten Daten beinhaltet.
 
13. Nicht-flüchtiges computerlesbares Medium, auf dem Computeranweisungen gespeichert sind, die bei ihrer Ausführung durch einen oder mehrere Prozessoren den einen oder die mehreren Prozessoren veranlassen, das Verfahren nach einem der Ansprüche 1 bis 6 durchzuführen.
 


Revendications

1. Procédé réalisé par un dispositif dans un réseau de communication sans fil (100), comprenant les étapes consistant à :

recevoir et stocker un identifiant de connexion de dispositif du dispositif pendant que le dispositif est dans un état actif, l'identifiant de connexion de dispositif du dispositif étant un identifiant de connexion dédié (DCID) qui est attribué au dispositif par un contrôleur de réseau (108) du réseau de communication sans fil (100), le dispositif (104) ayant différents états de fonctionnement avec différents ensembles de fonctionnalités dans chaque état, et au moins un certain degré de connectivité au réseau (100) étant pris en charge dans chaque état de fonctionnement, de sorte que le dispositif (104) conserve son DCID et une connexion permanente au réseau de communication sans fil (100) ;

passer de l'état actif à un état de veille, un ensemble réduit de fonctionnalités de dispositif étant pris en charge dans l'état de veille par comparaison avec l'ensemble de fonctionnalités de dispositif pris en charge dans l'état actif ;

surveiller périodiquement, pendant que le dispositif est dans l'état de veille, le réseau de communication sans fil (100) en ce qui concerne un message de radiorecherche (414, 510) qui inclut l'identifiant de connexion de dispositif du dispositif ; et

surveiller périodiquement, pendant que le dispositif est dans l'état de veille, le réseau de communication sans fil (100) en ce qui concerne un message de radiorecherche (612) qui inclut un indicateur de relais, l'indicateur de relais étant utilisé pour indiquer que le message de radiorecherche (612) devrait être relayé ou retransmis dans le réseau de communication sans fil (100) en vue de sa réception par un dispositif cible, et retransmettre (614) le message de radiorecherche (612) reçu sur la base de l'indicateur de relais.


 
2. Procédé selon la revendication 1, le procédé comprenant en outre la réception de données associées au message de radiorecherche (414, 510, 612) qui inclut l'identifiant de connexion de dispositif.
 
3. Procédé selon la revendication 2, comprenant en outre la transmission d'une confirmation de réception du message de radiorecherche (414, 510, 612) et de données, la réception des données et la transmission de la confirmation de réception étant réalisées par le dispositif dans l'état de veille.
 
4. Procédé selon la revendication 1, dans lequel le message de radiorecherche (612) reçu, qui inclut l'indicateur de relais, inclut en outre un identifiant de dispositif cible pour le dispositif cible qui spécifie une zone de dispositif cible et/ou un type de dispositif cible, et dans lequel la retransmission (614) du message de radiorecherche reçu est en outre basée sur la zone de dispositif cible et/ou sur le type de dispositif cible.
 
5. Procédé selon la revendication 1, dans lequel l'identifiant de connexion de dispositif du dispositif est associé à une localisation géographique relative et dans lequel le message de radiorecherche (612) reçu, qui inclut l'indicateur de relais, inclut en outre un identifiant de connexion de dispositif pour le dispositif cible qui est associé à la localisation géographique relative, et la retransmission (614) du message de radiorecherche est en outre basée sur une distance physique entre le dispositif et le dispositif cible.
 
6. Procédé selon la revendication 1, dans lequel le message de radiorecherche (414, 510), qui inclut l'identifiant de connexion de dispositif du dispositif, inclut en outre une information d'affectation de ressource pour le dispositif pour recevoir des données associées au message de radiorecherche (414, 510).
 
7. Dispositif sans fil (800), comprenant :

une interface de communication (820) ;

un processeur (802) ; et

un ou plusieurs supports non temporaires lisibles par ordinateur sur lesquels sont stockées des instructions lisibles par ordinateur pour transmettre et recevoir des données par l'intermédiaire de l'interface de communication (820), les instructions, lorsqu'elles sont exécutées par le processeur (802), donnant l'instruction au dispositif sans fil (800) de :

recevoir et stocker un identifiant de connexion de dispositif du dispositif sans fil (800) pendant que le dispositif sans fil est dans un état actif, l'identifiant de connexion de dispositif du dispositif sans fil (800) étant un identifiant de connexion dédié (DCID) qui est attribué au dispositif sans fil (800) par un contrôleur de réseau (108) d'un réseau de communication sans fil (100), le dispositif sans fil (800) ayant différents états de fonctionnement avec différents ensembles de fonctionnalités dans chaque état, et au moins un certain degré de connectivité au réseau (100) étant pris en charge dans chaque état de fonctionnement, de sorte que le dispositif sans fil (104) conserve son DCID et une connexion permanente au réseau de communication sans fil (100) ;

passer de l'état actif à un état de veille, un ensemble réduit de fonctionnalités de dispositif étant pris en charge dans l'état de veille par comparaison avec l'ensemble de fonctionnalités de dispositif pris en charge dans l'état actif ;

surveiller périodiquement, pendant que le dispositif sans fil est dans l'état de veille, le réseau de communication sans fil (100) en ce qui concerne un message de radiorecherche qui inclut l'identifiant de connexion de dispositif du dispositif sans fil (800) ; et

surveiller périodiquement, pendant que le dispositif est dans l'état de veille, le réseau de communication sans fil (100) en ce qui concerne un message de radiorecherche qui inclut un indicateur de relais, l'indicateur de relais étant utilisé pour indiquer que le message de radiorecherche devrait être relayé ou retransmis dans le réseau de communication sans fil (100) en vue de sa réception par un dispositif cible, et retransmettre le message de radiorecherche reçu sur la base de l'indicateur de relais.


 
8. Dispositif sans fil (800) selon la revendication 7, dans lequel les instructions, lorsqu'elles sont exécutées par le processeur (802), donnent en outre l'instruction au dispositif sans fil (800) de recevoir des données associées au message de radiorecherche qui inclut l'identifiant de connexion de dispositif.
 
9. Dispositif sans fil (800) selon la revendication 8, dans lequel les instructions, lorsqu'elles sont exécutées par le processeur (802), donnent en outre l'instruction au dispositif sans fil (800) de transmettre une confirmation de réception du message de radiorecherche et de données, les actions de réception des données et de transmission de la confirmation de réception étant réalisées par le dispositif sans fil (800) dans l'état de veille.
 
10. Dispositif sans fil (800) selon la revendication 7, dans lequel le message de radiorecherche reçu, qui inclut l'indicateur de relais, inclut en outre un identifiant de dispositif cible pour le dispositif cible qui spécifie une zone de dispositif cible et/ou un type de dispositif cible, et dans lequel les instructions, lorsqu'elles sont exécutées par le processeur (802), donnent en outre l'instruction au dispositif sans fil (800) de retransmettre le message de radiorecherche reçu sur la base de la zone de dispositif cible et/ou du type de dispositif cible.
 
11. Dispositif sans fil (800) selon la revendication 7, dans lequel l'identifiant de connexion de dispositif du dispositif sans fil (800) est associé à une localisation géographique relative et dans lequel le message de radiorecherche reçu, qui inclut l'indicateur de relais, inclut en outre un identifiant de connexion de dispositif pour le dispositif cible qui est associé à la localisation géographique relative, et les instructions, lorsqu'elles sont exécutées par le processeur (802), donnent en outre l'instruction au dispositif sans fil (800) de retransmettre le message de radiorecherche sur la base d'une distance physique entre le dispositif sans fil (800) et le dispositif cible.
 
12. Dispositif sans fil (800) selon la revendication 7, dans lequel le message de radiorecherche, qui inclut l'identifiant de connexion de dispositif du dispositif sans fil (800), inclut en outre une information d'affectation de ressource pour le dispositif sans fil (800) pour recevoir des données associées au message de radiorecherche.
 
13. Support non temporaire lisible par ordinateur, stockant des instructions informatiques qui, lorsqu'elles sont exécutées par un ou plusieurs processeurs, amènent le ou les processeurs à réaliser le procédé selon l'une quelconque des revendications 1 à 6.
 




Drawing





























Cited references

REFERENCES CITED IN THE DESCRIPTION



This list of references cited by the applicant is for the reader's convenience only. It does not form part of the European patent document. Even though great care has been taken in compiling the references, errors or omissions cannot be excluded and the EPO disclaims all liability in this regard.

Patent documents cited in the description




Non-patent literature cited in the description