Sign In to Follow Application
View All Documents & Correspondence

Method And System For Porting Vas Subcription Details In A Telecommunication Network

Abstract: The present invention describes a method and a system for communicating VAS subscription details of network element based Value Added Services and content based Value Added Services in a telecommunication network. The system is composed of various sub-components to receive a subscriber request for exporting VAS subscription details maintained by a first network operator, such that the VAS subscriptions of the subscriber are permanently & seamlessly ported to a second network operator from the first network operator. A data file comprising VAS subscription details of the subscriber is generated by a node of the first network operator and communicated to a node of the second network operator. The subscription details in the data file are communicated from the first network operator to the second network operator using universal identifiers for VAS and digital content registered with universal registries. FIGURE 1

Get Free WhatsApp Updates!
Notices, Deadlines & Correspondence

Patent Information

Application #
Filing Date
11 November 2014
Publication Number
52/2014
Publication Type
INA
Invention Field
COMMUNICATION
Status
Email
mail@lexorbis.com
Parent Application
Patent Number
Legal Status
Grant Date
2023-01-06
Renewal Date

Applicants

Comviva Technologies Limited
A-26, Info City, Sector 34, Gurgaon - 122001, Haryana, India

Inventors

1. KUMAR, Nitin
G-86, Sarita Vihar, New Delhi – 110076, India
2. SETHI, Tarun
35 Vaishali, Dabri-Palam Road, New Delhi – 110045, India

Specification

FIELD OF THE INVENTION:
The present invention relates to methods and system for porting subscription information from one network operator to another, during the procedure of mobile number portability.

BACKGROUND OF THE INVENTION:
The concept of mobile number portability (MNP) is now well known in terms of various types of telecommunication networks like Mobile communication network, PSTN, ISP, etc. The user availing the MNP facility generally switches from one operator to another because of network quality and any other customer care related issues. During such a scenario, as a subscriber moves from one network operator to another, any value added service (VAS) that the moving user had subscribed in an old network operator needs to be also relinquished.

Accordingly, in case the user wishes to avail the similar VAS with respect to a new network operator, the subscriber has to go through the rigorous procedure of re-application and re-subscription of the similar VAS. This is due to the fact that any telecommunication network till date has no way to import or port subscribed VAS from previous network. Accordingly, the new network operator also has to spend considerable effort in educating and helping the newly arrived user to discover and subscribe to the VAS.

Consider an example of RBT (Ring Back Tone) based VAS subscribed by the user in a home network with some specific kind of RBT features like special caller RBT, group RBT, conditional RBT etc. In case the customer moves to a new network, one has to re-visit the whole subscription process and configuration of settings.

Moreover, if the newly arrived user is reluctant to re-visit the VAS subscription and configuration process, it's a loss of revenue for the new network operator owing to non-subscription of such VAS, in which the user has been otherwise interested and has been a regular patron.

Accordingly, there has been a long felt need to completely port the VAS services from one mobile network operator to another as the user undertakes MNP to switch to a new network
Another need is to facilitate identification of any specific VAS and associated features across various network operators through unique identifiers.

OBJECT OF THE INVENTION:
Thus, it is an object of the present invention to enable a complete export of value added services (VAS) from an old network operator to a new network operator as a subscriber switches operators during mobile network portability (MNP).

Another object of the present invention is to enable aforesaid export of VAS by providing unique identifiers to a VAS as well as associated features for identification across various network operators.

Yet another object of the present invention is to enable aforesaid export of VAS by providing unique identifiers to various types of digital content associated with the VAS.

SUMMARY OF THE INVENTION:
Accordingly, the present invention provides a method of communicating VAS subscription details in a telecommunication network, the method comprising:
receiving, by a first network operator node, a request from a subscriber ported to a second network operator, for exporting VAS subscription details maintained by a first network operator in respect of the subscriber;
generating, by the first network operator node, a data file comprising subscription details maintained by the first network operator in respect of the subscriber; and
communicating, by the first network operator node, the generated data file to a second network operator node.

The present invention also provides a method of communicating VAS subscription details in a telecommunication network, the method comprising:
receiving, by a first network operator node, a request from a second network operator node for exporting VAS subscription details maintained by a first network operator in respect of a subscriber ported to a second network operator from the first network operator;
generating, by the first network operator node, a file in a predefined format based on combining the subscriber’s VAS subscription details extracted from at least one of a centralized subscription management system and a plurality of subscription management systems associated with the first network operator; and
communicating, by the first network operator node, the generated file to the second network operator node.

The present invention also furthermore provides a method of communicating VAS subscription details in a telecommunication network, the method comprising:
receiving, by a current network operator node, a request from a subscriber ported to a current network operator from a previous network operator, for importing the subscriber’s VAS subscription details from the previous network operator;
requesting, by the current network operator node, a designated node of the previous network operator to import VAS subscription details associated with the subscriber, wherein the VAS subscription details are imported as a file in a pre-defined format from the designated node, the file comprising subscription details maintained by at least one of a centralized subscription management system and a plurality of subscription management systems linked with the previous network operator;
selecting, by the current network operator node, a sub-set of the subscription details out of the subscription details present in the received file based on a subscriber input comprising at least one identifier related to at least one of a network element based VAS and a content based VAS;
transferring the sub-set of the subscription details to at least one of a centralized subscription management system and a plurality of subscription management systems linked with the current network operator for activating at least one VAS associated with said at least one identifier.

The present invention further provides a system for communicating VAS subscription details in a telecommunication network, the system comprising:
a receiver associated with a first network operator for receiving a request, from a subscriber ported to a second network operator, for exporting VAS subscription details maintained by the first network operator in respect of the subscriber;
a generator associated with the first network operator for generating a data file comprising subscription details maintained by the first network operator in respect of the subscriber; and
a transmitter associated with the first network operator for communicating the generated data file to a second network operator node.

