WO2019047139A1

WO2019047139A1 - Waking up configuration of communication device

Info

Publication number: WO2019047139A1
Application number: PCT/CN2017/100981
Authority: WO
Inventors: Jinyin Zhu; Zhiwei Qu
Original assignee: Telefonaktiebolaget LM Ericsson AB
Current assignee: Telefonaktiebolaget LM Ericsson AB
Priority date: 2017-09-08
Filing date: 2017-09-08
Publication date: 2019-03-14
Anticipated expiration: 2020-03-08

Abstract

A method for communications is proposed. The method may comprise obtaining configuration information from a network node. The configuration information may indicate a waking up configuration for a terminal device. The method may further comprise performing the waking up configuration based at least in part on the configuration information.

Description

[Title established by the ISA under Rule 37.2] WAKING UP CONFIGURATION OF COMMUNICATION DEVICE

FIELD OF THE INVENTION

The present disclosure generally relates to communications, and more specifically, to wireless communications.

BACKGROUND

This section introduces aspects that may facilitate a better understanding of the disclosure. Accordingly, the statements of this section are to be read in this light and are not to be understood as admissions about what is in the prior art or what is not in the prior art.

In a current vision of the future development of wireless communication networks, a number of autonomous wireless devices become increasingly important. These autonomous wireless devices may typically, more or less infrequently (for example, once per week to once per minute) participate in data communications with a wireless network. For example, a wireless device or user equipment (UE) , such as a machine-to-machine (M2M) communication device, a machine type communication (MTC) device and/or the like, may communicate with a server within or outside a cellular network. The server can configure the UE and facilitate data communications with the UE. For the sake of energy efficient, the UE may apply a power saving mode (PSM) or a discontinuous reception (DRX) mechanism to conserve energy.

SUMMARY

This summary is provided to introduce a selection of concepts in a simplified form that are further described below in detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

Lower cost communication devices or UEs such as MTC devices may facilitate and expedite implementation of the networked society such as an Internet of things (IoT) scenario or a cellular Internet of things (C-IoT) . An energy efficient mechanism such as PSM or DRX can allow a UE to spend most of the time in a sleep mode where no reception and/or transmission is required, while waking up to listen for certain traffic transmissions only on specific occasions. The functionality of fixed waking up time and duration may bring much benefit in such a way that an application server (AS) can have a well-planned schedule of activities especially when such activities need human-being’s engagement.

The present disclosure proposes a solution of waking up a communication device, which may enable a network node to configure a UE in an efficient way so that the UE can wake up at the specified time and keep being reachable for the duration as requested by an AS.

According to a first aspect of the present disclosure, there is provided a method implemented at a terminal device. The method may comprise obtaining configuration information from a network node. The configuration information may indicate a waking up configuration for the terminal device. The method may further comprise performing the waking up configuration based at least in part on the configuration information.

According to a second aspect of the present disclosure, there is provided an apparatus. The apparatus may comprise one or more processors and one or more memories comprising computer program codes. The one or more memories and the computer program codes may be configured to, with the one or more processors, cause the apparatus at least to perform any step of the method according to the first aspect of the present disclosure.

According to a third aspect of the present disclosure, there is provided a computer-readable medium having computer program codes embodied thereon for use with a computer. The computer program codes may comprise code for performing any step of the method according to the first aspect of the present disclosure.

According to a fourth aspect of the present disclosure, there is provided an apparatus. The apparatus may comprise an obtaining module and a performing module. In accordance with some exemplary embodiments, the obtaining module may be operable to carry out at least the obtaining step of the method according to the first aspect of the present disclosure. The performing module may be operable to carry out at least the performing step of the method according to the first aspect of the present disclosure.

According to a fifth aspect of the present disclosure, there is provided a method implemented at a network node. The method may comprise determining configuration information which indicates a waking up configuration for a terminal device. The method may further comprise providing the configuration information to the terminal device.

Optionally, the method according to the fifth aspect of the present disclosure may further comprise updating a status record of the terminal device based at least in part on the configuration information. For example, the status record may indicate a time slot within which the terminal device is reachable in communication.

According to a sixth aspect of the present disclosure, there is provided an apparatus. The apparatus may comprise one or more processors and one or more memories comprising computer program codes. The one or more memories and the computer program codes may be configured to, with the one or more processors, cause the apparatus at least to perform any step of the method according to the fifth aspect of the present disclosure.

According to a seventh aspect of the present disclosure, there is provided a computer-readable medium having computer program codes embodied thereon for use with a computer. The computer program codes may comprise code for performing any step of the method according to the fifth aspect of the present disclosure.

According to an eighth aspect of the present disclosure, there is provided an apparatus. The apparatus may comprise a determining module and a providing module. In accordance with some exemplary embodiments, the determining module may be operable to carry out at least the determining step of the method according to the fifth aspect of the present disclosure. The providing module may be operable to carry out at least the providing step of the method according to the fifth aspect of the present disclosure.

In accordance with some exemplary embodiments, the waking up configuration may comprise enabling the terminal device to be reachable in communication within a predefined time slot. For example, the configuration information may comprise one or more parameters indicating starting time and duration of the predefined time slot.

In accordance with some exemplary embodiments, the waking up configuration may be applicable for a group of devices comprising at least the terminal device.

In accordance with some exemplary embodiments, the configuration information may be a part of subscription data for the terminal device. Alternatively or additionally, the configuration information may be obtained in a non-access stratum message.

In accordance with some exemplary embodiments, the waking up configuration may be specified by a subscriber server or by an application server through a subscriber server. For example, the waking up configuration may be specified by triggering a configuration event.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosure itself, the preferable mode of use and further objectives are best understood by reference to the following detailed description of the embodiments when read in conjunction with the accompanying drawings, in which:

Fig. 1 is a diagram illustrating an exemplary network architecture for MTC according to an embodiment of the present disclosure；

Fig. 2 is a flowchart illustrating a method according to an embodiment of the present disclosure；

Fig. 3 is a flowchart illustrating a method according to another embodiment of the present disclosure；

Figs. 4A-4B are diagrams illustrating exemplary waking up configuration procedures according to some embodiments of the present disclosure；

