Patent Application
20120120845
Multimedia application information, multimedia “flows” (which may be referred to as media flows, or simply, flows), may be communicated to mobile nodes or user equipment (UE) across one or more wireless communication networks. A UE may include any device that may communicate with communications networks, including, but not limited to, mobile devices (e.g., mobile phones, mobile media devices, mobile computers, etc.), computing devices, media devices (e.g., video devices, audio devices, data devices, etc.), telephone devices (including landline devices), etc. A media flow may be transferred from one mobile node or UE to another mobile node or UE.
Such media flow transfers may be referred as Inter UE transfers (IUTs). IUTs may support transfers among IP Multimedia Subsystem (IMS) devices using session initiation protocol (SIP). However, there is no media flow transfer between different non-IMS devices in non-IMS based services. Currently, there is no known solution for peer UEs to dynamically and efficiently discover each other or to select a peer target, nor is there a solution to associate UEs together in a group, and/or to facilitate information exchange among UEs within a group.
Traffic replication and transfer are useful in a network to enable data to be transferred among multiple destinations, while maintaining a single session. Currently, however, there is also no support for traffic replication using Mobile IP.
This Summary is provided to introduce various concepts in a simplified form that are further described below the Detailed Description.
Systems, methods, and apparatus embodiments are described for configuring a group of user equipment that may be used to transfer media flow between members of the group of user equipment. As described herein, a group request message may be received that is associated with a first user equipment and a group of user equipment. The group of user equipment may then be configured based on the group request message. For example, the group request message may include a join group request message, a leave group request message, an update group request message, a query group request message, and/or a data group request message.
Systems, methods, and apparatus embodiments are described for enabling the transfer of a data flow between members of a group of user equipment. For example, an indication may be received to join the first user equipment to the group of user equipment. A mobile IP group request message may be sent that is configured to join a first user equipment to the group of user equipment. Data may be received that is associated with a second user equipment that is a member of the group of user equipment. A data flow may then be transferred to the second user equipment based on the receive data.
Systems, methods, and apparatus embodiments are described for replicating media flow in a network for transmission to a user device. As described herein, a request may be received to replicate a media flow towards a plurality of user equipment. A replication request message may be sent to the plurality of user equipment. The media flow may be replicated and the replicated media flow may be sent to the plurality of user equipment.
A detailed description of illustrative embodiments is described with reference to the FIGs. Although this description may provide detailed descriptions of possible embodiments, it should be noted that the details are intended to be exemplary and in no way limit the scope of the disclosed embodiments.
As illustrated in
In an example embodiment, a user associated with the mobile device 170 may establish a multimedia flow with a remote party associated with the computer 160. The multimedia flow may include one or more media components, such as a voice component 120 and/or a video component 130. The fixed line 180 and/or the projector 190 may be in operative connection with the IP network 110, the mobile device 170, and/or the computer 160. The fixed line 180 and/or the projector 190 may belong to one or more IMS subscriptions. These IMS subscriptions may differ from the IMS subscription of the mobile device 170. Additionally, the fixed line 180 and/or the projector 190 may belong to one or more network operators. These network operators may differ from the network operator of the mobile device 170.
A multimedia flow between the fixed line 180 and/or the projector 190 may be established with the remote party, such as the computer 160. The media flow may be received at the fixed line 180 and/or the projector 190. In another embodiment, the media flow may be broken into components and each component may be received by the fixed line 180 and/or the projector 190. For example, the voice component 120 of the media flow may be transferred to the fixed line 180 and the video component of the media flow may be transferred to the projector 190. When the media flow is received at the fixed line 180 and/or the projector 190, a collaborative session 150 may be established. Collaborative session control may be transferred from mobile device 170 to the fixed line 180 and/or the projector 190. For example, the collaborative session 150 may permit the fixed line 180 and/or the projector 190 to maintain control over the voice component 120 and/or the video component 130. In one embodiment, the collaborative session 140 may be terminated after collaborative session control and/or control over the media flow may be transferred to the collaborative session 150.
SCF 210 and UE-2204 may communicate IMS Service Control information 244 between each other. The UE-2204 and the PSS adapter/server 214 may communicate using media path 246. UE-2204 may send an SIP notification message 248 to IM CN Subsystem 206. The IM CN Subsystem 206 may send SIP notification message 250 to SCC 208. SCC 208 may send SIP notification message 252 to IM CN Subsystem 206 and IM CN Subsystem 206 may send SIP notification message 254 to UE-1201. SIP 200 notification message 256 may be sent from UE-1201 to IM CN Subsystem 206 and IM CN Subsystem 206 may send SIP 200 notification message 258 to SCC 208. SCC 208 may send SIP 200 notification message 260 to IM CN Subsystem 206 and IM CN Subsystem 206 may forward SIP 200 notification message 262 to UE-2204. At 264, the PSS session between UE-1201 and PSS adapter/server 214 may be torn down. At 264 the IUT may be completed and media traffic may flow to UE-2204.
In an embodiment, MIP protocol may be enhanced to support group functionalities. For example, IUT procedures using MIP protocol may use the MIP group functionalities to narrow potential targets for IUT. For example, UEs that are a member of a group may be considered for IUT. This may be more efficient than querying or discovering UEs that support IUT functionalities but may be unavailable for media flow transfers. In addition, information exchange between members of a group may be performed in an efficient manner, minimizing the number of messages sent over-the-air.
In an embodiment, the MIP protocol may support group functionality. For example, the MIP protocol may include a group request message to handle functions such as join a group, leave a group, renew the group membership (e.g., update), send data to members of a group (e.g., on application level), obtain the list of members of a group (e.g., indication/query), or the like.
Each HA may locally maintain a group table, a binding table, and/or a flow table. For example, HA1304 may locally maintain group table 316, binding table 318, and/or flow table 320, while HA2310 may maintain group table 324, binding table 326, and/or flow table 328. Group table 316 and group table 324 may include an entry for each member of a group. For example, group table 316 and group table 324 may include one or more entries for a UE in the group or may be empty. Each entry in the table may have a corresponding home address (HoA), a binding identifier (BID) corresponding to the UE served by the HA in which the group table is stored (e.g., BID1 or BID2), an HA IP address corresponding to the HA serving the UE (e.g., HA1 IP or HA2 IP), and/or a description of the UE. Binding tables 318 and 326 may include HoA information, binding identification information, Care-of-Address (CoA) information, and/or FID information for one or more HAs. Flow table 320 and flow table 328 may include an FID traffic selector and/or tunnel to a binding identification location.
The Session Controller (SC) 312 may forward MIP group messages from an HA to other HAs. For example, the group table 316 maintained by HA1304 may be received by SC 312 at 332 and forwarded by SC 312 to HA2310 at 334. Communications between each HA and the SC 312 may be performed using MIP protocol messages and/or other protocol messages for example. In one example embodiment, the SC 312 may maintain a group table, such as group table 322. Group table 322 may be received from HA1304 and/or HA2310 for example. Group table 322 may include one or more entries for a UE in each of one or more groups or the group table 322 may be empty. Each entry in group table 322 may have a corresponding home address (HoA), an HA IP address corresponding to the HA serving the UE (e.g., HA1 IP or HA2 IP), and/or a description of the UE.
In an alternative embodiment, the network may not include an SC, and the HA1304 may directly communicate to HA2310 at 336. Communications between the HA1304 and HA2310 may be performed using MIP protocol messages and/or other protocol messages for example.
In an embodiment, a group may be identified via a unique identifier. Groups may be pre-configured by the operator, one or more UE users, and/or another entity interested in configuring groups within a network. For example, groups such as Roger's group, phone group, or the like may be configured by a network operator. Groups may be configured dynamically by the operator, one or more UE users, and/or another entity interested in configuring groups within a network. For example, groups such as MyGroup, OfficeGroup, FriendsGroup, FamilyGroup, or the like may be configured by a particular UE user. Each group may be used to send data and/or media flow between members of the group.
Group messages may be propagated to members by HAs and/or the SC. For example, group messages (e.g., join messages and/or leave messages) may be duplicated and/or sent to HAs (e.g., via the SC) that may be serving members in the group. The HAs may maintain an accurate list of groups and the associated members. For example, original DATA group messages may be duplicated and directly sent to members of the group. Applications may use the DATA group mechanism to exchange information at application level with potential target UEs. For example, an application may want to know whether a potential target UE may support the application or the application may check the current load on a potential target UE.
In an embodiment, a UE may obtain the list of members of a specific group from its serving HA. For example, before a UE initiates an IUT, the UE may send a query, such as a QUERY group message, to its serving HA. The UE may request to be informed of changes related to the group membership. A UE may query a group of which the UE may be a member. Depending on the authorization information, the UE may query a group of which the UE may not be a member. Authorization may be configured and/or handled by the HA and/or the SC for example. In an embodiment, a query request may be rejected if the UE is not authorized to query groups of which the UE is not a member.
A UE may obtain application level information from discovered peers by exchanging messages with the peers. For example, before a UE initiates an IUT, the UE may send a message to a peer group member, or a potential target UE, to find out whether the UE supports a particular application. This mechanism may enable the exchange of other information among group members.
As described herein, a network may include a session control node such as a Session Controller (SC). The SC may be used to handle forwarding of MIP Group messages to HAs that have at least one UE registered in a current group. The SC may maintain a table of groups, associated HA's, and/or registered members. Each HA may not know the other HAs involved in a group.
Alternatively, the SC functionality may be added to the HAs if the SC is not present in the network. If the SC is not implemented in the network, each HA may interact directly with other HAs. In this case, each HA may know and use the IP address of the other HAs in performing communications with the other HAs.
In an embodiment, IUT procedures using MIP protocol may use the MIP group functionalities in IUT peer discovery and/or IUT target peer selection procedures. In an embodiment, the MIP group functionality may define peer discovery methods and may facilitate the target peer selection.
The disclosed systems, methods, and apparatus provide for performing an IUT among multiple devices within a network. An IUT may be performed from one interface or device to another. For example, as described herein, an IUT may be performed from a mobile phone to a local area network (LAN) line phone. Each device may discover select targets for IUT. To facilitate the IUT, data and/or media flow replication may be performed. For example, media flow replication may be performed prior to performing the IUT. Mobile IP (MIP) and/or IUT protocols may be implemented for performing the IUT and/or replication.
In an embodiment, the disclosed systems, methods, and apparatus provide for an inter-UE transfer (IUT) based peer discovery and target selection. Mobile IP (MIP) and/or IUT protocols may be used for IUT-based methods or processes as described herein. Although the disclosed embodiments may be generally illustrated herein by reference to MIP or IUT protocol, the embodiments are not limited to embodiments with Mobile IP or IUT protocol.
In an embodiment, MIP protocol may be used to support group functionalities. For example, IUT procedures using MIP protocol may use the MIP group functionalities to narrow potential targets for IUT. In an embodiment, the MIP group functionality may define a peer discovery method and/or may facilitate the target peer selection. For example, a UE may send a request for information related to a UE group. A home agent (HA) may receive the request and/or send information associated with one or more UEs of the UE group to the requesting UE. The requesting UE may then select a target UE for transferring a data flow based on the information received. In an embodiment, the network may include a session control node such as a Session Controller (SC) as described herein. The SC functionality may be added to the HAs if an SC is not present in the network.
An HA may maintain a group table that may store information related to duplicating and sending group messages to members of the group. The group table may be linked to, or be part of a binding table. For example, the group table may include information indicative of a group identifier, a UE's home IP address, a binding identifier, or “none” if the UE is not registered with the current HA, the IP address of the HA serving the specified UE, a description of the UE (e.g., laptop, TV, phone, etc), or other information related to members in the group.
The HA may receive a request such as a JOIN Group request to join a specific group. The HA may add the UE to the group table. If the UE is sending the JOIN request and is served by the HA, the JOIN request may be forwarded to the SC which may propagate it to the HAs that may have at least one UE registered to the group. If there is no SC used in the network, the JOIN request may be directly propagated to the other HAs (e.g., HAs may be configured with a list of other HAs). If the SC is sending the JOIN request and the UE is served by the HA, the JOIN request may be forwarded to the concerned UE.
The SC may maintain a group table that may include information related to duplicating and/or sending group messages to HAs serving members of the group. For example, the group table may include information indicative of group identifier, a UE's home IP address, the IP address of the HA serving the specified UE, a description of the UE (e.g. laptop, TV, phone, etc), and/or other information related to members in the group.
The SC may receive a request, such as a JOIN group request to join a specific group for example. The SC may add information related to the UE to the group table. The SC may forward the JOIN message to the HAs that have at least one UE registered to the group. The SC may also send a request such as a JOIN group request to request a UE to join a group. The SC may dynamically add a UE to a group. The message may be sent to the serving HA and to the HA's that may have at least one UE registered to the group.
The HA1406 may send a JOIN group request message 418 to SC 410. The JOIN group request message 418 may include parameters indicating that the group request is a JOIN group request, the name of the group (e.g., officeGroup), an HoA identifier (e.g., HoA1), an HA IP address (e.g., HA1 IP), and/or a UE type (e.g., phone). The SC 410 may create a group table at 420 corresponding to the officeGroup. The group table at 420 may include the name of the group (e.g., officeGroup), the HoA identifier corresponding to the entry in the group (e.g., HoA1), the HA IP address corresponding to the entry in the group (e.g, HA1 IP), and/or the UE type (e.g., phone).
As illustrated in
The HA2408 may send a JOIN group request 428 to SC 410. The JOIN group request 428 may include parameters indicating that the group request is a JOIN group request, the name of the group (e.g., officeGroup), an HoA identifier (e.g., HoA2), an HA IP address (e.g., HA2 IP), and/or a UE type (e.g., laptop). The SC 410 may add an entry to the group table at 430 that indicates that UE2404 is a member of the officeGroup. The group table at 430 may include an entry for each member that has joined the group. For example, the group table at 430 may include an entry corresponding to UE1402 and an entry corresponding to UE2404. Each entry may include the name of the group (e.g., officeGroup), the HoA corresponding to the entry (e.g., HoA1 or HoA2), the HA IP address corresponding to the entry (e.g., HA1 IP or HA2 IP), and/or the UE type corresponding to the entry (e.g., phone or laptop).
When a UE joins a group, the SC 410 may send join information to other HAs that are serving UEs registered to that group. For example, SC 410 may send a JOIN group request message 432 to HA1406 that indicates that another member has joined the group to which UE1402 is a member. The JOIN group request message 432 may include parameters indicating that another member joined the group, the name of the group (e.g., officeGroup), an HoA associated with the UE that joined the group (e.g., HoA2), an HA IP address associated with the UE that joined the group (e.g., HA2 IP), and/or a UE type associated with the UE that joined the group (e.g., laptop).
After HA1406 receives the JOIN group request message 432, HA1406 may update its group table at 434. For example, HA1406 may add an entry for UE2404 to the group table at 434. The group table at 434 may include an entry for each member that has joined the group. For example, the group table at 434 may include an entry corresponding to UE1402 and an entry corresponding to UE2404. Each entry may include the name of the group (e.g., officeGroup), the HoA corresponding to the entry, the known binding identifier associated with each entry (e.g., if binding identifier is unknown this may be indicated in the group table), the HA IP address corresponding to the entry, and/or the UE type corresponding to the entry (e.g., phone or laptop).
SC 410 may send a JOIN group request message 436 to HA2408 that indicates that another member has joined the group to which UE2404 is a member. The JOIN group request message 436 may include parameters indicating that another member joined the group, the name of the group (e.g., officeGroup), an HoA associated with the UE that joined the group (e.g., HoA1), an HA IP address associated with the UE that joined the group (e.g., HA1 IP), and/or a UE type associated with the UE that joined the group (e.g., phone).
After HA2408 receives the JOIN group request message 436, HA2408 may update its group table at 438. For example, HA2408 may add an entry corresponding to UE1402 to the group table at 438. The group table at 438 may include an entry for each member that has joined the group. For example, the group table at 438 may include an entry corresponding to UE1402 and an entry corresponding to UE2404. Each entry may include the name of the group (e.g., officeGroup), the HoA corresponding to the entry, the known binding identifier associated with the entry (e.g., if binding identifier is unknown this may be indicated in the group table), the HA IP address corresponding to the entry, and/or the UE type corresponding to the entry (e.g., phone or laptop).
At 448, SC 410 may add UE1402 to the newGroup. The SC 410 may send the JOIN information to the HAs that are serving UEs registered to the newGroup. For example, SC 410 may send a JOIN group request message 450 to HA1406. The JOIN group request message 450 may include parameters indicating that a member has been joined to a group, the name of the group (e.g., newGroup), an HoA associated with the UE that has been joined to the group (e.g., HoA1), an HA IP address associated with the UE that has been joined to the group (e.g., HA1 IP), and/or a UE type associated with the UE that has been joined to the group (e.g., phone). The HA1406 may send a JOIN group request message 452 to the UE1402. The JOIN group request message 452 may include parameters indicating that a member has been joined to a group, the name of the group (e.g., newGroup), an HoA associated with the UE that has been joined to the group, an HA IP address associated with the UE that has been joined to the group, and/or a UE type associated with the UE that has been joined to the group (e.g., phone). UE1402 may store the group information locally at 456.
SC 410 may also send a JOIN group request message 454 to HA2408. The JOIN group request message 454 may include parameters indicating that a member has been joined to a group, the name of the group (e.g., newGroup), an HoA associated with the UE that has been joined to the group, an HA IP address associated with the UE that has been joined to the group, and/or a UE type associated with the UE that has been joined to the group (e.g., phone).
The HA may send a request to leave a group, such as a LEAVE group request, to remove a UE from a group. For example, if a UE fails to renew its MIP registration, the UE may be considered as “not available anymore.” A LEAVE group request may be sent by the HA to the SC, on behalf of the UE. The HA may also receive a request to leave a group, such as a LEAVE group request. For example, the HA may receive a LEAVE group request from a UE served by the HA. The HA may send the request to the SC. The SC may propagate the request to the HAs that may have at least one UE registered to the group. If there is no SC used in the network, the LEAVE request may be directly propagated to the other HAs. In an example, the HA may receive a LEAVE group request associated with a UE from the SC. If the UE is served by the HA, the LEAVE request may be forwarded to the concerned UE. The UE may be removed from the group table. If no more UEs served by the current HA are members of this group, the UEs served by other HAs may be removed from the group table.
The SC may receive a request to leave a group, such as a LEAVE Group request. For example, the LEAVE message may be forwarded to the HA's that may have at least one UE registered to the group. The UE entry may be removed from the group table. The SC may also send a request to leave a group, such as a LEAVE Group request, to remove a UE from the group. The SC may dynamically remove a UE from a group that the SC may have created. The LEAVE message may be forwarded to the serving HA and to the HA's that may have at least one UE registered to the group.
The HA1506 may send a LEAVE group request message 522 to SC 510. The LEAVE group request message 522 may include parameters indicating that a member of a group wants to leave the group, the name of the group (e.g., officeGoup), an HoA associated with the UE that wants to leave the group, an HA IP address associated with the UE that wants to leave the group, and/or a UE type associated with the UE that wants to leave the group (e.g., phone). After SC 510 receives LEAVE group request message 522, SC 510 may remove the entry corresponding to UE1502 from its group table at 528.
The SC 510 may send a LEAVE group request message 526 to HA2508 to notify HA2508 that UE1 has left the officeGroup. The LEAVE group request message 526 may include parameters indicating that a member of a group wants to leave the group, the name of the group (e.g., officeGoup), an HoA associated with the UE that wants to leave the group, an HA IP address associated with the UE that wants to leave the group, and/or a UE type associated with the UE that wants to leave the group (e.g., phone). The LEAVE group request message may be sent to HA2508 so that HA2508 may update its group table to remove the entry corresponding to UE1502. At 530, HA2508 may remove the entry corresponding to UE1502 from its group table.
At 532, UE2504 may also decide to leave the officeGroup. For example, UE2504 may receive an indication from a user, a network operator, and/or another entity interested in configuring groups within a network. The UE2504 may send a LEAVE group request message 534 to HA2508, which may be the HA serving the UE2504 for example. The LEAVE group request message 534 may include parameters indicating that a member of a group wants to leave the group, the name of the group (e.g., officeGoup), a binding identifier associated with the UE that wants to leave the group, an HoA associated with the UE that wants to leave the group, an HA IP address associated with the UE that wants to leave the group, and/or a UE type associated with the UE that wants to leave the group (e.g., laptop). After HA2508 receives LEAVE group request message 534, HA2508 may remove the entry corresponding to UE2504 from its group table at 538. After UE1502 and UE2504 have been removed from the group table, the group table may be empty.
The HA2506 may send a LEAVE group request message 536 to SC 510. The LEAVE group request message 536 may include parameters indicating that a member of a group wants to leave the group, the name of the group (e.g., officeGoup), an HoA associated with the UE that wants to leave the group, an HA IP address associated with the UE that wants to leave the group, and/or a UE type associated with the UE that wants to leave the group (e.g., laptop). After SC 510 receives LEAVE group request message 536, SC 510 may remove the entry corresponding to UE2504 from its group table at 540. After UE1502 and UE2504 have been removed from the group table, the group table may be empty.
At 548, SC 510 removes UE1 from the SC-Group. SC 510 may remove the entry associated with UE1502 from its group table at 560. SC 510 may send a LEAVE group request message 550 to HA1506 indicating that UE1 is removed from the SC-Group. The LEAVE group request message 550 may include parameters indicating that a member of a group has been removed from the group, the name of the group (e.g., SC-Group), an HoA associated with the UE that has been removed from the group, an HA IP address associated with the UE that has been removed from the group, and/or a UE type associated with the UE that has been removed from the group (e.g., phone). After HA1506 receives LEAVE group request message 550, HA1506 may remove the entry corresponding to UE1504 from its group table at 558. After UE1502 has been removed from the group table at 558, the group table may be empty because no more UEs served by HA1506 may be members of the SC-Group.
After UE1502 has been removed from the SC-Group, the SC-Group entries may be removed from UE1502. For example, HA1506 may send a LEAVE group request message 552 to UE1502. The LEAVE group request message 552 may include parameters indicating that a member of a group has been removed from the group, the name of the group (e.g., SC-Group), a binding identifier associated with the UE that has been removed from the group, an HoA associated with the UE that has been removed from the group, an HA IP address associated with the UE that has been removed from the group, and/or a UE type associated with the UE that has been removed from the group (e.g., phone). At 556, UE1502 may clear the SC-Group information locally.
SC 510 may also send LEAVE group request message 554 to HA2508 so that HA2508 may update its group table. The LEAVE group request message 554 may include parameters indicating that a member of a group has been removed from the group, the name of the group (e.g., SC-Group), an HoA associated with the UE that has been removed from the group, an HA IP address associated with the UE that has been removed from the group, and/or a UE type associated with the UE that has been removed from the group (e.g., phone). HA2508 may remove the entry associated with UE1502 from its group table at 562. The group table at 562 may still include the entry associated with UE2504 in the SC-Group, as UE2504 remains a member of the SC-Group and HA2508 is serving UE2504.
The SC may receive a group update message such as an UPDATE group message. An UPDATE group message may be sent periodically to the SC as a “keepalive.” In an embodiment, if no update messages are received from an HA that may have at least one UE registered to at least one group, the UEs from that HA may be considered to have “left the group.” Indications may be sent to the other HAs such that the other HAs may update the local group table (the UEs may be considered as “not available” and may be removed from the table).
As illustrated in
At 624, HA2608 fails to send an UPDATE group request message. For example, the failure to send the message may be due to an internal failure at the HA2608. As a result, the group registration for UE2604, which is served by HA2608, may be lost. At 626, the periodic timer associated with HA2608 may expire and all group entries related to HA2608 may be deleted. For example, the SC 610 may remove the officeGroup entry corresponding to the UEs being served by HA2608 from the group table at 632. SC 610 may send a LEAVE group request message 628 to HA1606, which may enable HA1606 to update its group table at 630 to remove the officeGroup entry corresponding to UE2604 from the group table. The LEAVE group request message 628 may include parameters indicating that a member of a group has been removed from the group (e.g., LEAVE parameter), the name of the group (e.g., officeGroup), an HoA associated with the UE that has been removed from the group, and/or an HA IP address associated with the UE that has been removed from the group.
At 634, the HA1606 may not receive an indication from UE1602 to stay in the group and may determine that it should leave the officeGroup on behalf of UE1602. Once the HA1606 determines to leave the officeGroup, the group registration may be lost. The HA1606 may then remove the entry in its group table corresponding to UE1602 at 638. The HA1606 may send a LEAVE group request message 636 to the SC 610, so that the SC 610 may update its group table at 640. The LEAVE group request message 636 may include parameters indicating that a member of a group has been removed from the group (e.g., LEAVE parameter), the name of the group (e.g., officeGroup), an HoA associated with the UE that has been removed from the group, and/or an HA IP address associated with the UE that has been removed from the group.
In an embodiment, the HA may receive a request, such as a QUERY group request for example, to query group information. The HA may send a QUERY response message including one or more entries associated to the specified group identifier.
As illustrated in
At 718, UE1702 decides to query the officeGroup and/or ask for updates. The UE1702 may send a QUERY group request message 720 to HA1706. The QUERY group request message 720 may include parameters indicating the type of message (e.g., QUERY message), the name of the group (e.g., officeGroup), and/or that an update indication is turned on. HA1706 may send QUERY group response message 722 to UE1702. The QUERY group response message 722 may include parameters indicating the type of message (e.g., QUERY message), the name of the group (e.g., officeGroup), the number of members in the group (e.g., 2 members), an HoA associated with each UE that is a member of the group, an HA IP address associated with each UE that is a member of the group, and/or a UE type for each UE that is a member of the group (e.g., phone or laptop).
At 724, the UE2704 may leave the officeGroup. UE2704 may send a LEAVE group request message 726 to the HA2708. The LEAVE group request message 726 may include parameters indicating that a member of a group is leaving the group (e.g., LEAVE parameter), the name of the group (e.g., officeGroup), a binding identifier associated with the member leaving the group, an HoA associated with the member leaving the group, an HA IP address associated with the member leaving the group, and/or a UE type associated with the member leaving the group (e.g., laptop).
The HA2708 may send a LEAVE group request message 728 to the SC 710. The LEAVE group request message 728 may include parameters indicating that a member of a group is leaving the group (e.g., LEAVE parameter), the name of the group (e.g., officeGroup), an HoA associated with the UE that is leaving the group, an HA IP address associated with the UE that is leaving the group, and/or a UE type associated with the UE that is leaving the group (e.g., laptop). The SC 710 may send a LEAVE group request message 732 to the HA1706. The LEAVE group request message 732 may include parameters indicating that a member of a group is leaving the group (e.g., LEAVE parameter), the name of the group (e.g., officeGroup), an HoA associated with the UE that is a member of the group, an HA IP address associated with the UE that is a member of the group, and/or a UE type associated with the UE that is a member of the group (e.g., laptop).
The HA1706 may send a QUERY group indication message 730 to UE1702 that may indicate to UE1702 that UE2 has left the group. The QUERY group indication message may include parameters indicating the type of message (e.g., QUERY message), the name of the group (e.g., officeGroup), the number of members in the group (e.g., 1 member), an HoA associated with the UE that is a member of the group, an HA IP address associated with the UE that is a member of the group, and/or a UE type associated with the UE that is a member of the group (e.g., phone).
At 734, the UE1702 may disable group updates. For example, the UE1702 may disable group updates when it is the last member left in a group. The UE1702 may send a QUERY group request message 736 to HA1706. The QUERY group request message 736 may include parameters indicating the type of message (e.g., QUERY message), the name of the group (e.g., officeGroup), and/or an indication to turn updates off. HA1706 may send a QUERY group response message 738 to UE1702. The QUERY group response message 738 may include parameters indicating the type of message (e.g., QUERY message), the name of the group (e.g., officeGroup), the number of members in the group, an HoA associated with the UE that is a member of the group, an HA IP address associated with the UE that is a member of the group, and/or a UE type associated with the UE that is a member of the group (e.g., phone).
In an embodiment, the UE may send a data request such as a DATA group request to obtain information from one or more members in the group. For example, an application running on the UE may send application layer information to a specific group of UEs. The data message may be sent to the serving HA. The HA may duplicate and send the data message to the other members of the group that the HA may be serving. The HA may also send the data message to the SC when some members are registered with other HAs.
An HA may receive a data request, such as a DATA group request for example. The data may be duplicated and/or may be sent to registered UEs, for example, using unicast messages (CoAs). In an embodiment, the MIP header may be removed from the data. The message may be forwarded to the SC if at least one UE that may be a member of the group is not served by the current HA (e.g. no Binding ID). The SC may forward the message to the appropriate HAs that may de-encapsulate the message and send the message to group member UEs that the HAs may serve.
The HA may receive a data request, such as a DATA group request. The data may be duplicated and may be sent to registered UEs, for example, using unicast messages (CoAs). The SC may forward the message to the HA's that may have at least one UE registered to the group. The SC may also send a data request such as a DATA Group request. The SC may send data to a group. The data include information that enables an IUT or transfer of media flow between UEs for example. The message may be sent to the HAs that are serving UEs registered to the group. HAs may take care of duplicating and sending the data to the members of the group that they are serving.
At 818, UE1802 may decide to send data to the members of the officeGroup. For example, UE1802 may send a DATA group request message 822 to HA1808. The DATA group request message 822 may include parameters indicating the type of message (e.g., DATA message), the name of a group (e.g., officeGroup), and/or the data to be sent to the members of the group. HA1808 may send the data to members served by HA1808 and/or forward the data to SC 812 if some members of the group are served by another HA, such as HA2810 for example. Alternatively, HA1808 may send the data to a UE that is not locally registered, such as UE3806 for example. For example, the HA1808 may send data to a UE that is not registered to HA1808 using the HoA associated with the UE.
HA1808 may send the data directly to other members of the group served by HA1808. For example, HA1808 may send the data received from UE1802 to UE2804. The data may be sent using IP packet 826 for example. IP packet 826 may include parameters indicating the source of the IP packet 826 (e.g., HA1808), the destination of the IP packet 826 (e.g., CoA2), the source of the data (e.g., HoA1), the destination of the data (e.g., HoA2), and/or the data itself.
HA1808 may send data to the SC 812 to distribute to other members of the group not served by HA1808. For example, HA1808 may send a DATA group request message 828 to SC 812. The DATA group request message may include parameters indicating the type of message (e.g., DATA message), the name of the group (e.g., officeGroup), and/or the data to be sent to other members of the group. SC 812 may forward the data to an HA serving another UE in the group. For example, SC 812 may send a DATA group request message 830 to HA2810. The DATA group request message 830 may include parameters indicating the type of message (e.g., DATA message), the name of the group (e.g., officeGroup), and/or the data to be sent to other members of the group. The HA2810 may send the data to UE3806. For example, the HA2810 may send IP packet 832 to UE3806. IP packet 832 may include the source of the IP packet (e.g., HA2), the destination of the IP packet (e.g., CoA3), the source of the data (e.g., HoA1), the destination of the data (e.g, HoA3), and/or the data itself. The data may be sent to the served UEs when the request comes from the SC 812.
Data may also originate and/or be originally sent through the SC 812. For example, SC 812 may determine to send data to the officeGroup at 836. The SC 812 may send a DATA group request message 834 to HA1808 and/or a DATA group request message 844 to HA2810. HA1808 may decide to send the data to members served by HA1808 at 838. For example, HA1808 may send data to the members served by HA1808 by using their respective CoA. HA1808 may then send IP packet message 840 to UE1802 and IP packet message 842 to UE2804. IP packets 840 and 842 may include the source of the IP packet (e.g., HA1), the destination of the IP packet (e.g., CoA1 or CoA2), the source of the data (e.g., SC 812), the destination of the data (e.g, HoA1 or HoA2), and/or the data itself. The data may be sent to the served UEs when the request comes from the SC 812. HA2810 may also decide to send the data to the members served by HA2810. For example, HA2810 may send data to UE3806 using the CoA3 corresponding to UE3806. The HA2810 may send an IP packet message 848 to UE3806. The IP packet message may include the source of the IP packet (e.g., HA2), the destination of the IP packet (e.g., CoA3), the source of the data (e.g., SC 812), the destination of the data (e.g, HoA3), and/or the data itself.
The data that is sent between UEs in a group may include information that enables an IUT or transfer of media flow between UEs for example.
As illustrated in
As illustrated in
At 920, UE1902 may want to discover available peers for a possible IUT and/or may ask for automatic updates. UE1902 may send a QUERY group request 924 to HA1908. The QUERY group request 924 may include parameters indicating the type of message (e.g., QUERY message), the name of the group (e.g., officeGroup), and/or an indication to turn on the update procedure (e.g., updateON). In response to the QUERY group request 924, members of the group may be sent to the UE1902. For example, HA1908 may send a QUERY group response message 926 to the UE1902. QUERY group response message 926 may include parameters indicating the type of message (e.g., QUERY message), the name of the group (e.g., officeGroup), the number of members in the group (e.g., 3 members), the HoA corresponding to each member in the group (e.g., HoA1, HoA2, and HoA3), the HA IP address corresponding to each member in the group (e.g., HA1 IP and HA2 IP), and/or a UE type for each UE that is a member of the group (e.g., phone or laptop).
At 928, UE1902 may choose UE3906 may as the target UE for IUT, but UE3906 may have left the group and/or no longer be available for IUT. Learned information may be forwarded to the application layer. At 930, UE1902 may be informed that UE3 is not in the officeGroup anymore. For example, UE1902 may be informed using the LEAVE procedure as described herein. As the QUERY update is on, UE1902 may be informed of any changes in the group.
HA1908 may send QUERY group indication message 932 to UE1902. The QUERY group indication message may include parameters indicating the type of message (e.g., QUERY message), the name of the group (e.g., officeGroup), the number of members in the group (e.g., 2 members), the HoA corresponding to each member in the group (e.g., HoA1 and HoA2), the HA IP address corresponding to each member in the group (e.g., HA1 IP), and/or a UE type for each UE that is a member of the group (e.g., phone or laptop). At 934, UE1902 may react to UE3906 leaving the group by selecting UE2904 as the target UE, instead of UE3906.
MIP DATA group functionality may be used to exchange application level information with the discovered peers (e.g., after peer discovery). The request may include, but may not be limited to, one or more of what is the application in use and related information, query about network load, and/or query about load on the device. A response to the request may include, but may not be limited to, one or more of the following: whether the application or an equivalent is supported, version information, current load on the device, and/or current load on the network. The source device initiating the IUT may then select the target peer(s) based on the information received.
The information that may be exchanged using the MIP DATA group mechanism is not limited to what is described herein. With the mechanism for exchanging data between peer members, any kind of information may be exchanged.
As illustrated in
At 1020, UE11002 may want to discover available peers for a possible IUT and may ask for automatic updates. At 1024 UE11002 may want to discover available UEs that are part of the officeGroup. For example, UE11002 may use the QUERY procedure as described herein. UE21004 and UE31006 may be identified as available peers in the network. UE11002 may want to exchange an application's specific information with UE21004 and UE31006 at 1026 to help the target selection for IUT.
UE11002 may send DATA group request message 1028 to HA11008. The DATA group request message 1028 may include parameters indicating the type of message (e.g., DATA message), the name of the group (e.g., officeGroup), and/or the data (e.g., “application in use, device load”). HA11008 may send the data to registered members of HA11008 and/or forward the data to SC 1012, which may send the data to other HAs serving UEs not registered to HA1, such as HA21010 for example.
For example, HA11008 may send IP packet 1032 to UE21004, which is served by HA11008. IP packet 1032 may include the source of the IP packet (e.g., HA1), the destination of the IP packet (e.g., CoA2), the source of the data (e.g., HoA1), the destination of the data (e.g, HoA2), and/or the data itself (e.g., “application in use, device load”). The UE21004 may respond with an IP packet 1034. IP packet 1034 may include the source of the IP packet (e.g., HoA2), the destination of the IP packet (e.g., HoA1), and/or the data itself (e.g., “supported 25%”).
HA11008 may send the data received from UE21004 to UE11002. For example, HA11008 may send IP packet 1038 to UE 11002. The IP packet 1038 may include the source of the IP packet (e.g., HA1), the destination of the IP packet (e.g., CoA1), the source of the data (e.g., HoA2), the destination of the data (e.g, HoA1), and/or the data itself (e.g., “supported 25%”).
As described herein, HA11008 may send data to SC 1012 to forward the data to other HAs serving other members of the officeGroup. For example, HA11008 may send DATA group request message 1030 to SC 1012. The DATA group request message 1030 may include parameters indicating the type of message (e.g., DATA message), the name of the group (e.g., officeGroup), and/or the data (e.g., “application in use, device load”). The SC 1012 may send the data to HA21010 using DATA group request message 1036. The DATA group request message 1036 may include parameters indicating the type of message (e.g., DATA message), the name of the group (e.g., officeGroup), and/or the data (e.g., “application in use, device load”).
HA21010 may send the data to UE31006, which is served by HA21010. For example, HA21010 may send IP packet 1040 to UE31006. IP packet 1040 may include the source of the IP packet (e.g., HA2), the destination of the IP packet (e.g., CoA3), the source of the data (e.g., HoA1), the destination of the data (e.g, HoA3), and/or the data itself (e.g., “application in use, device load”).
After UE31006 receives the data from UE11002, information may be exchanged between UE31006 and UE11002. This data exchange may use MIP forwarding and/or IP routing for example. In response to the data received from UE11002, UE31006 may send data to UE11002, via HA11008. For example, UE31006 may send IP packet 1042 to HA11008. IP packet 1042 may include the source of the IP packet (e.g., HoA3), the destination of the IP packet (e.g., HoA1) and/or the data to be sent (e.g., “supported 50%”). HA11008 may send the data to UE11002 using IP packet 1044. The IP packet 1044 may include the source of the IP packet (e.g., HA1), the destination of the IP packet (e.g., CoA1), the source of the data (e.g., HoA3), the destination of the data (e.g, HoA1), and/or the data itself (e.g., “supported 50%”). The IP packet 1044 may be forwarded to the application layer.
After receiving data from UE21004 and UE31006, UE11002 may select a target UE for IUT or media flow transfer. For example, at 1046, UE11002 may select UE21004 as the target UE because UE21004 is less loaded than UE31006. UE11002 may then trigger an IUT to UE21004.
In an embodiment, MIP Protocol may include group messages.
Described herein are exemplary option types for the MIP group extensions and examples of the option specific data for each option type. For example, the option types may include a join request, a leave request, a query request, a query response, an update request, and/or a data request. A join request may include a binding identifier, a UE's Home IP Address, a serving HA's IP address, and/or a device description. A leave request may include a UE's Home IP Address, a serving HA's IP address, and/or a device description. A query request may include a flag to request/stop automatic updates. A query response may include a number of group members, a member's Home IP address, a member's HA IP address, and/or a member device description. An update request may include an HA's IP address. A data request may include an application's specific data. Each request also include any other information as described herein. The requests such as join, update, query, leave and/or data may have a corresponding “response” message that may include the status of the request (e.g. success/failure) and/or a request identifier.
HA11314 may communicate, via 1328, with SC 1316. HA21318 may communicate, via 1330, with SC 1316. MIP, IUT, and/or another protocol may be used for communication 1328 and/or communication 1330.
Each UE, HA, and SC may function as described herein with respect to using IUT protocol. In an embodiment, requests such as JOIN, LEAVE, QUERY, and/or DATA requests may be sent from the UE11302 to HA 1314 and/or from the UE21304 and/or UE31306 to HA 1318 using IUT protocol. Communication 1326, between HA11314 and HA 1318, may be performed using MIP protocol for example. Communications between HAs and PMIPs and/or UPDATE requests may be performed via MIP protocol.
Peer discovery may be executed using an IUT Protocol that may support the group functionality as described herein. The peer discovery sequence, such as shown in
Target peer selection may be executed using an IUT Protocol that may support the group functionality as described herein. The target peer selection sequence, such as shown in
In an embodiment, the IUT protocol may be protocol that supports group functionality. IUT protocol may be a protocol that supports the functionality described herein, including group functionality such as JOIN, LEAVE, QUERY, UPDATE, and/or DATA requests/responses. IUT protocol may support IUT functionality, such as IUT preparation, execution, and/or completion. A combination of protocols may be used together to implement the complete IUT procedures. For example, an application layer protocol may be used to handle information exchange at the application level (e.g., XMPP, H323, sip, etc.) while the IUT procedures may be handled by another protocol (e.g., MIP protocol). In an example, the group functionality may be implemented into a protocol that may be different than the IUT protocol handling the flow transfer and/or replication.
The embodiments described herein may transfer data from one network entity to another using traffic replication transfer. Traffic replication and transfer may be used in a network to enable data to be transmitted to and/or received from multiple destinations, while maintaining a single session. Traffic replication may use a Remote Party, the Session Continuity Controller (SCC), and/or a Media Replication Function (MRF). As described herein, an SCC and an SC may include the same and/or similar functionality.
In an embodiment, session replication may be performed by the use of a Remote Party in a pull mode, as illustrated in
As illustrated in
Media flow replication in may be performed by a network in a push mode, as illustrated in
As illustrated in
UE-11502 may be established as the controller at 1556. UE-21504 may be established as the controllee at 1558. At 1560, collaborative session control may be communicated between UE-11502 and SCC AS-11508. Media-A may be communicated between UE-11502 and MRF 1510 at 1566. At 1562, media-A may be communicated between MRF 1510 and remote party 1516. At 1564, media-A may be replicated from MRF 1510 to UE-21504.
Media flow replication may also be performed by a network in a pull mode, as illustrated in
As illustrated in
As described herein, traffic replication may be performed using Mobile IP. Traffic replication and/or transfer in a Mobile IP (MIP) system may be useful to transmit and/or receive data to and/or from multiple destinations, while maintaining a single session in the MIP system. According to one embodiment, flow replication and/or transfer may be enabled in an MIP system using an MIP protocol. For example, MIP messages may be used between a mobile device and a Home Agent (HA). MIP messages may also be used between HAs.
A REPLICATOR may receive data destined to and/or from a source device and may replicate it to target devices. The REPLICATOR may optionally process the data to be sent to the target devices. For example, the REPLICATOR may merge the data from two sources before sending it to another device. The REPLICATOR may be co-located with an HA or a Session Controller.
A Session Controller (SC), which may be similar to a Session Continuity Controller (SCC) in other systems, may handle session configuration with target devices and/or a REPLICATOR. The SC may handle authorization with an Authorization Entity. The SC may handle the communication with other SCs if the target devices are served by different SCs. The SC may be co-located with the HA or the REPLICATOR.
An Authorization Entity (AE) may be used to obtain authorization to execute the replication/transfer to other devices
A data replication mechanism may also be used as a method to accomplish inter-unit transfer (IUT).
A binding table may exist where a Home Address (HoA) may be associated to a single Care-of-Address (CoA). Additionally, the CoA may be updated when a user moves to another location and/or technology.
Dual Stack MIP may allow the registration of one or more internet protocol (IP) addresses and/or prefixes. Dual Stack MIP may also allow the transport of IP packets over a tunnel to an HA. Further, Dual Stack MIP may allow a mobile node to roam over multiple IPs. The use of Multiple Bindings may introduce Binding Identification (BID) mobility extension in Binding Update (BU), and/or Binding Acknowledgement (BA). Multiple Bindings may enable the creation of multiple binding entries on an HA or a Correspondent Node (CN), where one or more CoAs may be associated to a HoA. In Multiple Bindings, a UE may generate a BID for each CoA.
The use of Flow Bindings may include Flow Identification (FID) mobility extension in BU/BA. Flow Bindings may also include flows and may allow a particular flow to bind to one or more CoAs, such as a binding entry. A particular flow may bind to one or more CoAs without affecting other flows using the same HoA. Traffic selectors may be used to identify flows and may be compared with incoming IP packets. The use of Flow Bindings may allow a specification of policies that may be associated with each binding entry. Policies may use traffic selectors. Actions associated with policies may be actions such as delete or forward IP packets to the associated CoA for example.
Several operations may be performed to replicate and/or transfer data in an MIP system, such as authorization, session control, and/or data replication for example. Authorization may be handled by an AE or by an HA. Session control may be handled by an SC node, an HA, and/or a REPLICATOR. Data replication may be handled by a REPLICATOR, an HA, and/or an SC. The replicator may have the “intelligence/knowledge” to extract an application's data from a packet and resend it to the destinations over sessions between the REPLICATOR and the destinations, as illustrated in
Many different architecture models are described herein for data replication. Each architectural model described herein may be implemented separately or in combination with another architectural model, or any portion thereof
According to an embodiment, an HA may handle the authorization, the session control, and the replication. For example, an HA may handle the authorization, session control, and/or the data replication in an MIP system in one of two ways. In one example embodiment, a UE may request, via an HA associated with the UE, to replicate a flow towards another UE. In an alternative example embodiment, replication may be triggered by a target UE.
As illustrated in
Alternatively, as illustrated in
According to an embodiment, an HA may interact with a REPLICATOR, which may handle data replication to peer devices. For example, the HA may interact with a REPLICATOR, which handles data replication to peer devices. In one example embodiment, a UE may request, via an HA associated with the UE, to replicate a flow towards another user equipment. In an alternative example embodiment, replication may be triggered by a target UE.
As illustrated in
Alternatively, as illustrated in
According to an embodiment, an HA may interact with a Session Controller (SC), which may handle the session control. Replication may be handled by the REPLICATOR node or by the HA. The HA may interact with an SC in handling control information in an MIP system. The SC may handle the session control, and replication may be handled by the REPLICATOR node or by a HA. In one example embodiment, a UE may request, via an HA associated with the UE, to replicate a flow towards another user equipment. In an alternative example embodiment, replication may be triggered by a target UE.
As illustrated in
Alternatively, as illustrated in
According to an embodiment, an HA may interact with an Authorization Entity (AE), which may handle the authorization of the replication session. Replication may be handled by the REPLICATOR node or by the HA. Session Control may be handled by the SC node or by the HA. The HA may interact with an Authorization Entity (AE) in handling control information in a MIP architecture. The AE may handle the authorization of the replication session. Replication may be handled by the REPLICATOR node or by a HA. Session Control may be handled by the SC node or by a HA. At least two embodiments may be implemented. In one example embodiment, a UE may request, via an HA associated with the UE, to replicate a flow towards another user equipment. In an alternative example embodiment, replication may be triggered by a target UE.
As illustrated in
Alternatively, as illustrated in
According to an embodiment, an HA may interact with the REPLICATOR, which may handle data replication and session control. The HA may interact with a REPLICATOR that may perform the session control when handling control information in an MIP architecture. The REPLICATOR may handle data replication and/or session control. In one example embodiment, a UE may request, via an HA associated with the UE, to replicate a flow towards another user equipment. In an alternative example embodiment, replication may be triggered by a target UE.
As illustrated in
Alternatively, as illustrated in
According to an embodiment, devices may register with the entity handling session control to receive duplicated data. For example, UE devices may register with an entity that handles session control to receive duplicated control information. For example, UEs that want to participate in a replication session may register, via an associated HA. As illustrated in
As illustrated in
As illustrated in
A number of replication/transfer scenarios are contemplated, as described herein. For example, replicated data may be received from a Correspondent Node (CN) and/or replicated to multiple devices. In another example, the replicated data may have originated from participating devices and/or replicated to other participating devices. In one embodiment, the HA may handle data replication. In another embodiment, the REPLICATOR and/or the SC may handle data replication. The entity handling the data replication may also responsible for handling the sessions (e.g. TCP/UDP) between itself and the destinations. Data ACKs from the destinations may be sent to the entity handling the replication.
As illustrated in
As illustrated in
As illustrated in
CN 2902 may send data to HA12906 at 2930. HA12906 may decide to forward the data to UE12904 and/or replicate the data to UE22910, such as via HA22908 for example. HA12906 may send the data to UE12904 at 2932. The UE12904 may send a data ack to CN 2902 at 2942. The data may be replicated to HA22908 at 2938. At 2940, the data may be forwarded to UE22910. The UE22910 may send a data ack to HA12906 at 2944. HA12906 may handle session control with replicated destinations at 2946.
As illustrated in
REPLICATOR 3010 may replicate the data at 3036. A replication ack message may be sent from REPLICATOR 3010 to SC 3008 at 3042. At 3040, SC 3008 may send a replication response message to HA13006 at 3040. At 3038, HA13006 may send a binding ack message (e.g., an MIP binding ack message) to UE13004. HA13006 may add a “forward to REPLICATOR” message into BID1 at 3044 and generate configure the binding table at 3046.
CN 3002 may send data to HA13006 at 3048, which may be forwarded on to UE13004 at 3050. After UE13004 receives the data it may send a data ack at 3050 to CN 3002. HA13006 may also send data to the REPLICATOR 3010 at 3052, which may forward the data to HA23012 at 3054. After REPLICATOR 3010 receives the data, it may send a data ack to HA13006 at 3060. At 3056, HA23012 may send the data to UE23014. After UE23014 receives the data, it may send a data ack to REPLICATOR 3010 at 3062.
As illustrated in
UE13104 may determine the data requested by UE23114 at 3128. At 3130, UE13104 may send a replication ack message (e.g., an MIP replication ack message) to HA13106. A replication response message may be sent from HA13106 to SC 3108 at 3132. At 3136, HA13106 may add a “forward to REPLICATOR” message into the BID1 and update the binding table at 3142 (e.g., add a tunnel to the REPLICATOR IP address).
After receiving the replication ack message from UE13104, SC 3108 may send a replication request message to REPLICATOR 3110 at 3134. At 3138, REPLICATOR 3110 may prepare to replicate data. A replication ack message may be sent from the REPLICATOR 3110 to SC 3108 at 3140. After receiving the replication ack message at 3140, SC 3108 may send a replication response message to HA23112 at 3144. HA23112 may send a replication response message (e.g., MIP replication response message) to UE23114 at 3146. At 3148, UE23114 may prepare for receiving data (e.g., start an application for receiving and/or using the data).
At 3150, CN 3102 may send data to HA13106. HA13106 may forward the data to UE13104 at 3152 and UE13104 may send a data ack to CN 3102 at 3160. HA13106 may send data to REPLICATOR 3110 at 3154. For example the data may be sent to REPLICATOR 3110 for replication to UE23114. After REPLICATOR 3110 has received the data, it may send a data ack to HA13106 at 3162. At 3156, the data may be sent from REPLICATOR 3110 to HA23112. HA23112 may forward the data to UE23114 at 3158. After receiving the data at 3158, UE23114 may send a data ack to REPLICATOR 3110 at 3164.
As shown in
MIP_BindingUpdate( ) or the like may support a replication option, as illustrated in
MIP_ReplicationReq(identifier, application, application's specific data) or the like may be used to carry application information to prepare the targets for reception of the replicated data. MIP_ReplicationReq(identifier, application, application's specific data) or the like may also be used to request replication from another UE.
MIP_ReplicationRsp(identifier, status, application, application's specific data) or the like may be used to respond to a replication request. Additionally, MIP_ReplicationRsp(identifier, status, application, application's specific data) or the like may be used to carry application information to prepare the targets for the reception of replicated data, such as when a request may be sent from a target UE, as illustrated in
MIP_ReplicationInd(identifier, from_IP_address) or the like may be used by a target UE to request replication from another UE.
MIP_ReplicationAck(identifier, status, application, application's specific data) or the like may be used to respond to a replication indication. Additionally, MIP_ReplicationAck(identifier, status, application, application's specific data) or the like may be used to carry application information to prepare the targets for the reception of the replicated data.
As illustrated in
As shown in
The communications systems 3400 may also include a base station 3414a and a base station 3414b. Each of the base stations 3414a, 3414b may be any type of device configured to wirelessly interface with at least one of the WTRUs 3402a, 3402b, 3402c, 3402d to facilitate access to one or more communication networks, such as the core network 3406, the Internet 3410, and/or the networks 3412. By way of example, the base stations 3414a, 3414b may be a base transceiver station (BTS), a Node-B, an eNode B, a Home Node B, a Home eNode B, a site controller, an access point (AP), a wireless router, and the like. While the base stations 3414a, 3414b are each depicted as a single element, it will be appreciated that the base stations 3414a, 3414b may include any number of interconnected base stations and/or network elements.
The base station 3414a may be part of the RAN 3404, which may also include other base stations and/or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. The base station 3414a and/or the base station 3414b may be configured to transmit and/or receive wireless signals within a particular geographic region, which may be referred to as a cell (not shown). The cell may further be divided into cell sectors. For example, the cell associated with the base station 3414a may be divided into three sectors. Thus, in one embodiment, the base station 3414a may include three transceivers, i.e., one for each sector of the cell. In another embodiment, the base station 3414a may employ multiple-input multiple output (MIMO) technology and, therefore, may utilize multiple transceivers for each sector of the cell.
The base stations 3414a, 3414b may communicate with one or more of the WTRUs 3402a, 3402b, 3402c, 3402d over an air interface 3416, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 3416 may be established using any suitable radio access technology (RAT).
More specifically, as noted above, the communications system 3400 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. For example, the base station 3414a in the RAN 3404 and the WTRUs 3402a, 3402b, 3402c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 3416 using wideband CDMA (WCDMA). WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and/or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink Packet Access (HSDPA) and/or High-Speed Uplink Packet Access (HSUPA).
In another embodiment, the base station 3414a and the WTRUs 3402a, 3402b, 3402c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 3416 using Long Term Evolution (LTE) and/or LTE-Advanced (LTE-A).
In other embodiments, the base station 3414a and the WTRUs 3402a, 3402b, 3402c may implement radio technologies such as IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.
The base station 3414b in
The RAN 3404 may be in communication with the core network 3406, which may be any type of network configured to provide voice, data, applications, and/or voice over internet protocol (VoIP) services to one or more of the WTRUs 3402a, 3402b, 3402c, 3402d. For example, the core network 3406 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and/or perform high-level security functions, such as user authentication. Although not shown in
The core network 3406 may also serve as a gateway for the WTRUs 3402a, 3402b, 3402c, 3402d to access the PSTN 3408, the Internet 3410, and/or other networks 3412. The PSTN 3408 may include circuit-switched telephone networks that provide plain old telephone service (POTS). The Internet 3410 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and the internet protocol (IP) in the TCP/IP internet protocol suite. The networks 3412 may include wired or wireless communications networks owned and/or operated by other service providers. For example, the networks 3412 may include another core network connected to one or more RANs, which may employ the same RAT as the RAN 3404 or a different RAT.
Some or all of the WTRUs 3402a, 3402b, 3402c, 3402d in the communications system 3400 may include multi-mode capabilities, i.e., the WTRUs 3402a, 3402b, 3402c, 3402d may include multiple transceivers for communicating with different wireless networks over different wireless links. For example, the WTRU 3402c shown in
The processor 3418 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Array (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. The processor 3418 may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables the WTRU 3402 to operate in a wireless environment. The processor 3418 may be coupled to the transceiver 3420, which may be coupled to the transmit/receive element 3422. While
The transmit/receive element 3422 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 3414a) over the air interface 3416. For example, in one embodiment, the transmit/receive element 3422 may be an antenna configured to transmit and/or receive RF signals. In another embodiment, the transmit/receive element 3422 may be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example. In yet another embodiment, the transmit/receive element 3422 may be configured to transmit and receive both RF and light signals. It will be appreciated that the transmit/receive element 3422 may be configured to transmit and/or receive any combination of wireless signals.
In addition, although the transmit/receive element 3422 is depicted in
The transceiver 3420 may be configured to modulate the signals that are to be transmitted by the transmit/receive element 3422 and to demodulate the signals that are received by the transmit/receive element 3422. As noted above, the WTRU 3402 may have multi-mode capabilities. Thus, the transceiver 3420 may include multiple transceivers for enabling the WTRU 3402 to communicate via multiple RATs, such as UTRA and IEEE 802.11, for example.
The processor 3418 of the WTRU 3402 may be coupled to, and may receive user input data from, the speaker/microphone 3424, the keypad 3426, and/or the display/touchpad 3428 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit). The processor 3418 may also output user data to the speaker/microphone 3424, the keypad 3426, and/or the display/touchpad 3428. In addition, the processor 3418 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 3430 and/or the removable memory 3432. The non-removable memory 3430 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 3432 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 3418 may access information from, and store data in, memory that is not physically located on the WTRU 3402, such as on a server or a home computer (not shown).
The processor 3418 may receive power from the power source 3434, and may be configured to distribute and/or control the power to the other components in the WTRU 3402. The power source 3434 may be any suitable device for powering the WTRU 3402. For example, the power source 3434 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.
The processor 3418 may also be coupled to the GPS chipset 3436, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 3402. In addition to, or in lieu of, the information from the GPS chipset 3436, the WTRU 3402 may receive location information over the air interface 3416 from a base station (e.g., base stations 3414a, 3414b) and/or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 3402 may acquire location information by way of any suitable location-determination method while remaining consistent with an embodiment.
The processor 3418 may further be coupled to other peripherals 3438, which may include one or more software and/or hardware modules that provide additional features, functionality and/or wired or wireless connectivity. For example, the peripherals 3438 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, and the like.
As shown in
The core network 3406 shown in
The RNC 3442a in the RAN 3404 may be connected to the MSC 3446 in the core network 3406 via an IuCS interface. The MSC 3446 may be connected to the MGW 3444. The MSC 3446 and the MGW 3444 may provide the WTRUs 3402a, 3402b, 3402c with access to circuit-switched networks, such as the PSTN 3408, to facilitate communications between the WTRUs 3402a, 3402b, 3402c and traditional land-line communications devices.
The RNC 3442a in the RAN 3404 may also be connected to the SGSN 3448 in the core network 3406 via an IuPS interface. The SGSN 3448 may be connected to the GGSN 3450. The SGSN 3448 and the GGSN 3450 may provide the WTRUs 3402a, 3402b, and 3402c with access to packet-switched networks, such as the Internet 3410, to facilitate communications between and the WTRUs 3402a, 3402b, 3402c and IP-enabled devices.
As noted above, the core network 3406 may also be connected to the networks 3412, which may include other wired or wireless networks that are owned and/or operated by other service providers.
The RAN 3404 may include eNode-Bs 3460a, 3460b, and 3460c, though it will be appreciated that the RAN 3404 may include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs 3460a, 3460b, and 3460c may each include one or more transceivers for communicating with the WTRUs 3402a, 3402b, 3402c over the air interface 3416. In one embodiment, the eNode-Bs 3460a, 3460b, and 3460c may implement MIMO technology. Thus, the eNode-B 3460a, for example, may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 3402a.
Each of the eNode-Bs 3460a, 3460b, and 3460c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the uplink and/or downlink, and the like. As shown in
The core network 3406 shown in
The MME 3462 may be connected to each of the eNode-Bs 3462a, 3462b, and 3462c in the RAN 3404 via an Si interface and may serve as a control node. For example, the MME 3462 may be responsible for authenticating users of the WTRUs 3402a, 3402b, and 3402c, bearer activation/deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 3402a, 3402b, 3402c, and the like. The MME 3462 may also provide a control plane function for switching between the RAN 3404 and other RANs (not shown) that employ other radio technologies, such as GSM or WCDMA.
The serving gateway 3464 may be connected to each of the eNode Bs 3460a, 3460b, and 3460c in the RAN 3404 via the Si interface. The serving gateway 3464 may generally route and forward user data packets to/from the WTRUs 3402a, 3402b, and 3402c. The serving gateway 3464 may also perform other functions, such as anchoring user planes during inter-eNode B handovers, triggering paging when downlink data is available for the WTRUs 3402a, 3402b, and 3402c, managing and storing contexts of the WTRUs 3402a, 3402b, 3402c, and the like.
The serving gateway 3464 may also be connected to the PDN gateway 3466, which may provide the WTRUs 3402a, 3402b, and 3402c with access to packet-switched networks, such as the Internet 3410, to facilitate communications between the WTRUs 3402a, 3402b, 3402c and IP-enabled devices.
The core network 3406 may facilitate communications with other networks. For example, the core network 3406 may provide the WTRUs 3402a, 3402b, 3402c with access to circuit-switched networks, such as the PSTN 3408, to facilitate communications between the WTRUs 3402a, 3402b, and 3402c and traditional land-line communications devices. For example, the core network 3406 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the core network 3406 and the PSTN 3408. In addition, the core network 3406 may provide the WTRUs 3402a, 3402b, and 3402c with access to the networks 3412, which may include other wired or wireless networks that are owned and/or operated by other service providers.
As shown in
The air interface 3416 between the WTRUs 3402a, 3402b, and 3402c and the RAN 3404 may be defined as an R1 reference point that implements the IEEE 802.16 specification. In addition, each of the WTRUs 3402a, 3402b, and 3402c may establish a logical interface (not shown) with the core network 3406. The logical interface between the WTRUs 3402a, 3402b, 3402c and the core network 3406 may be defined as an R2 reference point, which may be used for authentication, authorization, IP host configuration management, and/or mobility management.
The communication link between each of the base stations 3480a, 3480b, and 3480c may be defined as an R8 reference point that includes protocols for facilitating WTRU handovers and the transfer of data between base stations. The communication link between the base stations 3480a, 3480b, and 3480c and the ASN gateway 3482 may be defined as an R6 reference point. The R6 reference point may include protocols for facilitating mobility management based on mobility events associated with each of the WTRUs 3402a, 3402b, 3402c.
As shown in
The MIP-HA may be responsible for IP address management, and may enable the WTRUs 3402a, 3402b, and 3402c to roam between different ASNs and/or different core networks. The MIP-HA 3484 may provide the WTRUs 3402a, 3402b, and 3402c with access to packet-switched networks, such as the Internet 3410, to facilitate communications between the WTRUs 3402a, 3402b, and 3402c and IP-enabled devices. The AAA server 3486 may be responsible for user authentication and for supporting user services. The gateway 3488 may facilitate interworking with other networks. For example, the gateway 3488 may provide the WTRUs 3402a, 3402b, and 3402c with access to circuit-switched networks, such as the PSTN 3408, to facilitate communications between the WTRUs 3402a, 3402b, and 3402c and traditional land-line communications devices. In addition, the gateway 3488 may provide the WTRUs 3402a, 3402b, and 3402c with access to the networks 3412, which may include other wired or wireless networks that are owned and/or operated by other service providers.
Although not shown in
Although features and elements are described above in particular combinations, one of ordinary skill in the art will appreciate that each feature or element can be used alone or in any combination with the other features and elements. In addition, the methods described herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.
This application claims the benefit of U.S. Provisional Patent Application Ser. No. 61/333,791, filed May 12, 2010, and U.S. Provisional Patent Application Ser. No. 61/357,465, filed Jun. 22, 2010, the contents of which are hereby incorporated by reference herein.
| Number | Date | Country | |
|---|---|---|---|
| 61333791 | May 2010 | US | |
| 61357465 | Jun 2010 | US |
