MXPA06010188A - System and method for pushing content to a terminal utilizing a network-initiated data service technique - Google Patents

System and method for pushing content to a terminal utilizing a network-initiated data service technique

Info

Publication number
MXPA06010188A
MXPA06010188A MXPA/A/2006/010188A MXPA06010188A MXPA06010188A MX PA06010188 A MXPA06010188 A MX PA06010188A MX PA06010188 A MXPA06010188 A MX PA06010188A MX PA06010188 A MXPA06010188 A MX PA06010188A
Authority
MX
Mexico
Prior art keywords
terminal
network
network node
introduction
node
Prior art date
Application number
MXPA/A/2006/010188A
Other languages
Spanish (es)
Inventor
Kiss Krisztian
Asthana Sarvesh
Original Assignee
Nokia Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Corporation filed Critical Nokia Corporation
Publication of MXPA06010188A publication Critical patent/MXPA06010188A/en

Links

Abstract

A system is provided for pushing content to a terminal located within a mobile network or a private network. The system includes a network node, such as a Session Initiation Protocol (SIP) proxy, located across a public network from the network. including the terminal. The network node is capable of subscribing to a push service on behalf of the terminal such that the network node is also capable of receiving push content in accordance with the push service. Thereafter, the network node is capable of establishing a network-initiated data session with the terminal.. In response to the network-initiated data session, the network node is further capable of registering the terminal such that the terminal is capable of receiving the push content based upon the registration.

Description

