Exchanging a compressed version of previously communicated session information in a communications system

An embodiment of the present invention relates to exchanging compressed versions of previously communicated session information in a communication system.

Wireless communication systems include 1st generation analog wireless telephone services (1G), 2nd generation (2G) digital wireless telephone services (including interim 2.5G and 2.75G networks), and 3rd generation (3G) high-speed data / internet. It has evolved through various generations, including compatible wireless services. Currently, many different types of wireless communication systems are used, including cellular systems and personal communication services (PCS) systems. Examples of known cellular systems are the Cellular Analog Advanced Mobile Phone System (AMPS), Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), and TDMA Global. There are digital cellular systems based on the System for Mobile access (GSM®) variant, and newer hybrid digital communication systems that use both TDMA and CDMA technologies.

The method for providing CDMA mobile communication is referred to herein as IS-95, TIA / EIA / IS-95-A entitled "Mobile Station-Base Station Compatibility Standard for Dual-Mode Wideband Spread Spectrum Cellular System". Was standardized in the United States by the American Telecommunications Industry Association / American Electronic Industries Alliance. Composite AMPS & CDMA systems are described in TIA / EIA standard IS-98. Other communication systems target what is called Broadband CDMA (W-CDMA), CDMA2000 (eg CDMA2000 1xEV-DO standard) or TD-SCDMA, IMT-2000 / UM, or International Mobile Telecommunications System 2000 / Universal. It is described in the Mobile Telecommunications System standard.

In a W-CDMA wireless communication system, a user device (UE) is a fixed-position Node B (cell site or cell) that supports a communication link or service within a specific geographic area adjacent to or surrounding the base station. Also called) to receive a signal. Node B is an access network (AN), which is a packet data network that uses standard Internet Engineering Task Force (IETF) -based protocols that generally support methods for distinguishing traffic based on quality of service (QoS) requirements. ) / Provide an entry point to the Radio Access Network (RAN). Therefore, Node B generally interacts with the UE over the air interface and with the RAN over the Internet Protocol (IP) network data packets.

In wireless communication systems, push-to-talk (PTT) capabilities are widespread in the service sector and consumers. PTT can support "dispatch" voice services running on standard commercial wireless infrastructure, such as W-CDMA, CDMA, FDMA, TDMA, and GSM®. In the dispatch model, communication between endpoints (eg, UEs) takes place within a virtual group, where the voice of one "speaker" is sent to one or more "listeners." A single instance of this type of communication is commonly referred to as a dispatch call, or simply a PTT call. A PTT call is an instantiation of a group that defines the characteristics of the call. A group is essentially defined by a member list and related information, such as a group name or group identification information.

Communication between mobile users often results in connection failures between devices when one or more devices become inaccessible to each other due to attenuation or other offline reasons. The user must retry the communication or allow the store-and-forward system to collect and capture the content.

<p num="0007"> Therefore, it is necessary to efficiently capture messages that could not be acquired by the mobile guaranteed delivery system by a method of efficiently notifying and matching newly added users to the group communication of current and past activities.</p>

<p num="0008"> In one embodiment, the server exchanges session data between a group of session participants (participants) during a communication session, and the exchanged session data includes session media and / or session signaling information. The server stores at least a subset of the exchanged session data. The server later establishes a connection with a given user device (UE) (eg, either after or during a communication session). The server determines a UE definition context that indicates how to compress session data that could not be obtained from a communication session so that it can be delivered to a given UE. The server selectively compresses at least a portion of the stored subset of exchanged session data that a given UE could not obtain based on the UE definition context, and the stored subset of the exchanged session data. Sends the selectively compressed portion to a given UE.</p><p num="0009"> A more complete understanding of the embodiments of the present invention and many of its concomitant benefits will be discussed with reference to the detailed description below and with the accompanying drawings presented merely to illustrate the invention, not to limit it. The better it is understood, the easier it will be.</p>

<figref num="1">FIG. 5 is a diagram of a wireless network architecture that supports an access terminal and an access network according to at least one embodiment of the present invention.</figref><figref num="2A">It is a figure which shows the core network of FIG. 1 by an embodiment of this invention.</figref><figref num="2B">It is a figure which shows the core network of FIG. 1 by another embodiment of this invention.</figref><figref num="2C">It is a figure which shows a certain example of the wireless communication system of FIG. 1 in more detail.</figref><figref num="3">It is a figure which shows the user equipment (UE) by at least one embodiment of this invention.</figref><figref num="4">It is a figure which shows the example of the conventional storage transfer process.</figref><figref num="5A">FIG. 5 illustrates a process of selectively compressing session data that a given UE cannot obtain when the given UE is detached from the communication session and the communication session is still active, according to an embodiment of the present invention.</figref><figref num="5B">FIG. 5 shows a process of selectively compressing session data according to an embodiment of the present invention, in which a given UE is detached from a communication session and cannot be acquired by the given UE after the communication session ends.</figref><figref num="6A">It is a figure which shows the process of selectively compressing the session data which a given UE cannot acquire after a given UE joins a communication session later by one Embodiment of this invention.</figref><figref num="6B">FIG. 5 is a diagram illustrating a process of selectively compressing session data that cannot be acquired by a given UE who has never actually been a participant in a communication session according to an embodiment of the present invention.</figref><figref num="6C">It is a figure which shows the process of selectively compressing session data for a given UE who participates in a communication session from an early stage according to one Embodiment of this invention.</figref><figref num="7A">It is a figure which shows the example which supplies the UE definition context used for selectively compressing session data to the application server by one Embodiment of this invention.</figref><figref num="7B">FIG. 5 is a diagram illustrating an example of supplying a UE definition context used to selectively compress session data to an application server according to another embodiment of the present invention.</figref><figref num="8A">It is a figure which shows the example of selectively compressing session data based on a UE definition context by one Embodiment of this invention.</figref><figref num="8B">It is a figure which shows the example of selectively compressing session data based on a UE definition context by one Embodiment of this invention.</figref><figref num="9">It is a figure which shows the communication device which contains the logic configured to perform a function by embodiment of this invention.</figref>

The following description and related drawings for a particular embodiment of the invention disclose aspects of the invention. Alternative embodiments can be devised without departing from the scope of the invention. Moreover, well-known elements of the invention are not described or omitted in detail so as not to obscure the relevant details of the invention.

The terms "exemplary" and / or "example" are used herein to mean "act as an example, case, or example." Any embodiment described herein as "exemplary" and / or "example" should not necessarily be construed as preferred or advantageous over other embodiments. Similarly, the term "embodiment of the invention" does not require that all embodiments of the invention include the features, advantages or modes of operation discussed.

In addition, many embodiments describe a set of actions that should be performed, for example, by elements of a computing device. The various operations described herein are performed by a particular circuit (eg, an application specific integrated circuit (ASIC)), by program instructions executed by one or more processors, or by a combination of both. You will be recognized to get. In addition, these series of operations described herein, at run time, store a corresponding set of computer instructions that cause the associated processor to perform the functions described herein, in any form of computer. It can be considered to be embodied as a whole within a readable storage medium. Thus, various aspects of the invention can be embodied in several different forms that are all intended to fall within the scope of the claimed subject matter. Further, for each embodiment described herein, the corresponding form of any such embodiment is described herein as, for example, as "logic configured to" perform the actions described. May be described.

A High Data Rate (HDR) subscriber station, referred to herein as a user device (UE), may be mobile or fixed, communicating with one or more access points (APs), which may be referred to as Node B. Can be done. The UE sends and receives data packets to and from the Wireless Network Controller (RNC) via one or more of Node B. Node B and RNC are part of a network called a radio access network (RAN). Radio access networks can carry voice and data packets between multiple access terminals.

Wireless access networks may be further connected to additional networks outside the wireless access network, such core networks as specific carrier-related servers and devices, as well as corporate intranets, the Internet, and public exchange telephone networks. Includes connections to other networks such as (PSTN), Serving General Packet Radio Service (GPRS) Support Node (SGSN), Gateway GPRS Support Node (GGSN), between each UE and such a network. It can carry voice and data packets. A UE that has established an active traffic channel connection with one or more Node Bs is sometimes referred to as the active UE and is sometimes referred to as the traffic state. One or more Nodes UEs in the process of establishing an active traffic channel (TCH) connection with B are sometimes referred to as the connection setup state. The UE can be any data device that communicates over a wireless or wired channel. The UE can also be any of several types of devices, including, but not limited to, PC Cards, CompactFlash® devices, external or internal modems, or wireless or wired phones. .. Communication links that the UE sends signals to Node B are called uplink channels (eg, reverse traffic channels, control channels, access channels, and so on). The communication links that Node B sends signals to the UE are called downlink channels (eg, paging channels, control channels, broadcast channels, forward traffic channels, etc.). The term traffic channel (TCH), as used herein, may refer to either an uplink / reverse traffic channel or a downlink / forward traffic channel.