The present invention also provides a system for communicating VAS subscription details in a telecommunication network, wherein the system comprises:
a receiver associated with a first network operator for receiving a request, from a second network operator node, for exporting VAS subscription details maintained by the first network operator in respect of a subscriber ported to a second network operator from the first network operator;
a generator associated with the first network operator for generating a file in a predefined format based on combining the subscriber’s VAS subscription details extracted, by an extractor, from at least one of a centralized subscription management system and a plurality of subscription management systems associated with the first network operator; and
a transmitter associated with the first network operator for communicating the generated file to the second network operator node.

The present invention also furthermore provides a system for communicating VAS subscription details in a telecommunication network, wherein the system comprises:
a receiver associated with a current network operator for receiving a request, from a subscriber ported to the current network operator from a previous network operator, for importing the subscriber’s VAS subscription details from the previous network operator;
a transmitter associated with the current network operator for sending a request to a designated node of the previous network operator to import VAS subscription details associated with the subscriber, wherein the VAS subscription details are imported as a file in a pre-defined format from the designated node, the file comprising subscription details maintained by at least one of a centralized subscription management system and a plurality of subscription management systems linked with the previous network operator;
a selector associated with the current network operator for selecting a sub-set of the subscription details out of the subscription details present in the received file based on a subscriber input comprising at least one identifier related to at least one of a network element based VAS and a content based VAS; and
an allocator associated with the current network operator for transferring the sub-set of the subscription details to at least one of a centralized subscription management system and a plurality of subscription management systems linked with the current network operator for activating at least one VAS associated with said at least one identifier.

To further clarify advantages and features of the present invention, a more particular description of the invention will be rendered by reference to specific embodiments thereof, which is illustrated in the appended drawings. It is appreciated that these drawings depict only typical embodiments of the invention and are therefore not to be considered limiting of its scope. The invention will be described and explained with additional specificity and detail with the accompanying drawings.

Brief Description of Figures:
These and other features, aspects, and advantages of the present invention will become better understood when the following detailed description is read with reference to the accompanying drawings in which like characters represent like parts throughout the drawings, wherein:

Figure 1 shows a flow chart corresponding to a first embodiment of the invention;
Figure 2 shows a detailed internal construction of a system in accordance with a first embodiment of the present invention;
Figure 3 shows a flow chart corresponding to a second embodiment of the invention;
Figure 4 shows a detailed internal construction of a system in accordance with a second embodiment of the present invention;
Figure 5 shows a flow chart corresponding to a third embodiment of the invention;
Figure 6 shows a detailed internal construction of a system in accordance with a third embodiment of the present invention;
Figure 7 shows a detailed internal construction of the system in accordance with figures 2, 4 and 6 of the present invention;
Figure 8 shows an exemplary control flow diagram represented with respect to exemplary components, in accordance with an embodiment of the invention;
Figure 9 depicts a universal VAS registry for registering VAS, in accordance with an embodiment of the present invention;
Figure 10 depicts a universal content registry for registering digital content, in accordance with an embodiment of the present invention;
Figure 11 depicts an exemplary registration of a content based VAS and a corresponding feature of said content based VAS, in accordance with an embodiment of the present invention;
Figure 12 depicts a template of a VAS subscription file, in accordance with an embodiment of the present invention;
Figure 13 depicts a composition of an exemplary VAS subscription file based on the template shown in Fig. 12, in accordance with an embodiment of the present invention.
Further, skilled artisans will appreciate that elements in the drawings are illustrated for simplicity and may not have been necessarily been drawn to scale. For example, the flow charts illustrate the method in terms of the most prominent steps involved to help to improve understanding of aspects of the present invention. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the embodiments of the present invention so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having benefit of the description herein.

Detailed Description:
For the purpose of promoting an understanding of the principles of the invention, reference will now be made to the embodiment illustrated in the drawings and specific language will be used to describe the same. It will nevertheless be understood that no limitation of the scope of the invention is thereby intended, such alterations and further modifications in the illustrated system, and such further applications of the principles of the invention as illustrated therein being contemplated as would normally occur to one skilled in the art to which the invention relates.

It will be understood by those skilled in the art that the foregoing general description and the following detailed description are exemplary and explanatory of the invention and are not intended to be restrictive thereof.

Reference throughout this specification to “an aspect”, “another aspect” or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, appearances of the phrase “in an embodiment”, “in another embodiment” and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment.

The terms "comprises", "comprising", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process or method that comprises a list of steps does not include only those steps but may include other steps not expressly listed or inherent to such process or method. Similarly, one or more devices or sub-systems or elements or structures or components proceeded by "comprises... a" does not, without more constraints, preclude the existence of other devices or other sub-systems or other elements or other structures or other components or additional devices or additional sub-systems or additional elements or additional structures or additional components.

Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. The system, methods, and examples provided herein are illustrative only and not intended to be limiting.

Embodiments of the present invention will be described below in detail with reference to the accompanying drawings.

As discussed within the background section, there is a need of VAS portability mechanism for porting a subscriber’s VAS subscription details from an old network operator to the new network operator. Various patent publications that attempt to work in such direction have been explained as follows:

US7096023 describes portability of IN supplementary services, wherein the ported station/number and non-ported station/number have been depicted. Every time there is an initiation of communication or supplementary service, number portability register is checked for ported station. Old network is also contacted to continue with ported station for an initiated communication and supplementary service. However, US7096023 doesn't describe any non-IN supplementary service or content-based VAS. Moreover, there is no mechanism to achieve a complete porting so that old network operator is never re-communicated. Further, there is no mechanism to port information about content used by user in the old network to the new network.

US 8,644,476 describes a method to detect from a request made by a subscriber of a first network that the subscriber desires to use the value added service (e.g. using a prefix number, number based triggering, or a Call Forward Unconditional mechanism). The control of the call is forwarded towards a second network node associated with a forwarding number in the second network. The value added service is executed by a second network node, and, when necessary, the call is further directed towards the subscriber in the first network associated with the terminating call.
However, US 8644476 describes first network and second network interfacing for every call and is restricted towards IN-supplementary services. Moreover, there is no mechanism to achieve a complete porting so that second network operator is never re-communicated. Further, said patent publication doesn't describe porting of any non-IN supplementary service, content-based VAS and mechanism to port information about content used by user for content-based VAS in the second network to the first network.