Figs. 5A-5B are diagrams illustrating exemplary waking up configuration procedure according to some embodiments of the present disclosure；

Fig. 6 is a block diagram illustrating an apparatus according to some embodiments of the present disclosure；

Fig. 7 is a block diagram illustrating another apparatus according to some embodiments of the present disclosure； and

Fig. 8 is a block diagram illustrating yet another apparatus according to some embodiments of the present disclosure.

DETAILED DESCRIPTION

The embodiments of the present disclosure are described in detail with reference to the accompanying drawings. It should be understood that these embodiments are discussed only for the purpose of enabling those skilled persons in the art to better understand and thus implement the present disclosure, rather than suggesting any limitations on the scope of the present disclosure. Reference throughout this specification to features, advantages, or similar language does not imply that all of the features and advantages that may be realized with the present disclosure should be or are in any single embodiment of the disclosure. Rather, language referring to the features and advantages is understood to mean that a specific feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the present disclosure. Furthermore, the described features, advantages, and characteristics of the disclosure may be combined in any suitable manner in one or more embodiments. One skilled in the relevant art will recognize that the disclosure may be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments of the disclosure.

As used herein, the term “wireless communication network” may refer to a network following any suitable communication standards, such as long term evolution-advanced (LTE-A) , LTE, wideband code division multiple access (WCDMA) , high-speed packet access (HSPA) , and so on. Furthermore, the communications between a terminal device and a network node in the wireless communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the future fifth generation (5G) communication protocols, and/or any other protocols either currently known or to be developed in the future.

The term “network node” may refer to a network device in a wireless communication network via which a terminal device accesses to the network and receives services therefrom. The network device may refer to a base station (BS) , an access point (AP) , a mobile management entity (MME) , multi-cell/multicast coordination entity (MCE) , a gateway, a server, a controller or any other suitable device in the wireless communication network. The BS may be, for example, a node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a next generation NodeB (gNodeB or gNB) , a remote radio unit (RRU) , a radio header (RH) , a remote radio head (RRH) , a relay, a low power node such as a femto, a pico, and so forth.

Yet further examples of the network node may comprise multi-standard radio (MSR) radio equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs) , base transceiver stations (BTSs) , transmission points, transmission nodes, MCEs, core network nodes, positioning nodes and/or the like. More generally, however, the network node may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a terminal device access to the wireless communication network or to provide some service to a terminal device that has accessed to the wireless communication network.

The term “terminal device” may refer to any end device that can access a wireless communication network and receive services therefrom. By way of example and not limitation, the terminal device may refer to a mobile terminal, a UE, or other suitable devices. The UE may be, for example, a subscriber station, a portable subscriber station, a mobile station (MS) or an access terminal (AT) . The terminal device may include, but not limited to, portable computers, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, a mobile phone, a cellular phone, a smart phone, a tablet, a wearable device, a personal digital assistant (PDA) , a vehicle, and the like.

The terminal device may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, and may in this case be referred to as a D2D communication device.

As yet another specific example, in an IoT scenario, a terminal device may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another terminal device and/or a network equipment. The terminal device may in this case be a M2M device, which may in a 3GPP context be referred to as a MTC device.

As one particular example, the terminal device may be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances, e.g. refrigerators, televisions, personal wearables such as watches etc. In other scenarios, a terminal device may represent a vehicle or other equipment, for example, a medical instrument that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.

As used herein, the terms “first” , “second” and so forth may refer to different elements. The singular forms “a” and “an” are intended to include the plural forms as well, unless the context clearly indicates otherwise. The terms “comprises” , “comprising” , “has” , “having” , “includes” and/or “including” as used herein, specify the presence of stated features, elements, and/or components and the like, but do not preclude the presence or addition of one or more other features, elements, components and/or combinations thereof. The term “based on” is to be read as “based at least in part on” . The term “one embodiment” and “an embodiment” are to be read as “at least one embodiment” . The term “another embodiment” is to be read as “at least one other embodiment” . Other definitions, explicit and implicit, may be included below.

Wireless communication technologies are currently being developed and improved to address the optimized network architecture and the enhanced communication coverage. For example, the C-IoT is a new radio technology which may be able to provide extended coverage for harsh environments such as basements, and is designed to serve a number of UEs using a very limited bandwidth. Cellular communication networks may be designed to support MTC as a form of data communication which involves one or more entities that do not necessarily need human interactions.

A terminal device such as a MTC device or UE may have lower demands on data rates than for example mobile broadband, but with higher requirements on, for example, low manufacturing cost, better coverage, and/or low operational power consumption. An energy-efficient mechanism such as PSM or extended idle-mode DRX cycle (eDRX) may be employed to reduce battery consumption and facilitate longer battery life. For example, a PSM and/or eDRX enabled UE can go into the PSM or sleep mode in case that no transmissions/re-transmissions and no pending re-transmissions are required for a period of time. The UE may only need to be awake periodically for a short amount of time to monitor the downlink (DL) transmissions. If new uplink (UL) data become available, the UE can wake up at any time and inform the network through configured UL resources.

Fig. 1 is a diagram illustrating an exemplary network architecture for MTC according to an embodiment of the present disclosure. A feature of the MTC concept is the ability for a machine to perform automatic data transmissions in a network where each data transmission can be initiated by a first machine, routed through a network, and delivered to one or more other machines so that the one or more other machines can take an action or otherwise respond to the first machine without or with limited human intervention. In another embodiment, a plurality of machines may initiate a data transmission to be routed through a network and delivered to one or more other machines. It will be appreciated that the MTC can be used in various communications networks, although the exemplary network architecture for MTC shown in Fig. 1 is in accordance with the 3^rd generation partnership project (3GPP) communication standard.

As illustrated in Fig. 1, a service capability server (SCS) 107 may provide services to the core network, devices and applications. The SCS 107 may be controlled by the operator of the home public land mobile network (HPLMN) or by an MTC service provider. The SCS 107 can communicate with a machine type communication interworking function (MTC-IWF) 106 via a Tsp interface or reference point. The MTC-IWF 106 may relay and/or translate signaling protocols used between itself and the SCS 107 to support MTC functionality. For example, the SCS 107 may request that the MTC-IWF 106 send a trigger to a MTC device.