FIG. 1 shows a block diagram of one exemplary embodiment of the wireless communication system 100 according to at least one embodiment of the present invention. System 100 is an access network that can connect UE102 to network equipment that provides data connectivity between packet-switched data networks (eg, intranet, Internet, and / or core network 126) and UE102, 108, 110, 112. Alternatively, it may include a wireless access network (RAN) 120 and a UE such as a mobile phone 102 communicating via the air interface 104. As shown herein, a UE is a mobile phone 102, a personal digital assistant 108, a pager 110 referred to herein as a bidirectional text pager, and a separate computer platform 112 with a wireless communication portal. Good. Accordingly, embodiments of the present invention include or have wireless communication capabilities, including, but not limited to, wireless modems, PCMCIA cards, personal computers, telephones, or any or partial combinations thereof. It can be realized on any form of UE. In addition, as used herein, the term "UE" in other communication protocols (ie other than W-CDMA) is compatible with "access terminal," "AT," "wireless device," and "client device." , "Mobile terminals," "mobile stations," and variants thereof.

With reference to FIG. 1 again, the interrelationships between the components of the wireless communication system 100 and the elements of the exemplary embodiments of the present invention are not limited to the configurations shown. System 100 is merely an example in which remote UEs such as wireless client computing devices 102, 108, 110, 112 communicate wirelessly between UEs and / or, but not limited to, the core network 126, the Internet, It may include any system that allows communication between components connected via air interface 104 and RAN120, including PSTN, SGSN, GGSN, and / or other remote servers.

The RAN120 controls the messages sent to the RNC122 (typically sent as data packets). RNC122 is Serving General Packet Radio Services (GPRS) Support Responsible for signaling, establishing, and disconnecting bearer channels (ie, data channels) between Node (SGSN) and UE 102/108/110/112. Also, if link-layer encryption is possible, the RNC122 encrypts the content before transferring it over the air interface 104. The functionality of the RNC122 is well known in the art and will not be discussed further for the sake of brevity. The core network 126 can communicate with the RNC122 via the network, the Internet, and / or the public switched telephone network (PSTN). Alternatively, the RNC122 can connect directly to the Internet or an external network. Generally, the network or internet connection between the core network 126 and the RNC122 transfers data, and the PSTN transfers voice information. The RNC122 can be connected to multiple Node B124s. In a manner similar to core network 126, RNC122 is typically Node by network, internet, and / or PSTN for data transfer and / or voice information. Connected to B124. Node B124 can wirelessly broadcast data messages to UEs like mobile phones 102. As is known in the art, Node B124, RNC122, and other components can form RAN120. However, alternative configurations may be used and the invention is not limited to the shown configurations. For example, in another embodiment, one or more of the functions of RNC122, and Node B124 may be contained in a single "hybrid" module that has both RNC122 and Node B124 functionality.

FIG. 2A shows a core network 126 according to an embodiment of the present invention. In particular, Figure 2A shows the components of the General Packet Radio Services (GPRS) core network implemented within a W-CDMA system. In the embodiment of FIG. 2A, the core network 126 includes a Serving GPRS Support Node (SGSN) 160, a Gateway GPRS Support Node (GGSN) 165, and the Internet 175. However, it should be appreciated that in alternative embodiments, parts of the Internet 175 and / or other components may be located outside the core network.

In general, GPRS is a protocol used by Global System for Mobile communications (GSM®) telephones to send Internet Protocol (IP) packets. The GPRS core network (eg, GGSN165 and one or more SGSN160s) is a central part of the GPRS system and also provides support for W-CDMA based 3G networks. The GPRS core network is an integrated part of the GSM® core network that provides mobility management, session management, and transport for IP packet services in GSM® and W-CDMA networks.

GPRS Tunneling Protocol (GTP) is an IP protocol that characterizes the GPRS core network. GTP allows GSM® or W-CDMA network end users (eg, UEs) to move around in the GGSN165 as if they were connected to the Internet from one location. It is a protocol. This is achieved by transferring the subscriber's data from the subscriber's current SGSN160 to the GGSN165, which is processing the subscriber's session.

Three forms of GTP, namely (i) GTP-U, (ii) GTP-C, and (iii) GTP'(GTP Prime) are used by the GPRS core network. GTP-U is used to transfer user data in tunnels separated by Packet Data Protocol (PDP) context. GTP-C is used for control signaling (for example, setting up and deleting PDP contexts, verifying GSN reachability, updating or changing such as when a subscriber moves from one SGSN to another). GTP'is used for the transfer of billing data from GSN to the billing function.

Referring to FIG. 2A, the GGSN165 acts as an interface between the GPRS backbone network (not shown) and the external packet data network 175. The GGSN165 extracts packet data in the associated Packet Data Protocol (PDP) format (eg, IP or PPP) from GPRS packets coming from the SGSN160 and sends the packets over the corresponding packet data network. In the opposite direction, incoming data packets are directed by the GGSN165 to the SGSN160, which manages and controls the radio access bearer (RAB) of the destination UE serviced by the RAN120. Thereby, the GGSN165 stores the current SGSN address of the target UE and its user's profile in its location register (eg, in the PDP context). The GGSN is responsible for IP address allocation and is the default router for connected UEs. The GGSN also performs authentication and billing functions.

In one example, the SGSN160 is representative of one of the many SGSNs in the core network 126. Each SGSN is responsible for delivering data packets to and from the UE within the relevant geographic service area. Tasks on the SGSN160 include packet routing and forwarding, mobility management (eg connection / disconnection and location management), logical link management, and authentication and billing capabilities. The SGSN location registers provide location information (eg, current cell, current VLR), and user profiles of all GPRS users registered with SGSN160 (eg, IMSI, PDP address used in the packet data network). Store in one or more PDP contexts, for example per user or UE. Therefore, the SGSN is (i) reverse tunneling of downlink GTP packets from the GGSN165, (ii) uplink tunneling of IP packets to the GGSN165, and (iii) mobility management as the UE travels between SGSN service areas. Execution, (iv) Responsible for mobile subscriber payment claims. As will be appreciated by those skilled in the art, in addition to (i) to (iv), SGSNs configured for GSM® / EDGE networks are compared to SGSNs configured for W-CDMA networks. And has slightly different functions.