SYSTEM AND METHOD OF INTRODUCING CONTENT IN A TERMINAL USING A DATA SERVICE TECHNIQUE INITIATED BY NETWORK Field of the Invention The present invention relates, in general, to systems and methods for the introduction of content in a terminal, and more particularly, to the introduction of content in a terminal using both the data session technique initiated by network as the Session Initiation Protocol (SIP).
BACKGROUND OF THE INVENTION The era of modern communications has brought about a tremendous expansion of wired networks e. wireless Computer networks, television networks and telephony networks are experiencing unprecedented technological expansion, fueled by consumer demand. Wireless and mobile network interconnection technologies have been targeted at consumer-related demands while providing greater flexibility and the need for information transfer. Current and future network interconnection technologies continue to facilitate the simplicity of the transfer and convenience of information to users. REF. 175633 The proliferation of local, regional and global networks, such as the Internet, has provided an infinity of information to society. These network interconnection technologies have expanded to include wireless and mobile technologies in an incremental manner. Through these networks, information can be downloaded into desktop computing systems, wireless systems, mobile systems, and so on. For example, information available through the Internet can now be downloaded to mobile wireless units, such as cell phones, personal digital assistants (PDA), laptop computers, etc. The second generation wireless service, often referred to as a 2G wireless service, is a current wireless service based on circuit-switched technology. In this regard, 2G systems, such as the Global Mobile Communications System (GSM), use digital radio technology for improved quality and a broader range of services through premium mobile technologies. generation. The third-generation wireless service, often referred to as a 3G wireless service, refers to a set of digital technologies that promises improvements in capacity, speed and efficiency by deploying new packet-based transmission methodologies between terminals and the network. Users of 3G devices and networks will have access to multimedia services, such as demand-based video, video conferencing, Web quick access and file transfer. Existing and future services are provided, and will continue to be, through network service operators who perform services and applications available to users of the mobile device through the network. A particular service feature that is currently available for communication of information is an entry or "introduction" feature (also known as a "notification" feature or "alert" feature). In a common client / server model, a client requires a service or information from a server, which then responds by transmitting the information to the client. In general, this is referred to as "extraction" technology, where the client pulls or extracts the information from the server. For example, the entry of a Uniform Resource Locator (URL) into a client device that is then sent to the server to retrieve the associated information is an extraction transaction. In contrast, the input technology or "introduction" refers, in a general way, to a medium that transmits the information to one or more devices without prior action by the user. In this way, there is no explicit request from the client before the server transmits its information, and therefore, the introduction technology includes, in an essential way, the transactions initiated by the server. The introduction technologies can be used in connection with various protocols and communication technologies. For example, some introductory representative technologies include the Short Messaging Service (SMS), the Wireless Application Protocol (WAP) Introduction, the Multimedia Messaging Service (MMS), its initials in English), the Protocol of Initiation of Session (SIP), as well as others. Where traditional introduction technologies are suitable to enter. content to customers, these technologies experience some drawbacks. It is considered a private network that comprises, connected or otherwise associated with, a mobile network such as a General Radio Packet Service Network (GPRS, for its acronym in English). In these examples, a client such as a mobile terminal communicating through a mobile network can initiate, in general, a communication session (for example, a SIP communication session) with a server through a Network Address Translator (NAT) located between the client and the -server, according to the "extraction" techniques. As will be appreciated, the NAT can transform a private IP address of the client into a public IP address that can be recognized by the server. However, the server can not normally initiate a similar communication session with the client through the NAT, such as in accordance with the "introduction" techniques. In this regard, customers within private and cellular networks commonly lack a static and public identity as a fixed IP address, and as such, servers often can not identify a desired client in the NAT. Mobile networks are usually configured in a way that prevents a server from initiating a SIP communication session with a respective client due to a number of reasons. First, depending on the topology of the network, the activation of IP connectivity for clients within the network can consume an undesirable amount of resources or reduce network performance even when there is no IP traffic through the network . Secondly, in the network, as in many private networks, there are more clients than available IP addresses. As such, the network could include a NAT, dynamically distributed IP addresses and IP private addresses. Third, the security needs and policies of many networks require that different types of IP traffic be prevented from entering the network. Often, this example also leads to the use of NAT, in particular, when mobile networks include a firewall or * firewall '/ associated gateway. To overcome the inconvenience that the NAT allows the servers to initiate a communication session with a client according to the "introduction" techniques, the networks can be configured, so that each client has a fixed IP address, where addresses are entries in a respective server of the Domain Name System (DNS, for its acronym in English). The NAT and any of the security components (for example, a firewall / gateway, etc.) of the network can also be configured to allow the server to initiate a communication session with a client and allow the routing of traffic to and from from the IP address distributed to the client. In addition, for example, the specific resources per network technology that are required for IP connectivity with each client in the network can be distributed when the client is connected to the network. This technique that allows servers to introduce content to clients, however, ignores the limitations of public networks that lead to the use of NAT components. Namely, this technique ignores the limitation of the available IP public addresses. Also, this technique ignores the ability of NAT components to communicate with firewalls / gateways that provide security functionality. Therefore, it would be desirable to design a system capable of allowing the servers to introduce content to the clients in a mobile or private network using a communication session technique initiated by a network that takes into account the limited space of address of the public networks and maintains the functionality of the firewall or 'fireall' and / or gateway in the respective network.
SUMMARY OF THE INVENTION In light of the foregoing background, the embodiments of the present invention provide an improved system and method for entering content into a terminal, typically, a mobile terminal having an associated IP private address, using a proprietary technique. data session initiated by network. In contrast to conventional techniques for entering content in a terminal, the embodiments of the present invention allow a network-initiated data session to be established with the terminal of a network node through the public network from the terminal. More particularly, the embodiments of the present invention allow the network nodes to establish a network-initiated data session with the terminal in a mode that takes into account the limited number of public IP addresses available and-maintains the functionality of the firewall 'and / or gateway for the mobile network including the terminal. In accordance with one aspect of the present invention, a system is provided for entering content into a terminal located within a mobile network or a private network. The system includes a network-node such as a Session Initiation Protocol (SIP) proxy, located through a public network of the network that includes the terminal. The network node is able to subscribe to an introduction ser on behalf of the terminal, so that the network node is also able to receive the introduction content according to the introduction ser. From here on, the network node is able to establish a data session initiated by network with the terminal. For example, the network node may be able to send an activator to the terminal independent of the public network, whereby the terminal is activated to register with the network node and the data session initiated by network is established. In response to the data session initiated by the network, the network node is able to register the terminal, so that the terminal will have the ability to receive the -content of introduction based on the record. More particularly, the network node may be able to receive and subsequently store the introductory content in a buffer. In these examples, the network node may be able to send the introduction content to the terminal from the buffer. Alternatively, the network node may be able to register the terminal, so that the terminal has the ability to subscribe to the introduction ser based on the registration. In these examples, the terminal may be able to receive the introduction content based on the terminal that subscribes to the introduction ser. The network node may be able to receive a registration message from the terminal through the public network, whereby the terminal is identified through the public network and the terminal is registered. For example, the network node may be able to receive the registration message from the terminal via the network address translator (NAT) and / or a firewall or? firewall '(FW) located between the network node and the terminal. In these examples, the network node may be able to establish a data session initiated by the network in a mode independent of the NAT and / or FW. Additionally or alternatively, the network node may be able to register the terminal, so that the terminal has the ability to receive the introduction content based on the identity of the terminal through the public network. In accordance with other aspects of the present invention, a terminal and method for entering content in a terminal is provided. Therefore, the embodiments of the present invention provide an improved system and method for entering content in a terminal using a network initiated data session technique. The embodiments of the present invention allow a terminal (i.e., a termination node) to subscribe, and subsequently receive the content that comes from an introduction ser without requiring additional addresses or many additional public IP addresses. The embodiments of the present invention further allow the network node to establish a network-initiated data session with the terminal without obviating the functionality of the firewall or .x firewall 'and / or gateway provided in other way to a mobile network including the terminal, such as by means of an FW. Therefore, the system and method of the embodiments of the present invention solve the problems identified by the prior art and provide additional advantages.
BRIEF DESCRIPTION OF THE DRAWINGS Having thus described the invention in general terms, reference will now be made to the accompanying figures, which are not necessarily drawn to scale, and where: Figure 1 is a schematic diagram block of a communication system according to an embodiment of the present invention that includes a public network and a mobile network in which a source node and a terminating node are coupled bi-directionally directly or indirectly; Figure 2 is a schematic block diagram of an entity capable of operating as a SIP client, in accordance with the embodiments of the present invention; Figure 3 is a schematic block diagram of a mobile station that could operate as a SIP client, according to the embodiments of the present invention; Figure 4A is a control flow diagram illustrating, more particularly, a method of entering content in a terminal according to an embodiment of the present invention; and Figure 4B is a control flow diagram illustrating, more particularly, a method of entering content in a terminal according to another embodiment of the present invention.
Detailed Description of the Invention In the following, the present invention will be described more fully hereinafter with reference to the accompanying figures, in which the preferred embodiments of the invention are shown. However, this invention could be included in many different forms and should not be construed as limiting the modalities set forth herein; rather, these embodiments are provided so that this description will be complete and complete, and will fully convey the scope of the invention to those skilled in the art. The same numbers refer to the same elements through the figures. With reference to Figure 1, an illustration of a type of system that would benefit from the present invention is provided. The system and method of the embodiments of the present invention will be mainly described in conjunction with mobile communications applications. However, it should be understood that the system and method of the embodiments of the present invention can be used in conjunction with a variety of other applications, both in the mobile communications industries and outside the mobile communications industries. As shown, the system 10 includes a public network 12, such as a public Internet Protocol (IP) network such as the Internet. The public network includes a number of network nodes, each of which typically comprises a processing element such as a server computer, a personal computer, a laptop-type laptop, or the like. More particularly, the public network may include one or more network nodes comprising the fixed terminals 14, each of which has the ability to communicate within or through the public network. The network nodes of the public network 12 may also include a proyx 16, such as the Session Initiation Protocol (SIP) proxy. Although not shown, the network nodes of the public network can also include a SIP registrar. In this regard, the registrar can be implemented in the SIP proxy, as is well known to those skilled in the art. As will be appreciated, call models such as SIP provide an application layer signaling protocol related to multimedia sessions (see for example, the I-ETF request for the comment document * RFC 3261, entitled: SIP: Session Initiation Protocol, June 2002, the contents of which are incorporated herein by reference in their entirety). Therefore, the SIP proxy is capable of receiving and transmitting SIP signaling messages, such as SIP signaling messages to and / or from a network node comprising a fixed terminal that operates as a source node. 20, as described in more detail below. The public network can also include one or more Domain Name System servers (DNS) 18. In this regard, each network node commonly has a unique IP address that has associated, usually easier to call back, a DNS host name.
Then, the DNS servers may be able to transform a DNS host name into an associated IP address, so that network traffic can be routed to the appropriate node in the network. In addition to the public network 12, the system 10 includes one or more private networks 24, such as Local Area Networks (LANs). Each private network, such as the public network, can include a number of network nodes. Likewise, like public network 12, the network nodes of each private network may include one or more DNS servers 26. Similarly as before, the DNS servers of private networks may be capable of transforming a hostname DNS in an IP associated address so that network traffic can be routed to the appropriate public or network node. The private network may also include one or more network nodes comprising the mobile terminals 32, each of which has the ability to communicate within or through the private network. The terminals 32 may comprise, for example, mobile phones, portable digital assistants (PDA), personal locators, laptop-type laptops, smart cards and other types of electronic systems. To make it easier for terminals 32 to access the private network, private network 24 can include one or more wireless access points (APs) (not shown), each of which can be connected to one or more terminals. In this regard, APs may comprise configured access points for communicating with the terminal in accordance with the techniques, such as, for example, radio frequency (RF), Bluetooth (BT), infrared (IrDA) or any of a number of different techniques. of interconnection of terrestrial and / or wireless networks, which include LAN and / or WLAN techniques. Also in the same way as the public network, the private network may include a source node 20, which is described in more detail below. As described below, the private network may include a terminating node € 3, which may be able to communicate with a source node. And also as described below, one or more of the terminals of the private network may have the ability to operate as a source node or a termination node. To facilitate communications between the network nodes of a public network 12 and the network nodes of the private networks 24, each private network may also include a Network Address Translator. { NAT) that interconnects the public network with the private network. As explained earlier in the background section, each NAT may be able to transform a public IP address of the public network into a private IP address of a network node of a respective private network, and vice versa, for communications between the public network. public network and the respective private network. As will be appreciated, the NAT may also include an Application Level Gateway (ALG) (not shown) capable of transforming the embedded IP addresses, for example, into application protocol data units (PDUs). In addition, the NAT may include or be associated with a firewall and / or gateway for the respective private network. As shown then, a NAT that includes or is associated with a firewall / gateway is shown as a NAT / FW 28. The system 10 may also include one or more mobile or cellular networks 30. The cellular networks may comprise one or more of a number of different mobile networks. In this regard, cellular networks may comprise any of a number of first generation (1G), second generation (2G), 2.5G and / or third generation (3G) cellular networks, and / or any one of a number of cellular networks. other cellular networks capable of operating in accordance with the embodiments of the present invention. For example, each cellular network may comprise a GSM (Global Mobile Communications System), IS-136 (Multiple Time Domain Access-TDMA), IS-95 (Code Division Multiple Access-CDMA), or network EDGE (Enhanced GSM Data Environment). Alternatively, one or more of the cellular networks may comprise GPRS networks ("General Radio Packet Service) or GPRS-based networks (for example, the Universal Mobile Telecommunications System-UMTS).
In the same way as public and private networks 12, 24, cellular networks 30 also include one or more network nodes. In this regard, the network nodes of each cellular network may include one or more mobile terminals 32 capable of communicating within and / or through a respective cellular network. And as described below, one or more of the mobile terminals are capable of operating as a source node 20, such as in the same way as the source nodes of the public and private networks. In addition, also as described below, one or more of the mobile terminals are capable of operating as a termination node 3-8, which as previously stated and as described below may be able to communicate with a node source by means of a SIP proxy 16 according to SIP. Within cellular networks 30, network nodes may also include one or more network signaling support nodes such as one or more SGSNs (GPRS signaling support nodes) 38, and one or more gateway support nodes, such as one or more GGSNs (GPRS gateway support nodes) 40. For example, the network nodes may include one or more SGSNs and one or more GGSNs, as described in a number of 3G Association Project specifications ( 3GPP). As will be appreciated by those skilled in the art, the SGSNs are capable of routing communications to and from the mobile terminals 32, and can also provide a connection to other network nodes when the terminals are involved in a communication session with these network nodes. On the other hand, GGSNs are capable of interconnecting cellular networks and private networks 24. In this regard, GGSNs are capable of performing traditional gateway actions, since these are well known. It should be noted that although cellular networks may include SGSNs and GGSNs, cellular networks may comprise other network nodes that operate similarly for other types of cellular networks. Next, reference is made to Figure 2, which illustrates a block diagram of an entity capable of operating as a network node (e.g., the SIP proxy 16, the origin node 20, the NAT / FW 28, termination node 36, SGSN 38, GGSN 40, etc.) within public network 12 private networks 24 or cellular networks 30 according to one embodiment of the present invention. Although shown as separate entities in some embodiments, one or more entities could support one or more of the network nodes, logically separate but co-located within the entity (s). For example, a single entity could support a logically separate but co-located source node and a SIP proxy. Also as indicated above, for example, a single entity could support a logically separate, though co-located, NAT and a firewall / gateway. As shown, the entity capable of operating as a network node can generally include a controller 42, a processor or the like connected to a memory 44. The controller can also be connected with at least one interface 46 or other means for the transmission and / or reception of data, content, or the like. The memory may comprise a volatile and / or non-volatile memory, and commonly stores the content, data or the like. For example, memory typically stores software applications, instructions or the like for the controller to perform the steps associated with the operation of the entity in accordance with the embodiments of the present invention. Also for example, the memory commonly stores the content transmitted from, or received by, the network node. Figure 3 illustrates a functional diagram of a mobile station that could operate as a mobile terminal 32 and as such, a source node 20 or a termination node 36, according to the embodiments of the invention. It should be understood that the mobile station illustrated and described below is simply illustrative of a type of mobile terminal that would benefit from the present invention and therefore, should not be taken to limit the scope of the present invention. While various modalities of the mobile station are illustrated and will be described hereinafter for purposes of example, other types of mobile terminals, such as personal digital assistants (PDA), personal locators, laptops of type 'laptop' and other types of voice and text communication systems, can easily employ the present invention. The mobile station includes a transmitter 48, a receiver 50, and a controller 52 that provides the signals and receives the signals from the transmitter and receiver, respectively. These signals include the signaling information according to the applicable cellular system air interface standard, and also the user conversation and / or user generated data. In this regard, the mobile station may be able to operate with one or more air interface standards, communication protocols, modulation types and access types. More particularly, the mobile station may be capable of operating in accordance with any of a number of communication protocols 1-G, 2G, 2.5G and / or 3G, or the like. For example, the mobile station could be able to operate in accordance with the 2G wireless communication protocols IS-136 (TDMA), • GSM and IS-95 (CDMA). Also for example, the mobile station could be capable of operating in accordance with the 2.5G wireless communication protocols -GPRS, the Enhanced Environment -GSM Data (EDGE), or the like. Some narrow-band AMPS (NAMPS), as well as also TACS mobile stations, could also benefit from the embodiments of the present invention such as mobile stations of double or higher mode (e.g., digital / analogue or TDMA / stations). CDMA / analog phones). It is understood that the controller 52 includes "the set of circuits required for the implementation of the audio and logical functions of the mobile station." For example, the controller could be comprised of a digital signal processing device, a microprocessor device and several Analog to digital converters, digital-to-analog converters and other support circuits The control and signal processing functions of the mobile stations are distributed among these devices in accordance with their respective capabilities. It includes the functionality of encoding in convolutional form and interleaving of messages and data before modulation and transmission.In addition, the controller can include an internal voice coder (VC) 52A, and could include an "internal data modem" ( DM) 52B In addition, the driver could include the functionality to operate one or more applications of software, which could be 'stored' e? ' the memory. The mobile station also comprises a user interface that includes a conventional headset or loudspeaker 54, a calling or calling device 56, a microphone 60, a display 62 and a user input interface, all of which are connected to the controller 52 The user input interface, which allows the mobile station to receive data, may comprise any of a number of devices that allow the mobile station to receive data, such as a keyboard 64, a touch screen or touch (not shown). ) or another input device. In embodiments that include a keyboard, the keyboard comprises a conventional numeric keypad (0-9) and related keys (#, *), and other keys used for the operation of the mobile station. Although not shown, the mobile station may further include an IrDA transceiver or other local data transfer device, so that data may be shared with and / or obtained from other devices such as other mobile stations, guidance systems of automobile, personal computers, printers, printed materials that include bar codes and the like. He ' Data sharing, as well as remote data sharing, can also be provided according to a number of different techniques. For example, the mobile station could include an RF transceiver capable of sharing data with other radio frequency transceivers, and / or with a transponder tag of Radio Frequency Identification (RFID), as is known to those skilled in the art. Additionally or alternatively, the mobile station could share data using the BT-branded wireless technology developed by the Bluetooth Special Interest Group. In addition, the mobile station could be able to share data according to any of a number of different interconnection techniques and wired and / or wireless networks, which include LAN and / or WLAN techniques. The mobile station may also include a memory, such as a subscriber identity module (SIM) 66, a removable subscriber identity module (R-UIM) or the like, which normally stores the information elements related to a mobile subscriber. In addition to the SIM, the mobile station may include another memory. In this regard, the mobile station may include a volatile memory 68, as well as another non-volatile memory 70, which may be embedded and / or may be removable. For example, the other non-volatile memory may comprise embedded or removable multimedia memory cards (MMCs), "Memory Stick" type memory cards that are manufactured by Sony Corporation, EEPROM cards, instant memory cards, hard disk or the like. The memories can store any of a number of pieces of information and data, which are used by the mobile station to implement the functions thereof. For example, the memories may store an identifier, such as an international mobile equipment identification code (IMEI), an international mobile subscriber identification code (IMSI), a mobile station integrated services digital network (MSISDN) code. , or similar, with the ability to uniquely identify the mobile station. Memories can also store content, so that they transmit it to or receive it from an origin node 20. As indicated in the background section, conventional techniques allow a source node to enter content into a node of origin. termination 36, such as the mobile terminal, ignore the limitations of public domains such as public network 12 (for example, the Internet) that lead to the use of NAT / FW 28 to interconnect the public network with a respective private network 24. A know, these techniques ignore the limitation of public IP addresses available. Also, this technique ignores the ability of the NAT / FW to provide a firewall and / or gateway functionality to a respective private network. Therefore, the embodiments of the present invention provide an improved system and method for entering content into a terminating node, wherein the terminating node resides in a private or cellular network (i.e., in a mobile network) . More particularly, the embodiments of the present invention provide a system and method that allow the originating nodes to enter content into terminating nodes using a data session technique initiated by re-d that takes into account the limited address space of public domains. In addition, the system and method may allow, but not necessarily, the originating nodes to introduce content into the terminating nodes, while maintaining the functionality of the firewall and / or gateway in the mobile network. As described below, the originating node initiates communication with a terminating node comprising a terminal within a cellular network 30. However, it should be understood that the terminating node may comprise, alternatively, a network node. from a private network, without departing from the spirit and scope of the present invention. As is well known to those skilled in the art, a SIP is an application layer control protocol that can establish, modify and terminate sessions or multimedia calls. The SIP is text based, uses the ISO 10646 standard in all UTF-8 coding. The syntax of the messages is similar to HTTP, except that the SIP can carry the transaction using either the User Datagram Protocol (UDP) or the Transmission Control Protocol (TCP). A SIP message can usually be characterized as either a request or a response and can be created next to the Internet Engineering Task Force (IETF) request format for comment document RFC 822 entitled: Standard for the Form t of ARPA Internet Text Messages, August 1982, the contents of which are incorporated herein by reference in their entirety. In general, the entities involved in a SIP session include a user agent (for example, the source node 20, the termination node 36, etc.), the SIP proxy 16, a registrar and a location service. The user agent can also operate as a server (UAC) that initiates a SIP request. The user agent can also operate as a server (UAS) that contacts the user when a SIP request is received, and sends back a response on behalf of the user. The SIP proxy, as indicated above, comprises an intermediate entity that can function, simultaneously, as a client and as a server. In this regard, the SIP proxy can interpret and modify a SIP request before sending it to other servers. The registrar that, as shown, can be implemented in the SIP proxy, accepts the user records (for example, the REGISTER messages) and can make this information available through a location service, which It also has the ability to be implemented in the SIP proxy. Then, the location service comprises an element used by the SIP proxy to obtain information about the possible location of the terminating node. Generally, a SIP message comprises a start line, one or more header fields, an empty line (carriage return line feed - CRLF) and an optional main part. In general, the start line of a SIP message indicates whether the message is a request (for example, INVITE, ACK, OPTIONS, BYE, CANCEL, REGISTER, REFER, etc.), or a response (for example, Information 100, Success 200, Redirection 300, Client Error 400, Server Error 500, Global Failure 600, etc.). The message header can include multiple headers indicating, for example, the source ("From:"), the destination ("To :;), the call identifier (" Call-ID: "), the message sequence (" Cseq: "), the contact (" Contact: "), the transaction path (" Via: ") , the duration ("Content-Length:") and the content ("Content-Type:") of the main part, if it was carried in the message, on the other hand, the main part of the message can include any of a number of different types of data, the interpretation of which is usually a function of the type of message.In general, the content of the main part may comprise a session description followed by a specific format such as the Session Description Protocol (SDP) ), text or the actions of the Extensible Signaling Language (XML) In this regard, the header field "Content-Type" (Content Type) provides the media type of the main part of the message. encoded, this encoding would normally be indicated in the header field "Content-E ncoding "(Content Coding), and the length of the main body would normally be given in the" Content-Length "header field. SIP-driven entities may include users that can be accessed through the SIP proxies 16 that these users support, where users can be identified by a Uniform Resource Locator (URL) SIP. In general, SIP URLs are used within SIP messages to indicate, for example, the sender or originator (From) (of)), the current destination on the start line (request URL) and the recipient or sender end (To) (To)) of a SIP request. As will be appreciated, the URL can take the form such as "userThost", where the word "user" normally identifies the user. { for example, the name, the telephone number of the user etc.) and the word "host" (host) identifies a proxy "SIP (for example, the domain name, IP address, etc.) that the user supports. In this respect, SIP URLs can be used to locate a user based on a domain name-to-IP address transformation by the DNS server 18, in particular, when the URL includes the domain name of the respective SIP proxy. In this regard, the originator may consult the DNS server which includes the destination address comprising the domain name of the SIP proxy As indicated above, the system 10 may include a source node 20 and a termination node 36. In general, the terminating node is able to subscribe to an introductory service, such as the SIP introduction service, of the originating node, so that the originating node can enter the content in the future. node of ter by means of a SIP proxy 16 that supports the termination node. As is well known to those skilled in the art, the SIP proxy may be able to send or transmit SIP signaling messages to the terminating node from the originating node and vice versa. However, in contrast to conventional SIP communication techniques, when the terminating node is located behind a NAT / FW 28 from. From the source node, the SIP proxy could not be able to identify the terminating node - through the NAT / FW when the originating node wishes to initiate a SIP communication session with the terminating node. More particularly, for example, the SIP proxy might not be able to identify the terminating node when the NAT / FW no longer maintains a transformation table entry between the terminating node or the SIP proxy no longer keeps a record of a public IP address and the port assigned by the NAT / FW to the terminating node. In accordance with embodiments of the present invention, then, the terminating node 36 may be able to instruct the SIP proxy 16 to subscribe to a service introducing a source node 20 in the name of the terminating node. So, the originating node can provide the introduction service to the SIP proxy on behalf of the terminating node. In turn, the SIP proxy can use a network initiated data session technique to communicate with the terminating node through the NAT / FW 28 in order to supply the introduction content to the terminating node. The SIP proxy can use any of a number of different data sessions initiated by network with the terminating node, thereby initiating communication with the terminating node, so that the SIP proxy can supply the introduction content to the node of completion. For example, the SIP proxy can use a network-initiated data session technique according to the specification of the Third Generation Partnership Project 2 (3GPP2) 3GPP2 S.PO090, entitled: Network-Initiated Data Session (NIDS), the contents of which are incorporated herein by reference in their entirety. In another example, the SIP proxy 16 may be able to send a non-IP-based trigger to the terminating node 36 independent of the public and private networks 12, 24, whereby the terminating node is instructed to register again with the SIP proxy, such as through the NAT / FW 28. In this regard, the SIP proxy may be able to send a short messaging service (SMS) message or an enhanced messaging service (EMS) message, or a multimedia messaging service (MMS) message on activation of Wireless Application Protocol (WAP) to the terminating node. In response to the trigger, the termination node can be re-registered with the SIP proxy, so that the SIP proxy can communicate with the terminating node through the NAT / FW from now on. More particularly, in response to the trigger, the terminating node can be registered with the SIP proxy through the NAT / FW, such that the NAT / FW assigns a public IP address to the terminating node, and so the proxy SIP can register the terminating node that includes the assigned IP public address. As indicated previously, the SIP proxy can implement a SIP agreement recorder with which the registrar functions are performed, in order to register the termination node. As described herein, it should be understood that the SIP proxy may comprise a SIP proxy that implements a corresponding registrar, in order to register and / or re-register the terminating node. To allow the SIP proxy 16 to send a non-IP-based trigger to the terminating node 36, the SIP proxy is able to identify the independent terminating node of an IP communication channel of the public and private networks 12, 24, and this way, through a communication channel independent of NAT / FW 28. For example, the SIP proxy may be able to identify an MSISDN or other global identifier associated with the terminating node. Based on the MSISDN, then, the -proxy SIP can send an activator of SMS, EMS, MMS or WAP introduction to the terminating node. In this regard, the SIP proxy may be able to recognize a non-IP-based identifier of the terminating node in any of a number of different modes. In an advantageous embodiment, the terminating node is registered with the SIP proxy before the SIP proxy receives the introduction content of the originating node 20 for the terminating node. As soon as the terminating node registers with the SIP proxy, then the terminating node can send to the SIP proxy an identifier (e.g., MSISDN) of the terminating node outside of an IP communication channel. For more information on this network initiated data session technique, see United States Patent Application No. 10/797, 765, entitled: System and Method for Establishing a Session Initiation Protocol Communication Session with a Mobile Terminal, submitted on March 10, 2004, the contents of which are incorporated herein by reference in their entirety. And for an example of another network initiated data session technique, see U.S. Patent Application No. 10 / 797,529 entitled "System and Method for Establishing an Internet Protocol Connection with a Terminated Network Node," presented on May 10. March 2004, the contents of which are also incorporated herein as a reference in their entirety. Reference is now made to Figures 4A and 4B, which illustrate the examples of a method of entering content in a terminating node 36 according to the embodiments of the present invention. For purposes of the examples shown in Figures 4A and 4B, a termination node having a private IP address is considered, and is capable of being identified by a user and a host domain name. Also, the termination node is considered to have an MSISDN. In addition, for example, a source node 21 proxy SIP 16 is considered, each of which has a public IP address. In addition, it is considered that a NAT / FW 28 is capable of assigning one or more IP addresses within a set of IP addresses.
As shown in Figure 4A, the terminating node 36 can instruct the SIP proxy 16 to subscribe to an introduction service of the originating node 20 on behalf of the terminating node by sending a SIP REFER message to the SIP proxy by means of a respective NAT / FW 28. As will be appreciated by those skilled in the art, the SIP REFER message can be used by the terminating node to require the SIP proxy to refer to a resource (i.e., the node introduction service). origin) identified in the REFER message, and to allow the terminating node to be notified of the output of the reference request. For more information on the SIP REFER technique, see the IEFT request in the comment document 'RFC 3515 entitled: The Session - Initiation Protocol (SIP) Refer Method, April 2003, the contents of which are incorporated herein, as, reference in its entirety. The SIP REFER message may include any of a number of pieces of information, as described above. For example, the header fields of the SIP REFER message may include a source identifying the private IP address of the terminating node 36. - The header fields may also include, for example, a destination identifying the public IP address of the SIP proxy 16, and a contact that identifies the user and the domain name of the termination node. In addition, the header fields can identify the source node 20 in a reference header field ("Refer-To:") which also recognizes the introduction service of the source node and instructs the SIP proxy to subscribe (ie , the method = SUBSCRIBE (SUBSCRIBE)) to the introduction service. In response to the SIP REFER message, the NAT / FW 28 can create a new transformation table entry for the terminating node 36 by associating the private IP address of the terminating node with a public IP address. If the NAT / FW currently has a transformation table entry for the terminating node with an IP public assigned address, however, the NAT / FW may look up the transformation table entry for the terminating ode. In addition to the creation of a new transformation table entry to allow communications between the intermediate node and the NAT / FW, if desired, the NAT / FW can also add a new firewall filter (FW) which allows communications from the NAT / FW and communications to the SIP proxy 16. Although not described herein, messages sent and / or received in accordance with the embodiments of the present invention may also include an open port. In these examples, the "NAT / FW can create transformation table entries as well as include the same or another communication port and can also operate in a mode taking into account this communication port (s). After the creation of a new transformation table entry or the search of an existing transformation table entry, the NAT / FW 28 can transform the private IP address of the terminating node 36 into the header fields of the SIP REFER message ( REFER TO SIP) in a public IP address assigned to the terminating node by the NAT / FW. Also, depending on the operation of the NAT / FW ALG, a contact identifying the user and the domain name of the terminating node can be transformed to identify the public IP address assigned to the terminating node. Then, after the transformation of the address of the SIP REFER message, the NAT / FW can pass the transformed SIP REFER message to the SIP proxy 16. Based on the reception of the transformed SIP message • REFER, the SIP proxy 16 can accept the SIP REFER message by returning an acceptance, such as the message (ACCEPTED (ACCEPT-DO)) 202, back to termination node 36 via NAT / FW 28. In this regard, the message (ACCEPTED) 202 can identify the terminating node through the public IP address assigned to the terminating node by the NAT / FW. Based on the reception of the message . { ACCEPTED) 202, then, the NAT / FW can transform the public assigned IP address into a private IP address of the terminating node. Then, the NAT / FW can send the message (ACCEPTED) 202 to the terminating node. Also, because the SIP REFER message requires the SIP proxy 16 to enter a subscription on behalf of the terminating node 36, the SIP proxy can create a SIP subscription for the reference request of the terminating node. After the creation of the subscription, then, the SIP proxy can return the SIP NOTIFY message (ie, NOTIFY (REFER)) to the terminating node, thereby notifying the terminating node that the proxy SIP has created a subscription for the reference request of the terminating node. And in the same way as before, the SIP proxy can send the SIP NOTIFY message to the terminating node via NAT / FW 28 by directing the SIP NOTIFY message to the IP public assigned address of the terminating node. In turn, the NAT / FW can transform the public IP address assigned to the terminating node to the private IP address of the terminating node and can send the SIP NOTIFY message to the terminating node. Then, in response to the SIP NOTIFY message, the terminating node can send an acknowledgment of the SIP NOTIFY, such as the message (OK) 200, back to the SIP proxy 'via NAT / FW, which transforms the IP private address of the terminating node in the IP public address assigned to the terminating node by the NAT / FW.
Also based on the reception of the SIP REFER message, the SIP proxy 16 can process the SIP REFER message by subscribing to the introduction service of the source node 20 on behalf of the terminating node 36 according to the SIP REFER message. In this regard, the SIP proxy can send a SIP SUBSCRIBE (SUBSCRIBE SIP) message to the originating node, whereupon it subscribes to the introduction service of the originating node. The SIP SUBSCRIBE message can include any of a number of different pieces of information, although according to the SIP REFER message, it recognizes the introduction service identified in the SIP REFER message. In addition, because the SIP proxy is subscribing to the introduction service on behalf of the terminating node, the SIP SUBSCRIBE message typically identifies the SIP proxy, which is opposite to the terminating node. Based on the reception of the SIP SUBSCRIBE message, the originating node 20 can recognize the reception of the SIP SUBSCRIBE message, by returning a message (OK) 200 to the SIP proxy 16. In addition, the originating node can create a subscription to the SIP SUBSCRIBE service. Introduction to the -proxy SIP. After the creation of the subscription, the originating node can return a SIP NOTIFY message (ie, NOTIFY (SUBSCRIBE)) to the SIP proxy, thereby notifying the SIP proxy that the originating node has created a subscription in the service of introduction of the source node for the SIP proxy. Based on the receipt of the SIP NOTIFY message, the SIP proxy, in accordance with the reference subscription, can notify the termination node 36 of the successful subscription. In this regard, the SIP proxy can send a SIP NOTIFY message (ie, NOTIFY (REFER)) to the terminating node via NAT / FW 28 by directing, in the same way as before, the SIP NOTIFY message to the address public IP address of the terminating node. Also, in the same way as before, the NAT / FW can transform the public IP address assigned to the terminating node into the private IP address of the terminating node. In addition, the terminating node can send a message (OK) 200 back to the SIP proxy via NAT / FW. At one or more points at a time once the SIP proxy 16 has subscribed with good results to the introduction service of the source node 20 on behalf of the terminating node 36, the terminating node can receive the introduction content from the originating node by means of the SIP proxy and according to the introduction service. In this regard, according to the subscription to the introduction service, the originating node can send a SIP NOTIFY message. { that is, NOTIFY (INC. CONTENT)) to the proxy "SIP that includes the introduction content." In the same way as before, based on the reception of the SIP NOTIFY message, the SIP proxy can return the message (OK) 200 to the node Also, based on the reception of the introductory content, the SIP proxy can transmit or send the introduction content to the terminating node 36 by means of the NAT / FW 28 according to the reference subscription entered by the SIP proxy For the termination node, in several examples, such as a "time-in-vivo" period, however, the NAT / FW 28 could remove the transformation table entry for the termination node 36. In addition or Alternatively, for example, the SIP proxy 16 could cease to maintain the registry entry for the terminating node, including the public IP address assigned to the terminating node by the NAT / FW. proxy SIP, and subsequently, enter a state of "passive or resting" operation. In any of these examples, as will be appreciated, the proxy 'SIP could not be able to identify the terminating node through the NAT / FW, whereby the introduction content is sent to the terminating node through the NAT / FW According to "the embodiments of the present invention, below," based on • the reception of the introduction content, the SIP proxy 16 can temporarily store the introduction content of the node of • source 20, in a memory (for example, memory 44) of the SIP proxy. Thereafter, the proxy SIP can establish a network-initiated data session with the terminating node 36. For example, the SIP proxy 16 can send a non-IP-based trigger to the terminating node based on an identifier not IP-based termination node, such as MSISDN. In turn, the non-IP-based trigger can instruct the terminating node to re-register with the SIP proxy. For example, the SIP proxy can send an SMS message, an EMS message, an MMS message or a WAP push trigger to the terminating node through the cellular network 30 independent of the public and private networks 12, 24, and so on. both, to NAT / FW. In response to the fact that the SIP proxy 16 establishes a network-initiated data session with the terminating node 36, the terminating node can be re-registered with the SIP proxy so that the NAT / FW 28 can once again assign a IP public address and a communication port to the terminating node, and the SIP proxy can update its registry entry for the terminating node. More particularly, for example, once the terminating node receives the trigger, the terminating node can send a SIP REGISTER message. { REGISTER SIP) to the SIP proxy through the respective NAT / FW. In response to the SIP REGISTER message, the NAT / FW can once again create a new transformation table entry for the terminating node by associating the IP private address of the terminating node with the public IP address. After the creation of a new transformation table entry, the NAT / FW 28 can transform the private IP address of the terminating node 36 into the SIP REGISTER message in the public IP address assigned to the terminating node by the NAT / FW. Then, the NAT / FW can pass the transformed SIP REGISTER message to the SIP proxy 16 for its registration. Based on the receipt of the transformed registration message, the SIP proxy can update the previous registration entry for the terminating node. Then, the SIP proxy can confirm the receipt and creation / update of the registry entry. In the same way as before, for example, the SIP proxy can send a message (OK) 200 to the terminating node via NAT / FW 28. After the new registration of the terminating node -36, the SIP proxy 16 can transmit or send the introduction content to the terminating node via NAT / FW 28, within a SIP MESSAGE. For more information on a technique for sending this message, see the IETF request for the RFC 3428 comment document entitled: Session Initiation Pr tocol (SIP) Extension for Instant Messaging, December 2002, the contents of which are incorporated in this as a reference in its entirety. In this regard, from the SIP proxy, the NAT / FW can receive the input content and look up the transformation table entry for the terminating node based on the IP public assigned address of the terminating node (which is identified as the destination of the introduction content). Then, the NAT / FW can transform the destination of the input content of the assigned public IP address to the private IP address of the terminating node. After the transformation of the destination of the introductory content, the NAT / FW can send the introductory content to the terminating node based on the private IP address of the terminating node. Next, although not shown, the terminating node can confirm the reception of the introduction content by sending a message (OK) 200 to the SIP proxy via the NAT / FW. Instead of the SIP proxy 16 storing the input content in a buffer and transmitting or sending the input content to the terminating node 36, the terminating node can be configured, so that after the new registration with the SIP proxy, the termination node subscribes to the introduction service with which, it receives the introduction content. In this regard, reference is now made to Figure 4B which illustrates a portion of a method of introducing content into a terminating node according to another embodiment of the present invention. As shown in Figure 4B, in the same way as before, once the SIP proxy has subscribed with good results to the introduction service of the source node 20 on behalf of the terminating node, the originating node can send to the SIP proxy a SIP NOTIFY message (ie, NOTIFY (INC. CONTENT)) that includes the introduction content according to the introduction service. Also in the same way as before, in response to the SIP NOTIFY message, the SIP proxy can return a message (OK) 200 to the originating node. Subsequently, the SIP proxy can establish a data service initiated by network with the terminating node, by sending a non-IP-based trigger to the terminating node. Then, in the same way as before, the terminating node can be re-registered with the SIP proxy through NAT / FW 28, so that the NAT / FW can once again assign a public IP address and a communication port to the terminating node, and the SIP proxy can update its registry entry for the terminating node. After the new registration with the SIP proxy 16, the terminating node 36 can subscribe with the introduction service of the originating node 20, so that the terminating node can receive the introduction content of the originating node, which is opposite to receive it from a SIP proxy buffer, as shown in Figure 4A. In this regard, when you configure the terminating node to instruct the SIP proxy, to -subscribe in the introduction service on behalf of the terminating node and subsequently, to subscribe to the introduction service once the SIP proxy receives the contents of the SIP proxy. In the introduction, the termination node only needs to occupy the network resources during periods of time when the originating node sends the introduction content according to the introduction service. As shown, the node. terminator 36 may subscribe to the introduction service by sending a SIP SUBSCRIBE message to source node 20 via NAT / FW 28 and SIP proxy 16, as shown in Figure 4B. More particularly, the terminating node can send a SIP SUBSCRIBE message, in the same way as before, which identifies the introduction service of the originating node and which identifies the terminating node, normally, that recognizes the private address. IP of the termination-node. Then, the NAT / FW can receive the SIP SUBSCRIBE message, in addition it can look for the transformation table entry for • the termination node and later, it can transform the private IP address of the terminating node into the SIP SUBSCRIBE message in the public address IP assigned to the terminating node by the NAT / FW. After the transformation of the IP private address of the terminating node to the public assigned IP address, the NAT / FW 28 can send the SIP SUBSCRIBE message to the SIP proxy ....
In turn, the SIP proxy can transmit or send the SIP SUBSCRIBE message to the source node. Based on the reception of the SIP SUBSCRIBE message, in the same way as before, the originating node 20 can recognize the reception of the SIP SUBSCRIBE message by returning a message (OK) 200 to the terminating node 36 via the SIP proxy 16 and the NAT / FW 28, which transforms the private IP address of the terminating node into the public IP address assigned to the terminating node. In addition, the originating node can create a subscription to the introduction service for the terminating node. After the creation of a subscription to the introduction service for the terminating node, the originating node can send a SIP NOTIFY message to the terminating node via the SIP proxy and the NAT / FW. As before, the SIP NOTIFY message can include the introduction content according to the introduction service subscription. In this regard, the SIP NOTIFY message may comprise the same SIP NOTIFY message received by the SIP proxy before the SIP proxy established the data service initiated by the network with the terminating node, although the SIP NOTIFY message now received by the SIP terminating node through the SIP proxy and the NAT / FW identifies the terminating node as the destination of the message. Based on the receipt of the SIP NOTIFY message including the introductory content, then, the terminating node can return the message (OK) 200 to the originating node via the NAT / FW and the SIP proxy. As described herein, the terminating node 36 is located behind the NAT / FW 28 starting from a source node 20. However, it should be appreciated that the terminating node can be located behind the firewall / gateway (FW) without a NAT between the terminating node and the originating node. In these examples, the embodiments of the present invention may be capable of allow the originating node to initiate communication with the terminating node in examples in which communication could otherwise be restricted by the FW, thereby maintaining the functionality of the firewall and / or gateway in the network that includes the terminal. For example, as will be appreciated by those skilled in the art, a system 10 that includes a NAT for the transformation of the private / public address is common to the networks that are communicated in accordance with Version 4 I-P. { IPv4). However, it must be understood that the system, or . portions of it, can be alternatively configured to communicate in accordance with Version 6 IP (IPv6), - which supports longer IP addresses than IPv4. In this regard, because! Pv6 supports longer IP addresses than IPv4, one or more of the private networks could not require a NAT to perform address / port transformations. In these examples, the system could not include a NAT or FW / NAT, but instead include a firewall / gateway (FW) capable of operating as a security mechanism for an associated private network, just as in the same way described earlier. Then, the system can operate as described above, although the terminating node can have an associated IPv6 public address. As such, the source or destination of the communications between the originating node and the terminating node, which otherwise identifies an IPv4 assigned public address of the terminating node that is transformed by a NAT into a private IPv4 address, can identify the IPv6 public address of the terminating node and can pass without transforming it from a public IPv4 address to a private IPv4 address or vice versa. Many modifications and other embodiments of the invention will come to the mind of a person skilled in the art to which this invention relates with the benefit of the teachings presented in the foregoing descriptions and associated drawings. Thus, it is understood that the invention will not be limited to the specific embodiments described and it is intended that the modifications and other embodiments be included within the scope of the appended claims. Although the specific terms are used herein, they are used only in a generic and descriptive sense and not for purposes of limitation. It is noted that in relation to this date the best method known by the applicant to carry out the aforementioned invention, is that which is clear from the present description of the invention.