The MTC-IWF 106 can communicate with a short message service (SMS) service center/gateway mobile switching center/interworking mobile switching center (SMS-SC/GMSC/IW MSC) 103 via a T4 interface or reference point. The MTC-IWF 106 in the HPLMN also can communicate with a mobile switching center/mobile management entity/serving general packet radio service support node (MSC/MME/SGSN) 110 in the virtual public land mobile network (VPLMN) via a T5a/b/c interface or reference point.

As further illustrated in Fig. 1, an S6m interface or reference point may connect the MTC-IWF 106 to a home subscriber server (HSS) 102. A MTC authentication authorization accounting (MTC-AAA) 101 and a service capability exposure function (SCEF) 105 can communicate with the HSS 102 via S6n and S6t interfaces, respectively. The HSS 102 can communicate with MME/

SGSNs

104 and 108 via an S6a/d interface or reference point. The SCEF 105 can communicate with the MME/

SGSNs

104 and 108 via a T6a/b interface or reference point. The SCEF 105 can be connected to an IW K-SCEF 109 through a T7 interface or reference point. The MME/SGSN 108 can communicate with the IW K-SCEF 109 via a T6ai/T6bi interface or reference point.

The SCS 107 may offer capabilities for use by one or more application server MTC applications. An AS (not shown in Fig. 1) may host one or more MTC applications. The MTC applications on the AS may interact with the SCS 107, UE MTC applications, and/or other MTC applications.

For the C-IoT deployment, there may be use cases where an AS needs to communicate with a UE (such as a MTC device) periodically at a fixed time slot, for example, from 11: 00 pm to 11: 05 pm every Monday, when power saving functionality such as PSM and/or eDRX is probably enabled. The typical use cases are downloading data to the MTC device, configuring the MTC device with new parameters, ordering the MTC device to take some collecting and reporting actions, etc.

In an exemplary embodiment, a UE with PSM and/or eDRX enabled may be reachable when the UE is in a connected state, or when the UE is in an idle state and is within the active time window and/or within the paging time window (PTW) . For the PSM, an active timer and optionally a periodical tracking area update/routing area update (TAU/RAU) timer may be requested by the UE and decided by the network. Similarly, some parameters for the eDRX may be requested by the UE and decided by the network.

If the UE is not in the PTW or if the UE enters the sleeping mode, it becomes unreachable. The next time the UE becomes reachable may be when the PTW occurs again and/or the UE wakes up again. The time when the UE is reachable may vary from time to time and is not predictable. However, the AS may need to communicate with the UE at a fixed time slot. Therefore, a mechanism securing that the UE and the AS can communicate with each other during a fixed time slot may be highly expected.

Taking the advantage of the predictable waking up configuration makes it possible to ensure that a UE can wake up at a fixed/given time and keep being reachable in communication for a certain period. In the proposed solution according to some exemplary embodiments of the present disclosure, a specific waking up configuration or provision may be applied to a UE so that an AS can communicate with the UE in a well-planned way.

Fig. 2 is a flowchart illustrating a method according to an embodiment of the present disclosure. The method illustrated in Fig. 2 may be performed by an apparatus implemented at a terminal device or communicatively coupled to a terminal device. In accordance with the exemplary embodiment, the terminal device may comprise a UE, a mobile station, a wireless device, a PDA, a laptop computer, a tablet computer, a smart phone, a portable device, a MTC device, or any other user device being capable of participating in communication of a wireless network.

According to the exemplary method illustrated in Fig. 2, the terminal device (such as a UE or a MTC device) can obtain configuration information from a network node (such as an access and mobility management function (AMF) , a MME, a SGSN or any other suitable network entity) , as shown in block 202. In an exemplary embodiment, the configuration information may indicate a waking up configuration for the terminal device. For example, the waking up configuration may comprise enabling the terminal device to be reachable in communication within a predefined time slot.

In accordance with an exemplary embodiment, the configuration information may comprise one or more parameters indicating starting time and duration of the predefined time slot. For example, the configuration information may comprise configuration parameters such as waking up time, waking up duration and/or the like. The waking up time may indicate an absolute waking up time for a UE. Alternatively, the waking up time may indicate an absolute waking up time in a day together with a definition of periodical occurrence, for example, daily, every Monday in a week, etc. The waking up duration may indicate how long that the UE needs to keep being reachable starting from the waking up time. In this way, the UE may be enabled to wake up at a fixed time and keep being reachable for a certain period as demanded by an AS or other suitable network entities.

In accordance with an exemplary embodiment, the waking up configuration may be applicable for a group of devices comprising at least the terminal device. In other words, the waking up configuration may be specified for a plurality UEs which can be regarded as a group of UEs sharing the same or similar network configuration. For example, in order to avoid the big impact on a network by traffic bursts and minimize the power consumption on a UE, the values of the configuration parameters (such as waking up time and waking up duration) and the number of UEs to which the configuration parameters may be applied need to be carefully set based at least in part on the service level agreement (SLA) . For large number of UEs to be configured, the AS can divide the UEs into different groups and the configuration parameter values for these groups may be different enough so as to make the potential traffic smooth.

In accordance with an exemplary embodiment, the configuration information may be a part of subscription data for the terminal device. For example, the waking up configuration parameters may be set as a part of subscription data for a UE and sent from a HSS to a MME/SGSN/AMF and then to the UE. The subscription data may be transmitted in a signaling message from the HSS to the MME/SGSN/AMF, such as an update location answer message, an insert subscriber data request message, and/or the like.

In accordance with an exemplary embodiment, the configuration information may be obtained by the terminal device in a non-access stratum (NAS) message. For example, the NAS message which can be used to carry the configuration parameters such as waking up time and waking up duration to the UE may comprise an attach accept message, a TAU/RAU accept message, and/or the like. In response to a reception of the waking up configuration parameters, for example, during an attach procedure, a TAU/RAU procedure and/or the like, the UE may store these parameters until the new configuration parameters are received or the universal integrated circuit card (UICC) is removed from the UE.