EP 1503 601 describes that upon activation of a value added service action in a first network, an action record related to this value added service is produced. This action record is transferred to a network node arranged between the first and the second network. On the basis of the data separated from the action record, the network node maps the value added service action of the first network into a corresponding value added service action of the second network, and transfers the value added service definitions of the first network resulting from the mapping to a service platform of the second network.

However, EP 1503 601 describes a perspective of subscriber roaming in different networks and availing VAS subscriptions associated with the home network operator through a common node shared between the home network node and visiting network node. Accordingly, there is no permanent or seamless porting of VAS subscriptions from one network to another. Moreover, said patent doesn't describe how porting of any content-based VAS and information about content used by user for content-based VAS from the first network to the second network is handled.

Overall, although the prior arts define mechanisms to enable same VAS services across networks by accessing old/first network either during a call or during a course or roaming, however, these prior arts do not describe any mechanism for permanent porting of VAS subscription, both content and non-content based VAS, of a user from one network to another network at the time of number porting.

To solve the aforesaid problems, the present invention proposes a generic mechanism to seamlessly port already subscribed VAS from an old network to new network such that old network is never accessed or contacted once the porting is complete. Accordingly, the subscriber is able to successfully avail all those VAS that he/she subscribed in older network, within the new ported network with negligible procedural tasks.

To facilitate the present invention, a universal VAS registry and a universal content registry have been also defined to uniformly track/identify standard VAS features and digital content so as to request porting by simply referring to standard/registered identifiers with Universal registries.

Now referring to figure 1, it can be seen that the present invention provides a method of communicating VAS subscription details in a telecommunication network, the method comprising:
receiving (step 120), by a first network operator node, a request from a subscriber ported to a second network operator, for exporting VAS subscription details maintained by a first network operator in respect of the subscriber;
generating (step 122), by the first network operator node, a data file comprising subscription details maintained by the first network operator in respect of the subscriber; and
communicating (step 124), by the first network operator node, the generated data file to a second network operator node.

In one embodiment of the invention, wherein the VAS subscription details comprises at least one VAS, and wherein the at least one VAS corresponds to at least one of a network element based VAS and a content based VAS.

In another embodiment of the invention, wherein the network element based VAS corresponds to a non-content based VAS.

In still another embodiment, wherein the content based VAS comprises at least a unique content ID, and optionally a unique physical file ID.

In a further embodiment of the invention, wherein the at least one VAS is identified by a unique VAS identifier and optionally comprises one or more of:
at least one unique field identifier;
at least one sub-field identifier; and
at least one unique feature identifier.

In yet another embodiment, wherein said at least one unique feature identifier comprises optionally one or more of:
at least one unique feature-field identifier; and
at least one sub-field identifier.

In another embodiment, wherein said at least one unique VAS identifier is allocated to said at least one VAS by a Universal Registry for Value Added Services based upon a request of registration of said at least one VAS by a corresponding vendor.

In yet another embodiment, wherein said Universal Registry for Value Added Services may optionally allocate one or more of said unique field identifier, said sub-field identifier, and said unique feature identifier to said at least one VAS requested for registration.

In a further more embodiment of the invention, wherein at least one pair of said unique content ID, and said unique content physical file ID is allocated to a digital content by a Universal Registry for Digital content, based upon receipt of a request for registration of said digital content by a digital content provider.

Referring to figure 2, the present invention also provides a system (200) for communicating VAS subscription details in a telecommunication network, the system (200) comprising:
a receiver (202) associated with a first network operator for receiving a request, from a subscriber ported to a second network operator, for exporting VAS subscription details maintained by the first network operator in respect of the subscriber;
a generator (204) associated with the first network operator for generating a data file comprising subscription details maintained by the first network operator in respect of the subscriber; and
a transmitter (206) associated with the first network operator for communicating the generated data file to a second network operator node.

In a further more embodiment of the invention, the system (200) may be implemented in a node operating in the telecommunication network for communicating the VAS subscription details.

Now referring to figure 3, it can be seen that the present invention provides a method of communicating VAS subscription details in a telecommunication network, the method comprising:
receiving, by a first network operator node, a request from a second network operator node for exporting VAS subscription details maintained by a first network operator in respect of a subscriber ported to a second network operator from the first network operator; (step 320)
generating, by the first network operator node, a file in a predefined format based on combining the subscriber’s VAS subscription details extracted from at least one of a centralized subscription management system and a plurality of subscription management systems associated with the first network operator; and (step 322)
communicating, by the first network operator node, the generated file to the second network operator node. (Step 324)

In an embodiment, wherein the file comprises the subscription details categorized in a hierarchal order of a plurality of unique identifiers comprising at least one unique VAS identifier optionally associated with one or more field identifiers.

In another embodiment, said hierarchal order of the plurality of unique identifiers optionally comprises one or more of: a unique feature identifier, a unique field identifier, a unique content identifier, and a unique content physical file identifier.

In still another embodiment, wherein the pre-defined file format of the file is a data exchange file format.

Referring to figure 4, the present invention also provides a system (400) for communicating VAS subscription details in a telecommunication network, the system (400) comprising:
a receiver (402) associated with a first network operator for receiving a request, from a second network operator node for exporting VAS subscription details maintained by the first network operator in respect of a subscriber ported to a second network operator from the first network operator;
a generator (404) associated with the first network operator for generating a file in a predefined format based on combining the subscriber’s VAS subscription details extracted, by an extractor (406), from at least one of a centralized subscription management system and a plurality of subscription management systems associated with the first network operator; and
a transmitter (408) associated with the first network operator for communicating the generated file to the second network operator node.

In a further more embodiment of the invention, the system (400) may be implemented in a node operating in the telecommunication network for communicating the VAS subscription details.

In yet another embodiment of the invention, the present invention further comprises a network node operating in a telecommunication network as the first network operator node, wherein said network node implements the system (200,400) for communicating VAS subscription details. In an example, such node may be referred to a VAS portability Gateway node.

