JP2009536006A - Profile change for roaming in communication environment - Google Patents

Abstract

The claimed subject matter relates to systems and methods for roaming in a wireless communication environment. In one aspect, a method for roaming between networks is provided. The method includes receiving a request for network access in the visited network and receiving a profile from the home network in response to the request. Upon receipt of the profile, one or more access terminals are selectively serviced based on at least a portion of the profile.

Description

(Cross-reference of related applications)
This application is a US provisional patent entitled “A Method and Apparatus for Network Access Subsystem” filed on Aug. 14, 2006, which is incorporated herein by reference. Application 60 / 837,656, filed May 1, 2006, US Provisional Patent Application No. 60 entitled “A Method and Apparatus for Subscriber Service Framework” No. 796,704, filed May 1, 2006, United States of America entitled “A method and Apparatus for Using Subscriber Profile to Authorize Subscriber” Provisional Patent Application No. 60 / 797,010, filed May 1, 2006, “Service Quality in FLASH Network US Provisional Patent Application No. 60 / 797,029 entitled “A Method and Apparatus for Quality of Service in a Flash Network”, filed on May 1, 2006, “Method of FLASH System” US Provisional Patent Application No. 60 / 796,808 entitled “A Method and Apparatus for Flash System”, filed May 1, 2006, “A Method and Apparatus for Flash System”. US Provisional Patent Application No. 60 / 797,038 entitled “Apparatus for Connection Control Protocol” and “A Method and Apparatus for Mobility Aware Resource Control” filed on May 1, 2006. And claims the benefit of US Provisional Patent Application No. 60 / 796,653, entitled “

  The following description relates generally to communication systems, and more particularly to enabling profile changes to support services when roaming between networks.

  Communication networks such as wireless communication networks, broadband networks, and other suitable networks are utilized in connection with data transfer, where the data includes document processing files, streaming video, multimedia files, audio data, etc. Can do. When using such a network, some subscribers of the network may be provided with different quality of service (QoS) parameters from other subscribers. According to one example, a first individual is subscribed to a digital subscriber line (DSL) network, which is provided with a first upload rate and download rate, while the first individual subscribed to a DSL network. The second individual pays a different contract fee than the first individual, and the second individual is provided with different upload and download speeds. More specifically, the first subscriber pays a first fee for a download connection speed of 1 megabyte / second and the second subscriber pays a second fee for a download connection speed of 512 kilobytes / second.

  In addition, different services can be provided to network users. For example, wireless network subscribers can purchase subscriptions that enable web browsing, text message delivery and reception, voice calls, data transmission (video, images, audio clips, etc.), games, and so on. Because the delivery requirements for application flows corresponding to different services are different, it may be desirable to associate the traffic flows of different services with different QoS parameters (latency, bandwidth, etc.). While traditional communication networks only support a relatively small service set, new communication networks based on the Internet protocol allow a potentially unlimited service set. This highlights the need for improvement in controlling services and managing associated QoS support.

  Some communication networks support roaming functions, in which the subscriber gains access via a visited network that is different from the home network to which the subscriber subscribes. . In the conventional method, in this case, the visited network and the home network are based on a similar technology, and thus the visited network simply allows the subscriber to use the service provided by the subscriber's home network. Absent. However, given the possibility that a larger number of different services in a new communication network can be combined with the desire to enable roaming between networks based on potentially different technologies, there is a need to have more control over service roaming. .

Summary of the Invention

  The following presents a simplified summary in order to provide a basic understanding of some aspects of the claimed subject matter. This summary is not an exhaustive overview, and it is not intended to identify key / critical elements or to delineate the scope of the claimed subject matter. Its sole purpose is to present some concepts in a simplified form as a prelude to the more detailed description that is discussed later.

  Roaming between networks is facilitated by a changeable profile that is exchanged when the access terminal roams from the home network to the visited network. When a mobile access terminal contacts a network other than the home network by roaming, the visited network (viewed from the terminal) can request a profile that describes the service that the home network should provide. This profile can be sent to the visited network upon receipt of access authorization for services from the home network. After receiving the profile, the visited network may also selectively provide similar services specified in the profile, a subset of services specified in the profile, and / or as originally specified in the profile. In addition to services, a superset of services can also be provided. Therefore, the profile can be changed, and the service originally specified by the home network can be added or deleted. A service may include quality of service considerations related to a number of different communication considerations such as bandwidth, latency, loss tolerance, and the like. By causing the visited network or domain to change the profile, the communication function can be dynamically expanded or reduced as conditions change.

  To the accomplishment of the foregoing and related ends, certain aspects are described herein in connection with the following description and the annexed drawings. However, these aspects are merely illustrative of some of the various ways in which the principles of the claimed subject matter may be used, and the claimed subject matter includes all such aspects and their equivalents. Other advantages and novel features will become apparent from the following detailed description when considered in conjunction with the drawings.