According to the exemplary method illustrated in Fig. 2, the terminal device can perform the waking up configuration based at least in part on the configuration information, as shown in block 204. For example, the terminal device such as a UE may behave according to the waking up configuration parameters. At the point of waking up time, if the UE is in the sleeping mode, the UE would wake up to be active. Then the UE may keep active within the period defined by the waking up duration. In accordance with an exemplary embodiment, within the period defined by the waking up duration, the eDRX functionality may be disabled. At the point of time of waking up time plus waking up duration, the UE may restart or resume the normal PSM and/or eDRX functionality. For example, the UE can restart the active timer and eDRX cycle. It may be appreciated that the waking up in such a way would not impact the mobile reachable timer and the implicit detach timer.

Fig. 3 is a flowchart illustrating a method according to another embodiment of the present disclosure. The method illustrated in Fig. 3 may be performed by an apparatus implemented at a network node or communicatively coupled to a network node. In accordance with the exemplary embodiment, the network node may comprise a MME, a SGSN, an AMF, a HSS, a SCEF, a SCS, an AS, or any other network device being capable of participating in the waking up configuration of a terminal device.

Corresponding to operations of the exemplary method as illustrated in Fig. 2, the network node in the exemplary method as illustrated in Fig. 3 may determine configuration information which indicates a waking up configuration for a terminal device, as shown in block 302. For example, the configuration information may comprise one or more parameters indicating starting time and duration of a predefined time slot. As such, the waking up configuration can enable the terminal device to be reachable in communication within the predefined time slot.

In accordance with the exemplary embodiment, the network node may provide the configuration information to the terminal device, as shown in block 304. For example, the configuration information may be transmitted from the network node to the terminal device directly or through one or more intermediate nodes. The waking up configuration can provide a predictable time slot within which the terminal device such as a UE is reachable, so that a network entity such as an AS can communicate with the UE in a well-planned way.

In accordance with an exemplary embodiment, the waking up configuration may be specified or provisioned by a subscriber server or by an AS through a subscriber server. Optionally, the waking up configuration may be specified or provisioned by triggering a configuration event. For example, the subscriber server such as a HSS may have a capability of provisioning the waking up configuration. In the case that the network node as described in connection with Fig. 3 comprises the HSS, the network node can determine the configuration information of the terminal device by locally specifying the waking up configuration for the terminal device. Alternatively or additionally, the network node can determine the configuration information of the terminal device by obtaining the waking up configuration specified or provisioned by a SCS/AS through a SCEF, for example, in response to a predefined event (such as a monitoring event or other network configuration event) being triggered. In an exemplary embodiment, the network node such as the HSS can transmit the determined waking up configuration to a MME/SGSN/AMF initiatively or as requested by the MME/SGSN/AMF.

In accordance with an exemplary embodiment, the network node as described in connection with Fig. 3 may comprise a SCS/AS and can determine the configuration information of the terminal device by locally specifying the waking up configuration for the terminal device. As mentioned previously, the waking up configuration may be applicable for a group of devices comprising at least the terminal device. In this case, the SCS/AS may indicate the group of devices (for example, by a group identifier) when transmitting the waking up configuration to a HSS through a SCEF.

In accordance with an exemplary embodiment, the network node as described in connection with Fig. 3 may comprise a SCEF. In this case, the SCEF can determine the configuration information of the terminal device in a signaling message from a SCS/AS to the SCEF, such as a monitoring request message, a T8 set suggested network configuration request message, or any other suitable message.

In accordance with an exemplary embodiment, the network node as described in connection with Fig. 3 may comprise a MME/SGSN/AMF. In this case, the MME/SGSN can determine the configuration information of the terminal device by requesting it from a HSS or through an initiative notification from the HSS. Then the configuration information may be provided from the MME/SGSN/AMF to the terminal device, for example, as a part of subscription data. Optionally, the configuration information may be provided to the terminal device in NAS message, such as an attach accept message, a TAU/RAU accept message or any other suitable message.

In accordance with an exemplary embodiment, based at least in part on the configuration information, the network node such as a MME/SGSN/AMF may update a status record of the terminal device. For example, the status record may indicate a time slot within which the terminal device (such as a UE) is reachable in communication. According to an exemplary embodiment, the time slot may be indicated by some waking up configuration parameters such as waking up time and waking up duration. At the point of waking up time, the MME/SGSN/AMF may consider the UE as active and set a paging processing flag (PPF) correspondingly. Within the period defined by the waking up duration, the MME/SGSN/AMF may initiate a potential data communication with the UE since the UE is considered as active according to the waking up configuration. Optionally, the eDRX functionality may be disabled within the period defined by the waking up duration. At the point of time of waking up time plus waking up duration, the MME/SGSN/AMF and the UE may restart or resume the normal PSM and/or eDRX functionality.

It will be realized that the waking up configuration parameters and the parameter setting described herein are just examples. Other suitable parameter settings, the associated waking up configuration parameters and the specific values thereof may also be applicable to implement the proposed methods.

In accordance with some exemplary embodiments, the UE may be configured or provisioned with the waking up configuration parameters (such as waking up time and waking up duration) through two schemes: one is relative static and the other is relative dynamic. For example, the static scheme may be regarded as a subscription data based configuration scheme and can be performed in a network scenario where a HSS has a capability of provisioning a waking up configuration. On the other hand, the dynamic scheme may be regarded as a SCEF based configuration scheme and can be adjusted by a SCS/AS upon the service requirements/needs.

Figs. 4A-4B are diagrams illustrating exemplary waking up configuration procedures according to some embodiments of the present disclosure. The exemplary waking up configuration procedures illustrated in Figs. 4A-4B may correspond to the subscription data based configuration scheme where the waking up configuration parameters such as waking up time and duration are provisioned in a HSS as a part of subscription data and sent to a MME/SGSN. Then the waking up configuration parameters may be sent to a UE during an attach procedure or a TAU/RAU procedure. It will be appreciated that signaling messages and network elements shown in Figs. 4A-4B are just as examples, and more or less alternative signaling messages and network elements may be involved in the waking up configuration procedure.