Now referring to figure 5, it can be seen that the present invention provides method of communicating VAS subscription details in a telecommunication network, the method comprising:
receiving (step 520), by a current network operator node, a request from a subscriber ported to a current network operator from a previous network operator, for importing the subscriber’s VAS subscription details from the previous network operator;
requesting (step 522), by the current network operator node, a designated node of the previous network operator to import VAS subscription details associated with the subscriber, wherein the VAS subscription details are imported as a file in a pre-defined format from the designated node, the file comprising subscription details maintained by at least one of a centralized subscription management system and a plurality of subscription management systems linked with the previous network operator;
selecting (step 524), by the current network operator node, a sub-set of the subscription details out of the subscription details present in the received file based on a subscriber input comprising at least one identifier related to at least one of a network element based VAS and a content based VAS; and
transferring (step 526) the sub-set of the subscription details to at least one of a centralized subscription management system and a plurality of subscription management systems linked with the current network operator for activating at least one VAS associated with said at least one identifier.

In another embodiment of the invention, the invention further comprises:
notifying (step 530) at least one error in the received file to the subscriber for re-generating a request for importing the subscriber’s VAS subscription details; and
communicating the re-generated request to the designated node of the first network operator for receiving an updated file in the pre-defined format.

In still another embodiment, wherein the pre-defined file format of the file is a data exchange file format.

In yet another embodiment, wherein said designated node is any network node of the previous network operator that is equivalent to first network operator described in preceding figures. Accordingly, like the first network node described in preceding figures, designated node also implements the system (200) or the system (400) and, in an example, may be referred to as the VAS Portability Gateway node of the previous network operator/first network operator.

Referring to figure 6, the present invention also provides a system (600) for communicating VAS subscription details in a telecommunication network, the system (600) comprising:
a receiver (602) associated with a current network operator for receiving a request, from a subscriber ported to the current network operator from a previous network operator, for importing the subscriber’s VAS subscription details from the previous network operator;
a transmitter (604) associated with the current network operator for sending a request to a designated node of the previous network operator to import VAS subscription details associated with the subscriber, wherein the VAS subscription details are imported as a file in a pre-defined format from the designated node, the file comprising subscription details maintained by at least one of a centralized subscription management system and a plurality of subscription management systems linked with the previous network operator;
a selector (606) associated with the current network operator for selecting a sub-set of the subscription details out of the subscription details present in the received file based on a subscriber input comprising at least one identifier related to at least one of a network element based VAS and a content based VAS; and
an allocator (608) associated with the current network operator for transferring the sub-set of the subscription details to at least one of a centralized subscription management system and a plurality of subscription management systems linked with the home network operator for activating at least one VAS associated with said at least one identifier.

In yet another embodiment, the present invention further comprises a network node operating in the telecommunication network as the current network operator node that is equivalent to the second network operator node as described in the preceding figures. Accordingly, the node implements the system (600) for communicating VAS subscription details, and in an example, may be referred to as the VAS portability Gateway node of the current network operator/the second network operator.

Referring to figure 7, yet another typical hardware configuration of the system 200, 400, 600, in the form of a computer system 200, 400, 600 is shown. The computer system 200, 400, 600 can include a set of instructions that can be executed to cause the computer system 200, 400, 600 to perform any one or more of the methods disclosed. The computer system 200, 400, 600 may operate as a standalone device or may be connected, e.g., using a network, to other computer systems or peripheral devices.

In a networked deployment, the computer system 200, 400, 600 may operate in the capacity of a server or as a client user computer in a server-client user network environment, or as a peer computer system in a peer-to-peer (or distributed) network environment. The computer system 200, 400, 600 can also be implemented as or incorporated into various devices, such as a network server, a personal computer (PC), a tablet PC, a personal digital assistant (PDA), a mobile device, a palmtop computer, a laptop computer, a desktop computer, a communications device, a network router, switch or bridge, or any other machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while a single computer system 200, 400, 600 is illustrated, the term "system" shall also be taken to include any collection of systems or sub-systems that individually or jointly execute a set, or multiple sets, of instructions to perform one or more computer functions.

The computer system 200, 400, 600 may include a processor 702 e.g., a central processing unit (CPU), a graphics processing unit (GPU), or both. The processor 702 may be a component in a variety of systems. For example, the processor 702 may be part of a standard personal computer or a workstation. The processor 702 may be one or more general processors, digital signal processors, application specific integrated circuits, field programmable gate arrays, servers, networks, digital circuits, analog circuits, combinations thereof, or other now known or later developed devices for analysing and processing data. The processor 702 may implement a software program, such as code generated manually (i.e., programmed).

The computer system 200, 400, 600 may include a memory 704, such as a memory 704 that can communicate via a bus 708. The memory 704 may be a main memory, a static memory, or a dynamic memory. The memory 704 may include, but is not limited to computer readable storage media such as various types of volatile and non-volatile storage media, including but not limited to random access memory, read-only memory, programmable read-only memory, electrically programmable read-only memory, electrically erasable read-only memory, flash memory, magnetic tape or disk, optical media and the like. In one example, the memory 704 includes a cache or random access memory for the processor 702. In alternative examples, the memory 704 is separate from the processor 702, such as a cache memory of a processor, the system memory, or other memory. The memory 704 may be an external storage device or database for storing data. Examples include a hard drive, compact disc ("CD"), digital video disc ("DVD"), memory card, memory stick, floppy disc, universal serial bus ("USB") memory device, or any other device operative to store data. The memory 704 is operable to store instructions executable by the processor 702. The functions, acts or tasks illustrated in the figures or described may be performed by the programmed processor 702 executing the instructions stored in the memory 704. The functions, acts or tasks are independent of the particular type of instructions set, storage media, processor or processing strategy and may be performed by software, hardware, integrated circuits, firm-ware, micro-code and the like, operating alone or in combination. Likewise, processing strategies may include multiprocessing, multitasking, parallel processing and the like.