RAN120 (or UTRAN in the Universal Mobile Telecommunications System (UMTS) system architecture) is a Radio Access Network Application. Communicate with SGSN160 via Part (RANAP) protocol. RANAP operates through transmission protocols such as Frame Relay or IP through the Iu interface (Iu-ps). The SGSN160 is an IP-based interface between the SGSN160 and other SGSNs (not shown) and the internal GGSN and uses the GTP protocols defined above (eg GTP-U, GTP-C, GTP', etc.). Communicate with the GGSN165 via the Gn interface used. In the embodiment of FIG. 2A, Gn between SGSN160 and GGSN165 carries both GTP-C and GTP-U. Although not shown in Figure 2A, the Gn interface is also used by the Domain Name System (DNS). The GGSN165 is connected to the Public Data Network (PDN) (not shown) and then to the Internet 175 either directly via the IP protocol Gi interface or through a Wireless Application Protocol (WAP) gateway.

FIG. 2B shows a core network 126 according to another embodiment of the present invention. FIG. 2B is similar to FIG. 2A, except that FIG. 2B shows an implementation of the direct tunnel function.

Direct tunnel is an optional feature in Iu mode that allows SGSN160 to establish a direct user plane tunnel, GTP-U, between RAN and GGSN in a packet switching (PS) domain. A direct tunnel capable SGSN, such as the SGSN160 in Figure 2B, can be configured in GGSN and RNC units regardless of whether the SGSN can use a direct user plane connection. The SGSN160 in Figure 2B handles control plane signaling and determines when a direct tunnel should be established. When the radio bearer (RAB) assigned to the PDP context is released (ie, the PDP context is preserved), a GTP-U tunnel between the GGSN165 and SGSN160 to allow processing of downlink packets. Is established.

An optional direct tunnel between SGSN160 and GGSN165 is usually (i) in the case of roaming (for example, because SGSN needs to know if GGSN is in the same PLMN or different PLMN), ( ii) The SGSN has received the Customized Applications for Mobile Enhanced Logic (CAMEL) subscription information in the subscriber profile from the home location register (HLR) and / or (iii) the GGSN165 does not support GTP protocol version 1. Is not allowed. With respect to CAMEL constraints, volume reporting from SGSN160 is not possible because SGSN160 can no longer see the user plane if a direct tunnel is established. Therefore, the use of direct tunnels is prohibited for subscribers with a profile that contains CAMEL subscription information, as the CAMEL server can call volume reports at any time during the lifetime of the PDP context.

The SGSN160 can be operating in a Packet Mobility Management (PMM) disconnected state, a PMM idle state, or a PMM connected state. In one example, the GTP connection shown in Figure 2B can be established for the direct tunnel function, which puts the SGSN160 in the PMM connection state and receives an Iu connection establishment request from the UE. The SGSN160 ensures that the new Iu connection and the existing Iu connection are for the same UE, and if they are for the same UE, the SGSN160 handles the new request and the existing Iu connection and its associated Release all RABs. To ensure that new Iu connections and existing connections are for the same UE, the SGSN160 can perform security functions. In the case where the Iu connection establishment request is for signaling only, the SGSN160 will update PDP Context if a direct tunnel is established for the UE. Send a Request to the associated GGSN165 to establish a GTP tunnel between SGSN160 and GGSN165. In the case where the Iu connection establishment request is for data transfer, SGSN160 immediately establishes a new direct tunnel, sends an Update PDP Context Request to the associated GGSN165, and downs the RNC address for the user plane and data. Can include a link Tunnel Endpoint Identifier (TEID).

When the UE has received the RRC connection release message, as soon as the UE enters the PMM idle state, the cause is "Instructed signaling connection reestablishment", even if the routing area has not changed since the last update. The routing area update (RAU) procedure is also performed. In one example, when the RNC is unable to contact the serving RNC to verify the UE due to a lack of Iur connections, the RNC issues an RRC Connection Release message due to "instructed signaling connection reestablishment". Send (see, for example, TS25.331 [52]). When the UE is pending sending user data, the UE reestablishes the wireless access bearer by performing subsequent service request procedures after the successful completion of the RAU procedure.

A PDP context is a data structure that exists on both SGSN160 and GGSN165, including communication session information for a particular UE when the UE has an active GPRS session. When the UE wants to start a GPRS communication session, it must first connect to SGSN160 and then activate the PDP context with GGSN165. This allocates the PDP context data structure on the SGSN160 that the subscriber is currently visiting and the GGSN165 that is servicing the UE access point.

FIG. 2C shows in more detail an example of the wireless communication system 100 of FIG. Specifically, referring to Figure 2C, UE1 ... N are shown as connecting to RAN120 at locations serviced by endpoints in different packet data networks. The example in Figure 2C is specific to W-CDMA systems and terminology, but it should be understood how Figure 2C can be modified to fit a 1xEV-DO system. Therefore, UE1 and UE3 go to RAN120 where they are serviced by the first packet data network endpoint 162 (which may correspond to, for example, SGSN, GGSN, PDSN, home agent (HA), external agent (FA), etc.). Connecting. The first packet data network endpoint 162 then goes through the routing unit 188 to the Internet 175 and / or the Authentication, Authorization and Accounting (AAA) Server 182, Provisioning Server 184, Internet Protocol (IP) Multimedia. Connect to one or more of the Subsystem (IMS) / Session Initiation Protocol (SIP) registration server 186 and / or the application server 170. UE2 and UE5 ... N connects to RAN120 at the portion serviced by the second packet data network endpoint 164 (which may correspond to, for example, SGSN, GGSN, PDSN, FA, HA, etc.). Similar to the first packet data network endpoint 162, the second packet data network endpoint 164 then goes through the routing unit 188 to the Internet 175 and / or AAA server 182, provisioning server 184, IMS /. Connect to one or more of the SIP registration server 186 and / or the application server 170. UE4 can connect directly to Internet 175 and then through Internet 175 to any of the above system components.

Referring to FIG. 2C, UE1, UE3, and UE5 ... N are shown as wireless mobile phones, UE2 is shown as a wireless tablet PC, and UE4 is shown as a wired desktop station. However, in other embodiments, the wireless communication system 100 can be connected to any type of UE, and the example shown in FIG. 2C does not limit the types of UEs that can be implemented in the system. I want to be understood. Also, AAA182, provisioning server 184, IMS / SIP registration server 186, and application server 170 are each structurally shown as separate servers, but in at least one embodiment of the invention, of these servers. One or more of them may be integrated.

Further, referring to FIG. 2C, the application server 170 is shown as containing 170B of multiple media control complexes (MCC) 1 ... N and 170A of multiple regional dispatchers 1 ... N. .. Collectively, the regional dispatchers 170A and MCC170B, in at least one embodiment, have communication sessions within the wireless communication system 100 (eg, half-duplex group communication sessions over IP unicast and / or IP multicast protocols). Included within application server 170, which can accommodate a distributed network of servers that collectively function to arbitrate. For example, communication sessions arbitrated by application server 170 can theoretically occur between UEs located somewhere in system 100, so reduce the latency of arbitrated communication sessions (for example, in North America). Multiple regional dispatchers 170A and MCCs are distributed (so that the MCC does not relay media to people among session participants located in China). Therefore, with reference to Application Server 170, it should be understood that the relevant functionality may be performed by one or more of the regional dispatchers 170A and / or one or more of the MCC170B. The regional dispatcher 170A is generally responsible for any function related to establishing a communication session (eg, processing signaling messages between UEs, scheduling and / or sending announcement messages, etc.), and the MCC170B is in a call. Responsible for hosting communication sessions between call instances, including the actual exchange of media during signaling and arbitrated communication sessions.

Referring to FIG. 3, a UE 200 (here a wireless device), for example a mobile phone, has a platform 202, which originates from the RAN 120 and eventually the core network 126, the Internet, and / or other. Can receive and execute software applications, data, and / or commands that may come from remote servers and networks. The platform 202 may include an application specific integrated circuit (ASIC) 208 or a transmitter / receiver 206 operably coupled to another processor, microprocessor, logic circuit, or other data processing device. The ASIC208 or other processor performs an application programming interface (API) 210 layer that interfaces with any resident program in the wireless device's memory 212. The memory 212 may consist of read-only memory or random access memory (RAM and ROM), EEPROM, flash card, or any memory common to computer platforms. Platform 202 may also include a local database 214 that can hold applications that are not actively used in memory 212. The local database 214 is generally a flash memory cell, but may be any secondary storage device known in the art, such as magnetic media, EEPROM, optical media, tape, software or hard disks. The components of the internal platform 202 are also operably coupled to external devices such as antenna 222, display 224, push-to-talk button 228 and keypad 226, among other components, as is known in the art. obtain.

Accordingly, certain embodiments of the present invention may include UEs that include the ability to perform the functions described herein. As those skilled in the art will appreciate, various logical elements are individual elements, software modules running on a processor, or any software and hardware to achieve the functionality disclosed herein. It can be embodied in combination. For example, ASIC208, memory 212, API210, and local database 214 can all be used collaboratively to load, store, and perform the various functions disclosed herein, thus providing these functions. The logic to execute can be distributed across various elements. Alternatively, the functionality can be integrated into one individual component. Therefore, the features of UE200 in FIG. 3 are considered merely exemplary and the invention is not limited to the features or configurations shown.

Wireless communication between UE102 or UE200 and RAN120 is, for example, Code Division Multiple Access (CDMA), W-CDMA, Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDM), It can be based on a variety of technologies, such as Global System for Mobile Communications (GSM®), or other protocols that can be used in wireless or data communication networks. For example, in W-CDMA, data communication generally involves client device 102, Node. It takes place between B124 and RNC122. The RNC122 can connect to multiple data networks such as core network 126, PSTN, internet, virtual private network, SGSN, GGSN, etc., so the UE102 or UE200 can access a wider communication network. .. As described above and known in the art, voice transmission and / or data can be transmitted from the RAN to the UE using a variety of networks and configurations. Therefore, the examples provided herein are not intended to limit embodiments of the invention, but merely to aid in the description of embodiments of the invention.

Storage transfer is a communication protocol in which data exchanged between session participants during a communication session is monitored and stored by a server such as application server 170. The server, in one embodiment, mediates the exchange of session data for a communication session. In another embodiment, the server does not have to be directly associated with the mediation and / or arbitration function of the communication session, it only needs to transfer the session data to the UE.

In another embodiment, the server is detached from the communication session so that it can later deliver the stored session data to the requesting UE for a UE that fails to receive at least part of the session data. Can be imported into. For example, session participants are disconnected from the communication session for any number of reasons, including limited wireless radio range (for example, session participants being allowed to use tunnels), noise, signal attenuation conditions, and so on. In some cases.