Claims (9)

  1. CLAIMS Having described the invention as above, the content of the following claims is claimed as property: 1. A system for introducing content in a terminal located within a mobile network and a private network, characterized in that it comprises: a network node located through a public network of the network - including the terminal, where the network node is able to subscribe to an introduction service on behalf of the terminal, so that the network node is also capable of receiving the introduction content according to the introduction service, wherein the network node is able to establish a data session initiated by network with the terminal, and wherein the network node may be able to register the terminal in response to the Data session initiated by network, so that the terminal will have the ability to receive the introduction content based on the record.
  2. 2. The system in accordance with the claim 1, characterized in that the network node is capable of receiving, and subsequently storing in an intermediate memory, the input content, and wherein the network node is capable of sending the input content to the terminal from the buffer .
  3. 3. The system according to claim 1, characterized in that the network node is capable of registering the terminal, so that the terminal is able to subscribe to the introduction service based on the record, and subsequently, receives the content of introduction on the basis of to the terminal that subscribes to the introduction service.
  4. 4. The system according to claim 1, characterized in that the network node is able to establish a data session initiated by network with the terminal by sending an activator to the terminal independent of the public network, thereby activating the terminal to register with the network node.
  5. 5. The system according to claim 1, characterized in that the network node is able to receive a registration message from the terminal through the public network, whereby the terminal is identified through the public network and registers the terminal, and wherein the network node is capable of registering the terminal so that the terminal is capable of receiving the introduction content based on the identity of the terminal through the public network. The system according to claim 5, characterized in that the network node is able to receive a terminal registration message at least by means of a network address translator (NAT) and a firewall (FW) located between the network node and the terminal, and wherein the network node is capable of establishing a data session initiated by the network in an independent mode at least one of the NAT and the FW. 7. The system in accordance with the claim 1, characterized in that the network node comprises a Session Initiation Protocol (SIP) proxy. S. A method of introducing content to a terminal located within one of a. mobile network and a private network, characterized in that it comprises: subscribing to a service introducing a network node located through a public network of the network that includes the terminal, where the subscription to the introduction service comprises the subscription to a introduction service on behalf of the terminal; receive the introduction content in the network node according to the introduction service; establish, in the network node, a data session initiated by network with the terminal; register the terminal with the network node in response to the data session initiated by network; and send the introduction content to the terminal based on the record. The method according to claim 8, characterized in that the reception of the content of introduction in the network node also includes the storage of the content of introduction in a buffer in the network node, and where the sending of the content of introduction comprises the transmission of the introduction content to the terminal from the buffer. 10. The method according to claim 8, further characterized in that it comprises: subscribing to the introduction service from the terminal based on the registration, wherein the sending of the introductory content comprises the transmission of the introduction content to the terminal based on the subscription to the introduction service starting from from the terminal. 11. The method according to the claim 8, characterized in that the establishment of a data session initiated by network with the terminal comprises the 'sending of an activator of the network node to the independent terminal of the public network whereby the terminal is activated to register with the network node. . 12. The method in accordance with the claim 8, characterized in that the registration of the terminal comprises the reception of a registration message in the network node of the terminal through the public network with which the terminal is identified through the public network, and where the sending of the introduction content includes the transmission of the introduction content based on the identity of the terminal through the public network. 13. The method according to the claim 12, characterized in that the reception of the registration message comprises receiving a registration message in the network node of the terminal by means of at least one network address translator (NAT) and a firewall (FW) located between the network node. and the terminal, and wherein the establishment of a network-initiated data session comprises establishing a data session initiated by the network in an independent mode at least one of the NAT and the FW. 14. The method according to the claim 8, characterized in that the subscription to the introduction service comprises subscribing to a service introducing a network node comprising a Session Initiation Protocol (SIP) proxy. 15. A terminal located within one of a mobile network and a private network, characterized in that it comprises: a -controller capable of instructing a network node to subscribe to an introduction service on behalf of the terminal, so that the node network receives the introduction content according to the introduction service, the network node is located through the public network of the network that includes the terminal, where the controller is able to instruct, to the network node for subscribe to the introduction service, so that the network node also establishes a data session initiated by network with the terminal, where the controller is able to register the terminal with the network node in response to the data session initiated by network and subsequently, receives the introduction content based on the record. • 1
  6. 6. The terminal in accordance with the claim '15, characterized in that the controller is capable of instructing the network node to subscribe to the introduction service, so that the network node receives and stores the input content in a buffer, so that' the controller is able to receive the introduction content of the buffer. .. • 1
  7. 7. The terminal according to claim 15, characterized in that - the controller is able to subscribe to the service of introduction in bas • to the registry, and where the controller. is able to receive the introductory content 'based on the subscription to the introduction service from the terminal. 1
  8. 8. The terminal according to claim 15, characterized in that the controller is capable of receiving an activator from the network node to the independent terminal of. the public network with which, a data session initiated by network is established and the terminal is activated to register with the network node. 1
  9. 9. The terminal according to claim 15, characterized in that the controller is able to send a registration message to the network node through the public network with which, the terminal is identified through the public network, that the network node is capable of registering the terminal, and wherein the controller is able to receive the introduction content based on the identity of the terminal through the public network. The terminal according to claim 19, characterized in that the controller is capable of sending a registration message to the network node at least by means of one of • a network address translator (NAT) and a firewall (FW) located between the network node and the terminal, and wherein the controller is able to instruct the network node to subscribe to the introduction service, so that the network node establishes the data session initiated by network in a independent mode of at least one of the NAT and the FW. The terminal according to claim 15, characterized in that the controller is capable of instructing the network node comprising the Session Initiation Protocol (SIP) proxy to subscribe to the introduction service on behalf of the terminal.