As shown, the computer system 200, 400, 600 may or may not further include a display unit 710, such as a liquid crystal display (LCD), an organic light emitting diode (OLED), a flat panel display, a solid state display, a cathode ray tube (CRT), a projector, a printer or other now known or later developed display device for outputting determined information. The display 710 may act as an interface for the user to see the functioning of the processor 702, or specifically as an interface with the software stored in the memory 704 or in the drive unit 716.

Additionally, the computer system 200, 400, 600 may include an input device 712 configured to allow a user to interact with any of the components of system 200, 400, 600. The input device 712 may be a number pad, a keyboard, or a cursor control device, such as a mouse, or a joystick, touch screen display, remote control or any other device operative to interact with the computer system 200, 400, 600.

The computer system 200, 400, 600 may also include a disk or optical drive unit 716. The disk drive unit 716 may include a computer-readable medium 722 in which one or more sets of instructions 724, e.g. software, can be embedded. Further, the instructions 724 may embody one or more of the methods or logic as described. In a particular example, the instructions 724 may reside completely, or at least partially, within the memory 704 or within the processor 702 during execution by the computer system 200, 400, 600. The memory 704 and the processor 702 also may include computer-readable media as discussed above.

The present invention contemplates a computer-readable medium that includes instructions 724 or receives and executes instructions 724 responsive to a propagated signal so that a device connected to a network 726 can communicate voice, video, audio, images or any other data over the network 726. Further, the instructions 724 may be transmitted or received over the network 726 via a communication port or interface 720 or using a bus 708. The communication port or interface 720 may be a part of the processor 702 or may be a separate component. The communication port 720 may be created in software or may be a physical connection in hardware. The communication port 720 may be configured to connect with a network 726, external media, the display 710, or any other components in system 200, 400, 600 or combinations thereof. The connection with the network 726 may be a physical connection, such as a wired Ethernet connection or may be established wirelessly as discussed later. Likewise, the additional connections with other components of the system 200, 400, 600may be physical connections or may be established wirelessly. The network 726 may alternatively be directly connected to the bus 708.

The network 726 may include wired networks, wireless networks, Ethernet AVB networks, or combinations thereof. The wireless network may be a cellular telephone network, an 802.11, 802.16, 802.20, 802.1Q or WiMax network. Further, the network 726 may be a public network, such as the Internet, a private network, such as an intranet, or combinations thereof, and may utilize a variety of networking protocols now available or later developed including, but not limited to TCP/IP based networking protocols.

In an alternative example, dedicated hardware implementations, such as application specific integrated circuits, programmable logic arrays and other hardware devices, can be constructed to implement various parts of the system 200, 400, 600.

Applications that may include the systems can broadly include a variety of electronic and computer systems. One or more examples described may implement functions using two or more specific interconnected hardware modules or devices with related control and data signals that can be communicated between and through the modules, or as portions of an application-specific integrated circuit. Accordingly, the present system encompasses software, firmware, and hardware implementations.

The system described may be implemented by software programs executable by a computer system. Further, in a non-limited example, implementations can include distributed processing, component/object distributed processing, and parallel processing. Alternatively, virtual computer system processing can be constructed to implement various parts of the system.

The system is not limited to operation with any particular standards and protocols. For example, standards for Internet and other packet switched network transmission (e.g., TCP/IP, UDP/IP, HTML, HTTP) may be used. Such standards are periodically superseded by faster or more efficient equivalents having essentially the same functions. Accordingly, replacement standards and protocols having the same or similar functions as those disclosed are considered equivalents thereof.

The forthcoming description of Fig. 8-10 depicts a system implementation of the present invention comprising the embodiments as described in Fig. 1 to 6, wherein the subscriber has moved from an old network operator to a new network operator, through availing mobile network portability.

Referring to Figure 8, vide step 8002, a user 800 ported to a new network submits a request to export or out port VAS to an old network operator node, which may be a VAS Portability Gateway node (VASPG2) 804 of the old network operator. The request from the subscriber 800 to VASPG2 804 is accepted based on subscriber’s MSISDN, which is also recognized by the old network operator apart from the new network operator.

Vide step 8004, the VASPG2 804 forwards the network request to a centralized VAS subscription management system 806 (VASSMS2) associated with the old network operator. VAS SMS2 may be in other implementation composed of a plurality of VAS subscription management systems.

Vide step 8006, VASPG2 804 collects all VAS subscription details of the requesting user from the centralized or multiple subscription management systems (VASSM2). Thereafter, VASPG2 804 generates a subscription file in a data exchange format e.g. standard data transfer format like XML, comprising all the VAS subscription details as collected in step 8004. Such file may also be referred to as a VAS portability dump (file). The composition of such file has been depicted in figures 12 and 13.

Vide step 8008, the user 800 ported to the new network operator submits a request to import VAS from the old network operator to a new network operator node, which may be a VAS Portability Gateway node (VASPG1) 802. The VASPG1 802 proceeds ahead with the processing of the request after identification of the ported subscriber as the old network operator’s former subscriber based on the subscriber MSISDN present within the request. In addition, VASPG1 802 gets on alert to receive the generated subscription file from the VASPG2 804 of the old network operator.

Vide step 8010, the VASPG1 802 of the new network operator initiates an interaction with VASPG2 804 of the old network operator on the basis of a typical transaction identification based protocol for request-response tracking. In other words, the VASPG1 802 generates a network request to VASPG2 804 for communicating the VAS subscription details or alternatively, a request for communicating the generated VAS subscription file.

Vide step 8012, as a result of the requesting performed in step 8010, the VAS subscription file as generated in step 8006 is communicated to the VASPG1 802 of the new network operator by the VASPG2 804 of the old network operator.

Vide step 8014, the VASPG1 802 selects a sub-set of the imported subscription details and allocates/transfers the sub-set to one centralized or multiple subscription management systems (VASSMS1) 808 associated with the current network operator for instantiating desired VAS. The selection of the sub-set is based on a subscriber input providing at least one VAS identifier, which is a unique identifier (UID) as issued by a Universal Registry for a particular VAS. Accordingly, the VAS corresponding to the identifier forms a part of the sub-set of the sub-set. Such identifiers have been elaborated later in the description of figures 9-12.