An example of a conventional storage forwarding implementation may target an email delivery procedure for which a given email target is not available to receive this given email. In this case, the email server stores a given email for later delivery, which is delivered via one or more periodic attempts to resend this given email to the target. It may be done at the request of the target (for example, when the target logs on to the mail server to check the e-mail that could not be obtained). Therefore, at a high level, storage transfer protocols generally store media in network entities for later delivery to target devices when media cannot be delivered in real time.

FIG. 4 shows an example of a conventional storage transfer process. Referring to FIG. 4, the application server 170 has a communication session (for example, N = 2 for a direct communication session or a one-to-one communication session and N&gt; 2 for a group communication session) between UE1 and UEN (for example, N&gt; 2). , Establish a half-duplex communication session such as PTT, a full-duplex communication session such as VolP) (400). Therefore, the application server 170 initiates arbitration of the communication session between UE1 and UEN by exchanging media during the communication session (405). During a communication session mediated by the application server 170, the application server 170 may use session data such as session media (eg, audio, video, text, etc.) and / or signaling information (eg, which UE is the floor holder at various times). It stores information that indicates that it is, information about which UE is participating in the communication session at various times, etc.) (410).

Referring to FIG. 4, it is assumed that UE1 is disconnected from the communication session (415) at some point during the communication session. For example, at 415, the user of UE1 may have decided to end the user joining the communication session, or UE1 may have lost connectivity with RAN120. However, despite UE1 being disconnected from the communication session at 415, UE2 ~ UEN continue to exchange media during the communication session (420). Therefore, it should be understood that UE1 cannot acquire the media exchanged between UE2 and UEN after being disconnected and no longer participating in the communication session.

UE1 reestablishes a connection with application server 170 at some point thereafter (for example, while the communication session is ongoing or after the communication session is completely terminated) (425). In response to the reconnection of 425, the application server 170 takes in the session data stored in 410 and transfers all session data that UE1 could not obtain after disconnecting 415 to UE1 (430).

As will be appreciated by those skilled in the art, servers running traditional storage transfer protocols generally transfer all session data that a particular UE cannot obtain for a communication session. However, users of a particular UE are only interested in some of the session data that could not be obtained (for example, non-video audio, session data obtained from a subset of other UEs other than UEs participating in the session). May not be there. Traditional storage and transfer protocols automatically discard or overwrite certain data when it becomes irrelevant (for example, by age or because the data is no longer accurate), but UE-defined criteria or It does not compress stored session data that a given UE could not obtain based on UE-specific criteria. Accordingly, embodiments of the present invention relate to selectively compressing session data that is specific to a given UE and / or could not be obtained by a given UE according to the context defined by the given UE. ..

FIG. 5A shows a process of selectively compressing session data that cannot be acquired by a given UE after the given UE (UE1) has been disconnected from the communication session, according to an embodiment of the invention. In particular, Figure 5A shows that a given UE rejoins the communication session while the communication session is still ongoing after being detached, and is selected as the given UE resumes joining the communication session. An example is shown in which session data that cannot be acquired is sent to a given UE.

2) Establish a communication session between (500A). Therefore, the application server 170 initiates arbitration of the communication session between UE1 and UEN by exchanging media during the communication session (505A). During a communication session mediated by the application server 170, the application server 170 exchanges session data such as session media (eg, audio, video, text, etc.) and / or signaling information (eg, which UE at various times). It stores information about who is the floor holder, information about which UEs are participating in the communication session at various times, etc.) (510A). Suppose UE1 disconnects from the communication session (515A) at some point during the communication session (for example, UE1 may have lost connectivity with RAN120). However, despite UE1 being detached from the communication session at 515A, UE2 ~ UEN continue to exchange session data during the communication session (520A). Therefore, it should be understood that UE1 cannot acquire session data exchanged between UE2 and UEN after being disconnected and no longer participating in a communication session. UE1 reestablishes a connection with application server 170 at some point after the communication session continues (525A). In response to the reconnection of 525A, the application server 170 takes in the session data stored in 510A and determines how much session data could not be obtained since UE1 was disconnected in 515A. Unlike Figure 4, where application server 170 simply transfers all of the session data that could not be retrieved to UE1, application server 170 then selects the stored session data that UE1 could not retrieve according to the UE definition context of UE1. Compress (530A). UE definition context Examples and various ways in which stored session data can be compressed are described in detail below. In general, the UE definition context may correspond to the context of UE1 or the user of UE1 (eg, a set of preferences, operating states, locations, etc.). For example, determining which application is running on UE1 can contribute to the UE definition context of UE1. Alternatively, the user may indicate that he is not interested in video content that can form part of the UE definition context of UE1 or content obtained from a particular UE. The application server 170 selectively compresses the session data at 530A and then transfers the compressed session data to UE1 (535A). After receiving the data transferred in the 535A, the UE1 presents the compressed session data and resumes UE1's participation in the active communication session by UE2 ~ UEN (540A). For example, the compressed session data may be presented as voice text conversion data exchanged between UE2 and UEN while UE1 was not present in the communication session, so UE1 may allow the user to perform text conversion data. By considering, it may be possible to "catch up" with other session participants and resume the communication session. Other examples of session data compression will be described in more detail below. The session server 170 selectively compresses the session data at 530A and then transfers the compressed session data to UE1 (535A). After receiving the data transferred in the 535A, the UE1 presents the compressed session data and resumes UE1's participation in the active communication session by UE2 ~ UEN (540A). For example, the compressed session data may be presented as voice text conversion data exchanged between UE2 and UEN while UE1 was not present in the communication session, so UE1 may allow the user to perform text conversion data. By considering, it may be possible to "catch up" with other session participants and resume the communication session. Other examples of session data compression will be described in more detail below. The session server 170 selectively compresses the session data at 530A and then transfers the compressed session data to UE1 (535A). After receiving the data transferred in 535A, UE1 presents the compressed session data and resumes UE1's participation in the active communication session by UE2 ~ UEN (540A). For example, the compressed session data may be presented as voice text conversion data exchanged between UE2 and UEN while UE1 was not present in the communication session, so UE1 may allow the user to perform text conversion data. By considering, it may be possible to "catch up" with other session participants and resume the communication session. Other examples of session data compression will be described in more detail below.

Figure 5A relates to application server 170 resuming UE1's participation in an still active communication session and provisioning UE1 with a selectively compressed version of session data that could not be obtained. On the other hand, FIG. 5B is intended for application server 170 to provision UE1 with a selectively compressed version of session data that could not be obtained after the communication session ended.

FIG. 5B shows a process of selectively compressing session data that a given UE cannot obtain after a given UE (UE1) has been disconnected from the communication session, according to an embodiment of the invention. In particular, in FIG. 5B, a given UE rejoins the communication session after the communication session ends, and selectively compressed unobtained session data is sent to the given UE.

Referring to Figure 5B, the application server 170 establishes a communication session between UE1 and UEN (500B). Therefore, the application server 170 initiates arbitration of the communication session between UE1 and UEN by exchanging session data during the communication session (505B). During a communication session mediated by the application server 170, the application server 170 may use session data such as session media (eg, audio, video, text, etc.) and / or signaling information (eg, which UE is the floor holder at various times). It stores information indicating that it is, information about which UE is participating in the communication session at various times, etc.) (510B). Suppose UE1 disconnects from the communication session (515B) at some point during the communication session (for example, UE1 may have lost connectivity with RAN120). However, despite UE1 being disconnected from the communication session at 515B, UE2 to UEN continue to exchange session data during the communication session (520B). Therefore, it should be understood that UE1 cannot acquire session data exchanged between UE2 and UEN after being disconnected and no longer participating in a communication session. At some point after the session ends (525B), application server 170 stops storing session data (530B). After the session ends (525B), UE1 reestablishes UE1's connection with application server 170 (535B). In response to the reconnection of the 535B, the application server 170 fetches the session data stored in the 510B and determines how much session data has not been acquired since the UE1 was disconnected in the 515B. The application server 170 is then remembered that UE1 could not get according to the UE definition context of UE1. Selectively compress the session data (540B). As pointed out above for 530A in Figure 5A, an example of a UE definition context and how session data can be selectively compressed will be described in more detail below. The application server 170 selectively compresses the session data in 540B and then transfers the compressed session data to UE1 (545B). Other examples of session data compression will be described in more detail below. After receiving the data transferred at 545B, UE1 presents session data compressed to catch up on the content of the communication session that UE1 could not join because it was disconnected (550B). As pointed out above for 540A in Figure 5A, other examples of session data compression will be described in more detail below.

Figure 5A and Figure 5B relate to the initial participant when UE1 started the session, while Figures 6A and 6B show that UE1 later joined the communication session and initially joined the session. The target is not a person.