MXPA/A/2006/010188A 2004-03-10 2006-09-07 System and method for pushing content to a terminal utilizing a network-initiated data service technique MXPA06010188A (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US10797491 2004-03-10

Publications (1)

Publication Number Publication Date
MXPA06010188A true MXPA06010188A (en) 2007-04-20

Family

ID=

Similar Documents

Publication Publication Date Title
US8085746B2 (en) System and method for pushing content to a terminal utilizing a network-initiated data service technique
US8989737B2 (en) System and method for establishing a session initiation protocol communication session with a mobile terminal
US7480254B2 (en) System, apparatus, and method for providing multi-application support using a single protocol stack
US8213404B2 (en) System and method for allocating session initiation protocol (SIP) identifications (IDs) to user agents
EP1929712B1 (en) Sip header reduction
US8090858B2 (en) Systems and methods for encapsulation based session initiation protocol through network address translation
KR20050122227A (en) System and method to provide interoperability between session initiation protocol and other messaging services
WO2007125434A2 (en) Address translation in a communication system
US20060274759A1 (en) Method and system for SIP-based mobility management
MXPA06010188A (en) System and method for pushing content to a terminal utilizing a network-initiated data service technique
CA2515547C (en) System and method for allocating session initiation protocol (sip) identifications (ids) to user agents
EP2084885B1 (en) Address translation