However, in case the received VAS subscription file is missing some details, then as a corrective measure, the VASSMS1 808 in turn requests VASPG1802 to generate a corrective request to VASPG2 for receiving at least the missing VAS subscription details.

Referring to Fig. 9, a universal VAS registry 902 has been depicted to register VAS as rendered by various VAS vendors 904 (1, 2, 3) or market players. By maintaining such universal registry 902, the present invention proposes a mechanism for a uniform identification of a network element based VAS (e.g. IN based VAS or non-content based VAS) or a content based VAS.

Further, as depicted within the figure, each VAS is centrally registered and gets a Unique VAS ID (UVID) (in form of an alphanumeric of length 15 digits) by the Universal Value Added Service Registry 902. Similarly each feature of VAS is also registered and also gets a Unique Feature ID (UFID), which is connected with UVID. Each unique VAS ID and its unique feature ID are in turn associated with a set of corresponding fields/parameters to specify some details related to the unique VAS ID and the particular feature ID, respectively. Such fields are defined at the time of registration of a new VAS by a VAS vendor 904. Further, new fields can also be added to an already created structure for a registered VAS.

By registering each VAS, the associated feature as well as associated content (if any), the porting of VAS is facilitated. This is so, as within the porting request by user, specific VAS may be mentioned for porting. Accordingly, the associated VAS and its corresponding features/content get automatically ported to a new network from an old network.

Referring to Fig. 10, a universal content registry 1002 has been depicted to register digital content by various vendors or content providers 1004 (1, 2, 3).

As shown further in the figure, each unique digital content piece (logical) is centrally registered and gets a Unique Content ID (UCID) (in form of an alphanumeric of length 15 digits), through the Universal Digital Content Registry 1002. For each UCID (Logical), depending upon the Media type (audio, video, text, images etc.) at least one Unique content physical File ID (UCPFID) is generated, which corresponds to individual physical file related to the content. Hence, a particular unique content may have a group of UCPFIDs.

In respect of aforementioned registries in Fig. 9 and Fig. 10, the aforementioned Universal VAS Registry 902 or Universal Digital Content Registry 1002 may be centrally managed by a single association/body/commission/governing body at national or international level and may be recognized by authorized telecom regulatory bodies worldwide.

The description related to Fig. 9 and 10 shall be now explained with the help of forthcoming example.

EXEMPLARY IMPLEMENTATION OF THE PRESENT INVENTION:

Referring to Fig 11, an example of registration of Caller Ring Back Tone (CRBT) related VAS, which is a content based VAS, and its Special Caller RBT feature is shown. The CRBT is assigned a Unique VAS ID (UVID), for the sake of example is assumed as RBT–VAS-ID. Such RBT-VAS-ID, has identifiers for fields that may be also registered. As shown in the figure, examples of such fields may include “SubscriptionDurationInDays” and “ContentValidityDurationInDays”. Each of such field in turn includes “price” as a sub-field.

Under RBT-VAS-ID, special caller RBT is assigned a Unique Feature ID (UFID). Under the feature ID, there are defined several fields and sub-fields, which also stand registered. Corresponding examples include "MobileNumber" &"UniqueContent Physical File ID". This pair of fields can occur any number of times during VAS porting depending on, in respect of how many callers, the user has set special RBTs.

Within the present example, the Unique Content Physical File ID (UCPFID) denotes an actual media file of a song (digital content), in respect of which the Unique Content ID (UCID) also stands registered. Such UCID corresponds to a “name/title” of the corresponding song and has been denoted by “XYZContentID”

Referring to Figure 12, a template of the VAS subscription file as communicated by the VASPG 2 to VASPG1 (refer Fig 8) is shown in respect of a content based VAS to be ported. Accordingly, such subscription file depicts an arrangement of a unique VAS identifier, a unique feature identifier, a unique field identifier, a unique content identifier, a unique content physical file identifier, etc, within the subscription file. In the present figure, details one of the “sub-fields” may be defined to contain a Unique content physical file ID as value.

Referring to Figure 13, an exemplary VAS subscription details file based on the template of subscription file (as shown in Fig 12) has been depicted. To achieve such representation, the template may be populated with details of registered Caller Ring Back Tone (CRBT) related VAS and its correspondingly registered Special Caller RBT feature and the registered content physical file ID as used in CRBT subscription. Such details have been already well explained with respect to Fig. 11.

Accordingly, as a result of the present example, when the subscription file as depicted in the present figure goes to the new network operator for porting, the new network operator comes to know that subscriber had subscription for RBT's special caller feature and the corresponding content subscribed for two mobile numbers with respect to the old network operator.

It is envisaged that the present invention provides an ease of transfer for VAS when users move from one operator to another operator. It helps users avail all those VAS that he/she subscribed in older network and also helps operators to get new users with a fast and methodical subscription porting.

Accordingly, even the new network operators are more benefitted upon receiving users from other network and need not educate the incoming users about the VAS as rendered by the new network operator.

The drawings and the forgoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment. For example, orders of processes described herein may be changed and are not limited to the manner described herein. Moreover, the actions of any flow diagram need not be implemented in the order shown; nor do all of the acts necessarily need to be performed. Also, those acts that are not dependent on other acts may be performed in parallel with the other acts. The scope of embodiments is by no means limited by these specific examples. Numerous variations, whether explicitly given in the specification or not, such as differences in structure, dimension, and use of material, are possible. The scope of embodiments is at least as broad as given by the following claims.

Benefits, other advantages, and solutions to problems have been described above with regard to specific embodiments. However, the benefits, advantages, solutions to problems, and any component(s) that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as a critical, required, or essential feature or component of any or all the claims.

