Patent Application
20190253557
The present invention relates to venue owner-controllable per-venue service configuration. More specifically, the present invention relates to measures (including methods, apparatuses and computer program products) for facilitating venue owner-controllable per-venue service configuration.
The present disclosure generally relates to location-aware services and configuration thereof in communication systems, such as 2G/3G/4G communication networks.
Conventionally, location-aware services are known, for which the location of a terminal device to be served is determined and the services are provided to the terminal device according to its location. Such location-aware services are typically configured by a network operator, to which the user of the terminal device in question is subscribed and via whose network the services are thus to be provided. Namely, in current service models, only the subscriber (user) and the operator have an agreement about services, e.g. location-aware services, which are to be provided by the operator to the subscriber or the subscriber's terminal device.
Accordingly, in current service models, a venue owner, i.e. a responsible for a certain venue area, is not involved in an agreement about services, e.g. location-aware services, between a subscriber and an operator. Accordingly, a venue owner is not capable of effecting or influencing a configuration of location-aware services (i.e. per-venue services) between a subscriber and an operator, even if the subscriber or the subscriber's terminal device is residing within the venue area controlled by the venue owner.
A venue may generally be any (limited) site or place, which is under the control and/or responsibility of a venue owner, and where a number of users with their terminal devices may gather. For example, a venue may be a locality such as a campus, a (e.g. religious) place, a stadium, an office building, a shopping center, or the like. In such venue, certain services or service restrictions may be desired or required by the venue owner. For example, in order to avoid disturbance of a meeting (e.g. an annual general meeting), a (e.g. religious) activity or gathering, an event, or the like in such venue, it may be expected that everybody turns off his/her terminal device or, at least, set his/her terminal device in a silence mode in which a ringing tone is suppressed.
In such exemplary situation, disturbance is difficult be avoided in a safe manner, especially with a high number of participants, as. The venue owner can typically not ensure that everybody has actually turned off his/her terminal device or, at least, set his/her terminal device in a silence mode. For example, everybody will be disturbed when a single participant's phone is ringing because of being left in a general mode and receiving a mobile-terminated (MT) call. While jammers could be installed so as to prevent any signaling and/or traffic to arrive the terminal devices residing in the venue area, such approach has several drawbacks, such as a reduced visibility of subscribers' availability for operators in their networks, a degradation of or an uncertainty about (realistic) key performance indicators (KPIs) for the operator's networks, a need for installation of various jammers for different frequencies, and the like.
Accordingly, it would be desirable for a venue owner to be capable of effecting or influencing a configuration of location-aware services (i.e. per-venue services) for subscribers or subscriber's terminal devices residing within the venue area controlled by the venue owner.
Thus, there is a need to facilitate venue owner-controllable per-venue service configuration.
Various exemplifying embodiments of the present invention aim at addressing at least part of the above issues and/or problems and drawbacks.
Various aspects of exemplifying embodiments of the present invention are set out in the appended claims.
According to an example aspect of the present invention, there is provided a method comprising configuring a per-venue service model of services of a network operator for terminal devices of subscribers of the network operator on the basis of an input by a venue owner of a venue, the per-venue service model including at least one configurable parameter for defining a venue-based service for terminal devices of subscribers residing in a specified venue area of the venue, and causing implementation of the configured per-venue service model for service provision for at least one of a network device of the network operator and a terminal device of a subscriber of the network operator.
According to an example aspect of the present invention, there is provided a method comprising handling a service for a terminal device of a subscriber of a network operator in a network of the network operator, verifying whether a per-venue service model of services of the network operator for terminal devices of subscribers of the network operator is applicable to the handled service for the terminal device, the per-venue service model being configurable by a venue owner of a venue and including at least one configurable parameter for defining a venue-based service for terminal devices of subscribers residing in a specified venue area of the venue, and controlling provision of the handled service to the terminal device in accordance with the per-venue service model when verified to be applicable.
According to an example aspect of the present invention, there is provided a method comprising receiving a service for a terminal device of a subscriber of a network operator via a network of the network operator, and providing the received service to the subscriber, wherein the service is received and/or provided in accordance with a per-venue service model of services of the network operator for terminal devices of subscribers of the network operator, the per-venue service model being configurable by a venue owner of a venue and including at least one configurable parameter for defining a venue-based service for terminal devices of subscribers residing in a specified venue area of the venue.
According to an example aspect of the present invention, there is provided an apparatus comprising means for, or a processor and a memory configured to store computer program code, wherein the processor is configured to cause the apparatus to perform, configuring a per-venue service model of services of a network operator for terminal devices of subscribers of the network operator on the basis of an input by a venue owner of a venue, the per-venue service model including at least one configurable parameter for defining a venue-based service for terminal devices of subscribers residing in a specified venue area of the venue, and causing implementation of the configured per-venue service model for service provision for at least one of a network device of the network operator and a terminal device of a subscriber of the network operator.
According to an example aspect of the present invention, there is provided an apparatus comprising means for, or a processor and a memory configured to store computer program code, wherein the processor is configured to cause the apparatus to perform, handling a service for a terminal device of a subscriber of a network operator in a network of the network operator, verifying whether a per-venue service model of services of the network operator for terminal devices of subscribers of the network operator is applicable to the handled service for the terminal device, the per-venue service model being configurable by a venue owner of a venue and including at least one configurable parameter for defining a venue-based service for terminal devices of subscribers residing in a specified venue area of the venue, and controlling provision of the handled service to the terminal device in accordance with the per-venue service model when verified to be applicable.
According to an example aspect of the present invention, there is provided an apparatus comprising means for, or a processor and a memory configured to store computer program code, wherein the processor is configured to cause the apparatus to perform, receiving a service for a terminal device of a subscriber of a network operator via a network of the network operator, and providing the received service to the subscriber, wherein the service is received and/or provided in accordance with a per-venue service model of services of the network operator for terminal devices of subscribers of the network operator, the per-venue service model being configurable by a venue owner of a venue and including at least one configurable parameter for defining a venue-based service for terminal devices of subscribers residing in a specified venue area of the venue.
According to an example aspect of the present invention, there is provided a computer program product comprising computer-executable computer program code which, when the program code is executed (or run) on a computer or the program is run on a computer (e.g. a computer of an apparatus according to any one of the aforementioned apparatus-related example aspects of the present invention), is configured to cause the computer to carry out the method according to any one of the aforementioned method-related example aspects of the present invention.
The computer program product may comprise or may be embodied as a (tangible/non-transitory) computer-readable (storage) medium or the like, on which the computer-executable computer program code is stored, and/or the program is directly loadable into an internal memory of the computer or a processor thereof.
Further developments and/or modifications of the aforementioned exemplary aspects of the present invention are set out in the following.
By way of exemplifying embodiments of the present invention, venue owner-controllable per-venue service configuration is facilitated.
In the following, the present invention will be described in greater detail by way of non-limiting examples with reference to the accompanying drawings, in which
The present invention is described herein with reference to particular non-limiting examples and to what are presently considered to be conceivable embodiments of the present invention. A person skilled in the art will appreciate that the invention is by no means limited to these examples and embodiments, and may be more broadly applied.
It is to be noted that the following description of the present invention and its embodiments mainly refers to specifications being used as non-limiting examples for certain exemplifying network configurations and system deployments. Namely, the present invention and its embodiments are mainly described in relation to GSM/UMTS/LTE/LTE-A specifications being used as non-limiting examples for certain exemplifying network configurations and deployments. As such, the description of exemplifying embodiments given herein specifically refers to terminology which is directly related thereto. Such terminology is only used in the context of the presented non-limiting examples and embodiments, and does naturally not limit the invention in any way. Rather, any other network configuration or system deployment, etc. may also be utilized as long as complying with wht is described herein and/or exemplifying embodiments described herein are applicable to it.
Hereinafter, various exemplifying embodiments and implementations of the present invention and its aspects are described using several variants and/or alternatives. It is generally noted that, according to certain needs and constraints, all of the described variants and/or alternatives may be provided alone or in any conceivable combination (also including combinations of individual features of the various variants and/or alternatives). In this description, the words “comprising” and “including” should be understood as not limiting the described exemplifying embodiments and implementations to consist of only those features that have been mentioned, and such exemplifying embodiments and implementations may also contain features, structures, units, modules etc. that have not been specifically mentioned.
As used herein, an operator may be an operator of any communication network, including 2G/3G/4G communication networks such as GSM/UMTS/LTE/LTE-A systems, or the like.
As used herein, a venue may be generally any (limited) site or place, which is under the control and/or responsibility of a venue owner, and where a number of users with their terminal devices may be located. For example, a venue may be a locality such as a campus, a (e.g. religious) place, a stadium, an office building, a shopping center, or the like. Namely, the term “venue owner” is to be construed in a broadest manner.
As used herein, a venue owner may be any person or authority, which “owns” a venue in the sense to have control and/or responsibility for the venue. Namely, the term “venue owner” is to be construed in a broadest manner, encompassing an owner in a legal sense, as well as any other responsible, or the like. Generally speaking, the venue may be regarded as a sphere (of control and/or responsibility) of the corresponding venue owner.
According to exemplifying embodiments of the present invention, in general terms, there are provided measures and mechanisms for facilitating venue owner-controllable per-venue service configuration.
In the drawings, it is noted that lines/arrows interconnecting individual blocks or entities are generally meant to illustrate an operational coupling there-between, which may be a physical and/or logical coupling, which on the one hand is implementation-independent (e.g. wired or wireless) and on the other hand may also comprise an arbitrary number of intermediary functional blocks or entities not shown.
As shown in
In such exemplary system configuration, the operator network may be or comprise any 2G/3G/4G communication network, such as e.g. a GSM/UMTS/LTE/LTE-A communication network. The network device may be or comprise any network device in a radio access network or on a base site level, such as a base station of a cell, a femto cell, a micro cell or a pico cell, a base transceiver station (BTS), a NodeB, an eNodeB or a relay node, or any network device in a core network or on a base site control level, such as a base station controller (BSC) or a radio network controller (RNC), or he like. The network device, including any one of the above-mentioned types of network devices could be located on a hierarchy level under a higher-hierarchy network element such as e.g. a MSC Server System (MSS), or the like. The terminal device may be or comprise any device on the terminal/endpoint side of a communication network or system, such as e.g. a mobile station (MS) or a user equipment (UE), or the like.
As shown in
The per-venue service model according to exemplifying embodiments of the present invention includes the at least one configurable parameter, which may be for defining a type of service and/or application for which the per-venue service model is applicable. For example, such type of service/application may include a mobile-terminated voice or data call or messaging service (including e.g. Skype, Yahoo messenger, etc.), a mobile-originated voice or data call or messaging service (including e.g. Skype, Yahoo messenger, etc.), any other type of MT/MO service/call (such as e.g. CSFB), a CS domain service, a PS domain service, a (RBT-based) advertisement announcement and/or replay feature, or the like. Further, the at least one configurable parameter in the per-venue service model according to exemplifying embodiments of the present invention may be for defining one or more a time period (e.g. a single time window, a periodically recurring/periodic time window with a specific periodicity of e.g. a day, a week, a month or a year), in which the per-venue service model is applicable, a content and/or source for service provision in accordance with the per-venue service model (e.g. an audio, visual or audiovisual content to be reproduced to a user, service content from a specific service provider), and a control scheme for service provision in accordance with the per-venue service model (e.g. how a specific service is to be processed by a network device in the course of service handling/provisioning). Such configurability of the per-venue service model according to exemplifying embodiments of the present invention can cover or implement the concept of liquid applications.
As one non-limiting example, the per-venue service model may be defined so as to allow or inhibit issuance of a MO call (i.e. a MO voice and/or data call) and/or reception of a MT call (i.e. a MT voice and/or data call) during the time of a religious activity or gathering for all terminal devices or their users residing in the area of a religious place. As another non-limiting example, the per-venue service model may be defined for a service by which a specific content is played to terminal devices or their users residing in the specific venue are with the (pre-defined or real-time) control of the venue owner, such as e.g. providing the replay of a goal in a soccer match and/or advertisements during the half-time break of the soccer match to the audience in a stadium, which may be controlled by the owner, tenant or operator of the stadium. As still another non-limiting example, the per-venue service model may be defined for a CSFB service/call in that CSFB is enabled/activated for terminal devices residing in a specific (venue) area, e.g. in a specific cell of a 4G (LTE/LTE-A) network, wherein a MT (VoLTE) call to a LTE/LTE-A-capable terminal device, being SGs-associated in the VLR, is handled in the MSS/VLR by sending a page (a CS page via LTE/LTE-A access) towards an appropriate MME (which may be selected based on MME FQDN), the current location of the called terminal device is retrieved from the MME, and CSFB service is applied for the called terminal device such that the MT (VoLTE) call is transferred from the 4G (LTE/LTE-A) network to a 2G/3G network. Otherwise, when the CSFB service is not applied to the non-fulfillment of a condition such as the terminal residing in the specific cell, MT (VoLTE) call is provided via the 4G (LTE/LTE-A) network. Such CSFB service may be configured to be applied for a specific time, and the MT (VoLTE) call can be transferred back from the 2G/3G network to the 4G (LTE/LTE-A) network after lapse of this specific time.
In the per-venue service model according to exemplifying embodiments of the present invention, the venue area may be specified by one or more cells (or cell IDs) of the operator network, together with their associated one or more location areas (or location area codes (LACs)), or by a dedicated location area (or location area code (LAC)) comprising one or more cells of the operator, or by a dedicated geographical area definition (such as e.g. a geographical center and a radius (and potentially also a sector definition) for the venue area). That is, the specified venue area may utilize a conventionally available network area definition or a newly defined network area definition or a newly defined (network-independent) area definition for the purpose of pre-venue service configuration according to exemplifying embodiments of the present invention. In case of a network area definition, a network device may determine whether or not a terminal device resides within the specified venue area. In case of a (network-independent) area definition, a terminal device may determine whether or not it resides within the specified venue area (by way of positioning-related computations), or a network device may determine whether or not a terminal device resides within the specified venue area when the terminal device has previously provided its current position information to the network device.
As shown in
As shown in
As shown in
In the present procedure, the service provision is assumed to be (fully) controlled in accordance with the per-venue service model at the network device (i.e. the network device exhibits full service control). Stated in other words, the service is received at the terminal device in accordance with the per-venue service model. Accordingly, the terminal device is not required to effect a further control on the received service, i.e. no verification of the applicability of the per-venue service model to the received serviced and no control of the provision of the received service to the subscriber in accordance with the per-venue service model are required at the terminal device.
For an illustrative example for the application of such procedure, reference is made to
As shown in
As shown in
In the present procedure, the service provision to the terminal device is assumed to be controlled in accordance with the per-venue service model at the network device, and the service provision to the subscriber is assumed to be controlled at the terminal device (i.e. the network device and the terminal device exhibit a common/combined service control, wherein the portion of service control being exhibited at the network device and the service device may vary). Stated in other words, the service is received at the terminal device in accordance with the per-venue service model. Yet, the terminal device is configured to effect a further control on the received service on the basis of its provision in accordance with the per-venue service model, while no verification of the applicability of the per-venue service model to the received service is required at the terminal device. Service provisioning control can be accomplished on a location basis (e.g. a per cell basis), an activity basis, or the like.
For an illustrative example for the application of such procedure, reference is made to
In the procedures of any one of
As shown in
As shown in
In the present procedure, the service provision is assumed to be (fully) controlled in accordance with the per-venue service model at the terminal device (i.e. the terminal device exhibits full service control). Stated in other words, the service is received at the terminal device in a normal manner, and the received service is provided to the subscriber at the terminal device in accordance with the per-venue service model. Accordingly, the terminal device effects a control on the received service, i.e. both verification of the applicability of the per-venue service model to the received serviced and control of the provision of the received service to the subscriber in accordance with the per-venue service model.
In the procedures of
In the present case, although the full service control/provision will happen at the terminal device, the network device may provide some indication or trigger to the terminal device, which indicates or triggers that the current service/session should be handled under a per-venue service model by the terminal device.
In the procedures of any one of
As shown in
As shown in
As shown in
When all of the checking operations performed in such method yield an affirmative result, it is determined that the per-venue service model is applicable to the service in processing. Otherwise, when one of the checking operations performed in such method yields a negative result, it is determined that the per-venue service model is not applicable to the service in processing.
It is noted that the sequence of the checking operations can be different from that illustrated in
As shown in
When one of the checking operations performed in such method yields an affirmative result, it is determined that the terminal device is residing in the specified venue area. Otherwise, when none of the checking operations performed in such method yields an affirmative result, it is determined that the terminal device is not residing in the specified venue area.
Stated in other words, the terminal device may be determined to reside in the specified venue area when the current LAC of the terminal device itself is fully configurable in the per-venue service model by the venue owner or the cell/cell being configurable in the per-venue service model by the venue owner belong to the current LAC of the terminal device, and, in case the current LAC of the terminal device itself is not fully configurable in the per-venue service model by the venue owner, when additionally the current cell of the terminal device belongs to the cell/cell being configurable in the per-venue service model by the venue owner.
In the following, exemplifying embodiments of the present invention are described with reference to a non-limiting example use case of the above-described principles and procedures.
In the non-limiting example use case underlying the subsequent description, it is assumed that a service of a network operator, which is to be provided to terminal devices of the network operator's subscribers, is a mobile-terminated (MT) call, wherein the call may e.g. comprises a voice call or a data call. Further, it is assumed that the per-venue service model defines a venue-based service for mobile-terminated (MT) calls by suppressing a call arrival tone (e.g. a ringing tone) at the terminal device for mobile-terminated (MT) calls. Such venue-based service for mobile-terminated (MT) calls is assumed to be applicable for terminal devices residing in a specified venue area during a defined time period (time window) only.
Such non-limiting use case can for example refer to a scenario of a religious place representing the venue in question, wherein the venue area thereof may be specified by one or more cells of an operator network, which could be implemented e.g. by one or more base stations or relay nodes of a cell, a femto cell, a micro cell or a pico cell of the operator network. It is assumed that the venue owner, e.g. the parish council, wants to avoid any disturbance during religious activities or gatherings in this religious place, and thus configures a venue-based silence service, in which the specified venue area is defined as a silence zone, the times of religious activities or gatherings are defines as silence time, and the service provision in the silence zone during the silence time is defined to suppress a call arrival tone (e.g. a ringing tone) at the terminal devices for mobile-terminated (MT) calls.
Accordingly, the per-venue service model may be configured by way of corresponding configurable parameters by defining the cell or cells or geographical area of the silence zone, wherein the LAC of the relevant cell or cells could also be included in this entry, and a time period (time window) for the silence time. The time period (time window) can be a single time or a series of time instances, e.g. a periodically recurring time/occasion per day, week, month and/or year. Also, the definition of the silken zone can be accomplished by using a dedicated LAC for the one or more cells where silence is to be applied, thereby simplifying implementation.
Such non-limiting use case is described hereinafter with reference to a network deployment of 3GPP Release 10, while it is to be understood that it is equally applicable to any other network deployment as well, including any 2G/3G/4G communication network such as any GSM/UMTS/LTE/LTE-A system.
For the subsequent description of
The basic MT call flow of
As shown in
As shown in
The processing of the missed call event may be configurable, e.g. by way of the one or more configurable parameters of the per-venue service model. Such configurability of the missed call event can involve e.g. whether one or more messages are to be sent, which type of message or messages is to be sent, whether the message or messages is/are to be sent in real time or in an aggregated manner when such message or messages are to be sent (e.g. during the silence time or at the end of the silence time), and so on. Also, any one of such configurations can be defined to apply per some defined criteria.
In the context of processing of the missed call event, a missed call alert may be initiated or updated. Also, a respective announcement may be generated, and/or respective counters (e.g. for counting a number of stopped MT calls, callers, etc.) may be initiated or updated accordingly.
As one example, the processing of the missed call event may comprise generating and issuing a message for notifying the subscriber of the terminal device about the MT call which has been stopped at the MSS B. For example, a SMS message for the one MT call may be composed and sent straight away upon stopping of the MT call. Sending a SMS message instead of proceeding in a normal call flow including ringing can be accomplished using a MSS-related feature named “Feature 1606: Missed Call Logs Service”.
As another example, the processing of the missed call event may comprise registering the MT call, generating one or more messages for notifying the subscriber of the terminal device about all MT calls during a predetermined time period (which may be equal to or shorter than the defined time period of the per-venue service), and issuing the one or more messages after lapse of the predetermined time period or the defined time period (e.g. the silence time). For example, one or more SMS messages for a number of registered MT calls may be composed and sent after lapse of a configurable time period, i.e. as the time window finishes. When there were more than one MT calls or callers, a number of SMS messages corresponding to the number of MT calls or callers may be composed and sent.
If direct (e.g. SMS) message delivery is possible, then the MSS B being the host of the B party may deliver the (e.g. SMS) message directly itself. Otherwise, the MSS B may give the (e.g. SMS) message to the SMS center (SMSC) or a missed call alert server (in case such is available in the operator network).
As a result of such procedure at the network device, the terminal device does not receive a MT call during the silence time when being located in the silence zone, but may receive one or more (e.g. SMS) messages indicating the stopped MT call or calls during the silence time, either in or after the silence time. That is, the terminal device receives, as the MT call service, a per-venue MT call service in the form of a message (instead of the MT call as such). The thus received pre-venue MT call service may then be provided to the subscriber by displaying the one or more (e.g. SMS) messages received from the operator network (possibly also including blinking in order to indicate message arrival). The terminal device may further suppress any message arrival tone according to the implemented per-venue service model for MT calls for the received MT call service.
In the illustrated example of per-venue service provisioning in a pre-paging phase, the MSS B provides the MSRN of the terminal device to the HLR, which may then sent a SRI ACK message together with the MSRN to the MSS A after the VLR check, and a IAM message with the caller's ID is received at the MSS B only later on (i.e. typically after the verification of pre-venue service model applicability). Upon having the caller's ID and the decision of applicability of the per-venue service model, the network device is able to compose and send a corresponding message or messages to the terminal device representing the B party as a missed call event.
As shown in
The processing of the missed call event in the procedure of
As a result of such procedure at the network device, the terminal device does not receive a MT call during the silence time when being located in the silence zone, but may receive one or more (e.g. SMS) messages indicating the stopped MT call or calls during the silence time, either in or after the silence time. That is, the terminal device receives, as the MT call service, a per-venue MT call service in the form of a message (instead of the MT call as such). The thus received pre-venue MT call service may then be provided to the subscriber by displaying the one or more (e.g. SMS) messages received from the operator network (possibly also including blinking in order to indicate message arrival). The terminal device may further suppress any message arrival tone according to the implemented per-venue service model for MT calls for the received MT call service.
In the illustrated example of per-venue service provisioning in a non-pre-paging phase (e.g. in a setup phase of a channel allocation/assignment phase), the MSS B provides the MSRN of the terminal device to the HLR, which may then sent a SRI ACK message together with the MSRN to the MSS A after the VLR check, and a IAM message with the caller's ID is received at the MSS B straight away (i.e. typically before the verification of pre-venue service model applicability). Upon having the caller's ID and the decision of applicability of the per-venue service model, the network device is able to compose and send a corresponding message or messages to the terminal device representing the B party as a missed call event.
As shown in
When the implemented per-venue service model for MT calls is determined to be not applicable for the handled MT call service, the MT call flow proceeds in a normal manner towards the terminal device, i.e. the BSS B. In the illustrated example, the call flow is normally continued by way of sending a normal setup message (including a standard message header) to the BSS B.
When the implemented per-venue service model for MT calls is determined to be applicable for the handled MT call service, the MT call flow towards the terminal device is continued and indication for suppressing the call arrival tone for the MT call at the terminal device is issued according to the per-venue service model for MT calls (or, in particular, a defined control scheme thereof). In the illustrated example, the call flow is continued by way of sending a setup message with a specifically configured message header including a silence indication to the BSS B.
As a result of such procedure at the network device, the terminal device receives a MT call during the silence time when being located in the silence zone, but such MT call is received with a dedicated setup message including a silence indication (e.g. a flag, an information element, or the like) indicating an instruction to suppress the call arrival tone for the received MT call at the terminal device. That is, the terminal device receives the MT call service, and controls provision of the received MT call service to the subscriber by suppressing the call arrival tone for the MT call in response to the received indication (or instruction) for suppressing the call arrival tone for the MT call. The thus received pre-venue MT call service may then be provided to the subscriber by displaying an indication for the arrival thereof, e.g. by blinking, without producing any tone (or only a display indication tone) in connection with such display.
From a practical point of view, the terminal device, upon being alerted, i.e. having detected that the terminal device is supposed to ring in a normal call flow, the terminal device rather inhibits ringing and checks whether the relevant message (e.g. a setup message) includes a corresponding indication (e.g. a silence indication) and, if so, finally/fully prevents ringing.
In a modification of the illustrated procedure, when the implemented per-venue service model for MT calls is determined to be applicable for the handled MT call service, the MSS B may additionally (e.g. together with or in the setup message) issue information on a geographical center and a radius of the specified venue area according to the per-venue service model for MT calls (or, in particular, a defined control scheme thereof). Then, in the context of controlling provision of the received service to the subscriber, the terminal device may, upon receiving the information on a geographical center and a radius of the specified venue area, calculate the position of the terminal device, and check whether the terminal device is residing in the specified venue area on the basis of the received information and the calculated position. Accordingly, the provision of the received service may be controlled in accordance with the per-venue service model when the terminal device is determined to reside in the specified venue area. Namely, with the assumption that the terminal device is capable of determining its accurate current position, in addition to a silence indication, the radius and center of the silence zone may be sent for the relevant silence zone from network, and the terminal device may re-/determine its current position so as to determine whether it is exactly within the silence zone or not. Thereby, improvements may be achieved in terms of accuracy and location determination tolerances between the network and the terminal device.
In the illustrated example of per-venue service provisioning, applicability thereof in a non-pre-paging phase (e.g. in a setup phase of a channel allocation/assignment phase) is assumed. Thus, the MSS B provides the MSRN of the terminal device to the HLR, which may then sent a SRI ACK message together with the MSRN to the MSS A after the VLR check, and a IAM message with the caller's ID is received at the MSS B straight away (i.e. typically before the verification of pre-venue service model applicability). Yet, as indicated above, the illustrated example of per-venue service provisioning is equally applicable in a pre-paging phase, in which the IAM message with the caller's ID may be received at the MSS B only later on (i.e. typically after the verification of pre-venue service model applicability). Upon having the caller's ID and the decision of applicability of the per-venue service model, the network device is able to send a corresponding indication (in the present example, a silence indication) to the terminal device representing the B party.
According to exemplifying embodiments of the present invention, such as those illustrated in
By virtue of exemplifying embodiments of the present invention, as evident from the above, venue owner-controllable per-venue service configuration is facilitated. Such venue owner-controllable per-venue service configuration may be accomplished by way of a per-venue service model according to exemplifying embodiments of the present invention
Such venue owner-controllable per-venue service configuration and/or such (data centric and/or voice centric) per-venue service model according to exemplifying embodiments of the present invention enables a venue owner to effect or influence a configuration of location-aware services (i.e. per-venue services) between a subscriber and an operator, for the case that the subscriber or the subscriber's terminal device is residing within the venue area controlled by the venue owner.
Accordingly, there is provided a technique for a venue owner to host his/her/its own services/applications through configuration control of a corresponding per-venue service model for services of a network operator according to the venue owner's own needs and desires (rather then those of the network operator). Thereby, the venue owner can affect service provisioning between the network operator and the subscriber in that the venue owner is given a reasonable control to have configurable parameters of per-venue services to be provided via a network device in his/her/its venue configured per his/her/its needs, and also to host certain applications/services in his/her/its venue defined per his/her/its control. For example, the ownership or controllability of liquid applications can thereby be given to the venue owner for his/her/its discretionary decision instead of solely by the network operator's decision.
Generally, such venue owner-controllable per-venue service configuration is applicable to many different scenarios and use cases, wherein only some illustrative examples thereof are described above in a non-limiting manner. That is, a venue owner is generally enabled to tackle specific services in terms of service provisioning within his/her/its specified venue area in a manner controllable by the venue owner, wherein such venue-owner based service provisioning control may be accomplished on a per cell basis.
The above-described methods, procedures and functions may be implemented by respective functional elements, entities, modules, units, processors, or the like, as described below.
While in the foregoing exemplifying embodiments of the present invention are described mainly with reference to methods, procedures and functions, corresponding exemplifying embodiments of the present invention also cover respective apparatuses, entities, modules, units, network nodes and/or systems, including both software and/or hardware thereof.
Respective exemplifying embodiments of the present invention are described below referring to
In
Further, in
As indicated in
The processor 11 and/or the interface 13 of the apparatus 10 may also include a modem or the like to facilitate communication over a (hardwire or wireless) link, respectively. The interface 13 of the apparatus 10 may include a suitable transmitter, receiver or transceiver connected or coupled to one or more antennas, antenna units, such as antenna arrays or communication facilities or means for (hardwire or wireless) communications with the linked, coupled or connected device(s), respectively. The interface 13 of the apparatus 10 is generally configured to communicate with at least one other apparatus, device, node or entity (in particular, the connector thereof).
The memory 12 of the apparatus 10 may represent a (non-transitory/tangible) storage medium and store respective programs, program products, macros or applets, etc. or parts of them, which may be assumed to comprise program instructions or computer program code that, when executed by the respective processor, enables the respective electronic device or apparatus to operate in accordance with the exemplifying embodiments of the present invention.
In general terms, respective apparatuses (and/or parts thereof) may represent means for performing respective operations and/or exhibiting respective functionalities, and/or the respective devices (and/or parts thereof) may have functions for performing respective operations and/or exhibiting respective functionalities.
In view of the above, the thus illustrated apparatus 10 is suitable for use in practicing one or more of the exemplifying embodiments of the present invention, as described herein.
When in the subsequent description it is stated that the processor (or some other means) is configured to perform some function, this is to be construed to be equivalent to a description stating that a (i.e. at least one) processor or corresponding circuitry, potentially in cooperation with a computer program code stored in the memory of the respective apparatus or otherwise available (it should be appreciated that the memory may also be an external memory or provided/realized by a cloud service or the like), is configured to cause the apparatus to perform at least the thus mentioned function. Also, such function is to be construed to be equivalently implementable by specifically configured circuitry or means for performing the respective function (i.e. the expression “processor configured to [cause the apparatus to] perform xxx-ing” is construed to be equivalent to an expression such as “means for xxx-ing”).
The thus illustrated apparatus 10 may represent or realize/embody a (part of a) network operator device according to exemplifying embodiments of the present invention, and it may be configured to perform a procedure and/or exhibit a functionality as described (for the network operator entity) in
In this case, the apparatus 10 may be caused or the apparatus 10 or its processor 11 (possibly together with computer program code stored in the memory 12), in its most basic form, is configured to perform configuring a per-venue service model of services of a network operator for terminal devices of subscribers of the network operator on the basis of an input by a venue owner of a venue, the per-venue service model including at least one configurable parameter for defining a venue-based service for terminal devices of subscribers residing in a specified venue area of the venue, and causing implementation of the configured per-venue service model for service provision for at least one of a network device of the network operator and a terminal device of a subscriber of the network operator.
The thus illustrated apparatus 10 may represent or realize/embody a (part of a) network device according to exemplifying embodiments of the present invention, and it may be configured to perform a procedure and/or exhibit a functionality as described (for the network device) in any one of
In this case, the apparatus 10 may be caused or the apparatus 10 or its processor 11 (possibly together with computer program code stored in the memory 12), in its most basic form, is configured to perform handling a service for a terminal device of a subscriber of a network operator in a network of the network operator, verifying whether a per-venue service model of services of the network operator for terminal devices of subscribers of the network operator is applicable to the handled service for the terminal device, the per-venue service model being configurable by a venue owner of a venue and including at least one configurable parameter for defining a venue-based service for terminal devices of subscribers residing in a specified venue area of the venue, and controlling provision of the handled service to the terminal device in accordance with the per-venue service model when verified to be applicable.
The thus illustrated apparatus 10 may represent or realize/embody a (part of a) terminal device according to exemplifying embodiments of the present invention, and it may be configured to perform a procedure and/or exhibit a functionality as described (for the terminal device) in any one of
In this case, the apparatus 10 may be caused or the apparatus 10 or its processor 11 (possibly together with computer program code stored in the memory 12), in its most basic form, is configured to perform receiving a service for a terminal device of a subscriber of a network operator via a network of the network operator, and providing the received service to the subscriber, wherein the service is received and/or provided in accordance with a per-venue service model of services of the network operator for terminal devices of subscribers of the network operator, the per-venue service model being configurable by a venue owner of a venue and including at least one configurable parameter for defining a venue-based service for terminal devices of subscribers residing in a specified venue area of the venue.
For further details regarding the operability/functionality of the individual apparatuses according to exemplifying embodiments of the present invention, reference is made to the above description in connection with any one of
As mentioned above, any apparatus according to exemplifying embodiments of the present invention may be structured by comprising respective means for performing corresponding operations, procedures and/or functions. For example, such means may be implemented/realized on the basis of an apparatus structure, as exemplified in
As shown in
According to exemplifying embodiments, as described above, it is noted that the apparatus 100 may further comprise means for accessing a configuration tool for the per-venue service model by the venue owner using at least one of a predefined port, address, username, password, authentication or encryption (denoted as configuration tool accessing means 130), and means for inputting a setting vale for the at least one configurable parameter by the venue owner (denoted as setting value inputting means 140)
As shown in
According to exemplifying embodiments, as described above, it is noted that the apparatus 200 may further comprise one or more of:
As shown in
According to exemplifying embodiments, as described above, it is noted that the apparatus 300 may further comprise one or more of:
In
According to exemplifying embodiments of the present invention, any one of the processor, the memory and the connector, as well as any one of the means, may be implemented as individual modules, chips, chipsets, circuitries or the like, or one or more of them can be implemented as a common module, chip, chipset, circuitry or the like, respectively.
According to exemplifying embodiments of the present invention, a system may comprise any conceivable combination of the thus depicted devices/apparatuses and other network elements, which are configured to cooperate as described above.
In general, it is to be noted that respective functional blocks or elements according to above-described aspects can be implemented by any known means, either in hardware and/or software, respectively, if it is only adapted to perform the described functions of the respective parts. The mentioned method steps can be realized in individual functional blocks or by individual devices, or one or more of the method steps can be realized in a single functional block or by a single device.
Generally, any method step is suitable to be implemented as software or by hardware without changing the idea of the present invention. Such software may be software code independent and can be specified using any known or future developed programming language, such as e.g. Java, C++, C, and Assembler, as long as the functionality defined by the method steps is preserved. Such hardware may be hardware type independent and can be implemented using any known or future developed hardware technology or any hybrids of these, such as MOS (Metal Oxide Semiconductor), CMOS (Complementary MOS), BiMOS (Bipolar MOS), BiCMOS (Bipolar CMOS), ECL (Emitter Coupled Logic), TTL (Transistor-Transistor Logic), etc., using for example ASIC (Application Specific IC (Integrated Circuit)) components, FPGA (Field-programmable Gate Arrays) components, CPLD (Complex Programmable Logic Device) components or DSP (Digital Signal Processor) components. A device/apparatus may be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of a device/apparatus or module, instead of being hardware implemented, be implemented as software in a (software) module such as a computer program or a computer program product comprising executable software code portions for execution/being run on a processor. A device may be regarded as a device/apparatus or as an assembly of more than one device/apparatus, whether functionally in cooperation with each other or functionally independently of each other but in a same device housing, for example.
Apparatuses and/or means or parts thereof can be implemented as individual devices, but this does not exclude that they may be implemented in a distributed fashion throughout the system, as long as the functionality of the device is preserved. Such and similar principles are to be considered as known to a skilled person.
Software in the sense of the present description comprises software code as such comprising code means or portions or a computer program or a computer program product for performing the respective functions, as well as software (or a computer program or a computer program product) embodied on a tangible medium such as a computer-readable (storage) medium having stored thereon a respective data structure or code means/portions or embodied in a signal or in a chip, potentially during processing thereof.
The present invention also covers any conceivable combination of method steps and operations described above, and any conceivable combination of nodes, apparatuses, modules or elements described above, as long as the above-described concepts of methodology and structural arrangement are applicable.
In view of the above, there are provided measures for venue owner-controllable per-venue service configuration. Such measures could comprise configuring a per-venue service model of services of a network operator for terminal devices of subscribers of the network operator on the basis of an input by a venue owner of a venue, the per-venue service model including at least one configurable parameter for defining a venue-based service for terminal devices of subscribers residing in a specified venue area of the venue, and controlling provision of services of the network operator to terminal devices or subscribers of terminal devices in accordance with the per-venue service model depending on applicability thereof for the service provision.
Even though the invention is described above with reference to the examples according to the accompanying drawings, it is to be understood that the invention is not restricted thereto. Rather, it is apparent to those skilled in the art that the present invention can be modified in many ways without departing from the scope of the inventive idea as disclosed herein.
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15039190 | May 2016 | US |
| Child | 16394771 | US |
