Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L67/00—Network arrangements or protocols for supporting network services or applications
  • H04L67/01—Protocols
  • H04L67/04—Protocols specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L67/00—Network arrangements or protocols for supporting network services or applications
  • H04L67/14—Session management
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
  • H04L69/24—Negotiation of communication capabilities
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
  • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
  • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
  • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
  • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
  • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
  • H04L69/327—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the session layer [OSI layer 5]
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
  • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
  • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
  • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
  • H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W72/00—Local resource management
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W76/00—Connection management
  • H04W76/10—Connection setup
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W76/00—Connection management
  • H04W76/20—Manipulation of established connections

Definitions

• the present invention relates to signaling frameworks for wireless communications and more particularly to a signaling framework that allows applications to control the manner in which designated signaling messages are transmitted by a wireless network.
• IP-based protocols allow rapid, cost effective development and deployment of innovative voice and multi-media services without concern for the underlying transport network, and enable interoperability between disparate devices ranging from cellular telephones to laptop computers.
• IP-based protocols developed for wire-line networks for mobile computing environments presents many challenges. Many of the IP-based protocols, such as SIP, are text based. The signaling messages used in these protocols tend to be large. Because radio resources in a wireless network are scarce, the transmission of numerous large signaling messages could consume significant bandwidth that could be used for voice and data services. Further, larger message size typically implies longer transmission time. Many applications are sensitive to delays; thus long packet latencies are undesirable. Packet loss is another concern in wireless networks. Many 4740-202
• the signaling protocols being developed for wireless data services are IP-based networks and are designed to be access independent. While much effort is being expended to make such signaling protocols as efficient and reliable as possible, messages delivered over wireless networks may require special treatment to optimize use of radio resources or to make communications more reliable.
• the present invention provides a signaling framework for wireless communications that allows applications to control the way in which signaling messages are transmitted over a wireless network so as to optimize use of radio resources or to guarantee a certain level of reliability.
• the present invention may be used, for example, to control the manner in which signaling messages are transmitted between a base station and a mobile terminal.
• the signaling framework includes an application layer, a session control protocol layer, and a wireless adaptation layer (WAL).
• the application layer contains an application for communicating with remote devices.
• the session control protocol layer resides below said application layer and maintains a communication session between two devices.
• the wireless adaptation layer resides below said session control protocol layer and controls the manner in which signaling messages are transmitted over an air interface. 4740-202
• the application generates signaling messages and associated wireless adaptation control directives, both of which get sent to the wireless adaptation layer through the session control protocol layer.
• the application may generate signaling messages having wireless control directives embedded therein.
• the wireless adaptation layer is responsive to the wireless adaptation control directives to control how signaling messages should be transmitted.
• the wireless adaptation layer may use a different signaling compression algorithm for designated signaling messages, or may request that special signaling bearers or other resources be used to transmit the signaling messages over a wireless network.
• the wireless application layer may elect to use a common channel rather than a dedicated channel to transmit certain messages to minimize transmission delays.
• the wireless adaptation control directives pass transparently through the session control protocol layer from the application to the wireless adaptation layer.
• the application may associate each wireless adaptation control directive with a specific signaling message to allow the wireless adaptation layer to determine on a message by message basis how to transmit signaling messages over the air interface. For example, the application could associate a wireless adaptation control directive with messages requiring special treatment. Signaling messages not associated with a wireless adaptation control directive would be subjected to default handling.
• the application may use explicit signaling or implicit signaling to pass wireless adaptation control directives through the session control protocol layer to the wireless adaptation layer. Explicit signaling may comprise inserting information into the signaling message, e.g., in a header field for example, that is ignored by the session control protocol layer.
• implicit signaling the application may use different port numbers for different signaling messages. That is, the application may use a specific port, e.g., user datagram protocol (UDP) port or transmission control protocol (TCP) port, 4740-202
• the session control protocol layer passes port information transparently through to the wireless adaptation layer but otherwise ignores port numbers.
• the WAL processes the signaling messages differently based on the port over which the message is received.
• FIG. 1 is a functional block diagram of a wireless network using the signaling framework of the present invention.
• Fig. 2 is a functional block diagram illustrating the IP multimedia subsystem and its relationship to the core network in the wireless network of Figure 1.
• Figure 3 is a diagram illustrating data and signaling flow paths between wireless networks.
• Figure 4 is a diagram of a signaling framework for IP-based communications according to the prior art.
• Figure 5 is a diagram of a signaling framework for IP-based communications according to the present invention.
• Figure 6 is a diagram illustrating end to end signaling between mobile terminals according to the present invention.
• Figure 7 is a diagram illustrating signaling between a mobile terminal and a home network according to the present invention.
• FIG. 1 illustrates the main functional elements of a wireless network 10 that employs the signaling framework of the present invention.
• the wireless network comprises a radio access network (RAN) 20, a core network (CN) 30, and an IP 4740-202
• the RAN 20 supports radio communications with mobile terminals 100 over an air interface, such as cdma2000 or wideband CDMA (W- CDMA).
• the wireless network 10 typically includes more than one RAN 20 though only one is shown in Figure 1.
• the CN 30 provides a connection to the Internet 12 or other packet data network (PDN) for packet switched services such as Internet access, and may provide a connection to the Public Switched Telephone Network (PSTN) 14 and/or the Integrated Digital Services Network (ISDN) 16 for circuit-switched services, such as voice and fax services.
• PDN packet data network
• PSTN Public Switched Telephone Network
• ISDN Integrated Digital Services Network
• the CN 30 may, for example, comprise a General Packet Radio Services (GPRS) network or a cdma2000 network. Other types of network could also be used.
• GPRS General Packet Radio Services
• the CN 30 includes an access gateway 32 for interconnecting with the IMS 40.
• the access gateway 32 may comprise a GPRS Gateway Serving Node (GGSN) for GPRS networks or a Packet Data Serving Node (PDSN) for cdma2000 networks.
• GGSN GPRS Gateway Serving Node
• PDSN Packet Data Serving Node
• the IMS 40 provides access independent, IP-based multi-media services to mobile subscribers and supports voice over IP (VoIP). While the present invention is described in the context of communications between a mobile terminal 100 and an IMS 40, it is useful in other contexts where signaling messages need to be transmitted over a wireless network 10. Therefore, the description of the invention in this context should not be construed as limiting the invention.
• the IMS 40 uses open interfaces and an access independent session control protocol (SCP), such as the Session Initiation Protocol (SIP), to support multi-media applications.
• SCP session control protocol
• SIP Session Initiation Protocol
• the SIP is an application layer control protocol for establishing, modifying and terminating communication sessions between one or more participants. These sessions may include, for example, Internet multimedia conferences, Internet telephony calls, and multimedia distributions.
• SIP is described in the IETF document RFC 2543. While a preferred embodiment of the invention as described herein uses the SIP, those skilled in the art will appreciate that the present invention may use other SCPs as 4740-202
• SIP is a signaling protocol that uses ASCII-based signaling messages to establish a conference or call between two or more participants. Users are identified by a unique address referred to herein as the SIP address. Users register with a registrar server using their assigned SIP addresses. The registrar server provides this address to a location server upon request.
• a SIP request is sent to a SIP server (either a proxy server or a redirect server).
• the request includes the calling party address and called party address in a message header.
• a proxy server receives the SIP request, it forwards the SIP request to the called party.
• the called party may be another user or may be an application server in the user's home network.
• the called party responds to the proxy server, which in turn, forwards the response to the calling party.
• the calling party acknowledges the response and a session is then established between the calling party and the called party.
• Real-time Transfer Protocol RTP is used for the communication between the calling party and the called party.
• a redirect server receives the SIP request, the redirect server contacts the location server to determine the path to the called party, and then sends that information to the calling party.
• the calling party acknowledges receipt of the information and then resends the SIP request to the server identified in the redirection information (which could be the called party of a proxy server).
• the called party responds and the calling party acknowledges the response, communications then begin using RTP.
• SIP is used only to process signaling messages related to call control and session management. 4740-202
• SIP enables applications within the wireless network 10 to establish a communications session.
• the applications may reside in a mobile terminal 100 or in an application server in the IMS 40. Additionally, the applications may reside in different networks 10.
• Figure 2 illustrates the basic elements of the IMS 40 and its relationship to the
• the IMS 40 includes one or more Call State Control Functions (CSCFs) 42, a Media Gateway Control Function (MGCF) 44, a Media Gateway (MGW) 46, a Transport Signaling Gateway (T-SGW) 48, and a Home Subscriber Server (HSS) 50, which are interconnected by an IP network.
• the IMS 40 may further include an application server 52 providing multimedia services to mobile terminals 100.
• the CSCFs 42 function as SIP servers to process session control signaling used to establish, maintain and terminate a communication session.
• the protocol used for a majority of the signaling in the IMS 40 is the SIP.
• Functions performed by the CSCFs 42 include call control, address translation, authentication, capability negotiation, and subscriber profile management.
• the IMS 40 may include additional elements, such as MRFP and MRFC.
• the HSS 50 interfaces with the CSCFs 42 to provide information about the subscriber's current location and subscription information.
• the application server provides multimedia services or other services to mobile subscribers.
• the MGCF 44, MGW 46 and T-SGW 48 support interworking with external networks, such as the PSTN or ISDN.
• the MGCF 44 controls one or more MGWs 46 that manage the connections between the external network and the IMS 40.
• the MGCF 44 configures the MGW 46 and converts SIP messages into a different format, such as ISDN User Part (ISUP) messages.
• ISUP ISDN User Part
• the MGCF 44 forwards the converted messages to the T-SGW 48, which interfaces the IMS 40 to external signaling network, such as the SS7 network.
• the T-SGW 48 includes a protocol converter to convert IP messages to SS7 and vice versa. 4740-202
• Figure 3 illustrates an exemplary flow of signaling messages and user data in a typical communication session initiated by a mobile terminal 100.
• the mobile terminal 100 To send and receive SIP messages over the wireless network 10, the mobile terminal 100 establishes a bidirectional packet data session with the IMS 40, which is illustrated in Fig. 1 by a dotted line to establish a signaling path.
• the signaling path must be established before any SIP messages can be sent.
• Signaling messages originating with the mobile terminal 100 follows the path illustrated by a dotted line in Figure 3.
• Signaling messages pass through the RAN 20, and CN 30, to a CSCF 42 in a visited mobile network 10 functioning as a proxy server.
• the CSCF 42 in the visited network forwards the signaling messages to the home network 10.
• a CSCF 42 in the IMS 40 of the home network forwards the SIP message to the appropriate destination, which may be a mobile terminal 100, an application server 52 within the home network 10, a third party application server in a different network 10, or to PSTN or ISDN.
• a CSCF 42, referred to as the serving CSCF 42, in the home network provides call control session management for the session.
• User data follows a different path (shown by a solid line) than signaling messages. User data passes through the RAN 20 and CN 30 in the visited network. The user data, however, bypasses the CSCFs 42 and passes directly to the Internet or to the MGW 46. A similar signaling and data flow exists for signaling messages and data traveling from an application server 52 in the wireless network 10 to the mobile terminal 100.
• FIG 4 shows the relationship between the SCP and other protocols in a conventional signaling framework. For simplicity, protocol layers not pertinent to the invention are omitted.
• the SCP layer is between the application layer and the wireless infrastructure.
• the SCP layer performs functions needed to establish, maintain, modify, and terminate calls between two or more parties.
• the most common SCP is SIP.
• the SCP layer in the network 10 provides supporting functions such as message routing, authentication, authorization, accounting, location management, capability negotiation, and security.
• Signal compression may be implemented in the SCP layer to allow messages to be sent more efficiently over the wireless infrastructure/air interface.
• SIP messages may be subjected to special treatment by the access gateway 32.
• SIP Session Initiation Protocol
• SIP Session Initiation Protocol
• SIP Session Initiation Protocol
• SIP Session Initiation Protocol
• Some messages are long and may require additional compression beyond that provided by SIP.
• some messages may require special treatment for transmission over the wireless network 10 to guarantee response times or optimize use of radio resources.
• the ability of the access gateway 32 to apply special treatment to all SIP messages does not provide the flexibility needed for communications over the wireless network 10. Not all SIP messages will require special treatment for transmission of the wireless network 10. Applying special treatment to all SIP messages, therefore, may lead to insufficient use of resources.
• SIP may be used to establish a communication session for a push-to-talk telephony application in a mobile terminal 100.
• the SIP client in the mobile terminal 100 sends an INVITE message to the called party. It is desirable for this application that the INVITE message be delivered as quickly as possible, otherwise a session may not be established by the time that the user begins 4740-202
• the SCP layer is not context sensitive and has no way of knowing that the INVITE message requires special treatment for this particular application. Therefore, it would be beneficial if the INVITE message could be flagged by the push-to-talk application in the mobile terminal 100 for special treatment.
• the present invention provides a new signaling framework that enables applications to identify particular signaling messages that require special treatment.
• a wireless adaptation layer (WAL) is inserted in the protocol stack between the SCP layer and transport medium as shown in Fig. 5.
• the WAL is a new protocol layer that performs tasks related to optimizations for communications over a wireless communication link.
• the functional entities within the WAL may reside in various network components, such as a CSCF 42 in the IMS 40 or in a base station controller in the RAN 20. That is, the functions of the wireless application layer may be distributed among network components as needed depending on the optimizations to be performed.
• the WAL determines on a per message basis whether to subject signaling messages to special treatment or to a default treatment. Special treatment may, for example, comprise transmitting the signaling message over a specific radio channel, using a specific bearer service, or using signaling compression or other techniques to minimize use of radio resources.
• Applications communicate with the WAL by generating wireless adaptation control directives that are associated with signaling messages that require special treatment. These directives are ignored by the SCP layer and are processed in the WAL.
• FIG. 5 This transparent signaling between the application layer and the WAL across the SCP layer is illustrated in Figure 5.
• an application in a mobile terminal 100 or an application server 52 can request special treatment of particular SIP messages without modifying the SCP layer.
• the application can send a wireless adaptation directive to the WAL to request special treatment of the INVITE message. 4740-202
• the WAL may decide to use a common channel rather than a dedicated channel to transmit the INVITE message to the network to reduce transmission delays. If a dedicated channel is already established and available, the WAL may use the dedicated channel. The WAL may also compress the INVITE message to reduce transmission time over the air interface to the network. Compression also reduces waste of common resources if a common channel is used.
• the method of giving wireless adaptation control directives to the WAL may vary, depending upon the session control protocol being used. Both explicit and implicit signaling methods may be used.
• explicit signaling the application may insert information into a signaling message, e.g. SIP message, that passes transparently through the SCP layer and is processed in the WAL. This method allows new functions to be added to the applications and the WAL without making changes in the SCP layer.
• implicit signaling the application may use different port numbers for different message types. That is, the application may use a specific port, e.g., UDP or TCP port, for signaling messages requiring special treatment.
• the SCP layer could be designed to pass port information transparently but to otherwise ignore port numbers.
• the WAL would process messages differently based on the port over which the message is received.
• the access gateway 32 or base station controller in the RAN 20 may identify SIP messages needing special treatment by matching packets corresponding to SIP messages to a specific port, e.g., UDP or TCP port and apply special treatment to packets matching the designated port.
• the special treatment might comprise, for example, sending the packet over a specific channel, or configuring a communication channel in a specific way to provide greater reliability or reduce delays.
• optimization of the communication resources used to transmit the signaling message may be performed locally between the mobile terminal 100 and the 4740-202
• the optimizations can be negotiated between the mobile terminal 100 and a visited network at the time the mobile terminal 100 registers with the network 10.
• SIP for example, contains support for capability negotiation. This negotiation could involve the SCP layer, but could also take place entirely within the WAL, making the optimizations totally transparent to the layers above.
• a mobile terminal 100 supporting WAL extensions can communicate with another mobile terminal 100 that does not support the WAL extensions.
• Such communication is possible because the protocols in the SCP layer perform call control and session management independently of the mechanism used for transport.
• the WAL directives will simply be ignored by any entities that do not recognize those directives.
• the WAL directives can also be used in true end-to-end fashion as shown in Figure 6. They can be added by any of the applications shown in Figure 6, including applications within the network 10.
• An application residing in a mobile terminal 100 that does not support the WAL functionality can, itself, associate directives with a SIP message to control a function in the WAL in the network 10 or at a receiving mobile terminal 100.
• Figure 7 illustrates signaling between a mobile terminal 100 in a visited network and the home network.
• the visited network implement the WAL protocols.
• the wireless adaptation directives will simply pass transparently through the visited network to the home network 10. Entities that do not recognize the directive will still be able to receive and process the signaling messages conventionally. The only consequence is that the optimizations may not be performed. 4740-202
• the special handling required for a particular message may be implemented in the WAL itself. For example, where a particular signal compression method is required, such compression can be implemented in the WAL. In other cases, special handling will necessarily involve the access network and/or air interface. For mobile terminals, this type of special handling is not a problem.
• the special handling may be negotiated between the mobile terminal 100 and wireless network 10 by the WAL. Setting up special handling for messages transmitted to the mobile terminal 100 may require a different treatment. In this case, the application associates a directive with the message to be transmitted to the mobile terminal 100. The WAL recognizes this directive and forwards the signaling message to the mobile terminal 100 in a manner that enables it to be identified by the access gateway 32.
• the message may be transmitted to the access gateway 32 over a specific port or may use a specified IP address.
• the access gateway 32 can then easily identify the packets requiring special handling by filtering the packets.
• the access gateway 32 could determine how to handle packets based on message content, but such message processing is not as efficient as packet filtering.
• Adding a WAL controlled by a user application adds a great deal of flexibility without impacting the function of the SCP layer.
• Applications may function with or without the WAL, or with an adaptation layer that does not support all of the desired optimizations. WAL directives not supported will simply be ignored by the SCP layer and/or wireless adaptation layer functions that do not support the requested feature.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Mobile Radio Communication Systems (AREA)
• Communication Control (AREA)
• Telephonic Communication Services (AREA)

Priority Applications (3)

Applications Claiming Priority (2)

Publications (1)

Family

ID=29732795

Family Applications (1)

Country Status (5)

Cited By (1)

Families Citing this family (25)

Citations (3)

Family Cites Families (10)

• 2002
  • 2002-06-12 US US10/171,525 patent/US20030233457A1/en not_active Abandoned
• 2003
  • 2003-06-04 WO PCT/IB2003/002108 patent/WO2003107709A1/en not_active Ceased
  • 2003-06-04 AU AU2003240154A patent/AU2003240154A1/en not_active Abandoned
  • 2003-06-04 CN CN038134160A patent/CN1659921B/zh not_active Expired - Fee Related
  • 2003-06-04 JP JP2004514379A patent/JP4268129B2/ja not_active Expired - Fee Related

Patent Citations (3)

Also Published As

Similar Documents

Legal Events