CLAIMS:WE CLAIM:
1. A method of communicating VAS subscription details in a telecommunication network, the method comprises:
receiving (step 120), by a first network operator node, a request from a subscriber ported to a second network operator, for exporting VAS subscription details maintained by a first network operator in respect of the subscriber;
generating (step 122), by the first network operator node, a data file comprising subscription details maintained by the first network operator in respect of the subscriber; and
communicating (step 124), by the first network operator node, the generated data file to a second network operator node.

2. The method as claimed in claim 1, wherein the VAS subscription details comprises at least one VAS, and wherein the at least one VAS corresponds to at least one of a network element based VAS and a content based VAS.

3. The method as claimed in claim 2, wherein the network element based VAS corresponds to a non-content based VAS

4. The method as claimed in any of the preceding claims, wherein the content based VAS comprises a unique content ID.

5. The method as claimed in any of the preceding claims, wherein the content based VAS is associated with a unique content physical file ID.

6. The method as claimed in in any of the preceding claims, wherein the at least one VAS is identified by at least one unique VAS identifier.

7. The method as claimed in in any of the preceding claims, wherein the at least one unique VAS identifier is associated with one or more of:
at least one unique field identifier;
at least one unique sub-field identifier; and
at least one unique feature identifier.

8. The method as claimed in any of the preceding claims, wherein said at least one unique feature identifier is associated with one or more of:
at least one unique feature-field identifier; and
at least one sub-field identifier.

9. The method as claimed in any of the preceding claims, wherein said at least one unique VAS identifier is allocated to said at least one VAS by a Universal Registry for Value Added Services based upon a request of registration of said at least one VAS by a corresponding vendor.

10. The method as claimed in any of the preceding claims, wherein said Universal Registry for Value Added Services allocates one or more of said unique field identifier, said sub-field identifier, and said unique feature identifier to said at least one VAS requested for registration.

11. The method as claimed in preceding claims, wherein at least one pair of said unique content ID and said unique content physical file ID is allocated to a digital content by a Universal Registry for Digital content, based upon receipt of a request for registration of said digital content by a digital content provider.

12. A system (200) for communicating VAS subscription details in a telecommunication network, the system (200) comprising:
a receiver (202) associated with a first network operator for receiving a request from a subscriber ported to a second network operator, for exporting VAS subscription details maintained by the first network operator in respect of the subscriber;
a generator (204) associated with the first network operator for generating a data file comprising subscription details maintained by the first network operator in respect of the subscriber; and
a transmitter (206) associated with a first network operator for communicating the generated data file to a second network operator node.

13. A method of communicating VAS subscription details in a telecommunication network, the method comprising:
receiving (step 320), by a first network operator node, a request from a second network operator node for exporting VAS subscription details maintained by a first network operator in respect of a subscriber ported to a second network operator from the first network operator;
generating (step 322), by the first network operator node, a file in a predefined format based on combining the subscriber’s VAS subscription details extracted from at least one of a centralized subscription management system and a plurality of subscription management systems associated with the first network operator; and
communicating (step 324), by the first network operator node, the generated file to the second network operator node.

14. The method as claimed in claim 13, wherein the file comprises the subscription details categorized in a hierarchal order of a plurality of unique identifiers comprising at least one
unique VAS identifier associated with one or more field identifiers.

15. The method as claimed in claim 14, wherein said hierarchal order of the plurality of unique identifiers further comprises one or more of: a unique feature identifier, a unique field identifier, a unique content identifier, and a unique content physical file identifier.

16. The method as claimed in claim 13, wherein the pre-defined file format of the file is a data exchange file format.

17. A system (400) for communicating VAS subscription details in a telecommunication network, the system (400) comprising:
a receiver (402) associated with a first network operator for receiving a request from a second network operator node for exporting VAS subscription details maintained by the first network operator in respect of a subscriber ported to a second network operator from the first network operator;
a generator (404) associated with the first network operator for generating a file in a predefined format based on combining the subscriber’s VAS subscription details extracted, by an extractor (406), from at least one of a centralized subscription management system and a plurality of subscription management systems associated with the first network operator; and
a transmitter (408) associated with the first network operator for communicating the generated file to the second network operator node.

18. A network node operating in the telecommunication network as the first network operator node as claimed in any of the preceding claims, wherein said network node implements the system (200,400) for communicating VAS subscription details.

19. The network node as claimed in claim 18, wherein said network node corresponds to a VAS portability Gateway node.

20. A method of communicating VAS subscription details in a telecommunication network, the method comprising:
receiving (step 520), by a current network operator node, a request from a subscriber ported to a current network operator from a previous network operator, for importing the subscriber’s VAS subscription details from the previous network operator;
requesting (step 522), by the current network operator node, a designated node of the previous network operator to import VAS subscription details associated with the subscriber, wherein the VAS subscription details are imported as a file in a pre-defined format from the designated node, the file comprising subscription details maintained by at least one of a centralized subscription management system and a plurality of subscription management systems linked with the previous network operator;
selecting (step 524), by the current network operator node, a sub-set of the subscription details out of the subscription details present in the received file based on a subscriber input comprising at least one identifier related to at least one of a network element based VAS and a content based VAS; and
transferring (step 526) the sub-set of the subscription details to at least one of a centralized subscription management system and a plurality of subscription management systems linked with the current network operator for activating at least one VAS associated with said at least one identifier.

21. The method as claimed in claim 20, further comprising:
notifying (step 530) at least one error in the received file to the subscriber for re-generating a request for importing the subscriber’s VAS subscription details; and
communicating the re-generated request to the designated node of the first network operator for receiving an updated file in the pre-defined format.

22. The method as claimed in claim 20, wherein the pre-defined file format of the file is a data exchange file format.

23. The method as claimed in claim 20, wherein said designated node is any network node of the previous network operator and corresponds to the node as claimed in any of the claims 18-19.