According to the procedure shown in Fig. 4A, a UE 401 may initiate an attach/TAU/RAU procedure by sending 411 an attach/TAU/RAU request message to a MME/SGSN 402. In the case that there is no subscription data available, the MME/SGSN 402 may send 412 an update location request message to a HSS 403. The HSS 403 may send 413 an update location answer message to the MME/SGSN 402. The waking up configuration parameters such as waking up time and duration may be included in the update location answer message. The MME/SGSN 402 can store these parameters as received. Then the MME/SGSN 402 may send 414 an attach/TAU/RAU accept message to the UE 401. Thus, the UE 401 can obtain the waking up configuration parameters such as waking up time and duration included in the attach/TAU/RAU accept message.

According to the procedure shown in Fig. 4B, the HSS 403 may send 421 an insert subscriber data request message to the MME/SGSN 402. In this way, the HSS 403 can initiatively provide the waking up configuration parameters such as waking up time and duration to the MME/SGSN 402, for example, for the purpose of updating the waking up configuration. The MME/SGSN 402 can store the waking up configuration parameters and send 422 an insert subscriber data answer message to the HSS 403. During a subsequent attach procedure or TAU/RAU procedure 423, the MME/SGSN 402 may include the waking up configuration parameters such as waking up time and duration in an attach or TAU/RAU accept message to the UE 401. Optionally, the MME/SGSN 402 can initiate a detach procedure to the UE 401 for requiring the UE 401 to perform a reattach procedure, when the UE 401 is reachable but there is no TAU/RAU procedure triggered or ongoing. In this way, the MME/SGSN 402 can provide the waking up configuration parameters to the UE 401 more quickly and timely.

Figs. 5A-5B are diagrams illustrating exemplary waking up configuration procedure according to some embodiments of the present disclosure. The exemplary waking up configuration procedures illustrated in Figs. 5A-5B may correspond to the SCEF based configuration scheme where the waking up configuration parameters such as waking up time and duration are provisioned by a SCS/AS via a HSS. For example, upon a request from the SCS/AS, the SCEF can correspondingly configure the waking up configuration parameters in the HSS and a MME/SGSN for a UE or a group of UEs. Then the parameters may be sent to an individual UE during a subsequent attach procedure or a TAU/RAU procedure. After the parameters are successfully sent to the UE, the MME/SGSN may report a configuration result to the SCEF and then to the SCS/AS. Optionally, this kind of configuration may be considered as a one-time request. It will be appreciated that signaling messages and network elements shown in Figs. 5A-5B are just as examples, and more or less alternative signaling messages and network elements may be involved in the waking up configuration procedure.

According to the procedure shown in Fig. 5A, the SCS/AS 505 may send 511 a monitoring request message to the SCEF 504. For example, the SCS/AS 505 may set a parameter of monitoring type to “waking up time configuration” and include some waking up configuration parameters such as waking up time and duration in the message. That is to say, the waking up configuration may be initiated by triggering a monitoring event. In accordance with an exemplary embodiment, if the SCS/AS 505 wants to configure a monitoring event for a group of UEs, the SCS/AS 505 can include some parameters associated with the waking up configuration with respect to the group of UEs, such as an external group identifier, group reporting guard time and/or the like, in the monitoring request message sent to the SCEF 504.

Correspondingly, the SCEF 504 can handle 512 the received monitoring request message according to a predefined criterion. For example, the SCEF 504 may reject the request if the SCS/AS 505 is not authorized or the configuration parameters are not authorized. In the case that the SCEF 505 accepts the request from the SCS/AS 505, a monitoring request message containing the waking up configuration parameters such as waking up time and duration may be sent 513 to the HSS 503.

Similarly, the HSS 503 can handle 514 the received monitoring request message according to a predefined criterion. For example, the HSS 503 may reject the request if the configuration parameters are not authorized. In the case that the HSS 503 accepts the request from the SCEF 504, the HSS 503 may store the waking up configuration parameters received in the monitoring request message.

In accordance with an exemplary embodiment where the monitoring event is configured for a group of UEs, the HSS 503 may receive the monitoring request message with an external group identifier for the group based processing. Optionally, the HSS 503 can send 515a a monitoring response message (for example, comprising a SCEF reference identifier, a cause and/or the like) to the SCEF 504 to acknowledge acceptance of the monitoring request immediately before beginning the processing of individual UEs, indicating that the group based processing is in progress. The HSS 503 may delete the monitoring event configuration identified by the SCEF reference identifier, if it was requested. Correspondingly, the SCEF 504 may reply 515b to the SCS/AS 505 with a monitoring response to indicate that the group based processing is in progress.

According to an exemplary embodiment, the waking up configuration parameters may be configured to the UE 501 as a part of subscriber data. For example, the HSS 503 may send 516 an insert subscriber data request message comprising waking up configuration parameters such as waking up time and duration to the MME/SGSN 502. Correspondingly, the MME/SGSN 502 can handle 517 the received message, for example, by storing the waking up configuration parameters and updating a status record of the UE 501. Then the MME/SGSN 502 may send 518 an insert subscriber data answer message to the HSS 503. Similarly, the HSS 503 may send 519 a monitoring response message to the SCEF 504 which may send 520 a monitoring response message to the SCS/AS 505 accordingly.

In accordance with an exemplary embodiment, the MME/SGSN 502 may configure the waking up configuration parameters to the UE 501 during a subsequent attach procedure or a TAU/RAU procedure 521, for example, by including the waking up time and duration in an attach accept message or a TAU/RAU accept message to the UE 501. Optionally, the MME/SGSN 502 may initiate a detach procedure to the UE 501 for requiring the UE 501 to reattach, when the UE 501 is reachable but there is no TAU/RAU procedure triggered or ongoing.