FIG. 6A illustrates the process of selectively compressing session data that a given UE cannot obtain after a given UE (UE1) later joins a communication session, according to an embodiment of the invention. is there. In particular, Figure 6A is selectively compressed so that a given UE joins a communication session after the communication session begins and "catch up" with respect to the existing communication session, rather than the original participant. The session data that could not be acquired is sent to a given UE. In this embodiment, UE1 catches up or catches up before joining the communication session (eg, a text transcript of the communication session's live voice and selectively compressed session data that could not be obtained). You can participate in parallel with.

Referring to FIG. 6A, the application server 170 establishes a communication session between UE2 and UEN (600A). Therefore, the application server 170 initiates arbitration of the communication session between UE2 and UEN by exchanging session data during the communication session (605A). During a communication session mediated by application server 170, application server 170 stores session data such as session media and / or signaling information (610A). Suppose UE1 who was not the original participant joins the communication session (615A) at some point during the communication session. Therefore, it should be understood that UE1 cannot acquire session data exchanged between UE2 and UEN before joining a communication session. The application server 170 takes in the session data stored in the 610A in response to UE1 joining the communication session and determines how much session data could not be obtained before UE1 joined in the 615A. The application server 170 then selectively compresses the stored session data that UE1 could not obtain according to the UE definition context of UE1 (620A). As pointed out above for 530A in Figure 5A, an example of a UE definition context and how session data can be selectively compressed will be described in more detail below. The application server 170 selectively compresses the session data at 620A and then transfers the compressed session data to UE1 (625A). After receiving the data transferred at 625A, UE1 presents the user with compressed session data so that the user can catch up on the content of the communication session (630A). As pointed out above for 540A in Figure 5A, other examples of session data compression will be described in more detail below. In a further example, at 630A The presentation may be made before UE1 begins to actively participate in a real-time communication session with UE2-UEN (for example, UE1 fast-forwards session data that could not be obtained until real-time). It may play in mode or fast mode and then be actively involved in a real-time communication session). In an alternative example, the presentation at the 630A may occur at the same time as or in parallel with the UE1 starting to actively participate in the communication session (eg, the UE1 may be audio media or video for a real-time communication session). You may also present a text transcript of the session data that could not be obtained while playing live media such as media).

Figure 6A relates to acquiring session data that a UE that later joined an active communication session could not acquire in the previous communication session. On the other hand, FIG. 6B is intended for the UE to acquire unacquirable or archived session data related to an terminated communication session that was not actually a participant.