Detailed description

  Systems and methods are provided for facilitating roaming in a wireless communication network. In one aspect, a method for roaming between networks is provided. The method includes receiving a request for network access in the visited network and receiving a profile from the home network in response to the request. Upon receipt of the profile, service is selectively provided to one or more access terminals based on at least a portion of the profile. The profile may be modified by the visited network to provide services similar to those originally specified by the home network, a subset of these services, and / or a superset of these services.

  Furthermore, various aspects related to the terminal are described herein. A terminal may also be called a system, user equipment, subscriber unit, subscriber station, mobile station, mobile device, remote station, remote terminal, access terminal, user terminal, user agent, or user equipment. User equipment is cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, PDA, handheld device with wireless connection function, module in terminal, attached to host device, or attached to host device It can be a card that can be built in (such as a PCMCIA card) or other processing device connected to a wireless modem.

  Further, aspects of the claimed subject matter are standards that produce software, firmware, hardware, or any combination thereof for controlling a computer or computer component to implement various aspects of the claimed subject matter. May be implemented as a method, apparatus, or article of manufacture using conventional programming and / or engineering techniques. The term “article of manufacture” as used herein is intended to encompass a computer program accessible from any computer-readable device, carrier wave, or media. For example, computer readable media include, but are not limited to, magnetic storage devices (hard disks, floppy disks, magnetic strips, etc.), optical disks (compact disks (CDs), digital versatile disks (DVDs), etc.), smart Cards, and flash memory devices (cards, sticks, key drives, etc.) may be included. In addition, it should be understood that the carrier wave can also be used to carry computer readable electronic data such as used when sending and receiving voice mail or accessing a network such as a cellular network. Of course, those skilled in the art will recognize many modifications may be made to this configuration without departing from the spirit or scope of the invention described herein.

  Referring now to FIG. 1, system 100 illustrates profile changes for roaming that facilitate communications over a wireless network. A wireless terminal 102 (also referred to as a host) interacts with an access node 104 that is also in communication with a visited network or domain 106, where the visited network is when the wireless or access terminal roams from service provision by the home network 110. Is something you will encounter. It can also be seen that the access node 104 can be considered part of the visited network or domain 106. The access node 104, also referred to as a base station or access router, is included in the visited network 106 for services such as service request authentication, service authorization, session establishment, etc., as described in more detail below. Various nodes, elements, and / or systems are used. First, the visited network 106 receives a request for network access from the wireless terminal 102. After some handshaking with the home network 110 to determine the services available to the wireless terminal 102, an access authorization 114 is generated by the home network and a profile 120 describing the service is transmitted from the home network in response to the request. The

  Upon receiving the profile 120, the visited network 106 can selectively provide service to one or more access terminals based on at least a portion of the received profile 120. As described in more detail below, the service specified in the profile shall be related to the quality of service (QoS) parameters of the individual wireless terminals and the communication session established by the request to the visited network 106. be able to. In one aspect, the visited network 106 processes, modifies, deletes, or adds services of the profile 120. This allows visited network 106 to selectively provide a subset of services from profile 120 and / or provide additional services other than those specified in the profile. By enabling profile changes, the visited network can dynamically adapt its serving content based on current resource conditions or other considerations.

  In one aspect, the system 100 can provide services and services associated with a subscriber and / or a subscriber device 102 when roaming, for example, when gaining access through a local network rather than the home operator's network 110. Quality of service (QoS) support can be controlled. In such a roaming scenario, services and QoS support defined by 110 home operators are selectively supported in the serving operator's network 106 so that the serving operator can add and It is desirable to have the flexibility to provide alternative services and QoS support.

  According to another aspect, the subscriber profile 120 can be included in the access authorization message 114 sent from the home network 110 authentication authorization server (AAS) or the like to the visited network AAS. It should be understood that profile 120 may be exchanged between different network components. Subsequently, an access authorization message 114 is generated, and the subscriber profile 120 is sent from, for example, the serving AAS to the access node 104 to which the subscriber device 102 requests access. Subscriber profile 120 defines the configuration of one or more QoS parameters and / or between different application services that are allowed to be used between subscribers and / or given subscribers at a later time. Contains pre-authorization information for QoS configuration changes as required to provide service differentiation.

  The subscriber profile 120 provided by the home AAS or other network component may be modified by one or more components in the visited network 106, such as the visited AAS and / or access node. Thus, the visited network operator can change the subscriber profile 120 to match the service provided on the visited operator's network 106, such as adding, changing, or deleting a service. By allowing changes to the profile 120, the system 100 allows flexibility in controlling services and QoS when roaming. This makes it possible to change the subscriber service, for example, to add, change, delete, etc. for the visited network operator. This approach of changing profiles in the visited network 106 also evolves the provided service definition for the flexibility of defining services in the subscriber profile 120 using XML (or other structure). Also make it possible.

  The terminal 102 can be used to access a module such as an SD card, a network card, a wireless network card, a computer (including a laptop, a desktop, a personal digital assistant (PDA)), a mobile phone, a smartphone, or other network, for example. Any suitable terminal can be used. The terminal 102 accesses the network via the access node 104. For example, the terminal 102 can be coupled to the access node 104 via a wired connection such as an Ethernet (registered trademark) cable, a USB connection, or the like. In another example, the connection between terminal 102 and access node 104 may be wireless, where access node 104 is a base station and terminal 102 is a wireless terminal. For example, terminal 102 and access node 104 may include, but are not limited to, time division multiple access (TDMA), code division multiple access (CDMA), frequency division multiple access (FDMA), orthogonal frequency division multiplexing (OFDM), FLASH OFDM, Interact via any suitable wireless protocol, including Orthogonal Frequency Division Multiple Access (OFDMA), or any other suitable protocol.

  Similar to terminal 102, access node 104 may be an access node associated with a wired or wireless network. For this purpose, the access node 104 may be a router, a switch, or the like, for example. The access node 104 can include one or more interfaces, such as communication modules, for interacting with other network nodes. In addition, the access node 104 may be a base station (or wireless access point) in a cellular network, where the base station (or wireless access point) provides a wireless coverage area for multiple subscribers. Used for. Such a base station (or wireless access point) may be arranged to provide a continuous coverage area to one or more cellular telephones and / or other wireless terminals.

  As described above, the system 100 can also include an authentication authorization server (AAS) at 106 and 110, which allows the terminal 102 to use the access node 104 to send / receive data over the network. Help you to be able to. Although the AAS 106 is illustrated as a separate entity, it will be appreciated that it may be included within the access node 104. With respect to authentication / authorization, terminal 102 may provide data indicating such terminal 102 and / or subscriber identity associated with terminal 102 to AAS 106 via access node 104. The access node 104 can also relay the identification data to the AAS 106 without modification, and can modify such data according to any suitable data format / protocol. Upon receipt of the identification indication, the AAS 106 may authenticate the terminal / subscriber identification information and determine whether one or more services are permitted for the terminal 102 (and / or subscriber).

  The authentication / authorization process may include an exchange of one or more signals between terminal 102, access node 104, and / or AAS 106, and in some embodiments. If service is granted to terminal 102 and / or a subscriber associated with terminal 102, AAS 106 relays the modified profile assigned to terminal 102 (or associated subscriber) to access node 104. This profile can include a description of at least QoS parameters associated with one or more traffic flows associated with terminal 102 and identify data flows (based on inspection of packet header and / or packet payload) Etc.) can be defined as a series of related data packets. The profile 120 may also include filter rules that facilitate the association of data packets with traffic flows and the association of a specified QoS process to several traffic flows and / or data packets. According to an example, a data packet having a header indicating that such a packet is related to voice data can be collectively referred to as a traffic flow. Similarly, a data packet indicating that such a packet is related to video data may be a separate traffic flow.

  Upon receiving the profile, the access node 104 can monitor and execute the QoS process described in the received profile. For example, parameters that may be utilized in connection with the described QoS processing are those relating to the acceptable latency associated with the traffic flow, and the access node 104 may accept the allowance described in the profile provided from the AAS 106. Scheduling for traffic flows can be performed to maintain latency. Other QoS parameters in the received profile may relate to the lowest acceptable data rate for a particular traffic flow type, the highest acceptable data rate for a particular traffic flow type, and so on. Such a parameter can also be defined as a numerical value (eg, the lowest data rate for the first traffic flow type is 128 Kb / sec, etc.) and / or relatively defined (eg, The waiting time for the first traffic flow type should be 1/2 the waiting time for the second traffic flow type, etc.). Furthermore, the definition of parameters can be conditional on certain (one or more) system and network conditions. In one example, a particular parameter is defined relatively until a threshold is reached, and thereafter defined as a numerical value (eg, the minimum data rate for the first traffic flow is 2 of the second traffic flow). Should be twice as large, but not more than 1 megabyte per second).

  In addition, the profile provided from the AAS 106 to the access node 104 can support object instances included in the profile, thereby reducing duplication of parameter definitions within the profile. For example, a gaming application that is authorized for use with terminal 102 may use three parallel traffic flows to support such an application. Rather than defining parameters for each traffic flow, a definition can be created for a single traffic flow and an instance of such definition can be used for the associated traffic flow. In addition, the profile can include filter rules (such as classifications) that identify individual traffic flows and associate the filter rules in association with associating this traffic flow with an instance that determines the QoS treatment to be assigned to the traffic flow. Can be used. Upon receiving the profile, the access node 104 may be configured to provide QoS processing to the terminal 102 as defined in the profile and pre-authorization data set 120. Thus, the access node 104 can provide different QoS processing for various traffic flows and multiple users, thereby enhancing system performance and user experience.

  Referring now to FIG. 2, an example network access system 200 that can use profile data that can be changed when roaming is illustrated. Prior to proceeding, the components and protocols shown in system 200 are exemplary in nature and that more or fewer components may be used and / or protocols other than those shown may be used. Note that it can also be used. System 200 includes a wireless terminal (WT) 210 that is connected to a base station (BS) 216 via a 220 FLASH air interface. BS 216 interacts with a local authentication authorization (AAL) server 224 via a network link. AAL 224 may be provided as part of a mobile network server (MNS). The AAL 224 communicates with other AA servers such as a home AA server (AAH) 230 and an external AA server (AAF) 234. The home network 240 can be provided with a service by the AA server 230 including the original service setting record of the WT 210. The local or visited network 244 is a network to which the WT 210 makes a network connection by accident.

  If the WT 210 tries to connect directly to the home network 240 (by geographical location), the connection to the home network may be, for example, a BS, MNS / AAL, all located within the home network (unlike that shown in FIG. 2). , And communication between AAHs. It can be seen that the WT 210 is local to the visited network during roaming (as shown in FIG. 2) and local to the home network 240 except during roaming. The system 200 also illustrates the following exemplary protocol used when controlling network access. These protocols may include connection control protocol (CCP), secure association protocol (SAP), remote dial-in user service (RADIUS) protocol, and / or extensible authentication protocol (EAP). As will be appreciated, other protocols can be used to control network access.

  Referring now to FIG. 3 and FIG. 4 together, a two-step authentication protocol is shown. In one example, two authentication stages for network access can be used using one or two different extensible authorization protocol (EAP) methods. The first stage shown in FIG. 3 includes authentication between the wireless terminal (WT) 310 and the home network AA server (AAH) 320 via the base station 330 and the local network AA server (AAL) 340. In the second stage, as shown in FIG. 4, authentication between the WT 310 and the local network AA server 340 is performed. This two-step authentication procedure is generally performed regardless of whether the WT 310 is located within its home operator network or roaming with another operator network. The WT 310 is expected to be served locally by the AAL 340, which is independent of its AAH 320. Two-factor authentication allows scalable roaming and allows proper handling of key materials and services in the local network, whether the network is home or located. The two stages of EAP should be independent of each other. In other words, different mechanisms may be used at each stage, and mutual authentication between the WT 310 and the AA servers 320 and 340 can be performed.

  In the first authentication stage shown in FIG. 3, the AAL 340 acts as a RADIUS proxy. It should be understood that other authentication protocols may be used. In the second stage, authentication is performed between the WT 310 and the local network (AAL server) 340, and AAH is not involved as shown in FIG. Adding a second step, which is authentication with the local network, allows the WT 310 to establish trust locally. The local network can be part of the external operator's network (ie, other than the home operator) or part of the home operator's management domain. Local trust establishment uses AAL340 as a trusted third party for other protocols to shield AAF / AAH from the effects of local mobility (whether or not the WT is roaming) Can be used for a number of reasons, including to make it possible and to provide a higher degree of subscriber identity confidentiality.

  The authentication phase with the local network enables subscriber anonymity support. AAL 340 allocates a temporary identifier to WT 310, which is not linked to the WT's permanent identifier by "listening" to the air interface. This is due in part to the mechanism set to ensure that the temporary WT identifier is sent to the WT 310 and to ensure confidentiality. In this case, the WT 310 can also use this temporary identifier later to gain network access authority in this local network, for other host configuration purposes required if the WT is in the home network. It can also be used. In addition to establishing trust, profiles can also be exchanged to further define services.

  Turning now to FIG. 5, an example profile 500 is shown in accordance with one or more aspects described herein. Profile 500 is a logical grouping of parameters that define aspects of services that are allowed to be used by a subscriber (a specific mobile terminal). However, the fields / elements in the profile 500 can be changed and, for example, how each element is defined can be changed as long as the claims of the present invention are followed. It can be seen that the number of elements can be changed, the number of elements can be changed, and the names of the elements can be changed. Profile 500 can be associated with FLASH service element 502, which is a logical group of parameters associated with establishing and maintaining a connection via an interface, such as an air interface, including a FLASH air interface. is there. The FLASH service element 502 can be associated with a location constraint element 504, which is a set of parameters that define a location (or attachment point) for granting subscribers access to the service. When the location constraint element 504 is included in the profile 500, access can be restricted as defined by the elements included in the location constraint element 504. The absence of the location constraint element 504 indicates that access is not limited to a list of predefined locations, but may be restricted by other means such as a roaming contract.

  The profile 500 can further include a network element 506, which can be a set of parameters associated with a particular network for granting access rights to subscribers (terminals) for service. it can. Access rights can be limited to only the set of networks indicated, and can not be granted via other networks as needed. Network element 506 can be associated with network identifier element 508, which can be a globally unique identifier of the network for granting subscribers access to the service. The network element 506 can be further associated with a zone element 510, which is defined as a set of parameters associated with a particular zone in the network for granting subscribers access to the service. Can do. Access rights within the network can be limited to only the set of zones indicated in zone element 510. By not including the zone element 510, it can be shown that the access rights in the network indicated in the network identifier element 508 are not limited to a predefined set of zones.

  Zone element 510 can be associated with zone identifier element 512, which can be a locally unique identifier of a zone in the network for granting subscribers access to the service. Zone element 510 can also be associated with base station element 514, which can be associated with a particular base station or access node (within a zone of the network) to grant subscribers access to the service. It can be defined as a set of associated parameters. Access authority within a zone can be limited to only the indicated set of base stations in base station element 514. By not including base station element 514, it can be shown that access rights within the indicated zone are not limited to a particular set of base stations.

  Base station element 514 can be associated with a base station identifier 516, which can be a locally unique identifier of a base station within a zone of the network for granting subscribers access to the service. Can do. The base station element 514 can also be associated with a link element 518, which provides the subscriber with access to the service (corresponding to the identified base station in the zone of the network). It can be a set of parameters associated with a particular link. For example, access authority via a base station can be limited to only the set of links specified in the link element 518, and by not including the link element 518 in the profile, access authority via the corresponding base station It can be shown that is not limited to a specific set of links.

  The link element 518 can be associated with a logical link control identifier element 520, which is the local link of the link corresponding to a base station in the zone of the network for granting subscribers access to the service. Can be a unique identifier. A link element 518 can also be associated with a connection element 522, which is a set of parameters associated with a particular connection for granting subscribers access to the service. For example, access authority over a link can be limited to only the set of connections indicated. By not including a connection element, it can be shown that access rights over the corresponding link are not restricted to a defined set of connections. Therefore, it is desirable not to include the connection element 522 in the profile 500 when the access authority through a specific link is not further restricted. A connection element 522 can be associated with a connection identifier element 524, which is a locally unique connection of a connection corresponding to a link and a base station in a zone of the network for granting the subscriber access to the service. Identifier.

  The profile 500 can also include a location update interval element 526, which should be performed by the wireless terminal while the wireless terminal is in a “sleep” mode, for example. It can be a period (such as in seconds) between successive temporal instances. The monitoring interval element 528 may indicate a period (eg, in milliseconds) between successive temporal instances during which a call should be monitored by the wireless terminal while in the “sleep” mode. The profile 500 can further include a service set element 530 (described in detail below), which is a logical data configuration of services and subscriber services related to enabling and controlling the service. Set can be included. Such elements 530 can include QoS parameters associated with a number of traffic flows associated with a particular terminal (such as a wireless terminal). Element 530 also includes a pre-authorization template or data for dynamic quality of service configuration from the access node. Information that makes up a profile, including QoS parameters, can be communicated using XML, and the structure and other characteristics of this information, such as data type, format, and / or value restrictions, are defined by the associated XML schema. can do.

  Referring now to FIG. 6, an exemplary service set element 600 (such as service set element 530 of FIG. 5) is shown and described. However, such elements are merely shown as examples, and that the elements in the figures and / or the logical relationships between the elements can be deleted, changed, or retained in accordance with the claimed subject matter. Should be understood. QoS definition and control may be based on at least a portion of the two data structures in the service set element 600, namely the service class element 602 and the subscriber service element 604. Although illustrated as “subscriber” service elements, it is understood that such elements can also be associated with subscriber equipment such as wireless terminals. Thus, the subscriber service element can also be included in the profile as a result of identifying the terminal indication and / or identifying the subscriber indication. Depending on the service to be provided, there may be more than one or both of these data structures in the profile. The service class element 602 (data structure) can provide a common mechanism for defining the QoS processing of traffic flows associated with a particular service class instance. For example, a packet provided to / from a host device is classified into one or more traffic flows, and a given traffic flow may include only a specific packet stream corresponding to a specific application. May include a set of packet streams corresponding to.

  Each identified traffic flow can then be associated with an instance of one or more service class elements (602). The associated service class for each identified traffic flow can provide the basis for admission control, scheduling, and traffic coordination functions of host equipment and / or access nodes (access routers, base stations, etc.). The service class element 602 may be related to QoS processing, but the service set element 600 is specific to support policy control (such as service authorization) and service definition (setting parameter values, identified traffic flows and QoS). Associated with an instance of a service class). Each service set element may include zero or more service class elements and zero or more subscriber service elements.

  Turning now to FIG. 7, an exemplary service class element (such as service class element 602 shown in FIG. 6) is shown. Again, the service class element 700 is shown as an example of one specific scheme for defining QoS processing in a profile. Other ways of defining QoS processing within a profile are also contemplated by the inventors and are within the scope of the appended claims. The service class element 700 can include a service class identifier 702, which can be a globally unique identifier (such as 32 bits) of the defined service class, where x and y are respectively It can be expressed using the notation x: y which can be a hexadecimal value corresponding to the first bit number (prefix) and the second bit number (suffix) of the service class identifier 702. For example, a set of service classes defined by a particular operator or standard organization can utilize a common service class identifier prefix.

  The service class element 700 can also include an admission priority element 704. In a service class that defines a delivery goal that requires allocation of dedicated resources (such as a service class that specifies minimum speed and / or latency limits), admission priority element 704 determines admission control decisions for resource allocation. Indicate the relative order of such service classes to do. The specific usage of admission priority may vary from implementation to implementation, and possible usage includes a priority queue of pending resource allocation requests and / or a priority usage of resource allocation.

  Maximum rate element 706 can indicate the maximum data rate that can be provided to the traffic flow associated with an instance of a particular class of service. The maximum speed element 706 can be further defined by token bucket parameters, as described in the token speed element 708 and bucket depth element 710. The token rate element 708 can be in kilobits per second (kilo represents 1000), and the bucket depth element 710 can be in bytes, for example.

  The minimum rate element 712 may indicate a target minimum data rate to be provided for traffic flows associated with an instance of the service class. The minimum rate element 712 can be further defined by a token rate element 714, a bucket depth element 716, a peak rate element 718, a minimum regulatory unit element 720, and a maximum packet size element 722. Token rate element 714 and peak rate element 718 can be in kilobits per second (kilo represents 1000), bucket depth element 716, minimum regulatory unit element 720, and maximum packet size element 722 are in bytes. can do.

  The shared weight element 724 is the relative percentage of services (such as speed and resources) that should be received when a traffic flow associated with an instance of one service class competes with a traffic flow associated with another service class instance for a service. Can be used to indicate Thus, after the delivery goals (minimum speed and / or latency limit) of all accepted service class instances have been met, the remaining service capacity is usually limited (eg by indicating the maximum speed) Between competing service class instances that are not done needs to be distributed in proportion to the sharing weight corresponding to each instance.

  Latency tolerance element 726 indicates an allowed access link latency for packets belonging to a traffic flow associated with an instance of a service class, where the access link latency includes a delay associated with queuing, scheduling, and transmission. . Packets belonging to a traffic flow associated with an instance of this class of service should be delivered over the access link with a high probability and having a latency below the indicated tolerance. As an example, the latency tolerance element 726 can be associated with milliseconds.

  The loss tolerance element 728 can indicate an acceptable probability of loss of packets belonging to a traffic flow associated with an instance of a service class, where loss sources include queue management and unrecoverable transmission errors. It is. Packets belonging to the traffic flow associated with the identified class of service class should be delivered via an access link that has a loss probability below the indicated tolerance. The loss tolerance element 728 can include, for example, data related to the number of lost packets per 100,000 packets. Differentiated service (DS) code point 730 may indicate a DS code point at which packets in the traffic flow associated with the identified class of service class should be marked.

  The compression hint element 732 can indicate that it is likely that header compression can be applied to packets belonging to a traffic flow associated with a particular instance of a service class. The compression hint element 732 can include information that helps determine the type of compression that can be applied and / or the parameters required for compression.

  Referring to FIG. 8, an exemplary subscriber service element 800 (such as subscriber service element 604 of FIG. 6) is shown and described. Again, element 800 is shown as one specific way of defining a service. Other ways of defining services are contemplated by the inventors and are within the scope of the appended claims. The subscriber service element 800 can include a subscriber service identifier element 804, which can be a globally unique identifier for a subscriber service, where x and y are subscriptions, respectively. Can be represented using the notation x: y, which can be a hexadecimal value corresponding to the first bit set (prefix) and the last bit set (suffix) of the service identifier element 804. A set of subscriber services defined by a particular operator or standards body can use a common subscriber service identifier prefix. Region element 806 can indicate the domain with which the subscriber service is associated, and by not including region element 806 can indicate that the subscriber service is associated with the local domain. This provides the basis for better control of services when roaming between various network operators.

  Subscriber service element 800 may include a policy decision point (PDP) identifier element 810. The PDP identifier element 810 may be an identifier such as an IP address or a host name of a PDP to be used for a QoS configuration change request associated with a specific subscriber service. Subscriber service element 800 is further a logical collection of service class instances, filter rules, and service class instance templates applicable to egress traffic from an access router to a subscriber via a corresponding access link. An Egress element 812 and an Ingress element 814 that is a logical collection of service class instances, filter rules, and service class instance templates applicable to ingressing traffic from a subscriber to an access router via a corresponding access link Can be included.

  The Egress element 812 and the Ingress element 814 can include one or more service class instance elements 816, 818, respectively. Service class instance elements 816 and 818 define a static service class instance, for example, where an instance of this is required and the traffic flow identifies the particular service class element associated with it by one or more filter rules be able to. A static service class instance can conceptually be considered a permanently required instance of a particular service class. Depending on the corresponding service class parameters, admission control decisions may be required. Thus, at any given time, static service class instances may or may not be acted upon (accepted, etc.) depending on resource availability and admission priority, but need to be activated whenever possible .

  The Egress element 812 and the Ingress element 814 can also include one or more filter rule elements 820 and 822, respectively. Filter rule elements 820 and 822 define classification filter rules for mapping packets belonging to a traffic flow to a defined service class instance. Each filter rule element has a priority, a packet matching criteria specification (a value corresponding to one or more packet headers or payload fields) Value range), and an indication of the class of service instance to which the matching packet should be associated. The filter rule elements 820, 822 can also be used to discard packets belonging to traffic flows by mapping them to null service class instances.

  The Egress element 812 and the Ingress element 814 may also include one or more service class instance template elements 830 and 840, respectively. Service class instance template elements 830, 840 define the pre-authorization of dynamic service class instances, such as identifying specific service class elements for which instances can be dynamically requested, and required service class instances Policy constraints, and / or filter rules used to associate traffic flows with required service class instances.

  Referring to FIG. 9, an example roaming system 900 is shown that can use the aforementioned modifiable profile. The system 900 shows a roaming scenario in which a subscriber host (SH) 910 acquires access authority via a network other than the visited network 920, that is, the home network 930 of the SH 910. In this example, there may typically be a roaming agreement 940 between the home network operator and the visited network operator. The home network operator may typically be involved in SH910 authentication and access authorization. Assuming that the home operator grants access authority to the SH 910, the visited network operator can cause the SH to receive services via the visited network operator's local access network. However, either or both network operators can provide basic network services and higher layer services. Dashed lines in system 900 conceptually represent basic network services and / or higher layer services. When roaming, the SH 910 may receive service from the visited / local domain 920, the home network or domain 930, or both. Thus, a subscriber service mechanism (such as a subscriber profile that directs service authorization) needs to provide enough information to allow support of the service by either domain. The scenario system 900 may also represent an example of an MVNO, such as a case where the home network 930 is a mobile virtual network operator (MVNO). In this case, the MVNO may include the required network elements and software that supports “roaming” but not the access network. Thus, SH 910 is administratively associated with MVNO, but cannot directly access home network 930 and appears to be roaming by visited network 920.

  Referring to FIG. 10, the system 1000 shows a virtual homing scenario. The virtual homing scenario shown in system 1000 represents another example that supports MVNO, such as the case where virtual home 1030 is MVNO, and the virtual private network (VPN), such as the case where virtual home 1030 is a local network The example which supports is also shown. A general distinction from the system 900 described above is that in the system 1000, the SH 1010 is administratively associated with the local network 1020 through which access authority is acquired, and the local network 1020 is the home network. In the point. Thus, the local / home network operator will typically be involved in SH1010 authentication and access authorization. However, the SH 1010 also has an association with the illustrated virtual home 1030, which can be MVNO or a private organization such as a company to which VPN service is to be provided. Dashed lines are drawn as in system 900, which indicates that basic network services such as addressing / routing, as well as potentially higher layer services, are home / local domain 1020, virtual home domain 1030, or these It shows that it can be provided by both.

  Referring to FIG. 11, system 1100 illustrates virtual homing and roaming scenarios. A system 1100 represents a combination of scenarios shown in the system 900 and the system 1000 described above. In this example, SH 1110 is associated with home network 1120 and virtual home 1130 while gaining access authority via visited network 1140. Again, the home network operator would typically be involved in SH1110 authentication and access authorization. However, this system 1100 has three dashed arrows drawn, which indicate that basic network services such as addressing / routing, as well as potential higher layer services are located / local domain 1140, home domain 1120, It shows that it can be provided by a virtual home domain 1130, or a combination of these three domains.

  Referring to FIG. 12, a method 1200 related to profile modification and roaming is shown. For ease of explanation, the method is illustrated and described as a sequence of operations, but the method is not limited to this sequence of operations, and some operations may be performed in one or more embodiments. Thus, it should be understood and appreciated that the order may be different from the order shown and described herein and / or may be performed concurrently with other operations. For example, those skilled in the art will understand and appreciate that a method could alternatively be represented as a series of interrelated states or events, such as in a state diagram. Moreover, not all illustrated acts may be employed to implement a methodology in accordance with the claimed subject matter.

  The method 1200 will be described with reference to FIG. 12 in detail. Method 1200 begins at 1202 and at 1204 a request for service from a visited network is generated. For example, a mobile terminal is initially authorized through a home network, and the current mobile terminal requests access authority to a subsequent network, also called a visited network or domain, depending on its location. At 1206, a profile is requested from the home network. Such a request may be generated by the visited network in response to a request for 1204 services. The profile currently defines services such as, for example, quality of service parameters supported when this terminal is authorized by the home network. When an access authorization is generated by the home network at 1208, a profile is transmitted from the home network to the visited network. As mentioned above, the home network can include virtual aspects such as provided by a mobile virtual network operator (MVNO) or other virtual private network components.

  Access authorization may be performed after a handshake signal or code is exchanged between the home network and the visited network. At 1210, the received profile can be left as is or modified as needed. Profile changes may include adding services to the profile, deleting services from the profile, and / or adjusting parameters associated with individual services in the profile. Therefore, the visited network can provide a service similar to the home network in consideration of the received profile, and provide a reduced service set when one or more services are deleted from the profile. It is also possible to provide a superset of services when adding services to the profile received by the visited network. At 1212, the profile can be used to provide a desired set of services to the wireless access terminal.

  13 and 14 together, a system related to profile change and roaming is shown for terminals, operator networks, access nodes, and their traffic flows. Each system is represented as a series of interrelated functional blocks, and each block may represent a function performed by a processor, software, hardware, firmware, or any suitable combination thereof.

  Referring to FIG. 13 in detail, the system 1300 facilitates communication from the visited network. System 1300 includes a logic module 1302 that receives a subscriber profile generated from a home network. The logic module 1304 is used to change the subscriber profile, and the logic module 1306 is used to provide services based in part on the changed subscriber profile. Changing a subscriber profile can include adding or deleting services in the profile, or changing / editing parameters in the profile.

  Referring now to FIG. 14, a system 1400 facilitates communication from a home network in a roaming environment. System 1400 includes a logic module 1402 that generates a subscriber profile from a home network. This includes a logic module 1404 that annotates the subscriber profile to allow changes to the profile and a logic module 1406 that grants access to the home network.

  With reference to FIG. 15, illustrated is an example network 1500 where profile data can be used for roaming between networks. Shown in system 1500 is an operator interconnect network 1510 with two access routers (AR) 1514 and 1518 for subscriber host (SH) 1520 to gain access and several other network elements. Has been. The logical interface between the various elements is shown using dashed lines. ARs 1514 to 1518 are network elements in the service control situation. This is because they are arranged to control access rights to services available through the operator's infrastructure and directly control the QoS of such services via the access link. However, in a perfect solution, several other network elements may play a role, for example, controlling the operation of ARs 1514-1518. In the following discussion, each logical interface and associated network elements shown in system 1500 are considered.

  Fundamental to the concept of controlling services on an individual subscriber basis is an indication of trusted subscriber identity information (or subscriber identity information associated with SH 1520). Typically, the identification information indicated by the subscriber is authenticated using an extensible authentication protocol (EAP) or the like before the authority to access the network and higher layer services is granted. This initial authentication authorization process generally involves communication between elements intervening in requesting access rights, such as ARs 1514-1518, and a separate authentication authorization server (AAS) 1530, such as using a remote dial-in user service (RADIUS) protocol. Accompanied by. If the subscriber's identification information is authenticated by the AAS 1530 and the subscriber 1520 is permitted to gain access authority, an instruction that the access authority is granted is returned from the AAS 1530 to the element intervening in the access authority request.

  Following the initial access authorization, the ARs 1514 to 1518 start transmitting charging information such as the number of packets / bytes to the charging server (ACS) 1540. Traditional IP best effort services often consist of only a simple total number of packets / bytes of traffic sent and received. However, support for a richer set of subscriber services is likely to use a billing mechanism that enables service-based billing and billing. Thus, billing information, such as collected / reported by ARs 1514-1518, should include details regarding the services used and / or the level of QoS provided.

  According to the architecture presented herein, SH 1520 may change its attachment point from one AR to another, this process is generally referred to as handoff. Mobile IP (MIP) is a way to support mobility in IP interconnection networks, using tunnels to manage routing / forwarding, so that mobile hosts use the same address when changing attachment points. Makes it possible to continue. Using a context transfer (CT) mechanism, service disruption during handoff can be minimized. By transferring information about service authorization and QoS configuration between ARs at the time of handoff, equivalent services can be established more quickly and efficiently via the new AR. Upon receiving QoS configuration information associated with SH 1520 moving to the new AR, the new AR needs to perform admission control to determine if sufficient resources are available before providing the indicated service. Please note that there is.

  The resource control interface 1550 uses a signaling protocol for the SH 1550 to request a QoS configuration change following initial access authorization. As mentioned above, this includes a set of available QoS data and parameters that can be requested by SH 1520 as dynamic conditions require. In general, it cannot be assumed that end-to-end QoS is supported between SH 1520 and another host with which SH communicates. However, the system 1500 provides a QoS architecture in which resource reservation is required only at the ARs 1514-1518, rather than along the entire data path, for a wide service range. Alternative or additional resource control signaling may be used if resource reservation is required at another node along the data path. According to the model, SH 1520 should be able to request resources for both transmission and reception traffic. The system 1500 shows a resource control interface 1550 between the SH 1520 and the AR, but instead of SH, an equivalent from an element in the operator's interconnect network 1510, the operator host (OH) or application server. It is also possible to support QoS configuration through a similar resource control resource control interface.

  Policy control interface 1554 represents a mechanism for checking permission for QoS configuration changes, such as required via resource control interface 1550. Policy control interface 1554 is shown between AR 1514 and an unspecified network element that functions as PDP 1560, and that the PDP function may be located, for example, on a dedicated policy server, application server, or some other network element Please note that. A possible reason for this distinction is that the proper placement of the PDP function 1560 depends on the individual service. In general, different services can even be associated with different PDPs, and therefore, according to some embodiments of the present invention, the service definition includes an indication of the associated PDP.

  FIG. 16 shows a communication device 1600 that can be a wireless communication device such as a wireless terminal. Additionally or alternatively, the communication device 1600 can be located in a wired network. Communication device 1600 can include a memory 1602 that can retain instructions for configuring such device for terminal QoS data (and traffic flows associated with the terminal). Additionally, communication device 1600 includes a processor 1604 that can execute instructions in memory 1602 and / or instructions received from another network device, which configure communication device 1600 or an associated communication device. Can be related to

  Memory 1602 retains instructions for receiving a profile associated with one or more services, the profile can be associated with a home network component and can be changed via a visited network component, and a roaming access terminal Used to provide services to In another aspect, the memory retains instructions for generating a profile associated with one or more services, the profile can be associated with a home network component and can be changed by a service description component. The profile can be used, for example, to provide services to roaming access terminals.

  To provide another situation in one or more embodiments described herein, FIG. 17 illustrates an example communication system 1700 comprising multiple nodes interconnected by communication links. System 1700 uses orthogonal frequency division multiplexing (OFDM) signals to exchange information over a wireless link. However, other types of signals are contemplated (along with signals used in terrestrial networks) such as code division multiple access (CDMA) signals and time division multiple access (TDMA) signals. Nodes in the communication system 1700 exchange information using signals such as messages based on a communication protocol such as the Internet Protocol (IP). The communication link of system 1700 is implemented using, for example, wiring, fiber optic cable, and / or wireless communication technology. System 1700 includes a plurality of termination nodes 1702-1712 that access communication system 1700 via a plurality of access nodes 1714-1718. The termination nodes 1702 to 1712 can be, for example, wireless communication devices and terminals, and the access nodes 1714 to 1718 can be, for example, wireless access routers and base stations. Communication system 1700 also includes a number of other nodes 1720-1730 that are used to enable interconnection or provide specific services or functions.

  The communication system 1700 shows a network 1760 that includes an access control node 1720, a mobility support node 1722, a policy control node 1724, and an application server node 1726, all of which are respectively associated with corresponding network links 1732- 1738 is connected to the intermediate network node 1728. In some embodiments, an access control node, such as a remote authentication dial-in user service (RADIUS) or Diameter server, supports authentication, authorization, and / or billing of a terminal node and / or a service associated with the terminal node. In some embodiments, a mobility support node 1722, such as a Mobile IP home agent and / or a context transfer server, is associated with a traffic redirection to / from a terminal node and / or a terminal node between access nodes. The mobility of the end node between access nodes, such as handoff, is supported by forwarding or the like. In some embodiments, a policy control node 1724, such as a policy server or policy decision point (PDP), supports policy authorization for service or application layer sessions. In some embodiments, an application server node 1726, such as a session initiation protocol server, streaming media server, other application layer server, supports session signaling for services available from the end node and / or is available from the end node. Provide service or content.

  Intermediate network node 1728 within network 1760 provides interconnection with network nodes that are external to network 1760 via network link 1734. Network link 1734 is connected to intermediate network node 1730, which provides additional connectivity to access nodes 1714, 1716 and 1718, respectively, via network links 1736-1740. Each access node 1714-1718 is shown as providing a connection to a termination node 1702-1712, respectively, via a corresponding access link 1742-1752, respectively. In communication system 1700, each access node 1714-1718 is illustrated as being accessible using a wireless technology such as a wireless access link. However, wired technology may also be used in connection with providing access. The wireless coverage area, such as the communication cells 1754-1758 of each access node 1714-1718, is shown as a circle surrounding the corresponding access node.

  Communication system 1700 can be used as a basis for the description of various embodiments described herein. Alternative embodiments include various network topologies, including the number and type of nodes (including network nodes, access nodes, termination nodes, and various control, support, and server nodes), the number and types of links, and various The inter-node connectivity may be different from that of the communication system 1700. In addition, some of the functional entities shown in the communication system 1700 may be omitted or combined. In addition, the location or arrangement of these functional entities may be changed.

  FIG. 18 illustrates an exemplary termination node 1800, such as a wireless terminal. Terminal node 1800 is an illustration of an apparatus that may be used as any one of terminal nodes 1702-1712 (FIG. 17). End node 1800 includes a processor 1802, a wireless communication interface module 1804, a user input / output interface 1806 and a memory 1808 coupled together by a bus 1810. Thus, via bus 1810, the various components of end node 1800 can exchange information, signals and data. The components 1802-1808 of the termination node 1800 can be located within the housing 1812.

  The wireless communication interface module 1804 provides a mechanism for the internal components of the termination node 1800 to send and receive signals to and from network nodes, such as external devices and access nodes. The wireless communication interface module 1804 includes, for example, a receiving module 1814 with a corresponding receiving antenna 1816 that is used to couple the termination node 1800 to other network nodes, such as via a wireless communication path, and the like. A transmission side module 1818 including a transmission antenna 1820 is included.

  Termination node 1800 also includes a user input device 1822 such as a keypad and an output device 1824 such as a display, which are coupled to bus 1810 via user input / output interface 1806. Thus, the user input device 1822 / output device 1824 can exchange information, signals and data with other components of the termination node 1800 via the user input / output interface 1806 and the bus 1810. User input / output interface 1806 and associated devices 1822, 1824 provide a mechanism for a user to operate end node 1800 to accomplish various tasks. Specifically, user input device 1822 and user output device 1824 allow a user to control termination node 1800 and applications, such as modules, programs, routines and / or functions, executed in termination node 1800 memory. I will provide a.

  The processor 1802 controls the operation of the termination node 1800 to perform various signaling and processing under the control of various modules such as routines included in the memory 1808. Modules included in memory 1808 are executed at startup or when called by other modules. Modules exchange data, information, and signals when executed. Modules can also share data and information when executed. The memory 1808 of the end node 1800 includes a control signaling module 1826, an application module 1828, and a traffic control module 1830, which further includes configuration information 1832 and various additional modules.

  The control signaling module 1826 receives signals, such as messages, to control the operation and / or configuration of various aspects of the termination node 1800, including the traffic control module 1830 and the configuration information 1832 and the various modules it includes. And control processing related to transmission. In some embodiments, the control signaling module 1826 includes state information such as parameters, status and / or other information related to one or more signaling protocols supported by the termination node 1800 and / or the control signaling module 1826. Can do. Specifically, the control signaling module 1826 includes configuration information such as end node identification information and / or parameter settings, and operational information such as current processing status, status of pending message transactions.

  Application module 1828 controls processing and communication associated with one or more applications supported by end node 1800. In some embodiments, the processing of application module 1828 is to receive or transmit signals such as input / output of information via user input / output interface 1806, manipulation of information associated with the application, and / or messages associated with the application. Related tasks can be included. In some embodiments, application module 1828 includes state information such as parameters, status and / or other information related to the operation of one or more applications supported by application module 1828. Specifically, the application module 1828 includes configuration information such as user identification information and / or para-settings, and operational information such as current processing, status of pending responses. Applications supported by application module 1828 include, for example, voice over IP (VoIP), web browsing, audio / video streaming, instant messaging, file sharing, games, and the like.

  The traffic control module 1830 controls processing related to reception and transmission of data information such as messages, packets, and / or frames via the wireless communication interface module 1804. The exemplary traffic control module 1830 includes various additional modules that control various aspects of the QoS of the packet and / or traffic flow, such as configuration information 1832 and the sequence of associated packets. Various additional modules are included to perform certain functions and operations required in some embodiments to support specific aspects of traffic control. Modules may be omitted and / or combined as needed depending on the functional requirements of traffic control. The explanation of each additional module included in the traffic control module 1830 is as follows.

  The admission control module 1834 maintains information related to resource utilization / availability and determines whether sufficient resources are available to support the QoS parameters that are desirably associated with a particular traffic flow. Resource availability information maintained by the admission control module 1834 includes, for example, packet and / or frame queue capacity, scheduling capacity, and processing and memory capacity required to support one or more traffic flows. . Control signaling module 1826, application module 1828, and / or other modules included in end node 1800 may control admission to determine whether sufficient resources are available to support new or modified traffic flows. Module 1834 can be queried, in which case the admission control decision is a function of the QoS parameters of the particular traffic flow and the QoS parameters defined in the profile. Configuration information 1832 may include configuration information such as parameter settings that affect the operation of admission control module 1834, such as admission control thresholds that indicate the percentage of resources that can be allocated before rejecting the next request. .

  The uplink scheduler module 1836 may be in order and / or timing for data information such as messages, packets, and / or frames to be sent via the wireless communication interface module 1804, such as from the end node 1800 to the access node. And the like, and processes related to the allocation of transmission resources such as information coding rate, transmission time slot, and / or transmission power. The uplink scheduler module 1836 can schedule transmissions and allocate transmission resources as a function of QoS parameters associated with one or more traffic flows. In some embodiments, the scheduling and / or resource allocation operations performed by the uplink scheduler module 1836 are further a function of other factors such as channel conditions and power budget.

  Uplink PHY / MAC module 1838 is a physical (PHY) layer associated with the transmission of data information such as messages, packets, and / or frames via wireless communication interface module 1804, such as from end node 1800 to access node. And controls medium access control (MAC) layer processing. For example, the operation of the uplink PHY / MAC module 1838 includes both transmission and reception of control information such as signals and messages to coordinate the transmission of data information such as messages, packets, and / or frames. The configuration information 1832 includes information such as a frequency to be used for transmission, a band, a communication channel, a spreading code, a hopping code, an identifier associated with the terminal node 1800, a request dictionary that defines the use of an allocation request communication channel, and the like. Configuration information such as parameter settings that affect the operation of the link link PHY / MAC module 1838 may be included.

  Uplink Link LLC (ARQ) module 1840 is a logical link control (LLC) associated with the transmission of data information such as messages, packets, and / or frames via wireless communication interface module 1804, such as from end node 1800 to access node. ) Control layer processing. Uplink link LLC (ARQ) module 1840 includes processing associated with automatic retransmission request (ARQ) functions, such as retransmission of lost packets or frames. Uplink link LLC (ARQ) module 1840 further provides higher layer messages such as packets to provide additional functions such as multi-protocol multiplexing / demultiplexing by type field and error detection by using checksum field, for example. Processing related to the addition of LLC headers and / or trailers can also be included. Uplink link LLC (ARQ) module 1840 may also subdivide higher layer messages such as packets into multiple lower portions such as frames sent by uplink PHY / MAC module 1840. The configuration information 1832 may include configuration information that affects the operation of the uplink LLC (ARQ) module 1840, such as an ARQ window size, a maximum number of retransmissions, a drop timer.

  The uplink queue management module 1842 maintains information related to storage of data information to be sent via the wireless communication interface module 1804, such as from the end node 1800 to the access node, and controls processing. The uplink queue management module 1842 can control the storage of data information waiting for transmission, for example, and can maintain state information regarding the data information waiting for transmission for each traffic flow. Packets associated with the flow are stored in separate queues. For example, the uplink queue management module 1842 supports various queue management methods and / or functions such as various active queue management (AQM) mechanisms such as leading discard, trailing discard, and random initial detection (RED). To do. Configuration information 1832 may include configuration information that affects the operation of uplink queue management module 1842, such as queue limits, discard strategies, and / or AQM thresholds associated with one or more traffic flows. .

  Uplink classification module 1844 controls processing associated with identifying data information as belonging to a particular traffic flow before being sent via wireless communication interface module 1804, such as from end node 1800 to access node. To do. In some embodiments, messages, packets, and / or frames to be sent utilizing the wireless communication interface module 1804 may be changed by the uplink classification module 1844 based on examination of one or more header and / or payload fields. It is classified as belonging to one of the traffic flows. The results of classification by uplink classification module 1844 can affect the processing of classification data information by uplink queue management module 1842 and other modules in memory 1808. For example, this result determines the specific queue with which messages, packets, and / or frames are associated for storage, and also affects subsequent processing such as scheduling. Configuration information includes uplink links, such as a set of one or more classification filter rules that define criteria used to associate data information such as messages, packets, and / or frames as belonging to one or more traffic flows. Configuration information that affects the operation of the classification module 1844 can be included.

  The downlink PHY / MAC module 1846 controls processing of the PHY layer and the MAC layer related to reception of data information via the wireless communication interface module 1804. The operation of the downlink PHY / MAC module 1846 can include both transmission and reception of control information to coordinate the reception of data information. Configuration information 1804 includes configuration information that affects the operation of the downlink PHY / MAC module 1846, such as the frequency to be used for reception, the channel, the communication path, the spreading code or hopping code, and the identifier associated with the end node 1800. Can be included.

  Downlink link LLC (ARQ) module 1848 controls the LLC layer processing associated with receiving data information via wireless communication interface module 1804. Downlink link LLC (ARQ) module 1848 includes processing associated with ARQ functionality, such as retransmission of lost packets or frames. For example, the downlink LLC (ARQ) module 1848 further includes an LLC header that encapsulates higher layer messages and provides additional functions such as multi-protocol multiplexing / demultiplexing by type field and error detection by checksum field. Processing associated with the trailer can be included. The downlink LLC (ARQ) module 1848 may also reassemble frames received by the downlink PHY / MAC module 1846 into higher layer messages. The configuration information 1832 may include configuration information such as parameter settings that affect the operation of the downlink LLC (ARQ) module 1848, such as ARQ window size, maximum number of retransmissions, drop timer, etc., depending on the embodiment. including.

  FIG. 19 shows a detailed view of an exemplary access node 1900 implemented in accordance with the present invention. Access node 1900 is a detailed view of an apparatus that may be used as any one of access nodes 1714-1718 shown in FIG. In the embodiment of FIG. 19, the access node 1900 includes a processor 1902, a memory 1904, a network / interconnect network interface module 1906 and a wireless communication interface module 1908 coupled together by a bus 1910. Thus, via bus 1910, the various components of access node 1900 can exchange information, signals and data. Components 1902 to 1910 of access node 1900 are located inside housing 1912.

  Network / interconnect network interface module 1906 provides a mechanism for internal components of access node 1900 to send and receive signals to and from external devices and network nodes. The network / interconnect network interface module 1906 includes a receiver module 1914 and a transmitter module 1916 that are used to couple the node 1900 to other network nodes, such as via copper or fiber optic lines. The wireless communication interface module 1908 also provides a mechanism for internal components of the access node 1900 to send and receive signals to and from external devices such as termination nodes and network nodes. The wireless communication interface module 1908 includes a reception side module 1918 including a corresponding reception antenna 1920, a transmission side module 1922 including a corresponding transmission antenna 1924, and the like. The wireless communication interface module 1908 is used to couple the access node 1900 to another node via a wireless communication path or the like.

  A processor 1902 under the control of various modules, such as routines included in the memory 1904, controls the operation of the access node 1900 to perform various signaling and processing. The modules included in the memory 1904 are executed at startup or when called by other modules. Modules exchange data, information, and signals when executed. Modules can also share data and information when executed. In the embodiment of FIG. 19, the memory 1904 of the access node 1900 includes a control signaling module 1926 and a traffic control module 1928, which further includes configuration information 1930 and various additional modules 1932-1954.

  The control signaling module 1926 controls the operation and / or configuration of various aspects of the access node 1900, including the traffic control module 1928 and configuration information 1930 included in the traffic control module 1928 and various additional modules 1932-1954, etc. Control processing related to reception and transmission of signals such as messages. For example, control signaling module 1926 includes status information such as parameters, status and / or other information related to operation of access node 1900, and / or one or more signaling protocols supported by control signaling module 1926. Specifically, the control signaling module 1926 includes configuration information such as access node identification information and / or parameter settings, and information regarding the current processing state, operational information such as the status of pending transactions.

  The traffic control module 1928 controls processing related to the reception and transmission of data information such as messages, packets, and / or frames via the wireless communication interface module 1908. For example, the traffic control module may include various additional modules 1932-1954 that control various aspects of the quality of service of packets and / or traffic flows, such as configuration information 1930 and associated packet sequences. In some embodiments, the traffic control module 1928 includes parameters associated with operation of one or more of the access node 1900, the traffic control module 1928, and / or various additional modules 1932-1954 included in the traffic control module 1928. Contains status information such as status and / or other information. Configuration information 1930, such as parameter settings, determines, affects and / or defines the operation of traffic control module 1928 and / or various additional modules 1932-1954 included in traffic control module 1928. Various additional modules are included to perform certain functions and operations necessary to support certain aspects of traffic control in some embodiments. In various embodiments, modules may be omitted and / or combined as needed depending on the functional requirements of traffic control. The description of each additional module included in the traffic control module 1928 is as follows.

  Admission control module 1932 maintains information related to resource utilization / availability and determines whether sufficient resources are available to support the quality of service requirements of a particular traffic flow. Resource availability information maintained by the admission control module 1932 includes packet and / or frame queue capacity, scheduling capacity, and processing and memory capacity required to support one or more traffic flows. The control signaling module 1926 and / or other modules included in the access node 1900 query the admission control module 1932 to determine if sufficient resources are available to support the new or modified traffic flow. The admission control decision can be a function of the quality of service of the particular traffic flow and / or available resources. Configuration information 1930 may include configuration information, such as parameter settings, that affect the operation of admission control module 1932, such as an admission control threshold that indicates the percentage of resources that may be allocated before rejecting the next request. it can.

  The uplink scheduler module 1934 may include, for example, order and / or timing for data information such as messages, packets, and / or frames to be sent from one or more end nodes to the access node via the radio interface module 1908. Control processing related to transmission resource allocation, such as transmission scheduling, information coding rate, transmission time slot, and / or transmission power. The uplink scheduler module 1934 can schedule transmissions and allocate transmission resources as a function of quality of service requirements and / or constraints associated with one or more traffic flows and / or one or more terminal nodes. Configuration information 1930 may affect the operation of the uplink scheduler module 1934, such as priority, speed limits, latency limits, and / or shared weights associated with one or more traffic flows and / or end nodes. Can be included. In some embodiments, the scheduling and / or resource allocation operations performed by the uplink scheduler module 1934 are further a function of other factors such as channel conditions and power budget.

  Downlink scheduler module 1936 provides order and / or timing for data information, such as messages, packets, and / or frames, to be sent from access node 1900 to one or more end nodes via wireless interface module 1908. Control processing related to transmission scheduling such as, and allocation of transmission resources such as information coding rate, transmission time slot, and / or transmission power. The downlink scheduler module 1936 can schedule transmissions and allocate transmission resources as a function of quality of service requirements and / or constraints associated with one or more traffic flows and / or one or more terminal nodes. Configuration information 1930 affects the operation of the downlink scheduler module 1936, such as priority, speed limit, latency limit, and / or shared weight, associated with one or more traffic flows and / or end nodes. Can be included. In some embodiments, downlink scheduler module 1936 and / or resource allocation operations are further a function of other factors such as channel conditions and power budget.

  Uplink traffic adjustment module 1938 may measure, mark, or regulate data information such as messages, packets, and / or frames received via wireless interface module 1908, such as from a terminal node to access node 1900. Control processing related to traffic adjustment. Uplink traffic adjustment module 1938 performs traffic adjustments such as measurement, marking, and / or regulation as a function of quality of service requirements and / or constraints associated with one or more traffic flows and / or one or more end nodes. It can be carried out. Configuration information 1930 can include configuration information that affects the operation of uplink traffic adjustment module 1938, such as rate limits and / or marking values associated with one or more traffic flows and / or end nodes.

  Uplink classification module 1940 may process data information such as messages, packets, and / or frames received via air interface module 1908, such as from a termination node to access node 1900, by uplink traffic coordination module 1938. Control the processing associated with identifying as belonging to a particular traffic flow. In some embodiments, messages, packets, and / or frames received via the wireless communication interface module 1908 are based on inspection of one or more header and / or payload fields, and may vary by the uplink classification module 1940. Are classified as belonging to one of these. The results of classification by the uplink classification module 1940 can affect the processing of classified data information such as messages, packets, and / or frames by the uplink traffic coordination module 1938, eg, these results. Determines the specific data structure or state machine with which the message, packet, and / or frame is associated, and further affects subsequent processing such as instrumentation, marking, and / or regulation. Configuration information 1930 includes an uplink, such as a set of one or more classification filter rules that define criteria used to associate data information such as messages, packets, and / or frames as belonging to one or more traffic flows. Configuration information that affects the operation of the link classification module 1940 may be included.

  Uplink link LLC (ARQ) module 1942 controls the LLC layer processing associated with receiving data information such as packets and / or frames via wireless communication interface module 1908, such as from the end node to access node 1900. Uplink Link LLC (ARQ) module 1942 includes processing associated with ARQ functionality, such as retransmission of lost packets or frames. In some embodiments, the uplink LLC (ARQ) module 1942 further provides higher layer messages such as packets that provide additional functionality such as multi-protocol multiplexing / demultiplexing by type field and error detection by checksum field. Includes processing related to the encapsulating LLC header and / or trailer. The uplink LLC (ARQ) module 1942 can also reassemble frames received by the uplink PHY / MAC module 1944 into higher layer messages such as packets. The configuration information 1930 may include configuration information that affects the operation of the uplink LLC (ARQ) module 1942, such as an ARQ window size, a maximum number of retransmissions, a drop timer.

  Uplink PHY / MAC module 1944 performs PHY and MAC layer processing related to receiving data information, such as packets and / or frames, via wireless communication interface module 1908, such as from end node to access node 1900. Control. In some embodiments, the operation of the uplink PHY / MAC module 1944 includes both transmission and reception of control information such as signals and messages to coordinate reception of data information such as messages, packets, or frames. Configuration information 1930 includes configuration information that affects the operation of the uplink PHY / MAC module 1944, such as the frequency to be used for reception, the channel, the channel, the spreading code or hopping code, and the identifier associated with the access node 1900. Can be included.

  The downlink classification module 1946 belongs to a specific traffic flow before data information such as messages, packets, and / or frames is sent through the wireless communication interface module 1908, such as from the access node 1900 to the end node. Control processing related to identifying as. In some embodiments, messages, packets, and / or frames to be sent via the wireless communication interface module 1908 are based on inspection of one or more header and / or payload fields, and may vary by the downlink classification module 1946. Classified as belonging to one of the flows. The results of classification by the downlink classification module 1946 are used to process classified data information such as messages, packets, and / or frames by the downlink queue management module 1950 and other modules 1948, 1952, and 1954. For example, these results determine a particular queue with which messages, packets, and / or frames are associated for storage, and also affect subsequent processing such as scheduling. Configuration information 1930 includes a downlink, such as a set of one or more classification filter rules that define criteria used to associate data information such as messages, packets, and / or frames as belonging to one or more traffic flows. Configuration information such as parameter settings that affect the operation of the link classification module 1946 can be included.

  Downlink link traffic adjustment module 1948 measures, marks, and regulates data information, such as messages, packets, and / or frames, to be sent via air interface module 1908, such as from access node 1900 to a terminal node. Control processing related to traffic adjustment. Downlink traffic adjustment module 1948 performs traffic adjustments such as measurement, marking, and / or regulation as a function of quality of service requirements and / or constraints associated with one or more traffic flows and / or one or more end nodes. It can be carried out. Configuration information 1930 may include configuration information that affects the operation of downlink traffic adjustment module 1948, such as rate limits and / or marking values associated with one or more traffic flows and / or end nodes.

  The downlink queue management module 1950 stores information related to the storage of data information such as messages, packets, and / or frames to be sent via the wireless communication interface module 1908, such as from the access node 1900 to the end node. Maintain and control the process. The downlink queue management module can control storage of data information waiting for transmission for each traffic flow, and can maintain state information regarding data information waiting for transmission. Associated packets are stored in separate queues. In some embodiments, the downlink queue management module 1950 supports various queue management methods and / or functions, such as various AQM mechanisms such as leading discard, trailing discard, and RED. Configuration information 1930 may include configuration information that affects the operation of downlink queue management module 1950, such as queue limits, discard strategies, and / or AQM thresholds associated with one or more traffic flows. it can.

  Downlink link LLC (ARQ) module 1952 controls the LLC layer processing associated with the transmission of data information such as messages, packets, and / or frames via wireless communication interface module 1908, such as from access node 1900 to a terminal node. To do. Downlink link LLC (ARQ) module 1952 includes processing associated with ARQ functionality, such as retransmission of lost packets or frames. In some embodiments, the downlink LLC (ARQ) module 1952 further includes a packet or the like to provide additional functions such as multi-protocol multiplexing / demultiplexing by type field and error detection by using a checksum field. Includes processing related to the addition of LLC headers and / or trailers to higher layer messages. The downlink LLC (ARQ) module 1952 can also subdivide higher layer messages such as packets into multiple lower parts such as frames transmitted by the downlink PHY / MAC module 1954. . The configuration information 1930 may include configuration information that affects the operation of the downlink LLC (ARQ) module 1952, such as an ARQ window size, a maximum number of retransmissions, a drop timer.

  The downlink PHY / MAC module 1954 is a PHY and MAC layer associated with the transmission of data information such as messages, packets, and / or frames via the wireless communication interface module 1908, such as from an access node 1900 to a termination node. Control processing. In some embodiments, the operation of the downlink PHY / MAC module 1954 includes both transmission and reception of control information such as signals and messages to coordinate the transmission of data information such as messages, packets, or frames. Configuration information 1930 includes configuration information that affects the operation of the downlink PHY / MAC module 1954, such as the frequency to be used for transmission, the bandwidth, the channel, the spreading or hopping code, and the identifier associated with the access node 1900. be able to.

  FIG. 20 shows an example of signaling and traffic flows between various modules included in exemplary end node 1800 and exemplary access node 1900. Terminal node 1800 in FIG. 20 and access node 1900 in FIG. 20 are simplified diagrams of terminal node 1800 in FIG. 18 and access node 1900 in FIG. 19, respectively. The example of FIG. 20 shows an application module 1828 that sends and receives data information such as traffic flows comprising a sequence of messages, packets, or frames. In the exemplary system situation of FIG. 17, the termination node 1800 of FIG. 20 can be any one of the termination nodes 1702-1712 shown in FIG. 17, and the application module 1828 included in the termination node 1800 of FIG. The data information may be exchanged with another node in the system, for example, another terminal node 1702-1712 or application server node 1726 as shown in FIG. In FIG. 20 and the following description, a node with which the terminal node 1800 in FIG. 20 exchanges data information is referred to as a corresponding node.

  Data information such as a traffic flow comprising a sequence of messages, packets, or frames sent from the application module 1828 in the end node 1800 to the corresponding node is sent to a series of modules 1838-1844 included in the end node 1800 for processing. Passing is indicated by a series of arrows 2002-2008, after which data information is sent from the end node 1800 to the access node 1900, such as via the wireless communication interface module 1804. Data information such as a traffic flow including a sequence of messages, packets, or frames sent from the application module 1828 in the end node 1800 to the corresponding node following reception by the access node 1900, such as via the wireless communication interface module 1908, For processing before being forwarded from the access node 1900 towards the corresponding node, such as being addressed to an intermediate node connected to the access node via the network / interconnect network interface module 1906 according to the routing information Passing through a series of modules 1938-1944 included in the access node 1900 is indicated by a series of arrows 2010-2018.

  Data information such as traffic flows including a sequence of messages, packets, or frames sent from the corresponding node to the application module 1828 in the end node 1828 is received by the access node 1900, such as via the network / interconnect network interface module 1906. Is then indicated by a series of arrows 2020-2028 through a series of modules 1946-1954 included in the access node 1900 for processing, after which the data information is transmitted via a wireless communication interface module 1908 and the like. And sent from the access node 1900 to the end node 1800. Data information such as a traffic flow including a sequence of messages, packets, or frames sent from the corresponding node to the application module 1828 in the termination node 1800 following reception by the termination node 1800, such as via the wireless communication interface module 1804, , Through a series of modules 1846 and 1848 included in the termination node 1800 for processing before being passed to the application module 1828 in the termination node 1800.

  In addition to exchanging data information such as traffic flows, FIG. 20 also illustrates exchanging control information such as signaling flows and / or communication interfaces. Specifically, in the example of FIG. 20, the exchange of control information between the control signaling module 1926 and the traffic control module 1928 included in the access node 1900 is shown. Similarly, in the example of FIG. 20, the exchange of control information between the control signaling module 1826 and the traffic control module 1830 included in the end node 1800 is also shown. In both the access node 1900 and the end node 1800, the individual control signaling modules 1926/1826 in the access node 1900 / the end node 1800 are changed to the application modules in the end node 1800 by exchanging control information between the modules as shown. The configuration and / or operation of the various modules included in the individual traffic control modules 1928/1830 as required to provide proper quality of service processing of data information such as traffic flows to and from 1828. Such as setting, changing, and / or monitoring.

  Also, the exchange of control information such as signaling flows and / or communication interfaces can be performed a) between another node and the control signaling module 1926 in the access node 1900, b) the application module 1828 in the end node 1800 and the end node 1800. Also shown between the control signaling module 1826 in the access node 1900 and c) between the individual control signaling modules in the access node 1900 and the end node 1800. The exchange of control information such as signaling flows and / or communication interfaces may include: a) one or more other nodes, such as access control node 1720 and / or application server node 1726, b) application module 1828 in end node 1800, or c) The combination of one or more other nodes and the application module 1828 in the termination node 1800 in the termination node 1800 affects the configuration and / or operation of the traffic control module 1928/1830 in both the access node 1900 and the termination node 1800. Enable. Various embodiments of the present invention may and may support all or only a portion of the illustrated control information exchange as desired.

  What has been described above includes examples of one or more embodiments. Of course, for the purpose of describing the foregoing embodiments, it is not possible to describe every possible combination of components or methods, and many other combinations and substitutions of the various embodiments are possible. Those skilled in the art will understand. Accordingly, the foregoing embodiments are intended to embrace all such alterations, modifications and variations that fall within the spirit and scope of the appended claims. Further, to the extent that the word "includes" is used in the detailed description or claims, such a word is interpreted when the word "comprising" is used as a transitional word in the claims. It is intended to be included as well.

