Systems and Methods for Personalizing and/or Tailoring A Service Interface

• US 20150142986A1
• Filed: 04/27/2013
• Published: 05/21/2015
• Est. Priority Date: 04/27/2012
• Status: Active Grant

• Current Assignee: InterDigital Patent Holdings, Inc. (InterDigital, Inc.)
• Original Assignee: InterDigital Patent Holdings, Inc. (InterDigital, Inc.)
• Inventors: Reznik, Alexander, Shah, Yogendra C., Zeira, Eldad M., Pragada, Ravikumar V., Raghothaman, Balaji, Vanganuru, Kiran K., Sternberg, Gregory S., De Foy, Xavier, Choyi, Vinod Kumar
• Granted Patent: US 11,265,383 B2
• Time in Patent Office: Days
• US Class Current: 709/228
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04L 67/141 Setup of application sessions admission control or resource allocation in data switching networks H04L47/70
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 69/24 Negotiation of communication capabilities
• CPC Class Codes: H04W 12/08 Access security
• CPC Class Codes: H04W 4/50 Service provisioning or reconfiguring

Abstract

Systems and methods for enabling proximity services to be delivered as part of an application service and/or for providing tailored services and/or a differential quality of service (QoS) to a flow may be disclosed. For example, a temporary service name between an application and a server such as a D2D server may be established such that a UE and/or network may execute such a service at a later time without later involvement by the application and/or without exchanging credentials for the application with the network and vice versa.

Claims

1. A method of discovering devices to enable a session with an application server, the method comprising:

receiving a request to start a session for a service provided by the application server from a first device;

negotiating parameters of the session for the service with the network in response to the request including a temporary service name for the session; and

sending the temporary service name in response to the negotiated parameters to at least the first device requesting the session, the temporary service name being used by the first device to start the session for the service provided by the application server via the network.

2. The method of claim 1, wherein negotiating the parameters of the session or service in response to the request further comprises:

sending a request to start the session to the network;

establishing an agreement with the network for the parameters including the temporary service name; and

receiving the temporary service name.

3. The method of claim 2, wherein the temporary service name is received from at least one of the following:

the network, a proximity service (ProSe) server, or a device to device (D2D) server.

4. The method of claim 2, wherein the agreement for the parameters further comprises at least one of the following:

a user or device identity;

a billing or charging reference;

service security parameters;

service quality of service (QoS) requirements;

device to device (D2D) usage;

wireless local access network (WLAN) usage;

localization parameters;

a time restriction;

a nature of data exchanged for the service;

a link or interface type including device to device (D2D) or (ProSe);

or a designator for the individual or groups of users of the service.

5. The method of claim 1, further comprising:

receiving a request to join the session from a second device;

determining whether the second device is authorized to join the session; and

sending the temporary service name to the second device such that the second device can join the session with the first device when the second device is authorized to join the session.

6. The method of claim 1, further comprising:

receiving a request for a policy associated with the temporary service name; and

sending a policy associated with the temporary service name in response to the request for the policy.

7. The method of claim 1, further comprising sending a policy associated with the temporary service name via a push to the first device.

8. The method of claim 1, wherein the temporary service name for the session comprises at least one of the following:

an open identifier (OpenID) managed via a device to device (D2D) interface or a proximity service (ProSe) interface.

9. The method of claim 1, wherein the temporary service name for the session comprises a combination of a name for the service, a name of a user access group, and a name of the session for the service and user access group.

10. The method of claim 1, wherein the temporary service name is generated in the negotiation of the parameters via at least one of the following:

a hash or a key derivation function.

11. The method of claim 1, wherein the service comprises a device to device (D2D) service or a proximity service (ProSe) service.

12. The method of claim 1, wherein the temporary service name is mapped to a plurality of identifiers associated with the application.

13. A wireless transmit and receive unit (WTRU) for enabling a session with an application server via a network, the WTRU configured to:

send a request to join a session for a service provided by the application server;

receive a temporary service name in response to the request; and

join the session of the service provided by the application server via the network based on the temporary service name.

14. The WTRU of claim 13, wherein the WTRU is further configured to establish an internet protocol (IP) bearer with the network.

15. The WTRU of claim 13, wherein the WTRU is further configured to establish device to device (D2D) network service access with the network.

16. The WTRU of claim 13, wherein the WTRU is further configured to register the temporary service name to join the session.

17. The WTRU of claim 16, wherein the WTRU is further configured to:

determine whether the WTRU includes a policy for the service based on the registered temporary service name;

send a request for the policy when the WTRU does not the policy; and

receive the policy from the application server in response to the request for the policy; and

store the policy in the WTRU.

18. The WTRU of claim 16, wherein the WTRU is further configured to:

receive a policy for the service based on the registered temporary service name via a push from the application server; and

store the policy in the WTRU.

19. The WTRU of claim 16, wherein the WTRU is further configured to start an application associated with the service based on the registered temporary service name to join the session for the service.

20. The WTRU of claim 19, wherein the WTRU is further configured to:

detect a flow associated with the service during the session; and

apply the policy to the flow.

21. The WTRU of claim 13, wherein the temporary service name for a session comprises a combination of a name for the service, a name of a user access group, and a name of the session for the service and user access group.

22. The WTRU of claim 13, wherein the temporary service name is based on at least one of the following:

a hash or a key derivation function.

23. A method of discovering devices to enable a session with an application server via a network, the method comprising:

receiving a request to start a service provided by the application server from the application server;

negotiating parameters for the service with the application provider in response to the request including a temporary service name for the service; and

sending the temporary service name in response to the negotiated parameters to the application server, the application server being configured to broadcast the temporary service name to one or more devices on the network to join a session associated with the service provided by the application server via the network.

24. The method of claim 23, wherein the temporary service name for the session comprises at least one of the following:

an open identifier (OpenID) managed via a device to device (D2D) interface or a proximity service (ProSe) interface.

25. The method of claim 23, wherein the temporary service name for the session comprises a combination of a name for the service, a name of a user access group, and a name of the session for the service and user access group.

26. The method of claim 23, wherein the temporary service name is generated in the negotiation of the parameters via at least one of the following:

a hash or a key derivation function.

27. The method of claim 23, wherein negotiating the parameters of the session or service in response to the request further comprises:

receiving a request to start the session from the application server;

establishing an agreement with the application server for the parameters including the temporary service name; and

sending the temporary service name to the server.

28. The method of claim 27, wherein the agreement for the parameters further comprises at least one of the following:

a user or device identity;

a billing or charging reference;

service security parameters;

service quality of service (QoS) requirements;

device to device (D2D) usage;

wireless local access network (WLAN) usage;

localization parameters;

a time restriction;

a nature of data exchanged for the service;

a link or interface type including device to device (D2D) or ProSe;

or a designator for the individual or groups of users of the service.