24. A system (600) for communicating VAS subscription details in a telecommunication network, the system (600) comprising:
a receiver (602) associated with a current network operator for receiving a request from a subscriber ported to the current network operator from a previous network operator, for importing the subscriber’s VAS subscription details from the previous network operator;
a transmitter (604) associated with the current network operator for sending a request to a designated node of the previous network operator to import VAS subscription details associated with the subscriber, wherein the VAS subscription details are imported as a file in a pre-defined format from the designated node, the file comprising subscription details maintained by at least one of a centralized subscription management system and a plurality of subscription management systems linked with the previous network operator;
a selector (606) associated with the current network operator for selecting a sub-set of the subscription details out of the subscription details present in the received file based on a subscriber input comprising at least one identifier related to at least one of a network element based VAS and a content based VAS; and
an allocator (608) associated with the current network operator for transferring the sub-set of the subscription details to at least one of a centralized subscription management system and a plurality of subscription management systems linked with the home network operator for activating at least one VAS associated with said at least one identifier.

25. A network node operating in the telecommunication network as the second network operator node or the current network operator node as claimed in any of the claims 1-23, wherein said network node implements the system (600) as claimed in claim 24 for communicating VAS subscription details.

26. The network node as claimed in claim 25, wherein said network node corresponds to a VAS portability Gateway node.

Documents

Application Documents

# Name Date
1 3261-DEL-2014-IntimationOfGrant06-01-2023.pdf 2023-01-06
1 FORM 5.pdf 2014-11-14
2 Form 3.pdf 2014-11-14
2 3261-DEL-2014-PatentCertificate06-01-2023.pdf 2023-01-06
3 Form 26.pdf 2014-11-14
3 3261-DEL-2014-Written submissions and relevant documents [14-09-2022(online)].pdf 2022-09-14
4 Figures_1640IN039.pdf 2014-11-14
4 3261-DEL-2014-FORM-26 [27-08-2022(online)].pdf 2022-08-27
5 3261-DEL-2014-Correspondence to notify the Controller [26-08-2022(online)].pdf 2022-08-26
5 1640IN039_Draft specification.pdf 2014-11-14
6 Form-9(Online).pdf 2015-02-19
6 3261-DEL-2014-US(14)-ExtendedHearingNotice-(HearingDate-30-08-2022).pdf 2022-08-01
7 3261-DEL-2014-US(14)-ExtendedHearingNotice-(HearingDate-30-04-2021).pdf 2021-10-17
7 3261-del-2014-Form-1-(11-06-2015).pdf 2015-06-11
8 3261-DEL-2014-US(14)-HearingNotice-(HearingDate-09-02-2021).pdf 2021-10-17
8 3261-del-2014-Correspondence Others-(11-06-2015).pdf 2015-06-11
9 3261-DEL-2014-REQUEST FOR ADJOURNMENT OF HEARING UNDER RULE 129A [08-02-2021(online)].pdf 2021-02-08
9 3261-DEL-2014-FER.pdf 2018-12-17
10 3261-DEL-2014-CLAIMS [17-06-2019(online)].pdf 2019-06-17
10 3261-DEL-2014-OTHERS [17-06-2019(online)].pdf 2019-06-17
11 3261-DEL-2014-DRAWING [17-06-2019(online)].pdf 2019-06-17
11 3261-DEL-2014-FER_SER_REPLY [17-06-2019(online)].pdf 2019-06-17
12 3261-DEL-2014-DRAWING [17-06-2019(online)].pdf 2019-06-17
12 3261-DEL-2014-FER_SER_REPLY [17-06-2019(online)].pdf 2019-06-17
13 3261-DEL-2014-CLAIMS [17-06-2019(online)].pdf 2019-06-17
13 3261-DEL-2014-OTHERS [17-06-2019(online)].pdf 2019-06-17
14 3261-DEL-2014-FER.pdf 2018-12-17
14 3261-DEL-2014-REQUEST FOR ADJOURNMENT OF HEARING UNDER RULE 129A [08-02-2021(online)].pdf 2021-02-08
15 3261-del-2014-Correspondence Others-(11-06-2015).pdf 2015-06-11
15 3261-DEL-2014-US(14)-HearingNotice-(HearingDate-09-02-2021).pdf 2021-10-17
16 3261-del-2014-Form-1-(11-06-2015).pdf 2015-06-11
16 3261-DEL-2014-US(14)-ExtendedHearingNotice-(HearingDate-30-04-2021).pdf 2021-10-17
17 3261-DEL-2014-US(14)-ExtendedHearingNotice-(HearingDate-30-08-2022).pdf 2022-08-01
17 Form-9(Online).pdf 2015-02-19
18 1640IN039_Draft specification.pdf 2014-11-14
18 3261-DEL-2014-Correspondence to notify the Controller [26-08-2022(online)].pdf 2022-08-26
19 Figures_1640IN039.pdf 2014-11-14
19 3261-DEL-2014-FORM-26 [27-08-2022(online)].pdf 2022-08-27
20 Form 26.pdf 2014-11-14
20 3261-DEL-2014-Written submissions and relevant documents [14-09-2022(online)].pdf 2022-09-14
21 Form 3.pdf 2014-11-14
21 3261-DEL-2014-PatentCertificate06-01-2023.pdf 2023-01-06
22 FORM 5.pdf 2014-11-14
22 3261-DEL-2014-IntimationOfGrant06-01-2023.pdf 2023-01-06

Search Strategy

1 searchstrategy_31-07-2018.pdf

ERegister / Renewals

3rd: 10 Mar 2023

From 11/11/2016 - To 11/11/2017

4th: 10 Mar 2023

From 11/11/2017 - To 11/11/2018

5th: 10 Mar 2023

From 11/11/2018 - To 11/11/2019

6th: 10 Mar 2023

From 11/11/2019 - To 11/11/2020

7th: 10 Mar 2023

From 11/11/2020 - To 11/11/2021

8th: 10 Mar 2023

From 11/11/2021 - To 11/11/2022

9th: 10 Mar 2023

From 11/11/2022 - To 11/11/2023

10th: 30 Oct 2023

From 11/11/2023 - To 11/11/2024

11th: 13 Mar 2024

From 11/11/2024 - To 11/11/2025

12th: 11 Nov 2025

From 11/11/2025 - To 11/11/2026