In accordance with an exemplary embodiment, the MME/SGSN 502 may send 522 a monitoring indication message to the SCEF 504 to report a result of the waking up configuration in the MME/SGSN 502 and the UE 501. In the case that the waking up configuration is considered as a one-time request, the monitoring event configuration may be deleted by the MME/SGSN 502 upon completion of reporting the configuration result to the SCEF 504. Similarly, the SCEF 504 may send 523 a monitoring indication message to the SCS/AS 505 to report a result of the waking up configuration. Since the waking up configuration is considered as a one-time request, the monitoring event configuration may be deleted by the SCEF 504 upon completion of reporting the configuration result to the SCS/AS 505.

Alternatively, the waking up configuration of the UE 501 also may be provisioned by other suitable configuration events and//or network requests, in addition to the monitoring event and request as illustrated in Fig. 5A. For example, according to the procedure shown in Fig. 5B, the SCS/AS 505 may send 531 a T8 set suggested network configuration request message to the SCEF 504 to request to configure the waking up parameters in the MME/SGSN 502 and the UE 501. Optionally, the T8 set suggested network configuration request message may comprise some parameters related to the configuration, such as T8 transaction reference identifier (TTRI) , T8 long term transaction reference identifier (TLTRI) , an external identifier or mobile station integrated services digital network number (MSISDN) or external group identifier, a SCS/AS identifier, waking up time and duration, group reporting guard time, and/or the like. In accordance with an exemplary embodiment, the TTRI is a parameter which refers to transactions between the SCEF and the SCS/AS when using T8 interface. The transactions may comprise a request message followed by one or more response messages. The TTRI may be created by the originator of the transaction, and is unique through the duration of the transaction. Similarly, the TLTRI is a parameter which refers to long term transactions between the SCEF and the SCS/AS when using T8 interface. The long term transactions may comprise one or more request messages which may have one or more response messages (for example, one or more transactions represented by a TTRI) . The TLTRI may be created by the originator of the transaction, and is unique through the duration of the transaction. Optionally, the TTRI and/or the TLTRI may be stored on both the SCEF and the SCS/AS for the duration of the transaction.

As shown in Fig. 5B, the SCEF 504 can handle 532 the received request message according to a predefined criterion. For example, the SCEF 504 may store the received TLTRI and assign it to a SCEF reference identifier. Based on operator policies, if either the SCS/AS 505 is not authorized to perform this request (for example, if the SLA does not allow for it) or the set suggested network configuration request is malformed, the SCEF 504 can reject the request and provide a cause value appropriately indicating the error to the SCS/AS 505. Alternatively or additionally, the SCEF 504 can check whether the waking up configuration can be accepted based on the operator policies. If it is not accepted, the SCEF 504 may reject the request and provide a cause value indicating the rejection to the SCS/AS 505.

In the case that the SCEF 504 accepts the request, it may send 533 a set suggested network configuration request message to the HSS 503 to configure the waking up parameters in the HSS 503 and the MME/SGSN 502. For example, the set suggested network configuration request message may comprise some parameters related to the configuration, such as an external identifier or MSISDN or external group identifier, a SCEF identifier, a SCEF reference identifier, waking up time and duration, group reporting guard time, and/or the like.

Correspondingly, the HSS 503 can handle 534 the received request message according to a predefined criterion. In an exemplary embodiment, the HSS 503 may check the set suggested network configuration request message, for example, with regard to the existence of an external identifier or MSISDN or external group identifier or whether the waking up time and duration are acceptable. The HSS 503 may reject the request if this check fails. Optionally, the HSS 503 may provide a cause value indicating the reason for the failure condition to the SCEF 504.

In accordance with an exemplary embodiment where the waking up configuration is requested for a group of UEs, the SCEF 504 may receive the T8 set suggested network configuration request message with an external group identifier for the group based processing, and correspondingly the HSS 503 may receive the set suggested network configuration request message with the external group identifier for the group based processing. For the group based processing, the HSS 503 can send 535 a set suggested network configuration response message (for example, comprising a SCEF reference identifier, a cause and/or the like) to the SCEF 504 to acknowledge acceptance of the set suggested network configuration request before beginning the processing of individual UEs, indicating that the group processing is in progress. Similarly, the SCEF 504 may send 536 a T8 set suggested network configuration response message (for example, comprising a TTRI, a TLTRI, a cause and/or the like) to the SCS/AS 505. The cause value may indicate the progress of the group processing request.

According to an exemplary embodiment, the waking up parameters may be configured to the UE 501 as a part of subscriber data. For example, the HSS 503 may send 537 an insert subscriber data request message (for example, comprising waking up time and duration) to the MME/SGSN 502 for the individual UE or for each individual group member UE. If the set suggested network configuration request message from the SCEF 504 is for a group of UEs, the HSS 503 may send an insert subscriber data request message per UE to all the MME/SGSN (s) serving the members of the group.

The MME/SGSN 502 can handle 538 the request message received from the HSS 503 accordingly. For example, the MME/SGSN 502 may check whether the waking up time and duration in the request message are acceptable. If this check fails, the MME/SGSN 502 may reject the request and provide a cause value indicating the reason for the failure condition to the HSS 503. Based on operator policies, the MME/SGSN 502 may also reject the request due to other reasons (for example, overload or the HSS 503 has exceeded its quota or rate of submitting requests defined by a SLA) .

As shown in Fig. 5B, the MME/SGSN 502 may send 539 an insert subscriber data answer message to the HSS 503, based at least in part on a handling result of the insert subscriber data request. Correspondingly, the HSS 503 may send 540 a set suggested network configuration response message to the SCEF 504. Similarly, the SCEF 504 may send 541 a T8 set suggested network configuration response message to the SCS/AS 505.

In accordance with an exemplary embodiment where the set suggested network configuration request message from the SCEF 504 to the HSS 503 has no external group identifier, the waking up configuration is processed for a single UE. In this case, the HSS 503 may send 540, for the individual UE, a set suggested network configuration response message (for example, comprising a SCEF reference identifier, the cancelled SCEF reference identifier, a cause and/or the like) to the SCEF 504 to acknowledge acceptance of the set suggested network configuration request or indicate the rejection of the set suggested network configuration request.

Similarly, for the waking up configuration with respect to a single UE, the T8 set suggested network configuration request message from the SCS/AS 505 to the SCEF 504 has no external group identifier. In this case, the SCEF 504 may send 541 a T8 set suggested network configuration response message (for example, comprising a TTRI, a TLTRI, the cancelled TLTRI, a cause and/or the like) to the SCS/AS 505.

