Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W48/00—Access restriction; Network selection; Access point selection
  • H04W48/16—Discovering, processing access restriction or access information
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
  • H04W4/50—Service provisioning or reconfiguring
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W48/00—Access restriction; Network selection; Access point selection
  • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
  • H04W88/08—Access point devices
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W48/00—Access restriction; Network selection; Access point selection
  • H04W48/20—Selecting an access point
• • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
  • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
  • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
  • Y02D30/00—Reducing energy consumption in communication networks
  • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

• the present invention relates to wireless communications, and, in particular embodiments, to systems and methods for subscription and policy provisioning.
• Wi-Fi wireless fidelity
• a mobile device may engage in an On-line Sign Up (OSU) process to gain access to a Wi-Fi network.
• OSU On-line Sign Up
• the OSU process may allow the mobile device to subscribe to the network as well as to be provisioned network access credentials for secure access.
• Different protocols may be used for OSU depending on the capabilities of the mobile station as well as the base station. Accordingly, mechanisms for advertising and selecting OSU protocols are needed so that mobile devices may access Wi-Fi networks.
• a method for user subscription and provisioning in a wireless network includes transmitting a message comprising protocol capability information to one or more mobile stations.
• the protocol capability information specifies that a Wi-Fi AP is capable of using both an Open Mobile Alliance (OMA) - Device Management (OMA-DM) protocol and a Simple Object Access Protocol (SOAP) - Extensible Markup Language (SOAP-XML) protocol when establishing network access for the one or more mobile stations.
• OMA Open Mobile Alliance
• SOAP Simple Object Access Protocol
• SOAP-XML Extensible Markup Language
• another method for user subscription and provisioning in a wireless network includes receiving a broadcast message from a wireless fidelity (Wi-Fi) access point (AP).
• the broadcast message includes protocol capability information specifying that a Wi-Fi AP is capable of using both an
• OMA Open Mobile Alliance
• OMA-DM Device Management
• SOAP SOAP-XML
• SOAP-XML Extensible Markup Language
• a method for Wi-Fi local area network (WLAN) discovery includes sending an access network discovery and selection function (ANDSF) management object (MO) to a user equipment (UE) when the UE roams into a coverage area.
• the ANDSF MO includes a WLAN access type indication specifying at least one type of WLAN that is preferred by a network operator for UE connection.
• An apparatus for performing this method is also provided.
• FIG. 1 illustrates a diagram of a wireless network for communicating data
• FIG. 2 illustrates a diagram of an OSU Architecture
• FIG. 3 illustrates a flowchart of an embodiment method for performing user subscription and provisioning
• FIG. 4 illustrates a flowchart of another embodiment method for performing user subscription and provisioning
• FIG. 5 illustrates a table of OSU method list subfield values
• FIG. 6 illustrates a diagram of another embodiment OSU Provider field
• FIG. 7 illustrates a diagram of an embodiment OSU Provider field
• FIG. 8 illustrates a diagram of an embodiment ANQP message
• FIG. 9 illustrates a diagram of another embodiment ANQP message
• FIG. 10 illustrates a diagram of a terminal interacting with a server through an interface
• FIG. 11 illustrates a diagram of a terminal interacting with a home server and a visiting server through an interface
• FIG. 12 illustrates a block diagram of an embodiment communications device
• FIG. 13 illustrates a block diagram of an embodiment processing system.
• Wi-Fi access points (APs) and mobile devices typically perform OSU using either an Open Mobile Alliance (OMA) - Device Management (OMA-DM) protocol or a Simple Object Access Protocol (SOAP) - Extensible Markup Language (SOAP-XML) protocol.
• OMA Open Mobile Alliance
• SOAP Simple Object Access Protocol
• SOAP-XML Extensible Markup Language
• the protocol used for OSU may depend on the capability of the mobile stations and/or Wi-Fi APs.
• OMA-DM enabled mobile stations may seek Wi-Fi access points (APs) that support OMA-DM protocol
• SOAP-XML enabled mobile stations may seek Wi-Fi APs that support SOAP-XML protocol.
• vl .02 allow Wi-Fi APs to advertise their support of either the OMA-DM protocol or the SOAP- XML protocol (but not both) via broadcast messages (e.g., beacons, etc.). Accordingly, mobile stations may monitor broadcast messages while roaming between Wi-Fi hotspots in order to identify Wi-Fi APs that support their enabled OSU protocol.
• Wi-Fi APs that support both OMA-DM and SOAP-XML protocols may be unable to fully advertise their OSU capabilities using the conventional mechanisms defined in Hotspot 2.0, rel. 2, vl .02, e.g., which allow the Wi-Fi APs to advertise support of either OMA-DM protocol or the SOAP-XML protocol, but not both.
• Wi-Fi APs may choose between advertising their OMA-DM capability (and foregoing SOAP-XML enabled mobile stations) or their SOAP-XML capability (and foregoing OMA-DM enabled mobile stations). Accordingly, mechanisms for allowing Wi-Fi APs to advertise their support of both OMA-DM and SOAP-XML protocols are desired.
• the Wi- Fi AP may broadcast a message comprising an OSU method list subfield that indicates that the Wi-Fi AP supports both OMA-DM and SOAP-XML protocols. Accordingly, mobile stations receiving the broadcast message may recognize that the Wi-Fi AP supports both OMA-DM and SOAP-XML protocols.
• the broadcast message may be an Access Network Query Protocol (ANQP) message, a beacon message, or some other generic advertisement services (GAS) message.
• ANQP Access Network Query Protocol
• GAS generic advertisement services
• Additional aspects of this disclosure provide a WLAN access type indication that specifies a WLAN that is preferred by a network operator for UE connection. For example, a UE may roam into a coverage area having multiple WLANs.
• the WLAN access type indication provided herein allows the network operator to specify which of the WLAN access types (e.g., passpoint, non-passpoint, vendor specific, etc.) is preferred for UE connection.
• the WLAN access type indication may be included in an access network discovery and selection function (ANDSF) management object (MO) message.
• ANDSF access network discovery and selection function
• MO management object
• FIG. 1 illustrates a network 100 for communicating data.
• the network 100 comprises an access point (AP) 110 having a coverage area 112, a plurality of user equipments
• the AP 110 may comprise any component capable of providing wireless access by, inter alia, establishing uplink (dashed line) and/or downlink (dotted line) connections with the UEs 120, such as a base station, an enhanced base station (eNB), a femtocell, and other wirelessly enabled devices.
• the UEs 120 may comprise any component capable of establishing a wireless connection with the AP 110.
• the backhaul network 130 may be any component or collection of components that allow data to be exchanged between the AP
• FIG. 2 illustrates an Online Signup
• Architecture 200 having a Wi-Fi hotspot 201 and a plurality of service provider networks 202.
• a user uses the Wi-Fi hotspot 201 to access the service provider networks 202.
• FIG. 3 illustrates a method 300 for performing user subscription and provisioning in a wireless network, as may be performed by a Wi-Fi AP.
• the method 300 begins with step 310, where the Wi-Fi AP sets an OSU method list subfield to indicate that the Wi-Fi AP supports both OMA-DM and SOAP-XML protocols. Thereafter, the method 300 proceeds to step 320, where the Wi-Fi AP transmits a message comprising the OSU method list subfield to one or more mobile stations. The mobile stations may recognize that the Wi-Fi AP supports both
• the message transmitted in step 320 is a broadcast message, such as an (ANQP) message, a beacon message, or a generic advertisement services (GAS) message.
• the message transmitted in step 320 is a probe response message.
• FIG. 4 illustrates a method 400 for performing user subscription and provisioning in a wireless network, as may be performed by a mobile station.
• the method 400 begins with step 410, where the mobile station receives a message comprising an OSU method list sub field from a Wi-Fi AP. Thereafter, the method 400 proceeds to step 420, where the mobile station determines that the Wi-Fi AP supports both OMA-DM and SOAP-XML protocols in accordance with OSU method list subfield.
• the message may be a broadcast message, e.g., an ANQP message, a beacon message, a GAS message, or a unicast message, e.g., a probe response message.
• the OSU method list subfield may be transmitted by any mobile device (e.g., a mobile station, relay, etc.) to advertise the OMA- DM and SOAP-XML protocol capabilities of that mobile device, or of another device.
• a mobile station may communicate an OSU method list subfield to convey that the mobile station is OMA-DM and SOAP-XML enabled.
• a Wi-Fi AP may communicate the OSU method list subfield to convey that a policy server (or group of policy servers) connected to the Wi-Fi AP support OMA-DM and SOAP-XML protocols.
• OSU servers may be capable of providing only one protocol (e.g., either OMA-DM or SOAP-XML) for online sign up, and therefore may be unable to support both OMA-DM enabled and SOAP-XML enabled mobile devices.
• OMA-DM may be unable to support SOAP-XML enabled mobile devices
• SOAP-XML may be unable to support OMA-DM enabled mobile devices.
• a mechanism for allowing an OSU to concurrently support both OMA- DM and SOAP-XML capable devices is desired.
• Another issue is that there is no information about method for policy provisioning, which is problematic in so far as a device's capability may not match that of the policy server.
• a policy server providing OMA-DM for policy provisioning may be unable to provide a SOAP-XML capable device with policy information after the SOAP-XML capable device obtains a subscription from the OSU. Without obtaining the policy information, the device may be unable to access the service. As such, a mechanism for communicating provisioning information from a policy server to a device is desired.
• the OSU server and policy server may support multiple protocols for subscription and policy provisioning, which may allow the servers to support a diverse set of devices (e.g., devices with different capabilities).
• information specifying the capabilities supported by the OSU/policy server is transferred from the network to a device via one or more Access Network Query Protocol (ANQP) messages.
• ANQP Access Network Query Protocol
• FIG. 5 illustrates a table identifying a plurality of OSU method list subfield values for identifying OSU protocol capabilities of a device (e.g., Wi-Fi AP, policy server, a mobile station, etc.).
• a value (X) may be included in an OSU method list subfield to indicate support of both OMA-DM and SOAP-XML protocols.
• a device receiving such a message e.g., an ANQP message specifying a value that indicates both OMA-DM and SOAP-XML are supported
• an OSU server may identify which method/protocol is supported by the device when it receives a message from the device. Typically, this message may be the first message of the OSU message exchange.
• the OSU server may identify the method/protocol in accordance with the format of the message and/or an indicator in the message indicating which method/protocol is used by the device.
• the server may identify which method/protocol is supported by the device via a previous procedure (for example an ANQP query message).
• the OSU server may have different uniform resource identifiers (URIs) depending on which protocols it supports.
• URIs uniform resource identifiers
• an OSU server supporting OMA- DM may use a first URI (URI-1), while an OSU server supporting SOAP-XML may use a second URI (URI-2).
• An OSU server supporting both OMA-DM and SOAP-XML may have a different URI (e.g., URI-X).
• FIG. 6 illustrates an OSU Provider field 600 for advertising protocol capabilities of multiple OSU servers.
• the OSU provider field 600 includes an OSU server URI 2 Length field, an OSU Server URI 2 field (optional), and an OSU method 2 field (optional). Fields denoted as optional may be omitted/excluded from the OSU provider field 600, e.g., when the OSU server URI 2 length field has a value of zero.
• subscription may include a method for policy provisioning, which could be shown as 'Subscription/Policy/PolicyUpdate/OMA-DM/URI' or a
• the device When the device gets such information, it can access the correct URI based on the protocol supported by the device. If the server supports both methods/techniques for a single URI, then the device may negotiate with the server to determine which method/protocol will be used for policy provisioning. In an embodiment, the network may provide policy provisioning
• FIG. 7 illustrates an ANQP message, a beacon message, or some other generic advertisement services (GAS) messages.
• GAS generic advertisement services
• the policy provisioning method field may identify the protocol capabilities (e.g., OMA-DM and/or SOAP-XML) in a manner similar to that discussed above.
• the policy provisioning method field may indicate whether the policy provisioning protocol is the same as the OSU protocol. For instance, the policy provisioning information may indicate a value of zero when the policy provisioning method/protocol is the same as the OSU protocol, and a value of one when the policy
• provisioning method/protocol is different than the OSU protocol.
• a device may determine whether its protocol capability is supported by a policy server and/or Wi-Fi AP. If so, the device may sign up with the corresponding OSU server. If not, the device may look for a server or Wi- Fi AP that supports its protocol capability.
• FIG. 8 illustrates an ANQP message 800 comprising a Hotspot Policy Providers List format
• FIG. 9 illustrates an ANQP message 900 comprising a Policy Provider field format.
• the ANQP messages 800 and 900 may be communicated between Wi-Fi APs and Wi-Fi mobile stations (Wi-Fi STAs).
• Wi-Fi Alliance is defining a Hotspot 2.0 specification to help dual or single mode Wi-Fi devices select the appropriate WLAN when roaming into a coverage area having multiple WLANs.
• Aspects of this disclosure provide a WLAN access type indication in an ANDSF management object (MO) in order to allow the network operator to specify which WLAN or WLAN access type is preferred for UE connection.
• MO ANDSF management object
• the Wi-Fi Alliance defines a WFA management object (MO) (subscription MO) to store and manage these network selection operator policies.
• MO WFA management object
• 3 GPP also defines several mechanisms for a mobile device to decide and select the WLAN in a fixed network.
• One mechanism is to statically preconfigure policies on the user equipment (UE).
• Another is to dynamically provision policies via an access network discovery and selection function (ANDSF) server within the network.
• the policies are dynamically provisioned using an ANDSF MO, which allows the server to store and manage the operator's policies.
• FIG. 10 illustrates a UE interacting with an ANDSF through an S14 interface (e.g., an interface for IP level signaling) to obtain a network selection policy from the network.
• an S14 interface e.g., an interface for IP level signaling
• One of the pieces of information provided by the A DSF server to the UE to help perform access network selection is the inter-system routing policy (ISRP) information, which includes validity conditions, or conditions that indicate when a provided policy is valid.
• ISRP inter-system routing policy
• the validity conditions may include one or more filter rules, each of which identifying a prioritized list of access technologies/access networks that can be used by the UE (when available) to route traffic matching IP filters on an APN.
• a filter rule also identify which radio access technologies or networks that are restricted for traffic matching the IP filter on an APN.
• a filter rule may specify that a WLAN is not allowed for traffic flows being communicating using real time transport protocol (RTP) or RTP control protocol (RTCP) on a given APN.
• RTP real time transport protocol
• RTCP RTP control protocol
• FIG. 11 illustrates a UE obtaining an operator policy from an H- ANDSF server and/or a V-ANDSF server.
• the UE may follow the visited operator policy, as defined in 3GPP Technical Specification (TS) 23.402, which is incorporated herein by reference as if reproduced in its entirety.
• TS 3GPP Technical Specification
• Hotspot 2.0 After the deployment of Hotspot 2.0, it is possible to have a legacy access point (AP) and a hotspot 2.0 in the same area or the same network. Compared to a legacy AP, Hotspot 2.0 generally is more powerful and can provide higher quality service to customers. Accordingly, operators may want to provide different services to different customers. For instance, an operator can provide high rank customers with hotspots 2.0 and ensure they are not interfered with by lower rank customers who are directed to the legacy AP. Another problem arises when the current ANDSF server or other policies cannot distinguish between these two different WLANs for network selection.
• aspects of this disclosure provide mechanisms for supporting coexisting Hotspot 2.0 and non-hotspot networks. More specifically, embodiments of this disclosure provide indicators for a network to guide and control a mobile terminal to correctly select the appropriate Wi-Fi AP and obtain the right network selection policy from the visited network. An embodiment creates three new indicators from the network to the terminal. A first indication indicates whether a terminal needs to receive more network selection policy from a non-3 GPP visited network. A second indication from the network indicates the policy provision mechanism it is supporting. A third indication from the network indicates the policy server it is supporting.
• Embodiments described herein create a new WLAN access type indication for ANDSF policy (e.g., non- hotspot (HS), HS, and vendor specific) and enhance collaboration between ANDSF MO and WFA MO.
• ANDSF policy e.g., non- hotspot (HS), HS, and vendor specific
• Embodiments also provide operators with more flexibility and management capabilities for user mobility between Hotspot and legacy APs, as well as give operators more control over UE mobility between Wi-Fi and cellular networks. Aspects of this disclosure also provide better user experiences and increase operator revenue.
• Wi-Fi and cellular networks and devices e.g., Wi-Fi access point/access controllers, Wi-Fi plus cellular dual mode terminals, terminals with hotspot 2.0 support, ANDSF server, ANQP server, etc.
• a problem may arise if a visited operator only supports Wi-Fi service with a Wi-Fi Alliance (WFA) MO, as the visited operator network may include a WFA server while lacking a V-ANDSF server.
• WFA Wi-Fi Alliance
• aspects of this disclosure add an indicator in the ANDSF MO to indicate whether the UE needs to check with the visited WLAN for additional WFA specific network selection policy. For example, in ANDSF's network work selection policy, when the ANDSF server suggests the UE choose WLAN, it uses an indicator to tell the UE whether the UE should check the WFA MO for operator policy.
• indicators are included in ANQP or HS2.0 beacon signals (or HS2.0 probe response responses) to indicate a policy provision mechanism supported by the Hotspot (e.g., OMA-DM, SOAP_XML, etc.) as well as to indicate policy provisioning server provided by the operator, e.g., an ANDSF server, a WFA server, etc.
• a policy provision mechanism supported by the Hotspot e.g., OMA-DM, SOAP_XML, etc.
• policy provisioning server e.g., an ANDSF server, a WFA server, etc.
• aspects of this disclosure create a type access indicator for WLAN in ANDSF and HS2.0 policy, such as passpoint WLAN, non-passpoint WLAN, vendor-specific WLAN, and the like.
• the type access allows the operator to demonstrate a preference between different types of WLANs for network selection if both a Hotspot 2.0 capable hotspot (passpoint WLAN) and a non-HS2.0 capable hotspot exist in the same access location.
• a vendor specific WLAN may be used for operator or vendor specific usage, such as testing, trial or proprietary implementation, etc.
• the communications device 1200 may include a processor 1204, a memory 1206, a cellular interface 1210, a supplemental interface 1212, and a backhaul interface 1214, which may (or may not) be arranged as shown in FIG. 12.
• the processor 1204 may be any component capable of performing computations and/or other processing related tasks
• the memory 1206 may be any component capable of storing programming and/or instructions for the processor 1204.
• the cellular interface 1210 may be any component or collection of components that allows the communications device 1200 to communicate using a cellular signal, and may be used to receive and/or transmit information over a cellular connection of a cellular network.
• the supplemental interface 1212 may be any component or collection of components that allows the
• the communications device 1200 to communicate data or control information via a supplemental protocol.
• the supplemental interface 1212 may be a non-cellular wireless interface for communicating in accordance with a Wireless-Fidelity (Wi-Fi) or Bluetooth protocol.
• Wi-Fi Wireless-Fidelity
• Bluetooth Bluetooth protocol
• the supplemental interface 1212 may be a wireline interface.
• the backhaul interface 1214 may be optionally included in the communications device 1200, and may comprise any component or collection of components that allows the communications device 1200 to communicate with another device via a backhaul network.
• FIG. 13 is a block diagram of a processing system that may be used for
• the processing system may comprise a processing unit equipped with one or more input/output devices, such as a speaker, microphone, mouse, touchscreen, keypad, keyboard, printer, display, and the like.
• the processing unit may include a central processing unit (CPU), memory, a mass storage device, a video adapter, and an I/O interface connected to a bus.
• the bus may be one or more of any type of several bus architectures including a memory bus or memory controller, a peripheral bus, video bus, or the like.
• the CPU may comprise any type of electronic data processor.
• the memory may comprise any type of system memory such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), read-only memory (ROM), a combination thereof, or the like.
• the memory may include ROM for use at boot-up, and DRAM for program and data storage for use while executing programs.
• the mass storage device may comprise any type of storage device configured to store data, programs, and other information and to make the data, programs, and other information accessible via the bus.
• the mass storage device may comprise, for example, one or more of a solid state drive, hard disk drive, a magnetic disk drive, an optical disk drive, or the like.
• the processing unit also includes one or more network interfaces, which may comprise wired links, such as an Ethernet cable or the like, and/or wireless links to access nodes or different networks.
• the network interface allows the processing unit to communicate with remote units via the networks.
• the network interface may provide wireless communication via one or more transmitters/transmit antennas and one or more receiver s/receive antennas.
• the processing unit is coupled to a local-area network or a wide- area network for data processing and communications with remote devices, such as other processing units, the Internet, remote storage facilities, or the like.

Landscapes

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

Priority Applications (5)

Applications Claiming Priority (6)

Publications (1)

Family

ID=49878479

Family Applications (1)

Country Status (6)

Families Citing this family (18)

Citations (5)

Family Cites Families (16)

• 2013
  • 2013-07-02 US US13/933,358 patent/US9907014B2/en active Active
  • 2013-07-03 KR KR1020157001064A patent/KR101643681B1/ko active IP Right Grant
  • 2013-07-03 EP EP13812664.4A patent/EP2856737B1/de active Active
  • 2013-07-03 KR KR1020167019976A patent/KR101712903B1/ko active IP Right Grant
  • 2013-07-03 WO PCT/CN2013/078731 patent/WO2014005516A1/en active Application Filing
  • 2013-07-03 JP JP2015518821A patent/JP5993089B2/ja active Active
  • 2013-07-03 CN CN201380030938.1A patent/CN104396210B/zh active Active
• 2016
  • 2016-08-18 JP JP2016160472A patent/JP6209773B2/ja active Active

Patent Citations (5)

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events