FIG. 2 is a high-level block diagram illustrating a system provided to illustrate profile changes for roaming in a communication environment. It is a block diagram which shows the example of a network access system. It is a block diagram which shows the example of an authentication permission system. It is a block diagram which shows the example of an authentication permission system. It is a figure which shows the example of the content of the profile. It is a figure which shows the example of a format of a subscriber service set. It is a figure which shows the example of a service class type format. It is a figure which shows the example of a subscriber service type. It is a figure which shows the example of general roaming. It is a figure which shows the example of virtual homing. It is a figure which shows the example of virtual homing and roaming. 2 is a representative flow diagram illustrating a method of roaming and profile processing. 1 is a high-level block diagram illustrating a system that provides profile support during a roaming operation. FIG. 1 is a high-level block diagram illustrating a system that provides profile support during a roaming operation. FIG. 1 is a block diagram illustrating a system provided to illustrate a network that can support profile changes. FIG. FIG. 2 is a block diagram illustrating an apparatus for processing profiles and / or QoS parameters. It is a figure which shows the example of a communication system. It is a figure which shows the example of a termination | terminus node. It is a figure which shows the example of an access node. It is a figure which shows the example of the termination | terminus node which communicates with the example of an access node.

Claims (36)

A method of roaming between networks,
Receiving a request for network access in the visited network;
Receiving a profile from a home network in response to the request;
Selectively providing service to one or more access terminals based on at least a portion of the profile;
A method comprising:   The method of claim 1, wherein the service is associated with a quality of service (QoS) parameter.   The method according to claim 1, wherein the visited network changes, deletes, or adds to the profile.   The method of claim 3, wherein the visited network selectively provides a subset of services from the profile.   The method of claim 3, wherein the visited network provides additional services beyond those specified in the profile.   The method of claim 1, further comprising receiving the profile upon receipt of access authorization from the home network.   The method of claim 1, further comprising using a virtual homing component as part of a home network.   8. The method of claim 7, wherein the virtual homing component is associated with a mobile virtual network operator (MVNO).   The method of claim 8, wherein the virtual homing component is used with a roaming service.   The method of claim 1, further comprising performing authentication and authorization for a device on a visited network or a home network.   The method of claim 1, wherein the profile provides service differentiation between subscribers or application services allowed by a given subscriber.   The method of claim 1, further comprising modifying the profile according to an XML service description.   The profile may include a QoS parameter associated with the identification of a packet as belonging to a traffic flow, a parameter associated with traffic flow traffic adjustment, a parameter associated with traffic flow queuing / scheduling, or The method of claim 1, comprising parameters characterizing the traffic flow that enables an access node to determine a QoS configuration suitable for servicing the traffic flow. A memory that is associated with the home network component and is changeable by the visited network component and that retains instructions for receiving a profile associated with one or more services used to provide services to the roaming access terminal When,
A processor for executing the instructions;
A communication device comprising:   The communication apparatus according to claim 14, wherein the visited network component includes an authentication permission server that communicates with an authentication permission server associated with the home network component.   15. The communication device of claim 14, wherein the profile is associated with a quality of service (QoS) data set generated from the home network component.   The QoS data set is associated with one or more of latency associated with multiple traffic flows, a minimum data rate associated with multiple traffic flows, and a maximum data rate associated with multiple traffic flows. The communication device according to claim 16. Means for receiving a subscriber profile generated from a home network;
Means for changing the subscriber profile;
Means for providing a service based in part on the modified subscriber profile;
A communication device comprising:   The communication device of claim 18, wherein the means for changing the subscriber profile further comprises adding or deleting a service from the profile. Receiving a network service request from an access terminal;
Receiving a profile at a visited network component in view of the request;
Analyzing the profile to determine services available to process the request;
A machine-readable medium storing each machine-executable instruction.   The machine-readable medium of claim 20, further comprising modifying the profile in view of the available services.   The machine-readable medium of claim 21, wherein changing the profile further comprises adding a service to the profile, deleting a service from the profile, or editing a parameter in the profile. Requesting a subscriber profile taking into account visited network access requests;
Using the subscriber profile to selectively provide services by the profile as a subset of the profile or as a superset of the profile;
A processor that executes each instruction. A method of roaming between networks,
Receiving a profile request for network access in the home network;
Transmitting the profile from the home network in response to the profile request;
Generating an access authorization signal from the home network when transmitting the profile;
A method comprising:   25. The method of claim 24, wherein the profile includes a service associated with a quality of service (QoS) parameter.   The method of claim 24, further comprising changing, deleting, or adding a service to the profile.   The method of claim 24, further comprising using a virtual homing component as part of the home network.   28. The method of claim 27, wherein the virtual homing component is associated with a mobile virtual network operator (MVNO).   29. The method of claim 28, wherein the virtual homing component is used with a roaming service.   25. The method of claim 24, further comprising generating the profile according to an XML service description. A memory that is associated with the home network component and that can be modified by the service description component and that retains instructions for generating a profile associated with one or more services used to provide services to the roaming access terminal When,
A communication device comprising a processor that executes the instructions.   The communication device according to claim 31, wherein the service description component includes an XML schema component.   32. The communication device of claim 31, wherein the profile is associated with a quality of service (QoS) data set generated from the home network component. Means for generating a subscriber profile from the home network;
Means for annotating the profile to allow changes to the subscriber profile;
Means for granting access authority to the home network;
A communication device comprising: Receiving a profile request for network service in a home network in response to an access terminal request;
Generating a profile in consideration of the profile request;
Sending the profile as soon as access rights are granted from the home network;
A machine-readable medium storing each machine-executable instruction. Generating a subscriber profile taking into account visited network access requirements;
Enabling a change of a subscriber profile that can be used for a network other than a home network in order to facilitate selective provision of services by the profile;
A processor that executes each instruction.

Images