In accordance with an exemplary embodiment where the set suggested network configuration request message from the SCEF 504 to the HSS 503 has an external group identifier and the group reporting guard time, the waking up configuration is processed for a group of UEs. In this case, the HSS 503 may accumulate multiple responses for the group of UEs within the group reporting guard time. In response to the expiration of the group reporting guard time, the HSS 503 may send 540 to the SCEF 504 a set suggested network configuration response message (for example, comprising a SCEF reference identifier, a cause, a list of (external identifier or MSISDN, cancelled SCEF reference identifier, cause) , and/or the like) with the accumulated responses. Optionally, the HSS 503 may include a UE identity and a cause value indicating the reason for the failure in the response message if the configuration of this UE failed.

Similarly, for the waking up configuration with respect to a group of UEs, the T8 set suggested network configuration request message from the SCS/AS 505 to the SCEF 504 has an external group identifier and the group reporting guard time. In this case, the SCEF 504 may send 541 to the SCS/AS 505 a T8 set suggested network configuration response message (for example, comprising a TTRI, a TLTRI, a cause, a list of (external identifier or MSISDN, cancelled TLTRI, cause) , and/or the like) with the accumulated responses received 540 from the HSS 503.

In accordance with an exemplary embodiment, the MME/SGSN 502 may configure the waking up parameters to the UE 501 during a subsequent attach procedure or a TAU/RAU procedure 542, for example, by including the waking up time and duration in an attach accept message or a TAU/RAU accept message to the UE 501. Optionally, the MME/SGSN 502 can initiate a detach procedure to the UE 501 for requiring the UE 501 to reattach when the UE 501 is reachable in order to speed up the waking up configuration to the UE 501.

In accordance with some exemplary embodiments, one or more information elements related to the waking up configuration, such as waking up time and waking up duration, may be provisioned from the SCS/AS to the SCEF in a message via a T8 interface, and then to the HSS in a message via a S6t interface. Further, the waking up configuration can be provisioned to the MME/SGSN and the UE in proper signaling messages. For example, information elements such as waking up time and waking up duration may be added in an update location answer message and/or an insert subscriber data request message over an S6a/d interface between the HSS and the MME/SGSN. Then the MME/SGSN can add these information elements in a NAS message such as an attach accept message and/or a RAU/TAU accept message between the MME/SGSN and the UE.

The proposed solutions as illustrated with respect to Figs. 1-5B can enhance the communications between a terminal device and a network node as the terminal device may be enabled to wake up at a fixed time and keep being reachable for a certain period as demanded by the network node. In this way, the network node such as an AS can have a well-planned schedule of activities of the terminal device such as a UE.

The various blocks shown in Figs. 1-5B may be viewed as method steps, and/or as operations that result from operation of computer program code, and/or as a plurality of coupled logic circuit elements constructed to carry out the associated function (s) . The schematic flow chart diagrams described above are generally set forth as logical flow chart diagrams. As such, the depicted order and labeled steps are indicative of specific embodiments of the presented methods. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more steps, or portions thereof, of the illustrated methods. Additionally, the order in which a particular method occurs may or may not strictly adhere to the order of the corresponding steps shown.

Fig. 6 is a block diagram illustrating an apparatus 600 according to some embodiments of the present disclosure. As shown in Fig. 6, the apparatus 600 may comprise one or more processors such as processor 601 and one or more memories such as memory 602 storing computer program codes 603. In an exemplary embodiment, the one or more memories 602 and the computer program codes 603 may be configured to, with the one or more processors 601, cause the apparatus 600 at least to perform any operation of the method as described in connection with Fig. 2. In another exemplary embodiment, the one or more memories 602 and the computer program codes 603 may be configured to, with the one or more processors 601, cause the apparatus 600 at least to perform any operation of the method as described in connection with Fig. 3.

Alternatively or additionally, the one or more memories 602 and the computer program codes 603 may be configured to, with the one or more processors 601, cause the apparatus 600 at least to perform more or less operations to implement the proposed methods according to the exemplary embodiments of the present disclosure.

Fig. 7 is a block diagram illustrating another apparatus 700 according to some embodiments of the present disclosure. As shown in Fig. 7, the apparatus 700 may comprise an obtaining module 701 and a performing module 702. In an exemplary embodiment, the apparatus 700 may be implemented at a terminal device such as a UE, a MTC device or the like. The obtaining module 701 may be operable to carry out the operation in block 202, and the performing module 702 may be operable to carry out the operation in block 204. Optionally, the obtaining module 701 and/or the performing module 702 may be operable to carry out more or less operations to implement the proposed methods according to the exemplary embodiments of the present disclosure.

Fig. 8 is a block diagram illustrating yet another apparatus according to some embodiments of the present disclosure. As shown in Fig. 8, the apparatus 800 may comprise a determining module 801 and a providing module 802. In an exemplary embodiment, the apparatus 800 may be implemented at a network node such as a MME, a SGSN, an AMF, a HSS, a SCEF, a SCS, an AS, etc. The determining module 801 may be operable to carry out the operation in block 302, and the providing module 802 may be operable to carry out the operation in block 304. Optionally, the determining module 801 and/or the providing module 802 may be operable to carry out more or less operations to implement the proposed methods according to the exemplary embodiments of the present disclosure.

In general, the various exemplary embodiments may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although the disclosure is not limited thereto. While various aspects of the exemplary embodiments of this disclosure may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

As such, it should be appreciated that at least some aspects of the exemplary embodiments of the disclosure may be practiced in various components such as integrated circuit chips and modules. It should thus be appreciated that the exemplary embodiments of this disclosure may be realized in an apparatus that is embodied as an integrated circuit, where the integrated circuit may comprise circuitry (as well as possibly firmware) for embodying at least one or more of a data processor, a digital signal processor, baseband circuitry and radio frequency circuitry that are configurable so as to operate in accordance with the exemplary embodiments of this disclosure.