With reference to FIG. 6B, 600B to 610B correspond to 600A to 610A in FIG. 6A, and therefore 600B to 610B will not be described further for the sake of brevity. Suppose at some point after the communication session ends (615B), UE1 who was not a participant in the communication session requests some of the archived session data (620B). Requests made by UE1 on 620B are active (for example, UE1 sends a request to application server 170 for some archived session data) or implicitly (for example, UE1 is , UE2 ~ UEN may be some kind of administrator with preference settings to receive some part of the communication session with one or more of UE2 ~ UEN, for example, UE1 is controlled by the administrator and UE2 ~ UEN (Controlled by an employee of the administrator) Good. The application server 170 fetches the session data stored in the 610B in response to the request for the archived session data by UE1. The application server 170 then selectively compresses the stored session data that UE1 could not obtain according to the UE definition context of UE1 (625B). As pointed out above for 530A in Figure 5A, an example of a UE definition context and how session data can be selectively compressed will be described in more detail below. The application server 170 selectively compresses the session data at 625B and then transfers the compressed session data to UE1 (630B). After receiving the data transferred in the 630B, the UE1 presents the compressed session data obtained from the communication session requested by the UE1 (635B).

In a further example with respect to Figure 6B, UE1 is prompted to review the previous communication session after it has ended. In this case, instead of simply replaying the entire unsuccessful communication session to UE1, one or more of the UEs that actually participated in the previous communication session will have one or more "one or more" in the communication session. Specify a "catch-up point" to prompt application server 170 to compress session data for a communication session (at 625B) according to one or more catch-up points. For example, a catch-up point is the most relevant part of a communication session by the UE that participated in the communication session (for example, the most relevant part in general or the part of the communication session that is considered specifically related to UE1 in particular. ) May be used to point out or emphasize. The application server 170 may then transfer the selectively compressed session data with an emphasis on the catch-up point described above to UE1 at 630B.

In another example with respect to Figure 6B, UE1 to UEN may be part of the same communication group, but UE1 is "offline" during a communication session in this group as shown between UE2 to UEN in Figure 6B. It was. As mentioned above, one or more of the online UEs (ie, UE2 to UEN) mark the relevant location in the communication session (eg, "lead flam here" point or catch-up point) and the application server. You can be prompted to selectively compress (or synchronize) a subset of session data that could not be retrieved based on the position marked 170.

FIG. 6C shows an example in which FIG. 6B does not participate in a communication session in which UE1 has terminated, and then UE1 requests archived session data, and FIG. 6C shows that UE1 participates in a communication session and later. Similar to Figure 6B, except that it shows an example of requesting archived session data for the same communication session. Therefore, 600C and 605C are similar to 600B and 605B in FIG. 6B, respectively. However, at 600C and 605C UE1 is also a session participant. After 605C, 610C to 635C in FIG. 6C are similar to 610B to 635B in FIG. 6B, and therefore 610C to 635C will not be described further for the sake of brevity.

7A and 7B illustrate exemplary implementations of the processes 530A, 540B, 620A, 625B, and / or 625C of FIGS. 5A, 5B, 6A, 6B, and 6C, respectively, according to embodiments of the present invention. Shown. Referring to Figure 7A, before the communication session begins, UE1 preconfigures the UE definition context to be used to selectively compress session data for subsequent communication sessions in which UE1 cannot participate. Good (700A). For example, UE1 may estimate UE1's current bandwidth capacity for the application server 170 associated with the current network connection. In addition, UE1 may specify a set of user preferences as to which session data content should be included or excluded in relation to compression. After setting the UE definition context, the application server 170 performs selective compression operations based on the preset UE definition context in FIGS. 5A, 5B, 6A, 6B, and / or 6C. Perform the indicated process (705A). Compression may be based on a number of factors, including but not limited to bandwidth, past history of application servers 170 and UE1, session data types, and priority ranking of data to be pushed.

Referring to FIG. 7A, in one example, the UE definition context may include a list of UEs that UE1 is interested in and monitors. For example, UE1 may be controlled by employees who are interested in following session data originating from administrators, colleagues, and so on. Therefore, in this example, at 700A in FIG. 7A, a list of UEs may be added to the preset context of UE1. After UE1 fails to retrieve session data in any of Figures 5A-6C, application server 170 evaluates the portion of session data that could not be retrieved for UE1 and one of the session media is listed. Whether it originated from a UE and / or whether any signaling information is associated with any of the listed UEs (for example, when the listed UE joined the session or session When to exit from, when the UE shown in the list held the floor, etc.). The application server 170 compresses data on the 705A that could not be obtained by filtering session media originating from unlisted UEs and / or signaling information related to unlisted UEs. Then the rest of the session data may be sent to UE1 as selectively compressed session data.

Referring to Figure 7A, in another example, the UE definition context may include a set of one or more applications configured to run on UE1. For example, UE1 may want to retrieve session data that could not be retrieved and continue to run one or more applications (eg, a web browser). In this case, at 700A in Figure 7A, you may add a list of one or more applications to the UE1 preset context. After UE1 fails to get session data in any of Figures 5A-6C, the application server 170 evaluates the application currently running on UE1 and is one of the currently running applications. Or determine if more than one corresponds to the application listed. The application server 170 may compress the session data that could not be acquired in the 705A by modifying the session data that could not be acquired so as to match the behavior of the currently running application. For example, a web browser could be expected to consume half of the UE1's display screen, so the application server 170 could obtain the video resolution of the video portion of the session data that could not be obtained for the rest of the UE1's display screen. Session data that could not be obtained by lowering it to fit in half may be compressed.

Referring to Figure 7A, in another example, the UE definition context may contain a set of conversations on UE1. For example, UE1 may want to retrieve session data that could not be retrieved and continue to participate in one or more conversations (eg, text conversations, voice conversations, etc.). In this case, at 700A in Figure 7A, you may add a list of one or more conversations to the UE1 preset context. After UE1 fails to retrieve session data in any of Figures 5A-6C, application server 170 determines if UE1 is currently involved in one of the interactions shown in the list. Can be evaluated. The application server 170 may compress the session data that could not be acquired in the 705A by modifying the session data that could not be acquired to adapt to the current dialogue in UE1. For example, if UE1 is involved in a voice call, application server 170 compresses the session data that could not be obtained by converting the voice portion of the session data that could not be obtained into text so that it does not interfere with the voice call. You can. In another example, if UE1 is involved in a text dialogue and the session data that could not be retrieved contains text, application server 170 voices so that the text portion of the session data that could not be retrieved does not interfere with the text dialogue. Session data that could not be obtained by converting to may be compressed.

Referring to FIG. 7A, in another example, the UE definition context may include the bandwidth available in UE1. For example, UE1 may migrate between different bandwidth environments (eg WiFi, 3G, 1x, etc.) while traveling across wireless communication systems. In this case, at 700A in FIG. 7A, bandwidth information may be added to the preset context of UE1 and the bandwidth information associated with various compression preferences. After UE1 fails to retrieve session data in any of Figures 5A-6C, application server 170 evaluates UE1's current bandwidth and compares UE1's current bandwidth with UE1's compression preference. To identify a given compression protocol. The application server 170 may compress the session data that could not be acquired by modifying the session data that could not be acquired according to the identified compression protocol in the 705A. For example, when UE1 is in a low bandwidth environment, the application server 170 may compress the data that could not be obtained by separating the video portion and converting the audio portion to text. In another example, when UE1 is in an intermediate bandwidth environment, application server 170 may compress data that could not be obtained by reducing the resolution or data rate of the video portion.

Referring to FIG. 7A, in another example, a user of UE1 may access a plurality of different types of UEs, each with different device characteristics (eg, tablet computer, desktop computer, smartphone, laptop, etc.). In this example, the UE definition context may include the UE of the device type to which session data should be sent. The UE1 device type may be propagated to the application server 170 in the preset, so the application server 170 knows this device type at 700A in Figure 7A prior to compression, or as an alternative, as described in more detail below. The device type may be transmitted to the application server 170 by UE1 along with a request for session data at 700B in Figure 7B. The application server 170 may compress the session data that could not be acquired by modifying the session data that could not be acquired according to the identified device type of UE1 in the 705A. For example, if UE1 is a small Scherrer device (eg, a smartphone), the application server 170 may compress session data that could not be acquired by reducing the video resolution. In another example, when UE1 is connected to a large black and white display, the application server 170 compresses session data that could not be obtained by maintaining the video resolution but converting the video color to something like grayscale. You can.

FIG. 7B shows an example in which a UE definition context is defined in connection with a request to acquire at least a portion of session data that could not be acquired according to an embodiment of the present invention. Similar to Figure 7A.

Seeing Figure 7B, UE1 can connect to application server 170 and compress data that could not be retrieved, at least after the communication session has started (for example, during the communication session, after the communication session has ended). Request at least part of the session data that could not be retrieved while also showing the UE definition context of (700B). The application server 170 then selectively compresses the stored session data that UE1 could not obtain according to the UE definition context indicated by UE1 (705B).

Referring to FIG. 7B, in one example, the UE definition context shown in connection with a request for session data that could not be retrieved may include a list of UEs that UE1 is interested in and monitors. The application server 170 compresses the session media originating from the unlisted UE and / or the media that could not be obtained by filtering the signaling information related to the unlisted UE in the 705B. Then the rest of the session data may be sent to UE1 as selectively compressed session data.

Referring to Figure 7B, in one example, the UE definition context shown in connection with a request for session data that could not be retrieved contains a set of one or more applications configured to run on UE1. Good. For example, UE1 may indicate that it is actively involved in a web browsing session that occupies half of the display screen. In this example, application server 170 may compress the session data that could not be acquired by reducing the video resolution of the video portion of the session data that could not be acquired to fit the other half of the UE1 display screen. ..

Referring to FIG. 7B, in another example, the UE definition context shown in connection with the request for session data that could not be obtained may include a dialogue in which UE1 is actively involved. For example, if UE1 indicates that it is involved in a voice call, application server 170 could not get the session data by converting the voice part of the session data that could not be obtained into text so as not to interfere with the voice call. May be compressed. Another example shows that UE1 is involved in a text dialogue, and if the session data that could not be retrieved contains text, application server 170 does not interfere with the text portion of the session data that could not be retrieved. The session data that could not be acquired by converting to voice may be compressed.

Referring to FIG. 7B, in another example, the UE definition context shown in connection with the request for session data that could not be retrieved may include the current bandwidth in UE1. The application server 170 may compress the session data that could not be acquired in the 705A by modifying the session data that could not be acquired into a format suitable for the current bandwidth in UE1. For example, when UE1 is in a low bandwidth environment, the application server 170 may compress the data that could not be obtained by separating the video portion and converting the audio portion to text. In another example, when UE1 is in an intermediate bandwidth environment, application server 170 may compress data that could not be obtained by reducing the resolution or data rate of the video portion.

Referring to FIG. 7B, in another example, UE1 may recognize that it was unable to obtain session data related to the communication session. For example, if UE1 joins a communication session early and then loses UE1's connection, or if UE1 receives a delayed notification message for the communication session, UE1 logs on to application server 170 and the notifier communication session starts. You may be notified that it has already started or has ended. In response to such a verdict, an overview of file types that UE1 cannot get during a communication session with UE1 (eg audio files from UE2, video files, text files, files from UE located in California, UE1 You may supply files from the UE that are social networking contacts). UE1 then selects from the summary files (references to video, audio, dialogue, and / or other session data types) the specific file that UE1 wants to retrieve, and then UE-defines this file type preference. Package into context-forming requests (700B). After receiving the file request, the application server 170 transfers only the requested file to UE1 (705B). In some cases, UE1 may issue ancillary requests for other parts of the session data that could not be obtained (eg, the original video file with full resolution).

Referring to Figure 7B, in another example, another UE (not UE1) may provide the UE definition context for UE1. For example, another UE may insert a "marker" into the communication session to indicate that any UE or UE1 is interested (for example, if UE2 is aware that UE1 is interested in cave exploration). You may insert a marker in the dialogue to flag the part of the dialogue-only session on cave exploration for UE1). Therefore, when requesting session data that UE1 could not acquire, compression can be performed based in part on the above flags that form part of UE1's UE definition context.

As can be seen from the discussions in FIGS. 7A and 7B, the application server 170 selectively compresses the unobtainable portion of the session data so that it can be delivered to UE1. The method by which the unobtainable part of the session data can be compressed may be based on the UE definition context specific to UE1, which is (i) estimating the bandwidth for the UE through the new connection of the UE, or (ii) It may be based on several different factors or different algorithms, such as compression rules transmitted to the application server 170 through one or more session participants. Therefore, instead of simply transferring all the unacquirable data to UE1 as in the conventional storage transfer system, the application server 170 compresses the unacquirable data while considering the system constraints. , What kind of unobtained data to send to the UE, etc. may be more selective.

Further, in FIGS. 7A and 7B, the application server 170 may determine when to use its processing power to compress the data (eg, whether to compress the session data that UE1 could not obtain before requesting it). , Or compress session data that UE1 could not get in response to a request). Application Server 170 may create UE1-specific packages for a particular session.

Similar to FIGS. 7A and 7B, FIGS. 8A and 8B show processes 530A, 540B, 620A, 625B, and / of FIGS. 5A, 5B, 6A, 6B, and 6C, respectively, according to embodiments of the present invention. Alternatively, an exemplary implementation of the 625C is shown. However, Figures 7A and 7B focus on how the UE definition context is retrieved by the application server 170, and Figures 8A and 8B show how session data is actually compressed. Focusing.

Referring to FIG. 8A, the stored session data for a given communication session is sent by application server 170 at 800A in response to an implicit or explicit (ie, active) request for the stored session data. Loaded. After loading the stored session data, the application server 170 extracts the part of the stored session data that UE1 could not acquire (805A). As mentioned above, the session data that could not be acquired corresponds to all session data (for example, when UE1 did not participate in the communication session), or corresponds to less data than all session data. (For example, if UE1 only participates during some part of the communication session). Therefore, the 805A may be performed based on information about which part of the communication session UE1 could not participate in and which part of the communication session UE1 participated in (if any). The application server 170 was extracted based on the UE definition context which can be acquired as described above in 700A in Figure 7A and / or 700B in Figure 7B after extracting the session data that could not be acquired in 805A. Shrink (or "compress") parts (810A). An example of how reduction or compression can be performed on the 810A is described above for Figures 7A and 7B (for example, downsizing an 8x10 picture to the same resolution as viewing a 4x5 picture). Reducing video resolution in low bandwidth environments, excluding video and / or audio, converting audio files by converting audio to text, etc.), for brevity of these examples I will not explain further.

