Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L67/00—Network arrangements or protocols for supporting network services or applications
  • H04L67/01—Protocols
  • H04L67/04—Protocols specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L67/00—Network arrangements or protocols for supporting network services or applications
  • H04L67/50—Network services
  • H04L67/54—Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users

Definitions

• the invention relates to presence data of users of terminals of a multimedia system being capable of using a plurality of access technologies for the terminals.
• IP Multimedia Subsystems users can be made aware of other users' presence data, such as being available, in a meeting, in a phone call etc.
• An object of the invention is to reduce resource requirements for presence data updates.
• An application in the terminal for presenting presence data may store a list of users of the multimedia system, wherein only presence data of users on the list is presented.
• a second embodiment of the invention comprises a computer program for a terminal of a multimedia system.
• the computer program comprises computer program code which, when executed on the terminal, causes the terminal to change an update state of the terminal from a low update state to a high update state when a high priority event is detected, change the update state of the terminal from a high update state to a low update state when a low priority event is detected, and present more presence data of other users compared to when the terminal is in the low update state when the terminal is in the high update state.
• a third embodiment of the invention comprises a computer program product comprising a computer program according to the second embodiment and a computer readable means on which the computer program is stored.
• a fourth embodiment of the invention comprises a terminal of a multimedia system.
• the multimedia system comprises a presence server for recording presence data of users of terminals of the multimedia system being capable of using a plurality of access technologies for the terminals.
• the terminal comprises a high priority state updater arranged to change an update state of the terminal from a low update state to a high update state when a high priority event is detected, a low priority state updater arranged to change the update state of the terminal from a high update state to a low update state when a low priority event is detected, and a presence data presenter arranged to, when the terminal is in the high update state, present more presence data of other users compared to when the terminal is in the low update state .
• the presence data presenter may be arranged to store a list of users of the multimedia system, wherein only presence data of users on the list may be presented.
• the low priority state updater may be arranged to throttle presence updates.
• a fifth embodiment of the invention comprises a method executed in a resource list server of a multimedia system.
• the multimedia system comprises a presence server for
• the method comprises receiving a signal indicating a change of an update state of a terminal from a low update state to a high update state, receiving a signal indicating a change of the update state of the terminal from a high update state to a low update state, and when the terminal is in the high update state, send more presence data of other users to the terminal compared to when the terminal is in the low update state.
• a sixth embodiment of the invention comprises a computer program for a resource list server of a multimedia system.
• An eighth embodiment of the invention comprises a resource list server of a multimedia system.
• the multimedia system comprises a presence server for recording presence data of users of terminals of the multimedia system being capable of using a plurality of access technologies for the terminals.
• the resource list server comprises a signal receiver arranged to receive a signal indicating a change of an update state of a terminal from a low update state to a high update state, and to receive a signal indicating a change of the update state of the terminal from a high update state to a low update state, and a transmitter arranged, and when the terminal is in the high update state, to send more presence data of other users to the terminal compared to when the terminal is in the low update state.
• any feature of the first, second, third, fourth, fifth, sixth, seventh and eighth embodiments may, where appropriate, be applied to any other of these embodiments .
• Fig 1 is a schematic diagram showing an overview of an environment where an embodiment of the invention can be applied;
• Fig 2 illustrates how a presence enabler (PE) may comprise a resource list server (RLS);
• PE presence enabler
• RLS resource list server
• Fig 3 is a schematic diagram of components of the presence enabler of Figs 1 and 2;
• Fig 4 is a schematic diagram illustrating the relationships between user, services and terminals
• Fig 5 is a state diagram illustrating different update states of the terminal according to an embodiment of the present invention
• FIG. 7 shows an embodiment of the present invention applied to lists ;
• Fig 8 shows an alternative state diagram with three update states
• Fig 10 is a schematic diagram of components of the terminal, such as any one of the terminals of Figs 1 and 4;
• Fig 11 is a flow chart illustrating an embodiment of a method implemented in the terminal, such as any one of terminals of Figs 1 and 4;
• Fig 12 is a schematic diagram showing functional modules of the terminal of Figs 1 and 4;
• Fig 14 is a schematic diagram showing functional modules of the resource list server, such as the resource list server of Figs 1 and 2.
• FIG 1 is a schematic diagram showing an overview of an environment where an embodiment of the invention can be applied.
• a system 1 complying with the 3GPP (3rd Generation Partnership Project) standard for IP Multimedia Subsystem (IMS) is presented.
• IMS IP Multimedia Subsystem
• Various terminals 12a-c and 12' can be used in the system 1 to allow end user access using various access technologies for the terminals such as mobile (cellular) networks, wireless local area networks, or wired networks such as Ethernet/ADSL (Asymmetric Digital Subscriber Line).
• user terminals are exemplified by a mobile terminal 12a, such as a smart phone, PDA (personal digital assistant) or mobile phone, a computer 12b, such as a
• the P-CSCF 10 is connected to a Serving Call Session Control Function (S-CSCF) 13.
• S-CSCF Serving Call Session Control Function
• the S-CSCF is a central signalling node of the IMS system 1.
• a presence enabler (PE) 15 records presence data for users of the terminals 12a-c, 12'.
• the presence enabler 15 can record automatically updated presence data or user updated presence data.
• automatically updated presence data include that a user is in a phone call, that a user is in a meeting (if calendar information is present, e.g. in one of the clients 12a-c, 12'), and that a user just got out of a meeting.
• user updated presence data include that a user is having lunch, or a free text presence data update such as "working on client proposal".
• the user can indicate the current presence data (such as in a meeting, out for lunch, on vacation, etc.
• Fig 2 illustrates how the presence enabler (PE) 15 may comprise a resource list server (RLS) 16.
• the resource list server RLS 16 is connected, but separate from, the presence enabler 15.
• the resource list server 16 stores user lists for users of the IMS system 1 of Fig 1.
• the computer readable media 22 can be any combination of read and write memory (RAM) and read only memory (ROM) .
• the memory 22 also comprises persistent storage, which, for example, can be any single one or combination of magnetic memory, optical memory, or solid state memory.
• the computer readable media 22 can be co-located with memory for storing user list data of users of the IMS system 1.
• An input/output interface 24 is provided to allow the
• the presence enabler 15 to interact with other components, such as the S-CSCF 13 or indirectly clients 12a-c, 12'.
• the input/output interface 24 can for example be a network interface such as an Ethernet interface or an optical fibre input/output communication interface.
• the presence enabler 15 is co-located with another device, such as the resource list server 16, the controller 20, the computer readable media 22 and input/output interface 24 can be shared with the other device.
• the presence enabler 15 can be integrated in one unit, or it can be separated into several separate units, e.g. for reasons of upgradeability, ease of implementation or
• Fig 4 is a schematic diagram illustrating the relationships between user, services and terminals.
• there are three services a voice call service 32a, a video call service 32b and an instant messaging service 32c.
• the user has access to four terminals, a traditional telephone 12c, a mobile phone 12 ' , a smart phone 12a and a personal computer 12b.
• the traditional phone 12c can be used for the voice call service 32a; the mobile phone 12' can be used for the voice call service 32a and the video call service 32b; the smart phone can be used for the voice call service 32a, the video call service 32b and the instant messaging service 32c, while the personal computer 12b can only be used for the instant messaging service 32c.
• terminals can flexibly be used for any service
• Fig 5 is a state diagram illustrating different update states of the terminal 12a-c, 12' according to an embodiment of the present invention.
• the web client enabler 11 can be
• the terminal 12a-c is responsible for the illustrated state machine. In other cases, the terminal 12a-c is responsible to keep the state machine up to date.
• Each one of the terminal 12a-c, 12' has an application which presents presence data of other users on the user list, where the user list is for the user of the terminal and is stored in the resource list server 16.
• the user list is for the user of the terminal and is stored in the resource list server 16.
• a user A is running an application which presents presence data for users B, C and D.
• presence data changes for, e.g. user B this is directly updated in the application of user A.
• presence data updates are more restricted. This can for example be effected by throttling, where presence data updates are sent only once during a specified time period. Alternatively or
• content filtering can be applied in the low update state, e.g. by only letting presence data that is specifically entered by a user to be sent.
• the state machine changes 43 from the high update state 41 to the low update state 40 e.g. when roaming in a foreign network with a mobile terminal, which reduces data usage costs for the user.
• This state change 43 can also occur if the user does not use the application for presence data updates, as indicated by an inactivity timer expiring or by the application losing focus in the terminal (in other words, that another application takes priority in the user interface of the terminal).
• Another situation is when the terminal senses that it is stowed, such as put in a pocket or purse, e.g. using motion sensors (e.g. accelerometers ) and/or proximity sensors of the terminal, at which a low update state 40 should be assumed.
• any new presence data of users on the user list are sent to the terminal.
• Figs 6A and 6B are sequence diagrams illustrating
• the presence updates can occur using SIP (Session Initiation Protocol), XCAP (XML (Extensible Markup Language)
• SIP Session Initiation Protocol
• XCAP XML (Extensible Markup Language)
• A, B and C refer to the terminals of users A, B and C and not the users themselves. In other words, it is the terminals that perform the communication indicated in the diagrams, not the users.
• Terminal A 50 thus refers to the terminal that user A
• Fig 6A illustrates presence updates in the high update state 41 of Fig 5.
• the communication in Fig 6A starts e.g. when an application showing presence data is started on a terminal A 50.
• Terminal A 50 first sends a subscribe command 54 to the resource list server 16 to get all current updates of the user list for user A.
• the resource list server 16 retrieves the user list for user A which includes users B, C and D.
• the resource list server 16 then sends subscribe messages 55, 56, 57 to the presence enabler 15 for each of the users on the list. This will make the presence enabler 15 send any
• the presence enabler 15 thus responds to the resource list server 16 with notifications 58, 59, 60 of the current presence data of the users in question.
• the resource list server 16 sends a notification message 61 to terminal A 50 with all presence data for all the users on the user list for A.
• this is communicated in a publication message 63 to the presence enabler 15, which forwards this information in a notification message 64 to the resource list server 16.
• the resource list server 16 finally forwards the presence data to the terminal A 50 in a notification message 65.
• user A can have two user lists on the resource list server 16: one list of normal priority users and one list of high priority users. For example, user A might need to get hold of his/her manager and puts the manager in the high priority user list. In that situation, the resource list server 16 sends presence updates to terminal A 50 immediately for users on the high priority list, even if the terminal A 50 is in a low update state. It is also possible to have more user lists with communication options set for each user list, allowing fully configurable throttling and content filtering for the various lists.
• Fig 7 shows an embodiment of the present invention applied to lists .
• a list 50 of content e.g. a list of employees of a company is presented on a terminal, e.g. terminal 12a of Fig 1.
• the content is provided by a server.
• a window 51 also known as a sliding window, displays a subset of the list 50.
• the content within the view of the display 51 is downloaded from the server, along with content above to an upper limit 60 and below to a lower limit 62.
• the upper limit 60 and lower limit 62 follow the sliding window 51 when it is scrolled up or down.
• the margins in the direction of movement can be increased.
• the upper limit 60 is increased in distance from the top of the upper limit of the sliding window 51.
• the upper limit 60 returns to a fixed distance from the upper limit of the sliding window 51.
• Fig 8 shows an alternative state diagram with three update states.
• the low update state is divided into a
• a restricted low priority state is where, for example, no or an extremely low amount of presence data is sent to the terminal. This can for example be due to international roaming or that the battery power is lower than a threshold value.
• the transitions from the low priority state 80 to the high priority state 82 can e.g. be detection of terminal user activity 86, detection of foreground focus 87 of an
• a stowed location 83 such as a pocket or purse .
• transitions from the high priority state 82 to the low priority state 80 can e.g. be expiration of an inactivity timer 89, lost foreground focus 88 of an
• the transitions from the high priority state 80 to the restricted low priority state 84 can e.g. be the detection of international roaming 92 or detection of low battery 93, defined as battery power less than a threshold power.
• the transitions from the restricted low priority state 84 to the low priority state 80 can e.g. be a detection of higher battery power 90, defined as battery power more than a threshold power or detection of end of international roaming 91.
• Fig 9 shows one example of a computer program product 100 comprising computer readable means.
• a computer program 101 can be stored, which computer program can cause a controller to execute a method according to embodiments described herein.
• the computer program can cause a controller to execute a method according to embodiments described herein.
• the computer program can be stored in any way which is suitable for the computer program product.
• the memory 112 also comprises persistent storage, which, for example, can be any single one or
• An input/output interface 113 is provided to allow the terminal 12 to communicate with other network nodes, e.g. using a cellular network or a wireless local area network.
• a display 110 forms part of a user interface of the terminal 12.
• the display can be touch sensitive and/or a separate input device (not shown) can be provided.
• Fig 11 is a flow chart illustrating an embodiment of a method implemented in the terminal 12, such as any one of terminals 12a-c, 12' of Figs 1 and 4.
• a present less presence data step 120 a relatively low amount of presence data is presented. This corresponds to the low update state 40 of Fig 5.
• the high priority event can be a detection of user activity within an application for presenting the presence data, a detection that the application for presenting
• the method continues to a change state from low to high update step 124. Otherwise, the process continues to the present less presence data step 120.
• the change state from low to high update step 124 the state of the terminal is changed from low update state to the high update state, corresponding to the state change 42 of Fig 5.
• a high priority signal is also sent to the resource list server 16.
• a present more presence data step 126 a relatively high amount of presence data is presented. This corresponds to the high update state 41 of Fig 5.
• the low priority event can be a detection that the terminal is roaming, an expiry of an inactivity timer of the terminal, a detection in the terminal that an application for presenting the presence data loses focus, a detection of a remaining battery power level of the terminal being below a threshold level, and a detection that the terminal is stowed. If a low priority event has occurred, the method continues to a change state from high to low update step 129. Otherwise, the process continues to the present more presence data step 126.
• the state of the terminal is changed from high update state to the low update state, corresponding to the state change 43 of Fig 5.
• a low priority signal is also sent to the resource list server 16. The method then continues to the present less presence data step 120.
• the method can continue until the terminal is shut down or stops functioning.
• Fig 12 is a schematic diagram showing functional modules of the terminal of Figs 1 and 4.
• the modules can be implemented using software such as a computer program executing in the terminal. All modules depend on an execution environment (see Fig 10) which utilises a controller 111, a computer program product 112 and an I/O interface 113.
• a high state updater 130 is arranged to change an update state of the terminal 12, 12a-c, 12' from a low update state 40 to a high update state 41 when a high priority event is detected. This corresponds to the state change 42 of Fig 5.
• the state change is communicated to the resource list server 16.
• a low state updater 132 is arranged to change the update state of the terminal (12, 12a-c, 12') from a high update state 41 to a low update state 40 when a low priority event is detected. This corresponds to the state change 43 of Fig 5.
• the state change is communicated to the resource list server 16.
• a presence data presenter 134 is arranged to present presence data as received from the resource list server 16.
• Fig 13 is a flow chart illustrating an embodiment of a method implemented in the resource list server 16, such as the resource list server of Figs 1 and 2.
• the method concerns a method in the resource list server 16 to deal with the state of one terminal. The method occurs in parallel for as many terminals as is needed, as long as the resource list server 16 has sufficient capacity.
• a send less presence data step 140 a relatively low amount of presence data is sent from the resource list server to the terminal. This corresponds to the low update state 40 of Fig 5.
• the method determines if any high priority signals have been received. If a high priority signal has been received, the method continues to a change state from low to high update step 144. Otherwise, the process continues to the send less presence data step 120.
• the change state from low to high update step 144 the state of the terminal in question is changed from low update state to the high update state, corresponding to the state change 42 of Fig 5.
• a send more presence data step 146 a relatively high amount of presence data is sent to the terminal. This
• Fig 14 is a schematic diagram showing functional modules of the resource list server 16, such as the resource list server of Figs 1 and 2.
• the modules can be implemented using software such as a computer program executing in the
• All modules depend on an execution environment (see Fig 13) which utilises a controller 20, a computer program product 22 and an I/O interface 24.
• a signal receiver 150 is arranged to receive a signal
• a transmitter 152 is arranged, when the terminal 12, 12a-c, 12' is in the high update state, to send more presence data of other users to the terminal 12, 12a-c, 12' than when the terminal 12, 12a-c, 12' is in the low update state.

Landscapes

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

Priority Applications (3)

Applications Claiming Priority (2)

Publications (1)

Family

ID=43385621

Family Applications (1)

Country Status (4)

Families Citing this family (3)

Citations (1)

Family Cites Families (5)

• 2010
  • 2010-11-11 WO PCT/SE2010/051187 patent/WO2011071436A1/en active Application Filing
  • 2010-11-11 EP EP10776841.8A patent/EP2510672B1/en active Active
  • 2010-11-11 CN CN201080055543.3A patent/CN102652422B/zh active Active
  • 2010-12-10 US US12/965,248 patent/US8595310B2/en active Active

Patent Citations (1)

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events