It should be appreciated that at least some aspects of the exemplary embodiments of the disclosure may be embodied in computer-executable instructions, such as in one or more program modules, executed by one or more computers or other devices. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types when executed by a processor in a computer or other device. The computer executable instructions may be stored on a computer readable medium such as a hard disk, optical disk, removable storage media, solid state memory, random access memory (RAM) , etc. As will be appreciated by one of skill in the art, the function of the program modules may be combined or distributed as desired in various embodiments. In addition, the function may be embodied in whole or partly in firmware or hardware equivalents such as integrated circuits, field programmable gate arrays (FPGA) , and the like.

The present disclosure includes any novel feature or combination of features disclosed herein either explicitly or any generalization thereof. Various modifications and adaptations to the foregoing exemplary embodiments of this disclosure may become apparent to those skilled in the relevant arts in view of the foregoing description, when read in conjunction with the accompanying drawings. However, any and all modifications will still fall within the scope of the non-Limiting and exemplary embodiments of this disclosure.

Claims

A method implemented at a terminal device, comprising:

obtaining (202) configuration information from a network node, wherein the configuration information indicates a waking up configuration for the terminal device； and

performing (204) the waking up configuration based at least in part on the configuration information.
The method according to claim 1, wherein the waking up configuration comprises enabling the terminal device to be reachable in communication within a predefined time slot.
The method according to claim 2, wherein the configuration information comprises one or more parameters indicating starting time and duration of the predefined time slot.
The method according to any of claims 1 to 3, wherein the waking up configuration is applicable for a group of devices comprising at least the terminal device.
The method according to any of claims 1 to 4, wherein the configuration information is a part of subscription data for the terminal device.
The method according to any of claims 1 to 5, wherein the configuration information is obtained in a non-access stratum message.
The method according to any of claims 1 to 6, wherein the waking up configuration is specified by a subscriber server or by an application server through a subscriber server.
An apparatus (600) , comprising:

one or more processors (601) ； and

one or more memories (602) comprising computer program codes (603) ,

the one or more memories (602) and the computer program codes (603) configured to, with the one or more processors (601) , cause the apparatus (600) at least to:

obtain configuration information from a network node, wherein the configuration information indicates a waking up configuration for the apparatus； and

perform the waking up configuration based at least in part on the configuration information.
The apparatus according to claim 8, wherein the waking up configuration comprises enabling the apparatus to be reachable in communication within a predefined time slot.
The apparatus according to claim 9, wherein the configuration information comprises one or more parameters indicating starting time and duration of the predefined time slot.
The apparatus according to any of claims 8 to 10, wherein the waking up configuration is applicable for a group of devices comprising at least the apparatus.
The apparatus according to any of claims 8 to 11, wherein the configuration information is a part of subscription data for the apparatus.
The apparatus according to any of claims 8 to 12, wherein the configuration information is obtained in a non-access stratum message.
The apparatus according to any of claims 8 to 13, wherein the waking up configuration is specified by a subscriber server or by an application server through a subscriber server.
A method implemented at a network node, comprising:

determining (302) configuration information which indicates a waking up configuration for a terminal device； and

providing (304) the configuration information to the terminal device.
The method according to claim 15, wherein the waking up configuration comprises enabling the terminal device to be reachable in communication within a predefined time slot.
The method according to claim 16, wherein the configuration information comprises one or more parameters indicating starting time and duration of the predefined time slot.
The method according to any of claims 15 to 17, wherein the waking up configuration is applicable for a group of devices comprising at least the terminal device.
The method according to any of claims 15 to 18, wherein the configuration information is provided to the terminal device as a part of subscription data.
The method according to any of claims 15 to 19, wherein the configuration information is provided to the terminal device in a non-access stratum message.
The method according to any of claims 15 to 20, wherein the waking up configuration is specified by a subscriber server or by an application server through a subscriber server.
The method according to any of claims 15 to 21, wherein the waking up configuration is specified by triggering a configuration event.
The method according to any of claims 15 to 22, further comprising:

updating a status record of the terminal device based at least in part on the configuration information, wherein the status record indicates a time slot within which the terminal device is reachable in communication.
An apparatus (600) , comprising:

one or more processors (601) ； and

one or more memories (602) comprising computer program codes (603) ,

the one or more memories (602) and the computer program codes (603) configured to, with the one or more processors (601) , cause the apparatus (600) at least to:

determine configuration information which indicates a waking up configuration for a terminal device； and

provide the configuration information to the terminal device.
The apparatus according to claim 24, wherein the waking up configuration comprises enabling the terminal device to be reachable in communication within a predefined time slot.
The apparatus according to claim 25, wherein the configuration information comprises one or more parameters indicating starting time and duration of the predefined time slot.
The apparatus according to any of claims 24 to 26, wherein the waking up configuration is applicable for a group of devices comprising at least the terminal device.
The apparatus according to any of claims 24 to 27, wherein the configuration information is provided to the terminal device as a part of subscription data.
The apparatus according to any of claims 24 to 28, wherein the configuration information is provided to the terminal device in a non-access stratum message.
The apparatus according to any of claims 24 to 29, wherein the waking up configuration is specified by a subscriber server or by an application server through a subscriber server.
The apparatus according to any of claims 24 to 30, wherein the waking up configuration is specified by triggering a configuration event.
The apparatus according to any of claims 24 to 31, wherein the one or more memories and the computer program codes are configured to, with the one or more processors, cause the apparatus at least further to:

update a status record of the terminal device based at least in part on the configuration information, wherein the status record indicates a time slot within which the terminal device is reachable in communication.
A computer-readable medium having computer program codes (603) embodied thereon for use with a computer, wherein the computer program codes (603) comprise codes for performing the method according to any one of claims 1-7 and claims 15-23.
An apparatus (700) , comprising:

an obtaining module (701) for obtaining configuration information from a network node, wherein the configuration information indicates a waking up configuration for the apparatus； and

a performing module (702) for performing the waking up configuration based at least in part on the configuration information.
An apparatus (800) , comprising:

a determining module (801) for determining configuration information which indicates a waking up configuration for a terminal device； and

a providing module (802) for providing the configuration information to the terminal device.