FIG. 8B shows an exemplary implementation of 810A of FIG. 8A. In Figure 8B, application server 170 loads the UE definition context of UE1 after extracting the session data that UE1 could not get (800B). The application server 170 then excludes session media and / or session signaling information that UE1 is unlikely to be interested in from the extracted portion (ie, session data that could not be retrieved) based on the UE definition context of UE1. .. Therefore, the exclusion in the 805B is to filter the video if UE1 does not have a screen or the screen is currently occupied, to exclude parts of the communication session between UEs that UE1 is not interested in, etc. May include. As you can see, in other examples, session compression does not have to be interest-based, as shown in Figure 8B, but instead may be otherwise based on the UE definition context (eg, low bandwidth environment). To reduce the resolution of the video, etc.).

In addition, with respect to FIGS. 8A and 8B, session data excluded in 810A and / or 805B may additionally be based on data-specific contexts (regardless of UE definition context). For example, session data is not limited, but must always be sent (eg group management data, one-on-one media, group media, group addition / deletion, participation restrictions), and does not need to be sent after a long failure. Tag several categories, including data (eg, existence data), ancillary signaling (marked as ephemeral), and dialogue management data (eg, current relevant location, pre-participation "catch-up" location). May be done. Therefore, session data reduction or exclusion in the 810A and / or 805B is performed to take into account the data-specific context. For example, if UE1 does not explicitly indicate in the UE definition context of UE1 that it is or is not interested in the above data, this data can still be sent to UE1 or is specific to the data itself. It can also prevent sending to UE1 for reasons (ie applicable to the UE definition context of any UE).

In the description of the embodiment with respect to FIG. 5A, FIG. 5B, FIG. 6A, and / or FIG. 7A above, UE1 was unable to retrieve at least part of the session data for the communication session and was later reconnected to application server 170. Get the compressed version of the session data that could not be obtained. In an example where UE1 actively requests data that could not be retrieved, the application server 170 properly or efficiently (ie, UE1 is the application) a compressed version of the session data that could not be retrieved as described in detail below. You may try to push (so that the compressed version of session data that could not be obtained the moment you establish a connection with server 170 is not simply dumped to UE1).

The application server 170 (or push server) may evaluate a given set of factors to determine when to push a compressed version of session data that could not be obtained to UE1. A given set of factors includes (i) the priority of UE1, (ii) the priority of the UE that sent the session data that could not be obtained, (iii) the number of participants in the communication session, and (iv) communication. The type of media exchanged through the session, (v) the UE1 and / or UE device type that originated the session data that could not be obtained (for example, phone, PC, etc.), (vi) the system to which UE1 is connected. Types (eg WiFi, 3G, etc.), and / or UE1 battery life may be included. By evaluating a given set of factors, the load on the application server 170 (or push server) at any given point in time can be reduced or maintained at a manageable level.

For example, the load on the application server 170 (or push server) and / or the battery life of UE1 is transmitted via a series of slow pushes (ie, small file size transfers) of compressed versions of session data that could not be obtained. It may be controlled. In another example, some originators of session data that could not be retrieved may be high priority users (at least for UE1), and therefore, in a compressed version of session data that could not be retrieved, Media from high priority users may be pushed to a position before media from lower priority users. Alternatively, in the compression of session data that could not be obtained, the session data may be simply excluded from the lower priority UE.

