The present invention relates to real-time communications services in communication systems.
Particularly in the third-generation (3G) mobile communications systems, a public land mobile network (PLMN) infrastructure may be logically divided into core network (CN) 9,10,11,12 and access network (AN) infrastructures 5,6,7,8, as illustrated in
Push-to-talk over Cellular (PoC) is an overlay speech service in a mobile cellular network where a connection between two or more parties is established (typically) for a long period but the actual radio channels in the air interface are activated only when somebody is talking. This corresponds to the usage of the traditional radiotelephones where the used radio frequency is agreed between the parties (e.g. military/police radios, LA radios, walkie-talkie type of radios) and whenever somebody wants to talk s/he presses the tangent, which activates the radio transmission on the selected channel. The traditional radiotelephone services are simplex so that only one party (the one who is pressing the tangent) can talk at a time. More specifically, during voice communication with a “push-to-talk, release-to-listen” feature, a call is based on the use of a pressel (PTT, push-to-talk switch): by pressing PTT the user indicates his/her desire to speak, and the user equipment sends a service request to the network. Alternatively, a voice activity detector (VAD) or any suitable means can be used instead of the manual switch. The network either rejects the request or allocates the requested resources on the basis of predetermined criteria, such as the availability of resources, priority of the requesting user, etc. At the same time, a connection is also established to a receiving user, or users in the case of group communication. After the voice connection has been established, the requesting user can talk and the other users can listen. When the user releases PTT or, in the case of traffic inactivity, the event is detected in the network, and the resources may be released and/or the talk item may be granted to another user. Thus, the resources are reserved only for the actual speech transaction or speech item, instead of reserving the resources for a “call”.
Modern cellular networks, especially in the GSM/GPRS/UMTS network evolution, include new packet-mode (e.g. IP) voice and data services. Push-to-talk over Cellular (PoC) service can be provided as a packet-based user-level or application-level service so that the underlying communications system only provides the basic connections (i.e. IP connections) between group communications applications in the user terminals and a group communication service. The PoC communication service can be provided by a communication server system while the client applications reside in the user equipment or terminals. Examples of this approach are disclosed in co-pending U.S. patent application Ser. Nos. 09/835,867; 09/903,871; and 10/160,272; and in WO 02/085051.
With the PoC service, first the connection(s) between the parties is typically established via the packet-switched (PS) mobile network, for example a packet-switched (PS) core network. In practice, this means that a Voice over IP (VoIP) (group or one-to-one) call is set up between the parties. However, as described above, the difference to a conventional phone call is that the radio channel of the subscribers is activated only when somebody needs to talk and released when nobody is talking.
The PoC service is a practical solution for the cases when the parties need to talk relatively rarely but whenever somebody needs to talk, the connection has to be activated fast and easily (e.g. when giving instructions to the members of a hunting team in the forest or to a crane driver at a construction site). Because in this type of applications, the calls are typically long but the voice activity is low, it is essential to release the bearer (e.g. radio channels) when nobody is talking in order to save the radio and network capacity and terminal batteries. On the other hand, the bearer resources should be available with as small a delay as possible when voice activity again starts.
An object of the invention is to decrease the delay associated with voice transmission in real-time media communication.
The object is achieved by the invention defined in the attached independent claims. Preferred embodiments of the invention are defined in the sub-claims.
An aspect of the invention is a method of controlling a real-time media session, comprising
An aspect of the invention is a method of controlling a real-time media session, comprising
An aspect of the invention is a media communication server for providing real-time media sessions between sets of user equipment located in one or more access networks, wherein
In an embodiment of the invention, a media communication server is configured to send dummy media traffic to first and/or second user equipment only if the session inactivity prior to first signaling exceeds a certain threshold, in order to limit the amount of unnecessary dummy data sent.
An aspect of the invention is a support node for a packet-switched core network, wherein
An aspect of the invention is user equipment for a communication system, wherein
In an embodiment of the invention, the user equipment is configured to send dummy media traffic to the media communication server only if the session inactivity time prior to sending the first signaling exceeds a certain threshold, in order to limit the amount of unnecessary dummy data sent.
The invention is based on sending dummy data (e.g. a dummy message) in order to maintain a dedicated channel during the inactive periods of a real-time media session or to trigger an early dedicated-channel setup in an access network. The invention prevents sets of user equipment that are logged on to a real-time media (e.g. PoC) session from going to a radio resource idle state and, therefore, it prevents potential long extra delays during real-time media (e.g. PoC) service usage. The invention further allows sending and receiving user equipment to set up dedicated channels (DCH) already during the start-to-talk procedure of the transmitting user equipment, which in turn potentially reduces end-to-end delays during the conversation.
The above and other objects, features and advantages of the present invention will become more apparent in light of the following detailed description in conjunction with the drawings, in which
The present invention is applicable to communications systems enabling real-time media sessions between end-users. The real-time data may include real-time audio (e.g. speech), real-time video, or any other real-time data, or a combination thereof, i.e. real-time multimedia.
The present invention is especially applicable to communications systems allowing packet-mode real-time data communication, such as IP packet communication between end users. Thus, the real-time data communication may be carried out between end-user terminals over the Internet, for example.
The present invention offers a significant improvement for packet-mode speech communications. The voice over Internet Protocol (VoIP) enables speech communication over an IP connection. In some embodiments of the invention, the IP voice communication method employed is the Voice over IP (VoIP), but the invention is not limited to this particular method.
As an example of a system environment, to which the principles of the present invention may be applied, will be described with reference to
As regards the PoC type services, examples of this concept are disclosed in co-pending U.S. patent application Ser. Nos. 09/835,867; 09/903,871; 10/160,272; and in WO 02/085051. Conceptually, a packet-based media communications system is provided on top of the mobile network in order to provide media communications services to the user equipment UE through the communications system. The media communications system may be embodied as a server system, and it is generally referred to as a media communications server herein. There may be a plurality of media communications servers 14, 15. As illustrated in the example configuration of
User equipment UE may be a wireless device, such as mobile user equipment, or it may be a device connected by a fixed connection, such as a dispatcher station. Herein the term user equipment and the corresponding acronym UE is used to refer to any device or user equipment allowing the user to access network services.
As an exemplary embodiment, the user equipment UE, such as a Mobile Station MS, may have a PoC application on a user layer on top of the standard protocol stack used in the specific mobile communications system. An appropriate session control protocol, such as Session Initiation Protocol (SIP), may be used for the PoC control-plane signaling. The voice communication may be based on IP communication (such as voice over IP, VoIP), and RTP (Real-time Transport Protocol, defined in RFC1889) may be employed to handle the voice packet (VoIP) delivery on the user plane. The SIP and RTP protocols employ the underlying Transmission Control Protocol (TCP), User Datagram Protocol (UDP) and IP protocols that further employ the physical layer resources, such as the radio resources. For example, the underlying connection in a mobile communications network may be based on a GPRS connection.
An example of a possible implementation of user equipment is illustrated in a simplified block diagram shown in
In the embodiment of
In PS core networks based on GPRS or the like, UE a) performs a GPRS attach procedure, and b) establishes a PDP context (i.e. a bearer) used for SIP signaling. This PDP context will remain active throughout the period UE is connected to PS CN, i.e. from the initial registration and at least until deregistration. As a result, the PDP context provides UE with information that enables UE to construct an IP address. During the establishment of a session, UE establishes data stream(s) for media related to the session. Such data stream(s) may result in the activation of an additional PDP context(s), i.e. bearer(s). Such an additional PDP context(s) is established as a secondary PDP context associated with the PDP context used for signaling. In other core network environments, bearers of other type may be used. It should be appreciated that the basic invention is basically independent of the type of core network.
It should be appreciated that there are many applications of the Internet world that require the creation and management of a session, where a session is considered an exchange of data between a group of participants. The implementation of these applications is complicated by the practices of the participants: users may move between endpoints, they may be addressable by multiple names, and they may communicate in several different media—sometimes simultaneously. Therefore, the present invention is not restricted to PoC services but can be applied to the media flow management of such other applications as well.
Numerous protocols have been authored that carry various forms of real-time multimedia session data, such as voice, video, or text messages. The Session Initiation Protocol (SIP, RFC 3261) is a general-purpose tool for creating, modifying, and terminating sessions that works independently of underlying transport protocols and without dependency on the type of session that is being established. SIP can be used with other IETF protocols to build up a complete multimedia architecture. Typically, these architectures will include protocols such as the Real-time Transport Protocol (RTP) (RFC 1889) for transporting real-time data and providing QoS feedback, the Real-Time streaming protocol (RTSP) (RFC 2326) for controlling the delivery of streaming media, the Media Gateway Control Protocol (MEGACO) (RFC 3015) for controlling gateways to the Public Switched Telephone Network (PSTN), and the Session Description Protocol (SDP) (RFC 2327) for describing multimedia sessions.
It should be appreciated that VoIP and PoC are only examples of real-time media which the present invention can be applied to. It should also be appreciated that the type of media session set up on the application level or the protocols used for controlling the media session on that level are not relevant to the basic invention. The present invention primarily relates to controlling the access bearers on the access-network level, e.g. radio access bearers in RAN.
In the following, a few example embodiments of the present invention will be described using 3GPP RAN (WCDMA) as an example of the access network.
In the 3GPP radio access environment, the user equipment may assume various protocol states.
After power on, UE stays in Idle Mode until it transmits a request to establish an RRC (Radio Resource Control) Connection. In Idle Mode the connection of UE is closed on all layers of the access stratum. In Idle Mode UE is identified by non-access stratum identities, such as an International mobile subscriber identity (IMSI), Temporary mobile subscriber identity (TMSI) and Packet TMSI (P-TMSI). In addition, RNS has no information of its own on the individual Idle Mode UEs, and it can only address all UEs in a cell or all UEs monitoring a paging occasion.
The RRC Connected Mode is entered when the RRC Connection is, established. UE is assigned a radio network temporary identity (RNTI) to be used as UE identity on common transport channels. The transition to the RRC Connected Mode from the Idle Mode can only be initiated by UE by transmitting a request for an RRC Connection. The event is triggered either by a paging request from the network or by a request from higher layers in UE.
When UE receives a message from the network that confirms the RRC connection establishment, UE enters the CELL_FACH or CELL_DCH state of RRC Connected Mode. The RRC states within RRC Connected Mode reflect the level of UE connection and the transport channels that can be used by UE.
In the CELL_DCH state, a dedicated physical channel is allocated to UE in uplink and downlink, UE is known on cell level according to its current active set, and dedicated transport channels, downlink and uplink shared transport channels, and a combination of these transport channels may be used by UE.
The CELL_DCH-state is entered from Idle Mode through the setup of an RRC connection, or by establishing a dedicated physical channel from the CELL_FACH state. Transition to CELL_FACH state occurs when all dedicated channels have been released, which may be via explicit signaling (e.g. PHYSICAL CHANNEL RECONFIGURATION, Radio Bearer Reconfiguration, Radio Bearer Release, Radio Bearer Setup, Transport Channel Reconfiguration, etc.), or at the end of the time period for which the dedicated channel was allocated.
A transition from CELL_DCH-state to CELL_FACH state may occur after a predetermined period of inactivity. The period is monitored by means of an inactivity timer or timers. The period can be set to any value, typical value being 5 to 10 seconds.
In CELL_FACH state, no dedicated physical channel is allocated to UE and UE continuously monitors FACH in the downlink. RAN may know the position of UE on cell level, i.e. according to the cell where UE last made a cell update.
A transition from CELL_FACH to CELL_DCH state occurs, when a dedicated physical channel is established via explicit signaling (e.g. PHYSICAL CHANNEL RECONFIGURATION, RADIO BEARER RECONFIGURATION, RADIO BEARER RELEASE, RADIO BEARER SETUP, TRANSPORT CHANNEL RECONFIGURATION)
A transition from CELL-FACH state may occur after a predetermined period of inactivity. The period is monitored by means of an inactivity timer or timers. The period can be set to any value, a typical value being 5 to 10 seconds.
In CELL_PCH state, no dedicated physical channel is allocated to UE. UE selects one PCH (Paging Channel) with a suitable algorithm, and uses discontinuous reception (DRX) for monitoring the selected PCH. Thus, the power consumption in UE will be reduced. No uplink activity is possible. The position of UE is known by UTRAN on cell level according to the cell where UE last made a cell update in CELL_FACH state. A transition from CELL_PCH state into Idle mode may occur after a predetermined period of inactivity. The period is monitored by means of an inactivity timer or timers. The period can be set to any value, a typical value being relatively long, for instance 20 to 40 minutes.
Push-to-talk over Cellular (PoC) is a speech service in a mobile network where a connection between two or more parties is (typically) established for a long period but the actual radio channels in the air interface are activated only when somebody is talking. With the PoC service, the connections between the parties are typically established via a packet-switched mobile network. In practice this means that a Voice over IP (VoIP) (group) call is set up between the parties. However, the difference to a conventional phone call is that the radio channel of the subscribers is activated only when somebody needs to talk and released when nobody is talking. In more general terms, there is a streaming-type real-time media signal having a session of long duration but requiring dedicated access resources (e.g. DCH) only occasionally with fast set-up times. There is a need for a method and means for controlling the activating and releasing of the access bearer so that the fast set-up time is achieved.
As noted above, UE that does not transmit or receive any data (i.e. is inactive) will after some time go to radio resource control (RRC) Idle state. The operator can configure the timer controlling the inactivity of UE in RNC, the default inactivity threshold being normally in the order of dozens of minutes, for instance 30 minutes. The inactivity detection function of RNS (e.g. RNC) may also be based on some other criteria, such as traffic volume control, traffic measurement, RLC buffers, timers, etc. UE that is in idle state will need more time to set-up a new data connection. This is because the set up procedure involves more signaling (e.g. RRC). The time needed to go from idle state to active state (CELL_PCH) is more than five seconds, and to CELL_DCH typically more than 10 seconds.
The five-second setup time to go from Idle state to CELL_PCH is not an issue for end-users using data services such as FTP, web browsing, MMS, etc. This is mainly because these services can tolerate some extra delays if they are rare enough. However, for a PoC user that is logged on to a PoC session, five extra seconds of start-to-talk time or delay as compared with the other RRC states is definitely too much. The start-to-talk delay may be defined as the time after the PTT button is pressed until the start-to-speak indication is given to the user (the user can start speaking). According to performed PoC service usability studies, a start-to-speak delay of 4 to 5 seconds is still experienced as annoying. A delay of 1 second or less would not be noticed at all. A delay less than 3 seconds can be considered of a reasonable quality. Thus, there is a need to reduce the communication setup delays.
Referring now to
In an embodiment of the invention, the above issue is overcome such that the UEs that are in access networks (e.g. WCDMA) notify the server (e.g. by sending their dummy packets or any other packet) that they need to receive dummy data in order to keep them in active state. As a consequence, the server knows to which UE it should send dummy packets. Any system performance degradation in GPRS networks, for instance, is avoided. For example, in
According to an embodiment of the present invention, a support node in a packet-switched core network 10,11 that provides a real-time media connection to user equipment UE is configured to send during inactive periods of the real-time media connection dummy media towards the user equipment in order to reset an inactivity timer of a common channel state in the radio access network and to thereby prevent the respective user equipment from going to Idle state. In other words, the functionality described above regarding the PoC server (
Referring now to
As noted above, the communication setup delays are very critical performance indicators of the PoC service and other corresponding real-time media communication. DCH (dedicated radio channel) will need to be established for the PoC service at least for carrying voice data traffic. DCH establishment delays are around 1 second from the active states. The DCH establishment delays can be quite annoying during a PoC conversation especially because DCH delays are counted for each UE so the total end-to-end delay is up to 2*DCH setup time.
It should be appreciated that UE that is in cell_PCH state, for instance, will not go to cell_DCH (i.e. establish DCH) when it has data to send. UE measures the amount of data to be transmitted in the transmission buffer in UE and reports the buffer status to the radio network controller RNC in RNS in order to assist in dynamic radio bearer control. The measurement parameters can be set by RNC. Measurement reports can be triggered using two different mechanisms, periodical and event triggered. The reporting criteria are specified in the measurement control message and may include one or more of Buffer Occupancy, Average of Buffer Occupancy, and Variance of Buffer Occupancy. UE performs measurements and transmit measurement reports according to the measurement control information. For uplink data transmission, UE reports the observed traffic volume to the network in order for the network to re-evaluate the current allocation of resources. This report contains for example the amount of data to be transmitted or the buffer status in UE. The traffic volume or the buffer status depends on the activity of higher-layer functions in UE. For example, in the PoC service, the operation of a speech codec in UE may be such that when a voice activity detector (VAD) indicates silence (and/or the user does not press the tangent), the speech codec does not provide any data to the access network (e.g. to the RLC buffer) in UE, not even silence indicator frames, which are generated during a conventional voice connection supporting discontinuous transmission (DTX).
When the UE user wants to say something to the other member(s) in the PoC call, s/he presses the tangent in UE. The tangent button activates the speech codec regardless of the voice activity and the speech codec starts to generate data into the RLC buffer in UE. When UE is in a common channel state (e.g. CELL_FACH), it reports the event to RNC, which activates the transition to CELL_DCH state.
RNC allocates the required capacity (including DCH), detects a need to change the RLC parameters, carries out a radio link setup procedure with a base station BS, and commands UE to CELL_DCH state.
Similarly, RNC may detect a capacity need in the downlink direction (e.g. based on traffic volume measurements, the downlink buffer status) and activate the transition to CELL_DCH state.
The amount of data sent by UE needs to be large enough (128 bytes by default) and, therefore, signaling messages sent during the start-to- talk procedure may not be big enough to trigger DCH. These messages may instead be sent over RACH and FACH. The amount of data needed to trigger DCH is configurable but again optimal values can not be selected according to one service only in the radio access network RNS.
Thus, according to another aspect of the present invention, a media communications server (e.g. the PoC server), and possibly sending UE, is forced to send enough data so that the set-up of DCH is triggered during the start-to-talk procedure. This dummy data is preferably sent immediately after sending the actual signaling message relating to the initiated start-to-talk procedure. As noted above, signaling in the PoC environment comprises Session Initiation Protocol (SIP) messages and Real-time Transport Control Protocol (RTCP) messages. Messages typically related to the start-to-speak situation include SIP REFER Request, SIP INVITE Request, RTCP Floor Request, and RTCP Floor Taken message.
Compressed SIP signaling messages are slightly over 200 bytes in size whereas RTCP Floor Granted/Taken/Request messages are less than 100 bytes. In an embodiment of the invention, the amount of dummy data sent immediately after sending the signaling message (e.g. SIP REFER or RTCP FLOOR REQUEST or RTCP FLOOR TAKEN) is such that the total amount of data (signaling message+dummy data) is large enough to trigger DCH for the sending UE and/or the receiving UE(s). As a consequence, the amount of dummy data can be quite small: tens of bytes in case of a sent SIP message and around 150 bytes in case of an RTCP message. The aim of the invention is thus achieved with the minimum sent overhead data, and the capacity of the system is not wasted due to the invention.
Let us assume that the user equipment UE2 is initially in CELL_FACH state or CELL_PCH state. When the user of UE2 wants to say something to the other member(s) in the PoC session, s/he presses the pressel PTT 306 in UE. The PoC application 301 in the controller 305 detects that the pressel PTT is pressed (step 81 in
In an alternative embodiment of the invention, UE first waits (after the step 83 in
In still another embodiment, the sending UE2 does not send any dummy data. In such a case, the reduction of the delay will be achieved by the operation of the PoC server towards the receiving side, as will be explained below.
Upon receiving the initial start-to-speak message (such as the SIP TRANSFER) from and having sent the response (such as the RTCP Floor Granted) to UE2 (steps 91 and 92 in
The inventive operation of the PoC server for the receiving side may be applied alone or in combination with any of the above operations of the sending UE. It should be noted that although the sending UE would not send any dummy data to trigger the DCH setup, the server would still decrease speech round trip time delay by sending to the receiving UE a dummy message immediately after sending the RTCP FLOOR TAKEN message. This server-only solution may in fact be advantageous because it would allow to keep the start-to-speak time under 1 second (DCH establishment delay not counted) whereas the Speech round trip time would decrease significantly.
Alternatively, as in one of the embodiments described above, UE3 may send the actual message, e.g. RTCP Floor Granted message, first and the dummy data later. Still further, UE3 may send only the actual message, for example RTCP Floor Granted message.
Upon receiving the initial message (such as the RTCP Floor Request) from and having sent the response (such as the RTCP Floor Granted) to UE3, the PoC server will send an appropriate signaling message (such as the RTCP Floor Taken) to UE2. In an embodiment of the invention, the PoC server also sends dummy data with or immediately after the actual signaling message. The amount of data is such that it alone or together with the signaling message exceeds the DCH setup threshold in the serving RNS5 of UE2. As a consequence, a downlink DCH is setup for UE2 and the signaling message and the dummy data are sent to UE2 over the established DCH. Since DCH is now ready, the subsequent RTP voice stream from UE3 can be sent to UE2 without the DCH setup delay.
In all embodiments relating to the second aspect of the invention, the PoC server may selectively send dummy data only to the UEs which are located in appropriate access networks (such as WCDMA), as discussed above relating to the first aspect of the invention.
In all embodiments of the invention, the serving access networks of the sending UE and the receiving UE(s) may be the same one or different ones.
It should be appreciated that all the above operation beyond sending the dummy data for triggering the DCH setup or resetting inactivity timer may basically be implemented in accordance with the 3GPP specifications and existing PoC functionality.
Various embodiments of the invention have been described, but it will be appreciated by persons skilled in the art that these embodiments are merely illustrative and that many other embodiments are possible. The intended scope of the invention is set forth in the following claims, rather than the preceding description, and all variations that fall within the scope and spirit of the claims are intended to be embraced therein.
Number | Date | Country | Kind |
---|---|---|---|
20031912 | Dec 2003 | FI | national |
Number | Date | Country | |
---|---|---|---|
Parent | 10827535 | Apr 2004 | US |
Child | 12489072 | US |