In another example, as mentioned above, a given set of factors used to influence when to push a compressed version of unobtained session data to UE1 participates in a communication session. You may include the size of the group you are in. For example, if the communication session is one-to-one, it is known that all session data supplied by the other UE is targeted at UE1, and therefore pushes of session data that could not be obtained are prioritized. It can be carried out. Alternatively, if the communication session contains 1000 participants, it is statistically unlikely that a user of UE1 will be particularly interested in media from any one particular UE, and therefore from these UEs. Media push may be done at your convenience (ie, not necessarily according to priority). Of course, the application server 170 may have special knowledge of the relevance or priority of sending a UE to UE1 (for example, the sending UE is part of UE1's server-based address book). , Even if the number of participants in the communication session is relatively large, the session data transmitted by the UE may be pushed to the UE 1 according to the priority.

In another example, as mentioned above, the type of media exchanged over a communication session can affect whether or when to push a compressed version of session data that could not be obtained to UE1. is there. For example, if UE1 fails to get some existing updates (for example, some UEs join the communication session, while others are detached from the communication session, while UE1 is part of the communication session. (If not), UE1 could simply be expected to load presence information when rejoining the session, without having to receive presence updates via a priority-based push procedure. In other words, the existence push may be omitted in some cases.

In another example, as described above, a given set of factors may include the sender UE and / or the specification (or type) of the system to which session data that could not be obtained should be sent. For example, a sender UE that supplies session media while UE1 is disconnected from a communication session may indicate to application server 170 that session data should not be pushed to UE1. Rather, the application server 170 only has to wait for UE1 to request this session data. For example, session data that UE1 could not obtain may be supplied by UE2 and may correspond to a voice note or memo, and the user of UE2 may have a voice note or memo with a relatively low priority and UE1. It may be shown that it does not need to be pushed to (ie, it may be shown by including "no push", so UE1 is not interrupted in "real time" by voice notes and UE1 cannot be retrieved. Only interrupted when requesting session data). For example, the back-end server may attempt to deliver a voice note or note when it receives from UE2, but if UE1 is not accessible, application server 170 (or push server) will tell UE2 that this content UE1 does not have to wake up when marked with the "no push" flag. Alternatively, the application server 170 executes the decision logic of the application server 170 itself, even in the absence of an explicit "no push" flag from the sending UE or UE2, and gets UE1 to be considered a lower priority. Specific session data may be classified as "no push" so as not to be bothered by the session data that could not be done.

FIG. 9 shows a communication device 900 containing logic configured to perform a function according to an embodiment of the invention. The communication device 900 is, but is not limited to, UE102, 108, 110, 112 or 200, Node B or base station 124, RNC or base station controller 122, packet data network endpoint (eg SGSN160, GGSN165, etc.), server 170. It may correspond to any of the above-mentioned communication devices, including any of 1 to 186 and the like. Thus, the communication device 900 may accommodate any electronic device configured to communicate (or facilitate communication) with one or more other entities over the network.

Referring to FIG. 9, the communication device 900 includes a logic 905 configured to receive and / or transmit information. In one example, the communication device 900 is a wireless communication device (eg UE200, Node). When supporting (such as B124), the logic 905 configured to receive and / or transmit information is a wireless transmitter / receiver and associated hardware (eg RF antennas, modems, modulators and / or demodulators). Can include wireless communication interfaces such as (eg, Bluetooth®, WiFi, 2G, 3G, etc.). In another example, the logical 905, which is configured to receive and / or send information, has a wired communication interface (eg, a serial connection that can be a means of accessing the Internet 175, a USB or Firewire connection, an Ethernet® connection. Etc.). Therefore, if the communication device 900 corresponds to some type of network-based server (eg SGSN160, GGSN165, application server 170, etc.), the logical 905 configured to receive and / or send information is, in one example, It may support Ethernet cards that connect network-based servers to other communication entities via the Ethernet protocol. In a further example, the logic 905, which is configured to receive and / or transmit information, is a perceptual or measurement hardware (eg, accelerometer, temperature sensor, optical sensor) that the communication device 900 can be a means of monitoring its local environment. , Antennas for monitoring local RF signals, etc.) may be included. A logic 905 configured to receive and / or transmit information, when executed, a logic 905 configured to receive and / or transmit information to perform its receive and / or transmit functions. It may also include software that allows for related hardware. However, the logic 905 configured to receive and / or transmit information does not correspond to the software alone, and the logic 905 configured to receive and / or transmit information performs its functionality. Rely on at least partly the hardware to do so.

Referring to FIG. 9, the communication device 900 further includes a logic 910 configured to process information. In one example, the logic 910 configured to process information may include at least a processor. Illustrative implementations of processing types that can be implemented by logic 910 configured to process information include making decisions, establishing connections, and making choices between different information choices. Performing data-related evaluations, interacting with sensors coupled to the communication device 900 to perform measurement operations, from one form to another (eg, from .wmv. Includes, but is not limited to, translating information (between different protocols, such as avi). For example, the processors contained in a logic 910 configured to process information include general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic. It can correspond to a device, individual gate or transistor logic, individual hardware components, or any combination thereof designed to perform the functions described herein. The general purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, microcontroller, or state machine. Processors are also implemented as a combination of computing devices, such as a combination of DSP and microprocessor, multiple microprocessors, one or more microprocessors working with a DSP core, or any other such configuration. obtain. A logic 910 configured to process information, when executed, may also include software that allows the associated hardware of the logic 910 configured to process the information to perform its processing functions. However, the logic 910 configured to process information does not correspond to the software alone, and the logic 910 configured to process information is at least part of the hardware to perform its functionality. Rely on.

Referring to FIG. 9, the communication device 900 further includes a logic 915 configured to store information. In one example, a logical 915 configured to store information may include at least non-temporary memory and associated hardware (eg, a memory controller). For example, the non-temporary memory contained in a logical 915 configured to store information can be RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disks, removable disks, CD-ROMs, or the like. It can correspond to any other form of storage medium known in the art. A logic 915 configured to store information, when executed, may also include software that allows the associated hardware of the logic 915 configured to store the information to perform its storage function. However, the logic 915 configured to store information does not correspond to the software alone, and the logic 915 configured to store information is at least part of the hardware to perform its functionality. Rely on.

With reference to FIG. 9, the communication device 900 further optionally includes a logic 920 configured to present information. In one example, the logic 920 configured to present information may include at least the output device and associated hardware. For example, output devices include video output devices (eg, display screens, USB, HDMI®, ports that can carry video information, etc.), audio output devices (eg, speakers, microphone jacks, USB, HDMI). A port capable of carrying audio information, such as (registered trademark)), a vibrating device, and / or a means by which the information is formatted for output or actually output by the user or operator of the communication device 900. Any other device to obtain may be included. For example, if the communication device 900 corresponds to a UE 200 as shown in FIG. 3, the logic 920 configured to present information may include a display 224. In yet another example, the logical 920, which is configured to present information, saves on some communication devices, such as network communication devices that do not have local users (for example, network switches, routers, remote servers, etc.). You may. A logic 920 configured to present information, when executed, may also include software that allows the associated hardware of the logic 920 configured to present the information to perform its presentation function. However, the logic 920 configured to present information does not correspond to the software alone, and the logic 920 configured to present information is at least part of the hardware to perform its functionality. Rely on.

With reference to FIG. 9, the communication device 900 further optionally includes a logical 925 configured to receive local user input. In one example, a logical 925 configured to receive local user input may include at least user input devices and associated hardware. For example, user input devices include buttons, touch screen displays, keyboards, cameras, audio input devices (such as microphones or ports capable of carrying audio information such as microphone jacks), and / or communication devices 900. It may include any other device that can be a means of receiving information from the user or operator. For example, if the communication device 900 supports a UE 200 as shown in Figure 3, a logical 925 configured to receive local user input would have a display 224 (if a touch screen is implemented), a keypad 226, and so on. Can include. In yet another example, the logic 925 that is configured to receive local user input, network no local user click communication devices (e.g., network switches or routers, remote servers, etc.), such as, some It may be omitted for communication devices. Logic 925 configured to receive local user input, when executed, software that allows the associated hardware of Logic 925 configured to receive local user input to perform its input receiving function. Can also be included. However, the logical 925 configured to receive local user input does not correspond to the software alone, and the logical 925 configured to receive local user input is at least in the hardware to achieve its functionality. Partially rely on.

Referring to FIG. 9, the configured logics of 905 to 925 are shown as separate or different blocks in FIG. 9, but the hardware and / / for which each configured logic implements its functionality. Or it should be understood that the software can be partially duplicated. For example, any software used to facilitate the functionality of 905-925 configured logic can be stored in the non-temporary memory associated with logic 915 configured to store information. By doing so, each of the constructed logics of 905 to 925 translates its functionality (ie, in this case, software execution) into the behavior of the software stored by the logic 915 configured to store information. Implement on a partial basis. Similarly, hardware directly associated with one of the constructed logics can sometimes be borrowed or used by the other constructed logics. For example, a logical 910 processor configured to process information may format the data into an appropriate format before it is sent by a logical 905 configured to receive and / or send information. The logic 905, which is configured to receive and / or transmit information by doing so, has its functionality (ie, in this case, transmission of data), logic 910 configured to process the information. It is performed based in part on the behavior of the hardware (ie, processor) associated with. Moreover, the constructed logic of 905 to 925 or "logic constructed so" is not limited to a particular logic gate or logic element, but generally has the functionality described herein (hard). Refers to the ability to perform (via either hardware or a combination of hardware and software). Therefore, the constructed logics of 905 to 925 or "logics constructed so" are not necessarily implemented as logical gates or logical elements, even though they share the word "logic". Other Dialogues Between 905 and 925 Constructed Logic

Further, in one embodiment, the "unacquirable" session data may correspond to session data that was not received by a particular UE. Alternatively, the "could not get" session data may correspond to session data that is not delivered to a particular UE and then sent back to the UE. For example, a user first participates in a communication session through a given UE, then the user is unable to obtain some aspect of the communication session, thus revisiting the part of the session that the user could not participate in. You may want to. Therefore, session data that "could not be obtained" should not be construed as necessarily confined to the data exchanged during the UE failure period.

Those skilled in the art will appreciate that information and signals can be represented using any of a wide variety of techniques and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description are voltages, currents, electromagnetic waves, magnetic or magnetic particles, light fields or optical particles, or any of them. It can be represented by a combination.

Moreover, it is noted that the various exemplary logic blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. A trader will understand. To articulate this compatibility of hardware and software, various exemplary components, blocks, modules, circuits, and steps have been generally described above with respect to their functionality. Whether such functionality is implemented as hardware or software depends on specific application examples and design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in various ways for each particular application, but decisions on such implementation should not be construed as causing a deviation from the scope of the invention.

The various exemplary logic blocks, modules, and circuits described in connection with the embodiments disclosed herein include general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), and fields. Implemented in a programmable gate array (FPGA) or other programmable logic device, individual gate or transistor logic, individual hardware components, or any combination thereof designed to perform the functions described herein. Or can be executed. The general purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, microcontroller, or state machine. Processors are also implemented as a combination of computing devices, such as a combination of DSP and microprocessor, multiple microprocessors, one or more microprocessors working with a DSP core, or any other such configuration. Can be done.

The methods, sequences, and / or algorithms described in connection with the embodiments disclosed herein may be embodied directly in hardware, in software modules executed by a processor, or in combination thereof. .. The software module resides in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium known in the art. Can be done. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write the information to the storage medium. Alternatively, the storage medium can be integrated with the processor. Processors and storage media can reside in the ASIC. The ASIC can reside in the user terminal (eg UE). Alternatively, the processor and storage medium may reside as individual components in the user terminal.

In one or more exemplary embodiments, the features described may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the function may be stored on or transmitted on a computer-readable medium as one or more instructions or codes. Computer-readable media include both computer storage media and computer communication media, including any medium that facilitates the transfer of computer programs from one location to another. The storage medium can be any available medium that can be accessed by a computer. By way of example, but not by limitation, such computer-readable media are RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage device, or any desired form of instruction or data structure. It may include any other medium that can be used to transport or store program code and is accessible by a computer. Also, any connection is properly referred to as a computer-readable medium. For example, the software uses coaxial cable, fiber optic cable, twist pair, digital subscriber line (DSL), or wireless technology such as infrared, wireless, and microwave from a website, server, or other remote source. When transmitted, coaxial cables, fiber optic cables, twisted pairs, DSL, or wireless technologies such as infrared, wireless, and microwave are included in the definition of medium. As used herein, discs and discs are compact discs (CDs), laser discs (registered trademarks), optical discs, digital versatile discs (DVDs), floppy (registered trademarks) discs, and Including Blu-ray discs, discs typically reproduce data magnetically, and discs optically reproduce data with a laser. The above combinations are also computer readable

Although the above disclosure shows exemplary embodiments of the invention, it should be noted that various modifications and modifications are made herein without departing from the scope of the invention as defined by the appended claims. I want to be. The functions, steps and / or operations of the method claims according to the embodiments of the invention described herein may not be performed in a particular order. Further, the elements of the invention may be described or claimed in the singular, but the plural is contemplated unless explicitly stated to limit it to the singular.

100 wireless communication system 102, 108, 110, 112 UE 104 Air interface 120 RAN 122 RNC 124 Node B 126 Core network 160 Serving GPRS Support Node 162 First packet data network endpoint 164 Second packet data network endpoint 165 Gateway GPRS Support Node 170 application server 170A Regional Dispatcher 170B media control complex 175 internet 182 AAA server 184 Provisioning server 186 IMS / SIP Registration Server 188 Routing unit 900 communication device 905 Logic configured to receive and / or send information 910 Logic configured to process information 915 Logic configured to store information 920 Logic configured to present information 925 Logic configured to receive local user input