KR20090007618A - Modify profile for roaming in communication environment - Google Patents

Abstract

The present invention relates to systems and methods for roaming in a wireless communication environment. Roaming methods between networks are provided in one aspect. This 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 receiving the profile, selectively provide services to one or more access terminals based at least in part on the profile.

Description

PROFILE MODIFICATION FOR ROAMING IN A COMMUNICATIONS ENVIRONMENT}

The present invention relates generally to communication systems and more particularly to enabling profile modifications to support services when roaming between networks.

This application is a U.S. provisional patent with application number 60 / 837,656, filed August 14, 2006, and entitled "A Method and Apparatus for Network Access Subsystem"; application number 60 / 796,704 and filed 2006 US Provisional Patent, May 1, titled "A Method and Apparatus for Subscriber Service Framework", application number 60 / 797,010, filed May 1, 2006, and titled "A method and Apparatus for U.S. provisional patent with "Subscriber to Subscriber Profile to Authorize Subscriber", U.S. provisional patent with application number 60 / 797,029, filed May 1, 2006 and entitled "A Method and Apparatus for Quality of Service in a Flash Network" , US Provisional Patent Application No. 60 / 796,808, filed May 1, 2006, and entitled “A Method and Apparatus for Flash System”, Application No. 60 / 707,038, and filed May 1, 2006 And the name of the invention U.S. Provisional Patent with "A Method and Apparatus for Connection Control Protocol" and U.S. Provisional Application with application number 60 / 796,653, filed May 1, 2006 and entitled "A Method and Apparatus for Mobility Aware Resource Control" Claim the benefit of the patent, all of which are incorporated herein by reference.

Communication networks, such as wireless communication networks, broadband networks, and other suitable networks, are used in connection with data transfer, where data is word processing files, streaming video, multimedia files, voice data, and / or the like. May contain items. When using such networks, some subscribers to the networks may be provided different quality of service (QoS) parameters from other subscribers. For example, a first person may join a digital subscriber line (DSL) network, and first upload and download rates are provided, while a second person joined to the DSL network is subscribed to a different subscription than the first person. Can be paid for and different upload and download speeds can be provided. More specifically, the first subscriber may pay a first rate for 1 megabyte / second download connection rate while the second subscriber may pay a second rate for 512 kilobytes / second download connection rate .

In addition, different services may be provided to users of networks. For example, wireless network subscribers may have subscriptions that enable web browsing, text message delivery and reception, voice calls, data transmission (e.g., video, images, sound clips, ...), games, and the like. You can buy it. Because the delivery requirements of the application flows corresponding to the various services are different, it may be desirable to associate the traffic flows of the various services with different QoS parameters (e.g. latency, bandwidth, ...). . While existing communication networks only supported a relatively small set of services, emerging communication networks based on Internet protocols enable potentially unlimited sets of services. This demonstrates the need for managing improvements and associated QoS supports in control services.

Some communication networks support roaming capability, where a subscriber gains access through a visited network that is operating different from the home network to which the subscriber is subscribed. Typically, in such cases the visited home networks are based on similar technologies, and thus the visited network simply allows the subscriber to use the services provided by his home network. However, there is a need to control roaming of services more flexibly if there is a possibility that a number of different services in emerging communication networks are potentially associated with the desire to enable roaming between networks based on different technologies.

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

Roaming between networks is facilitated by modifiable profiles exchanged when the access terminal roams from a home network to a visited network. If the mobile access terminal is connected to a network other than the home network due to roaming, the visited network (from the terminal's point of view) may request a profile describing the services that may have been provided by the home network. The profile may be sent to the visited network upon receiving an access authorization for services from the home network. After receiving the profile, the visited network may optionally provide similar services specified by the profile, subsets of services specified by the profile, and / or services originally specified by the profile. In addition to these, they can provide a superset of services. Thus, the profile can be modified, where services can be added or deleted from the services originally specified by the home network. The services may include quality of service considerations associated with a plurality of different communication considerations such as bandwidth, latency, loss tolerances, and the like. By allowing a profile to be modified by the visited network or domains, communication performance can be dynamically upscaled or downscaled as conditions change.

To the accomplishment of the foregoing description and associated objects, specific illustrative aspects are described herein in connection with the following descriptions and the accompanying drawings. While these aspects are indicative, the claimed subject matter may be adopted in some of a variety of ways, and the claimed subject matter is also intended to include all such aspects and their equivalents. Other advantages and novel features may become apparent from the following detailed description when considered in connection with the drawings.

1 is a high level block diagram of a system provided to illustrate profile modification for roaming in a communication environment.

2 is a block diagram of an exemplary network access system.

3 and 4 are block diagrams illustrating an exemplary authentication and approval system.

5 illustrates exemplary content of a profile.

6 illustrates an exemplary format for a subscriber service set.

7 illustrates an example format for a service class type.

8 illustrates an exemplary subscriber service type.

9 shows a general roaming example.

10 is a diagram illustrating an example of virtual homing;

11 illustrates an example of virtual homing and roaming.

12 is an exemplary flow diagram illustrating one method for roaming and profile processing.

13 and 14 are high level block diagrams of a system for providing profile support during roaming operations.

15 is a block diagram of a system provided to illustrate an example network that can support profile modifications.

16 is a block diagram of an apparatus for processing profile and / or QoS parameters.

17 illustrates an example communication system.

18 illustrates an example end node.

19 illustrates an example access node.

20 illustrates an example end node in communication with an example access node.

Systems and methods are provided to facilitate roaming in a wireless communications network. In one aspect, a roaming method between networks is provided. This 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, selectively provide services to one or more access terminals based at least in part on the profile. The profile may be modified by the visited network to provide similar services, a subset of services, and / or a superset of services not originally specified by the home network.

Moreover, various aspects associated with a terminal are disclosed herein. A terminal may also be referred to as a system, user device, subscriber unit, subscriber station, mobile station, mobile device, remote station, remote terminal, access terminal, user terminal, user agent, or user equipment. User devices may include cellular phones, wireless telephones, Session Initiation Protocol (SIP) phones, wireless local loop (WLL) stations, PDAs, handheld devices with wireless connectivity, modules in terminals, host devices (e.g., , PCMCIA card) or other processing device connected to a wireless modem.

Moreover, aspects of the claimed subject matter can be implemented using computer or computing components to generate software, firmware, hardware, or any combination thereof using standard programming and / or engineering techniques to implement various aspects of the appended claims. It can be implemented as a method, apparatus or article of manufacture. The term "article of manufacture" as used herein is intended to include a computer program accessible from any computer-readable device, carrier, or media. For example, computer readable media may include magnetic storage devices (e.g. hard disks, floppy disks, magnetic strips ...), optical discs (e.g. compact discs (CD), digital versatile discs (DVD) ) ....), smart cards, and flash memory devices (eg, cards, sticks, key drives ...). Additionally, carrier waves may be used to transmit and receive computer-readable electronic data, such as data used to transmit and receive voice mail, or to access a network such as a cellular network. Of course, those skilled in the art will recognize that 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 modifications for roaming to facilitate communications in a wireless network. The wireless terminal 102 (also referred to as a host) communicates with an access node 104 that also communicates with the visited network or domain 106, from which the wireless or access terminal is serviced by the home network 110. Roaming encounters the visited network. It is noted that the access node 104 may also be considered as part of the visited network or domain 106. The access node 104 is also referred to as a base station or access router and can use the various nodes, elements and / or systems included in the visited network 106 for services such as service request authentication, service approval, session establishment, and the like. And they will be described in more detail below. Initially, 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 for the wireless terminal 102, an access grant 114 is generated by the home network and describes the services from the home network. Profile 120 is sent in response to the request.

Upon receipt of the profile 120, the visited network 106 may selectively provide services to one or more access terminals 102 based at least in part on the received profile 120. As will be described in more detail below, the services specified by the profile may relate to quality of service (QoS) parameters for an individual wireless terminal and a communication session established by a request to the visited network 106. In one aspect, the visited network 106 may process, modify, delete, or add services to the profile 120. This allows the visited network to selectively provide a subset of the services from the profile 120 and / or to provide additional services that are not specified by the profile. By allowing profile modifications, the visited network can dynamically tailor its offerings based on current resource conditions or other considerations.

In one aspect, the system 100 may be associated with a subscriber and / or subscriber device 102 when roaming, such as to gain access via the visited operator's network 110, for example as opposed to home. Allows control of associated quality of service (QoS) support and services. In this roaming scenario, services and QoS support defined by the home operator at 110 are optionally supported in the visited operator's network 106 and, if desired, the visited operator is an additional and / or alternative. It is desirable to have the flexibility of providing generic services and QoS support.

According to another aspect, the subscriber profile 120 may be included in, for example, an access grant message 114 sent from a home network 110 authentication and authorization server (AAS) to a visited network AAS. It should be understood that the profile 120 may be exchanged between other network components as well. Subsequently, the access grant message 114 is generated, where the subscriber profile 120 is sent, for example, from the visited AAS to the access node 104 and sends the access node 104 to it. The subscriber device 102 requests access. The subscriber profile 102 specifies the configuration of one or more QoS parameters and / or subsequent requests as needed to provide service differentiation between and / or between various application services authorized for use by a given subscriber. Pre-approval information for typical QoS configuration changes.

The subscriber profile 120 or other network component provided by the home AAS may be modified by the visited network 106, eg, one or more components in the visited AAS and / or the access node. have. Thus, the visited network operator may modify the subscriber profile 120 to match the services provided in the visited operator's network 106, eg, add, modify or delete services. By allowing modifications to the profile 120, the system 100 allows flexibility in controlling services and QoS when roaming. This allows subscriber services to be changed, such as added, modified, or deleted, by the visited network operator. This approach to changing the profile in the visited network 106 is also due to the flexibility of using XML (or other structure) to define services in the subscriber profile 120, provided service definitions. Enable evolution for.

Terminal 102 may include, for example, an SD card, a network card, a wireless network card, a computer (including laptops, desktops, personal digital assistants (PDAs)), mobile phones, smart phones, or a network. It can be a module such as any other suitable terminal that can be used to access it. Terminal 102 accesses the network by access node 104. For example, terminal 102 may communicate in conjunction with access node 104 by a wired connection, such as an Ethernet cable, a USB connection, or the like. In another example, the connection between terminal 102 and access node (! 04) may be wireless in nature, where access node (! 04) may be a base station, and terminal 102 may be a wireless terminal. For example, terminal 102 and access node 104 may include time division multiple access (TDMA), code division multiple access (CDMA), frequency division multiple access (FDMA), orthogonal frequency division multiplexing (OFDM), FLASH OFDM, The communication may be by any suitable wireless protocol such as 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, access node 104 may be, for example, a router, a switch, or the like. The access node 104 may include one or more interfaces, eg, communication modules, for communicating with other network nodes. Additionally, access node 104 may be a base station (or wireless access point) in a cellular type network, where the base stations (or wireless access points) are used to provide wireless coverage areas to a plurality of subscribers. Such base stations (or wireless access points) may be arranged to provide contiguous areas to one or more cellular phones and / or other wireless terminals.

As noted above, the system 100 may also include an authentication and authorization server (AAS) at 106 and 110, which allows the terminal 102 to transmit data over the network through the use of an access node 104. Assist in sending / receiving As shown as a separate entity, it is understood that AAS 106 may be included within access node 104. For authentication / authorization, terminal 102 may provide data to AAS 106 by access node 104 indicative of the identity of such terminal 102 and / or subscriber associated therewith. The access node 104 may relay identifying data to the AAS 106 without modification or may modify this data according to any suitable data format / protocol. Upon receiving the identification indicator, AAS 106 may authenticate the terminal / subscriber identity and determine whether terminal 102 (and / or subscriber) has been authorized for one or more services.

The process of authentication / authorization may include the exchange of one or more signals between the terminal 102, the access node 104, and / or the AAS 106, in some embodiments. If terminal 102 and / or subscriber associated with it are authorized for services, AAS 106 may relay the modified profile assigned to terminal 102 (or the associated subscriber) to access node 104. Wherein the profile includes a description of at least QoS parameters associated with one or more traffic flows for terminal 102, the data flow comprising a series of associated data packets (eg, packet headers and / or (Identified based on investigation of packet payloads). The profile 120 may also include filter rules that facilitate the association of data packets into traffic flows and the association of specified QoS processes with specific traffic flows and / or data packets. For example, data packets with headers indicating that these packets are associated with voice data may be referred to collectively as traffic flows. Similarly, data packets indicating that these packets are associated with video data can be individual traffic flows.

The access node 104 may, upon receipt of the profile, monitor and enforce the QoS processing described in the received profile. For example, a parameter that may be used in connection with the described QoS processing may relate to an acceptable latency associated with the traffic flow, and the access node 104 is acceptable as described in the profile provided from the AAS 106. Scheduling may be performed for traffic flows to maintain latency. Other QoS parameters in the received profile may relate to the minimum acceptable data rate for a particular traffic flow type, the maximum acceptable data rate for a particular traffic flow type, and the like. These parameters are numerically defined (eg, the minimum data rate for the first traffic flow type is 128 Kb / sec) and / or relatively (eg, the latency for the first traffic flow type is second). Half of the latency for the traffic flow type). In addition, the definition of parameters is conditioned on the specific system or network state (s). In one example, a particular parameter may be defined relatively and then numerically defined until a threshold is reached (eg, the minimum data rate for the first traffic flow should be twice the second traffic flow but 1 Not exceed Mbyte / sec).

In addition, the profile provided to the access node 104 from the AAS 106 may support object instances in that profile, thus reducing the duplication of parameter definitions within the profile. For example, a game application authorized to be used for terminal 102 may use three parallel traffic flows to support such an application. Rather than defining parameters for each traffic flow, a definition for a single traffic flow can be generated, and instances of this definition can be used for associated traffic flows. In addition, the profile may include filter (eg, classification) rules, wherein the filter rules may be used in connection with identifying a particular traffic flow and an instance that determines QoS processing to assign to the traffic flow. You can associate this flow with. The access node 104 may be configured to, upon receipt of the profile, provide QoS processing to terminal 102 as described in the profile and the pre-approved data set 120. Thus, access node 104 may provide different QoS flows for various traffic flows and multiple users, thereby improving system performance and user experience.

Referring now to FIG. 2, an example network access system 200 is illustrated that can use modifiable profile data when roaming. Prior to proceeding, the components and protocols shown in the system 200 are illustrative in nature, and similar components other than those shown may be employed, and / or other protocols besides the illustrated protocols may be used. It is noted. The system 200 includes a wireless terminal (WT) 210 connected at 220 to a base station (BS) 216 via flash wireless interfaces. The BS 216 communicates with a local authentication and authorization (AAL) server 224 via network links. The 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. Home network 240 may be serviced by the AA server 230 including the original service configuration records of the WT 210. Local or visited network 244 is a network through which the WT 210 obtains a network connection.

If the WT 210 attempts to connect directly to the home network 240 (due to its geographical location), the connection to the home network may, for example, differ from that shown in FIG. 2. All may include communication between the located BS, MNS / AAL and AAH. It is noted that the WT 210 is local to the visited network 244 when roaming (shown in FIG. 2), otherwise it is local to the home network 240. The system 200 also shows subsequent example protocols used when controlling network access. These may include access control protocol (CCP), security related protocol (SAP), remote dial-in user service (RADIUS) protocol, and / or extensible authentication protocol (EAP). As can be appreciated, other protocols can be used to control network access.

Referring now to FIGS. 3 and 4 together, two tiered authentication protocols are illustrated. In one example, two phases of authentication for an access network may be adopted using one or two different Extensible Authentication Protocol (EAP) schemes. The first state shown in FIG. 3 includes authentication between wireless terminal (WT) 310 and home network AA server (AAH) via base station 330 and local network AA server (AAL) 340. The second state, as shown in FIG. 4, achieves authentication between the WT 310 and the local network AA server 340. The two-state authentication procedure generally occurs regardless of whether the WT 310 is located within its home operator network or roams with another operator's network. The WT 310 is expected to be serviced locally by an AAL 340 independent of the AAH 310. Two-state authentication not only allows roamable scalable roaming, but also provides for proper processing of key items or services in the local network, which are home or visited networks. The two states of the EAP should be independent of each other. In other words, different mechanisms may be used in each state while mutual authentication of the WT 310 and AA servers 320, 340 may be maintained.

In the first authentication state shown in FIG. 3, the AAL 340 acts as a RADIUS proxy. It should be understood that other authentication protocols may be used. The second state achieves authentication between the WT 310 and the local network (AAL server) 340, where the AAH is not included as shown in FIG. Adding a second state of authentication with the local network allows the WT 310 to establish a trust locally. The local network may be part of an external operator's network (ie, not a home operator) or may be part of the home operator's administrative domain. Local trust settings enable the use of the AAL 340 as a trusted third party for other protocols to shield the AAF / AAH from local mobility impacts (whether or not the WT roams). And may be used for a variety of reasons, including to provide a greater degree of subscriber identity privacy.

Authentication status with the local network allows subscriber anonymity support. The AAL 340 assigns a temporary identifier to the WT 310, which cannot be linked to the permanent identifier of the WT by "listening" the air interface. This is in part due to the mechanisms that occur so that the temporary WT identifier is securely communicated to the WT 310 to ensure confidentiality. The WT 310 may then use this temporary identifier to obtain additional network access in this local network, or for other host configuration purposes as required if the WT is in the home network. have. In addition to establishing trusts, profiles can be exchanged to further define services.

Referring now to FIG. 5, an example profile 500 in accordance with one or more aspects described herein is illustrated. The profile 500 is a logical grouping of parameters specifying aspects of services authorized for use by a subscriber (specific mobile terminal). However, as long as it is in accordance with the claims, the fields / elements in the profile 500 may be changed, such that the way elements are specified may change, the logical arrangements may change, the number of elements may change, It is understood that the names of the elements may be changed. The profile 500 may be associated with a flash service element 502, which is a logical group of parameters associated with establishing and maintaining a connection by an interface, such as a wireless interface, including a FLASH wireless interface. Grouping. The flash service element 502 may be associated with a location constraint element 504, where the location constraint element is a collection of parameters that specify locations (or join points), and through the locations, the The subscriber may be authorized to access the services. When a location constraint element 504 is included within the profile 500, access may be restricted as specified by the elements included within the location constraint element 504. Omission of the location constraint element 504 indicates that access is not limited to a list of designated locations, but may be restricted by other means such as roaming agreements.

The profile 500 may further include a network element 506, which may be a set of parameters associated with a particular network, through which the subscriber (terminal) grants access to services. I can receive it. Network element 506 may be associated with network identifier element 508, which is a globally unique identifier of the network, through which the subscriber may be granted access to services. The network element 506 may further be associated with the zone element 510, which may be defined as a set of parameters associated with a particular zone in the network, through which the subscriber may access access to services. Can be approved. Access in the network may be limited to the set of indicated zones in the zone element 510. The absence of zone element 510 may indicate that access in the network identified within network identifier element 508 is not limited to a specified set of zones.

Zone element 510 may be associated with zone identifier element 512, which may be a locally unique identifier of a zone in a network, through which the subscriber is authorized to access services. Can be. Zone element 510 may also be associated with base station element 514, which may be defined as a set of parameters associated with a particular base station or access node (in a zone of a network), wherein the particular base station or The access node allows the subscriber to be granted access to services. Access in the zone may be limited to the indicated set of base stations in base station element 514. The absence of the base station element 514 may indicate that access in the identified zone is not limited to a particular set of base stations.

Base station element 514 may be associated with a base station identifier 516, which may be an identifier of a locally unique base station within the area of the network, through which the subscriber has access to services. Can be approved. Base station 514 may further be associated with link element 518, which may be a set of parameters associated with a particular link (corresponding to an identified base station within the area of the network), and over the particular link. The subscriber may be authorized to access the services. For example, access by a base station may be limited to a set of links designated within the link element 518, and the absence of a link element 518 in a profile may restrict access by the corresponding base station to a particular set of links. Can be displayed.

The link element 518 may be associated with a logical link control identifier element 520, which may be an identifier of a locally unique link corresponding to a base station within a zone of the network, The subscribers can be authorized to access services. Link element 518 may also be associated with connection element 522, which is a set of parameters associated with a particular connection, through which the subscriber is granted access to services. For example, access by a link may be limited to the set of indicated connections. The absence of a connection element may indicate that access by the corresponding link is not limited to a specified set of connections. Thus, if access by a particular link is not further restricted, it may be desirable not to include the connection element 522 in the profile 500. The connection element 522 may be associated with a connection identifier element 524, which may be an identifier of a locally unique connection corresponding to a link and a base station within a zone of the network, and through the network The subscriber may be authorized to access the services.

Profile 500 may additionally include a location update interval element 526, where the location update interval element may be a duration (eg, seconds) between successive instances in time, where the location update is an example. For example, these terminals must be performed by the wireless terminals while in the "sleep" mode. The monitoring interval element 528 can indicate the duration (eg, milliseconds) between successive instances in time, where monitoring for the pages will be performed by the wireless terminal during "sleep" mode. Profile 500 may additionally include a service set element 530 (described in detail below), which is a set of service class and subscriber service logical data configurations related to enabling and controlling services. It can include a set. This element 530 may include QoS parameters related to specific traffic flows associated with a particular terminal (eg, wireless terminal). The element 530 may also include pre-approved templates or data for dynamic quality of service configuration from the access node. The information consisting of the profiles containing the QoS parameters can be conveyed using XML, and other structures and other characteristics, for example the data type, formats, and / or value constraints of the information associated with It can be restricted by an XML schema.

Referring now to FIG. 6, an exemplary service set element 600 (eg, service set element 530 of FIG. 5) is shown and described. However, it should be understood that such elements are provided by way of example only, and that elements and / or logical associations between the elements may be deleted, changed, and maintained in accordance with the claimed subject matter. QoS definition and control may be based at least in part on two data configurations within service set element 600: service class element 602 and subscriber service element 604. As shown in the “subscriber” service element, it should be understood that such an element may be associated with a subscriber device such as, for example, a wireless terminal. Thus, the subscriber service element may be included in the profile as the outcome of the terminal's identification indicators and / or subscriber's identity indicators. Depending on the service to be provided, the profile may include multiple occurrences of any or all of these data configurations. The service class element 602 (data configuration) may provide a common mechanism for specifying QoS processing of traffic flows associated with instances of a particular service class. For example, packets provided to / from a host device may be classified into one or more traffic flows, where a given traffic flow may include only a particular packet stream corresponding to a particular application or a packet stream corresponding to multiple applications. May include aggregation.

Each identified traffic flow may be associated with an instance of one or more service class elements 602. The associated service class of each identified traffic flow can provide the basis for admission control, scheduling, and traffic coordination functions of the host device and / or access node (access router, base station, etc.). While the service class element 602 may belong to QoS processing, the service set element 600 may provide policy control (e.g., grant for services) and service definition (e.g., setting parameter values, QoS). Associations with identified traffic flows to support instances of specific service classes ...). Each service set element may include zero or more service class elements and zero or more subscriber service elements.

Referring now to Figure 7, an exemplary service class element (e.g., service class element 602 shown in Figure 6 is illustrated.) Again, service class element 700 is one to limit QoS processing in a profile. Other ways to do so are contemplated by the inventor and are intended to be within the scope of the claims appended hereto: Service class element 700 includes a service class identifier 702. This may be a globally unique identifier (eg, 32 bits) of a defined service class, which may be represented using the symbol x: y, where x and y are values of service class identifier 702. It may be hexadecimal values corresponding to the first number of bits (prefix) and the second number of bits (suffix), respectively. Sets of the classified services defined by service class may use a common prefix identifier.

The service class element 700 may also include an admission priority element 704. For service classes that specify target delivery targets that require allocation of dedicated resources (eg, service classes that specify minimum rate and / or latency bounds), the admission priority element 704 may assign a resource. It indicates the relative order of these service classes for the purpose of making admission control decisions. The specific use of the admission priority may be implementation dependent, and the possible uses may include priority for priority queuing of pending resource allocation requests and / or preemption of resource allocations.

The maximum rate element 706 can indicate the maximum data rate that can be provided in the traffic flow associated with an instance of a particular class of service. The maximum rate element 706 may be further defined by token bucket parameters as described within the token rate element 708 and the bucket depth element 710. For example, token rate element 708 may be in kilobytes / second (where kilo represents 1000) and bucket depth element 710 may be in bytes.

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

The share rate element 724 is relative to the service (eg, rate or resources) that a traffic flow associated with an instance of the service class should receive when competing with services having traffic flows associated with other service class instances. Can be used to indicate the ratio. Thus, after the target delivery targets (eg, minimum rate and / or latency bounds) are satisfied for all of the admitted service class instances, any remaining service capacities are corresponding to those of the service class instances. It should be distributed among competing service class instances that are not limited in proportion to the shared weights (eg, by indicating the maximum rate).

Latency tolerance element 726 indicates an acceptable access link latency for packets belonging to a traffic flow associated with an instance of the service class, where the access link latency includes delays associated with queuing, scheduling, and transmission. . With a high probability, packets belonging to a traffic flow associated with an instance of the class of service may be delivered over an access link having a latency below the indicated tolerance. As an example, latency tolerance element 726 may be associated with millisecond units.

The loss tolerance element 728 can indicate an acceptable loss probability for packets belonging to a traffic flow associated with an instance of the service class, the source of the loss including queue management and irrecoverable transmission errors. Packets belonging to a traffic flow associated with an instance of the identified service class must be delivered over an access link with a loss probability below the indicated tolerance. The loss tolerance element 728 may include data associated with the number of lost packets per 100,000 packet, for example. Differentiated services (DS) code point 730 may indicate a DS code point, and packets in the traffic flow associated with the instance of the service class identified as the DS code point should be marked.

The compression hint element 732 may indicate that header compression is easily applicable to packets belonging to a traffic flow associated with a particular instance of a service class. The compression hint element 732 may include information to assist in determining the applicable compression type and / or parameters required for compression.

Referring to FIG. 8, an example subscriber service element 800 is shown and described. Again, element 800 is provided as one specific way to define a service. Other ways of doing so may also be considered by the inventors and are intended to be within the scope of the claims appended hereto. The subscriber service element 800 may include a subscriber service identifier element 804, which may be a globally unique identifier of a particular subscriber service, which may be represented using the sign x: y, where x and y are Each may be hexadecimal values corresponding to the first bit set (prefix) and the last bit set (suffix) of the subscriber service identifier element 804. A set of subscriber services defined by a particular operator or standard organization may use a common subscriber service identifier prefix. The absence of the zone element 806 may indicate the domain to which the subscriber service is associated, and the zone element 806 may indicate the subscriber services associated with the local domain. This provides the basis for better control 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, for example, an IP address and a host name, of the PDP to be used for QoS configuration change requests associated with a particular subscriber service. The subscriber service element 800 is an exit element that is a logical grouping of service class instance templates that can be applied to enter traffic from an access router to subscribers over a corresponding access link, service class instances, filter rules, and corresponding access links. 812, and an incoming element 814, which is a logical grouping of service class instance templates that is applicable for injecting traffic from a subscriber to an access router via service class instances, filter rules, and a corresponding access link.

Each of the exit element 812 and the incoming element 814 may include one or more service class instance elements 816 and 818, respectively. Service class instance elements 816 and 818 may define static service class instances, for example, identify a particular service class element, wherein an instance of the particular service class element is required, and The particular service class element and traffic flow will be associated by one or more filter rules. Static service class instances can be conceptually viewed as persistently requested instances of a particular service class. Depending on the parameters of the corresponding service class, an admission control decision may be required. Thus, at any given point in time, a static service class instance may or may not be acted upon (eg, admitted) depending on resource availability and admission priority, but should be active whenever possible.

The outlet element 812 and the inlet element 814 may also include one or more filter rule elements 820, 822, respectively. Filter rule elements 820 and 822 define classifier filter rules for the purpose of mapping packets belonging to traffic flows having defined service class instances. Each filter rule element specifies the order that should be applied to other filter rule elements, a specification of packet matching criteria (eg, values or ranges of values corresponding to one or more packet header or payload fields). Priority to indicate, and an indication of the service class instance to which matching packets should be associated. Filter rule elements 820, 822 may be used to discard packets belonging to a traffic flow by mapping the packets to an instance of a null service class.

The exit element 812 and the incoming element 814 can also each include one or more service class instance template elements 830, 840 individually. Service class instance template elements 830,840 specify pre-approval for dynamic service class instances, for example, identifying the particular service class element from which the instance can be dynamically requested, as well as Filter rules used to associate traffic flows with service class instances and / or policy constraints on the requested service class instance.

Referring to FIG. 9, an exemplary roaming system 900 that can use the modifiable profiles described above is shown. The system 900 illustrates a roaming scenario, where subscriber host (SH) 910 obtains access through a visited network 920, ie, not its home network 930. In this example, there may typically be a roaming agreement 940 between the home network and visited network operators. The home network operator may typically be concerned with granting permission for authentication and access of the SH 910. Assuming that the home operator grants access to the SH 910, the visited network operator enables the SH to obtain services over his local access network. However, basic network services and higher layer services may be provided by one or both network operators. Dotted lines in system 900 conceptually represent basic network services and / or higher layer services. When roaming, it is possible for the SH 910 to receive services from the visited / local domain 920, home network or domain 930, or both. Thus, subscriber service mechanisms (e.g., a subscriber profile indicating authorization for services must provide sufficient information to enable support of services by either domain. The scenario system 900 is also mobile virtual). An example of a network operator (MVNO) may be shown, for example, where the home network 930 is an MVNO, in which case the MVNO is the software required to support "roaming" and the required network El. May include, but does not include, an access network, while SH 910 is administratively associated with an MVNO, the SH 910 is not directly accessible to the home network 930, It appears to roam through the visited network 920.

Referring to FIG. 10, the system 1000 illustrates a virtual homing scenario. The virtual homing scenario shown by the system 1000 represents another example of supporting MVNO, for example, when the virtual home 1030 is an MVNO and also supports a virtual private network (VPN). An example is shown, for example, when the virtual home 1030 is a private network. The general distinction from the system 900 described above is within the system 1000, where the SH 1010 is administratively associated with a local network 1020, through which the SH gains access via the local network, In other words, the local network is the home network. Thus, the local / home network operator is typically associated with permission authorization for authentication and access of the SH1010. However, the SH 1010 also has an association with the illustrated virtual home 1030, which may incorporate an MVNO or an entity for providing a private, eg VPN service. As in the system 900, basic network services, such as addressing / routing as well as potentially higher layer services, may be added to the home / local domain 1020, the virtual home domain 1030, or both. Dotted lines are shown that may be provided by.

Referring to FIG. 11, the system 1100 illustrates a virtual homing and roaming scenario. The system 1100 represents a combination of items shown in the systems 900 and 1000 described above. In this example, SH 1110 is associated with home network 1120 and virtual home 1130 while gaining access via visited network 1140. Again, a home network operator is typically associated with authorization of authorization for authentication and access of the SH 1110. However, in this system 1100, basic network services, such as addressing / routing as well as potentially higher layer services, are visited / local domain 1140, home domain 1120, virtual home domain 1130. Or three dashed arrows are shown to indicate that they may be provided by a combination of the three domains.

Referring to FIG. 12, a method 1200 associated with profile modification and roaming is shown. For simplicity of description, the method is shown and described as a series of acts, but it will be understood that the method is not limited by the order of the acts, because some acts, according to one or more embodiments, This may occur concurrently and / or in different orders with the other methods described and illustrated in FIG. For example, those skilled in the art will understand that an alternative may appear as a series of interrelated states or events, such as a state diagram. Moreover, not all illustrated acts may be used to implement a methodology in accordance with the claimed subject matter.

Referring specifically to FIG. 12, the method 1200 is illustrated. The method 1200 begins at 1202 and a request is generated for services from the visited network at 1204. For example, a mobile terminal may initially have been authorized through its home network and now because of its location, and the mobile terminal now requests access from subsequent networks, often referred to as the visited network or domain. At 1206, a profile is requested from the home network. This request may be generated at 1204 by the visited network in response to the request for services. The profile may currently specify services such as quality of service parameters supported, for example, if the terminal is approved by the home network. At 1208, the profile is sent from the home network to the visited network when generating an access grant by the home network. As noted previously, the home network may include virtual aspects such as provided by a mobile virtual network operator (MVNO) or other virtual private network component.

The access grant may occur after handshaking signals or codes are exchanged between the home network and the visited network. At 1210, the received profile may remain unchanged or modified if desired. Profile modifications may include adding services to the profile, deleting services from the profile, and / or adjusting parameters for an individual service within the profile. Thus, the visited network provides similar services to the home network in relation to the received profile and provides a reduced set of services if the profile deletes one or more services from the profile, or the visit When a network adds services to the received profile, it can provide a superset of services. At 1212, the profile may be used to provide a set of desired services to the wireless access terminal.

Referring now to Figures 13 and 14 at once, systems are provided that are associated with roaming and modifying profiles for terminals, operator networks, access nodes, and traffic flows the access nodes have. The systems appear as a series of interrelated functional blocks, which can represent functions implemented as a processor, software, hardware, firmware, or any suitable combination thereof.

Referring specifically to FIG. 13, illustrated is a system 1300 that facilitates communication from visited networks. The system 1300 includes a logic module 1302 for receiving a subscriber profile generated from a home network. Logic module 1304 may be employed to modify the subscriber profile, and logic module 1306 is used to provide services based at least in part on the modified subscriber profile. Modifying the subscriber profile may include adding or deleting services from the profile or modifying / editing parameters in the profile.

Referring now to FIG. 14, system 1400 illustrates a system 1400 that facilitates communication from a home network in a roaming environment. The system 1400 includes a logic module 1402 for generating a subscriber profile from a home network. This includes a logic module 1404 for annotating the subscriber profile to enable modifications to the profile and a logic module 1406 for granting access to the home network.

Referring now to FIG. 15, an example network 1500 is illustrated that may employ profile data for roaming between networks. The system 1500 shows an operator's inter-network 1510 with two access routers (AR) 1514, 1518, and some additional network elements, the access routers 1514. The subscriber host (SH) 1520 may gain access via 1518. Logical interfaces between the various elements are represented using dashed lines. The ARs 1514-1518 are network elements that are in the context of service control because these network elements control access to services available through the operator's infrastructure and through these access links. This is because it is located to directly control QoS for services. However, many other network elements likewise play a role in a complete solution, for example to control the operations of the ARs 1514-1518. The following description deals with each of the logical interfaces shown in the system 1500, as well as associated network elements.

A trusted indication of subscriber identity (or subscriber identity associated with the SH 1520) is fundamental to the notion of controlling services on an individual subscriber basis. Typically, the indicated identities of subscribers are authenticated using, for example, Extensible Authentication Protocol (EAP) before being granted access to the network and higher layer services. This initial authentication and authorization process commonly involves communication between the elements and, for example, using AR1514-1518 and individual authentication and authorization servers, for example using a remote dial-in user service (RADIUS) protocol. Access is requested via the element, such as (AAS) 1530. Assuming that the identity of the subscriber is authenticated by the AAS 1530 and that the subscriber 1520 is authorized to obtain access, an indication that access can be granted is the element for which access is requested from the AAS 1530. Will come back.

Following an initial access grant, the AR 1514-1518 may begin sending accounting information, such as packet / byte counts, to an accounting server (ACS) 1540. Accounting for existing IP best effort service often consists of simple aggregate packet / byte counts for transmitted / received traffic. However, supporting a richer set of subscriber services also readily adopts accounting mechanisms that enable service-based billing and billing. Thus, for example, the accounting information collected / reported by the AR 1514-1518 should include details considering the levels of services used and / or provided QoS.

In accordance with the architecture presented herein, the SH 1520 changes its joining point from one AR to another, and the process is generally referred to as handoff. Mobile IP (MIP) is an approach to supporting mobility in IP internetworkings that allows tunnels to manage routing / forwarding to allow the mobile host to continue using the same address as it changes the join point. Mechanisms for context transfer (CT) can be used to minimize service disruption during handoff. By conveying information about the QoS configuration between the ARs in service approval and handoff, the equivalent service can be set up faster and more efficiently with the new AR. Upon receiving QoS configuration information associated with the SH 1520 moving to the new AR, the new AR must perform admission control to determine whether sufficient resources are available before being provided to the indicated service.

The resource control interface 1550 uses a signaling protocol by which the SH 1550 can request QoS configuration information following an initial access grant. As noted above, this may include a set of available QoS data and parameters that may be requested by the SH 1520 as dynamic conditions are required. In general, one cannot assume that end-to-end QoS is supported between the SH 1520 and another host in communication with the SH. However, the system provides a QoS architecture for a wide range of services, and resource reserve is required only in the AR 1514-1518, not along the entire data path. If resource reserve is requested at additional nodes along the data paths, alternative or additional resource control signaling may be used. According to the model, the SH 1520 should be able to request resources for the received and transmitted traffic. Although the system 1500 illustrates a resource control interface 1550 between the SH 1520 and an AR, on behalf of the SH, an equivalent from the operator's internetwork 1510, an operator host (OH) or an application server, is equivalent. It is also possible to support QoS configuration via an alternative or similar resource control interface.

The policy control interface 1554 represents a mechanism by which the authorization may be checked, for example for QoS configuration changes requested via the resource control interface 1550. The policy control interface 1554 is shown between non-specific network elements that function as the AR 1514 and PDP 1560, where the PDP function is, for example, a dedicated policy server, an application server, or some Note that it can be located in other network elements. A possible reason for this distinction is that the proper placement of the PDP function 1560 may depend on a particular service. In general, different services may also be associated with different PDPs, and according to some embodiments of the present invention, the service definition includes an indication of the associated PDP.

16 illustrates a communication device 1600, which may be, for example, a wireless communication device such as a wireless terminal. Additionally or alternatively, communication device 1600 may reside within a wired network. The communications device 1600 can include a memory 1602 that can retain instructions for configuring such a device for QoS data (and associated traffic flows) for the terminal. Additionally, communications device 1600 may include a processor 1604 capable of executing instructions in memory 1602 and / or instructions received from other network devices, which instructions may include communications device 1600 or related communications. May be associated with configuring the device.

Memory 1602 retains instructions for receiving a profile associated with one or more services, where the profile may be associated with a home network component and modifiable via a visited network component, the profile being directed to a roaming access terminal. Used to provide services. In another aspect, the memory holds instructions for creating a profile associated with one or more services, where the profile may be associated with home network components and may be modifiable through a service description component. The profile can be used, for example, to provide services to a roaming access terminal.

17 is provided to illustrate an example communication system 1700 consisting of a plurality of nodes interconnected by communication links, to provide further context for one or more embodiments described herein. The system 1700 can use Orthogonal Frequency Division Multiplexing (OFDM) signals to transmit information over wireless links. However, other types of signals, such as code division multiple access (CDMA) signals or time division multiple access (TDMA) signals, are also taken into account (along with signals used in land-based networks). Nodes in the communication system 1700 exchange information using signals such as messages, for example based on communication protocols such as the Internet Protocol (IP). Communication links of the communication system 1700 may be implemented using, for example, wires, fiber optic cables, and / or wireless communication technologies. The system 1700 includes a plurality of end nodes 1702-1712, wherein the plurality of end nodes access the communication system 1700 by a plurality of access nodes 1714-1718. End nodes 1702-1712 can be, for example, wireless communication devices and terminals, and the access nodes 1714-1718 can be, for example, wireless access routers or base stations. The communication system 1700 also includes a number of other nodes 1720-1730 that are used to provide interconnection or to provide specific services and 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 correspond to corresponding networks. Links 1732-1738 are individually connected to intermediate network node 1728. In some embodiments, the access node, e.g., a remote authentication dial-in user service (RADIUS) or diameter server, may authenticate, authorize, and / or account for end nodes and / or services associated with end nodes. Support them. In some embodiments, the mobility support node 1722, for example, the mobile IP home agent and / or the context delivery server, is located between the rediredction and / or access nodes to / from the end nodes. The transfer of state associated with the end nodes supports the mobility of the end nodes between the access nodes, eg handoff. In some embodiments, a policy control node 1724, for example, a policy server or policy decision point (PDP), supports policy approval for services or application layer sessions. In some embodiments, the application server node 1726, eg, a session initiation protocol server, streaming media server, or other application layer server, supports session signaling for services available to end nodes and And / or provide content or services available to the end nodes.

Intermediate network node 1728 in network 1760 provides interconnection to network nodes that are external from the perspective of network 1760 by network link 1734. The network link 1734 is connected to the intermediate network node 1730, which further provides access to the access nodes 1714, 1416 and 1718 by the network links 1736-1740. . Each access node 1714-1718 is shown by corresponding access links 1702-1752 as providing connection to end nodes 1702-1712, respectively. In the communication system 1700, each access node 1714-1718 is shown as using a radio technology, such as, for example, wireless access links, to provide access. However, wired technology may also be used in connection with providing access. The wireless coverage area, for example communication cells 1754-1758 of each access node 1714-1718, is shown as a circle surrounding the corresponding node.

The communication system 1700 can be used as the basis for the description of the various embodiments described herein. Alternative embodiments include various network topologies, where the number and type of nodes (including network nodes, access nodes, end nodes as well as various control, support and server nodes), the number and type of links , And interconnections between the various nodes may be different from interconnections in communication system 1700. In addition, some of the functional entities shown in communication system 1700 may be omitted or combined. The location and placement of these functional entities may also change.

18 shows an example end node 1800, which is a wireless terminal, for example. End node 1800 represents an apparatus that can be used as any one of end 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, by bus 1810, various components of the end node 1800 may exchange information, signals, and data. Components 1802-1808 of the end node 1800 can be located within the housing 1812.

The wireless communication interface module 1804 provides a mechanism by which internal components of the end node 1800 may transmit and receive signals to / from external devices and network nodes, eg, access nodes. Can be. The wireless communication interface module 1804 is a receiver module 1814 with a corresponding receive antenna 1816, used for coupling the end node 1800 to other network nodes, for example, by wireless communication channels. And a transmitter module 1818 having a corresponding transmit antenna 1820.

End node 1800 may include a user input device 1822, such as a keypad and a user output device 1824, such as a display, which may be connected to a bus (via user input / output interface 1806). 1810). Thus, user input / output devices 1822 and 1824 can exchange information, signals, and data using user input / output interface 1806 and other components of end node 1800 by bus 1810. Can be. User input / output interface 1806 and associated devices 1822 and 1824 provide mechanisms that enable a user to operate end node 1800 to perform various tasks. In particular, user input device 1822 and user output device 1824 allow users to execute applications, such as modules, programs, in end node 1800 and memory 1808 of end node 1800. , Routines, and / or functions to allow control.

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

The control signaling module 1826 controls the configuration and / or operation of various aspects of the end node 1800, including, for example, the traffic control module 1830, as well as the configuration information 1832 and various additional modules included. To do this, for example, control processing associated with receiving and transmitting signals such as messages. In some embodiments, the control signaling module 1826 may provide status information, eg, parameters, associated with the operation of the end node 1800 and one or more signaling protocols supported by the control signaling module 1826. , Status, and / or other information. In particular, control signaling module 1826 includes configuration information such as, for example, end node identification and / or parameter settings, and information about current processing status, status of pending message transactions, and the like. The same operation information may be included.

Application module 1828 controls processing and communications related to one or more applications supported by end node 1800. In some embodiments, application module 1828 processing may include input / output of information by the user input / output interface 1806, manipulation of information associated with the application, and / or signals associated with the application, for example. For example, tasks related to receiving or sending messages. In some embodiments, application module 1828 includes state information, eg, parameters, state, and / or other information regarding the operation of one or more applications supported by application module 1828. In particular, application module 1828 may include configuration information such as, for example, user identification information and / or parameter settings, and operational information such as, for example, information about current processing status, status of pending responses, and the like. have. Applications supported by the application module 1828 include, for example, Voice over IP (VoIP), web browsing, streaming audio / video, instant messaging, file sharing, games, and the like.

The traffic control module 1830 controls the processing associated with receiving and transmitting data information such as, for example, messages, packets, and / or frames via the wireless communication interface module 1804. The exemplary traffic control module 1830 includes not only configuration information 1832, but also various additional modules that control various aspects of QoS for packets and / or traffic flows, such as, for example, a sequence of associated packets. Various additional modules are included, in some embodiments, to perform certain functions and operations as needed for certain aspects of traffic control. Modules may be omitted and / or combined when necessary according to the functional requirements of traffic control. A description of each additional module included in the traffic control module 1830 follows.

The admission control module 1834 maintains information about resource usage / availability, and determines whether sufficient resources are available to support QoS parameters that are preferably associated with specific traffic flows. Resource availability information maintained by the admission control module 1834 includes, for example, packet and / or frame queuing capacity, scheduling capacity, as well as processing and memory capacity used to support one or more traffic flows. The control signaling module 1826, the application module 1828, and / or other modules included in the end node 1800 may be used to determine whether sufficient resources are available to support new or modified traffic flows. 1834, where the admission control decision is a function of the QoS parameters of the particular traffic flow and the QoS parameters defined within the profile. The configuration information 1832 can be used to indicate, for example, parameter settings affecting the operation of the admission control module 1834, eg, the percentage of resources that can be allocated prior to rejecting further requests. It may include configuration information such as a threshold.

The uplink scheduler module 1836 may, for example, send data information to be transmitted by the wireless communication interface module 1804, eg, messages, packets and / or frames, from the end node 1800 to the access node. For example, control of allocation of transmission resources such as information coding rate, transmission time slots, and / or transmission power, and processing related to transmission scheduling such as order and / or timing. The uplink scheduler module 1836 can schedule transmissions and allocate transmission resources as a function of QoS parameter associated with one or more traffic flows. In some embodiments, scheduling and / or resource allocation operations are additionally a function of channel conditions and other factors, eg, power cost.

The uplink PHY / MAC module 1838 is, for example, from the end node 1800 to the access node, by the wireless communication interface module 1804, for example data such as messages, packets and / or frames. Controls physical (PHY) layer and media access control (MAC) layer processing associated with the transmission of information. For example, operation of the uplink PHY / MAC module 1838 may be used, for example, to coordinate transmission of data information such as messages, packets, and / or frames, for example, signals. Or both sending and receiving control information such as messages. The configuration information 1832 may include, for example, a frequency, band, channel, spreading or hopping code to be used for transmissions, an identifier associated with the end node 1800, a request dictionary specifying the use of an allocation request channel, and the like. It may include configuration information, such as, for example, parameter settings that affect the operation of the same uplink PHY / MAC module 1838.

The uplink LLC (ARQ) module 1840, for example, from the end node 1800 to the access node, via the wireless communication interface module 1804, for example messages, packets, and / or frames. Control Logical Link Control (LLC) related to transmitting data information such as The uplink LLC (ARQ) module 1840 includes processing associated with an Automated Repeat Request (ARQ) such as, for example, retransmission of lost packets or frames. The uplink LLC (ARQ) module 1840 provides additional functionality such as, for example, multi-protocol multiplexing / demultiplexing, for example, by means of error detection or type fields through the use of checksum fields. To provide, it may further include processing relating to the addition of the LLC header and / or trailer to higher layer messages such as, for example, packets. The uplink LLC (ARQ) module 1840 is a higher layer message, such as packets, for example, in multiple sub-parts, such as frames to be transmitted by the uplink PHY / MAC module 1840. Fragmentation of these may be performed additionally. The configuration information 1832 may include configuration information that affects the operation of the uplink LLC (ARQ), such as, for example, an ARQ window size, a maximum number of retransmissions, a discard timer, and the like.

The uplink queue management module 1882 maintains the information and also controls processing relating to the storage of data information to be transmitted by the wireless communication interface module 1804, for example, from the end node 1800 to the access node. do. The uplink queue management module 1842 may, for example, control the storage of data information awaiting transmission and maintain state information for the data information awaiting transmission on a per-traffic flow basis, for example, respectively. Packets associated with the traffic flow of may be stored in a separate queue. For example, the uplink queue management module 1882 may include random early detection (RED) as well as various queue management techniques and / or capabilities, such as, for example, head drop and tail drop. The same Active Queue Management (AQM) is supported. Configuration information 1832 may include configuration information that affects the operation of uplink queue management module 1842, such as queue restriction, drop policy, and / or AQM thresholds associated with one or more traffic flows.

The uplink classifier module 1844 performs processing relating to identification of data information belonging to specific traffic flows, for example, from the end node 1800 to the access node before being transmitted by the wireless communication interface module 1804. To control. In some embodiments, messages, packets, and / or frames to be transmitted through the use of wireless communication interface module 1804 are based on an uplink classifier module based on a survey of one or more header and / or payload fields. And classified as belonging to one of the various traffic flows. The results of the classification by the uplink classifier module 1844 may affect the management of classified data information by the uplink queue management module 1842 and the management of other modules in the memory 1808. For example, the results may determine the particular queue that messages, packets and / or frames will be associated with for storage and affect subsequent processing such as scheduling. The configuration information belongs to one or more traffic flows and, for example, specifies one or more classifier filters that specify criteria used to associate data information such as messages, packets, and / or frames. It may include configuration information that affects the operation of the uplink classifier module 1844, such as a set of rules.

Downlink PHY / MAC module 1846 controls PHY layer and MAC layer processing for receiving data information by wireless communication interface module 1804. Operation of the downlink PHY / MAC module 1846 includes both sending and receiving control information to coordinate the reception of data information. The configuration information 1804 affects the operation of the downlink PHY / MAC module 1846, such as, for example, frequency, bandwidth, channel, spreading code or hopping code to be used for reception, and an identifier associated with the end node 1800. May include configuration information.

Downlink LLC (ARQ) module 1848 controls LLC layer processing associated with receiving data information by wireless communication interface module 1804. Downlink LLC (ARQ) module 1848 includes processing associated with ARQ capabilities such as, for example, retransmission of lost packets or frames. For example, the downlink LLC (ARQ) module 1848 may additionally include processing for the LLC header and / or trailer that encapsulates the higher layer messages, for example by checking the type field or by the checksum field. Additional features such as multi-protocol multiplexing / demultiplexing with error detection are provided. Downlink LLC (ARQ) module 1848 may also perform reassembly of frames received in higher layer messages by the downlink PHY / MAC module 1846. The configuration information 1832 may, in some embodiments, affect the behavior of the downlink LLC (ARQ) module 1848, such as, for example, ARQ window size, maximum number of retransmissions, discard timer, and the like. For example, it includes configuration information such as parameter settings.

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

The network / internet interface module 1906 provides a mechanism by which internal components of the access node 1900 can transmit and receive signals to / from external devices and network nodes. The network / internet interface 1906 is a receiver module 1914 and transmitter module 1916 used to couple the node 1900 to other networks, eg, via copper wires or fiber optic lines. It includes. The wireless communication interface module 1908 also provides a mechanism by which internal components of the access node 1900 transmit signals to / from external devices and network nodes, eg, end nodes. Can be received. The wireless communication interface module 1908 includes, for example, a receiver module 1918 with a corresponding receive antenna 1920 and a transmitter module 1924 with a corresponding transmit antenna 1924. The wireless communication interface module 1908 is used to couple the access node 1900 to other nodes, for example by wireless communication channels.

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

The control signaling module 1926 includes, for example, an access node 1900 comprising a traffic control module 1928 and configuration information 1930 and various additional modules 1932-1954 included in various aspects of configuration and configuration. And / or control processing related to receiving and transmitting signals, such as messages, for controlling operations. For example, the control signaling module 1926 may be associated with an operation of the access node 1900 and / or one or more signaling protocols supported by the control signaling module 1926. Information and / or other information. In particular, the control signaling module 1926 may operate, such as, for example, configuration information such as access node identification and / or parameter settings, and information such as, for example, current processing status, status of pending message transactions. May contain information.

The traffic control module 1928 controls the processing for receiving and transmitting data information, such as, for example, messages, packets, and / or frames, by the wireless communication interface module 1908. For example, the traffic control module may include configuration information 1930 and various additional modules 1932-that control various aspects of traffic flows and / or quality of service for packets, such as, for example, a sequence of associated packets. 1954). In some embodiments, the traffic control module 1928 may, for example, provide information about the operation of the access node 1900, the traffic control module 1928, and / or one or more of a variety of additional modules included therein. Status information and / or other information such as For example, configuration information 1930, such as parameter settings, determines, influences, and / or specifies the operation of traffic control module 1928 and / or various additional modules 1932-1954 included. . The various additional modules are, in some embodiments, included to perform certain functions and operations when required to support certain aspects of traffic control. In various embodiments, modules may be omitted and / or combined as necessary depending on the functional requirements of traffic control. A description of each additional module included in the traffic control module 1928 follows.

The admission control module 1932 maintains information about resource usage / availability and determines whether sufficient resources are available to support quality of service requirements of a particular traffic flow. Resource availability information maintained by the admission control module 1932 includes, for example, packet and / or frame queuing capacity, scheduling capacity, as well as 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 may query the admission control module 1932 to determine whether sufficient resources are available to support the new or modified traffic flow. Where the admission control decision is a function of quality of service requirements and / or resources available for a particular traffic flow. The configuration information 1930 affects the operation of the admission control module 1932, for example, such as an admission control threshold indicating the percentage of resources that can be allocated prior to rejecting further requests. , Configuration information such as parameters settings.

The uplink scheduler module 1934 is transmitted by the air interface module 1908 from one or more end nodes to the access node, for example in data information such as messages, packets and / or frames. For example, control of allocation of transmission resources such as information coding rate, transmission time slots and / or transmission power, and processing relating to transmission scheduling such as, for example, order and / or timing. The uplink scheduler module 1934 can schedule transmissions and allocate transmission resources as a function of constraints and / or quality of service requirements associated with one or more traffic flows and / or one or more end nodes. Configuration information 1930 affects uplink scheduler module 1934 such as, for example, priority, rate bound, latency bound and / or shared weight associated with one or more traffic flows and / or end nodes. It may include configuration information. In some embodiments, the scheduling and / or resource allocation operations performed by uplink scheduler module 1934 can additionally be a function of other factors, such as, for example, channel conditions and power cost.

Downlink scheduler module 1936 is data information such as messages, packets, and / or frames to be transmitted from access node 1900 to one or more end nodes via air interface module 1908. For the allocation of transmission resources such as, for example, information coding rate, transmission time slots, and / or transmission power, and processing relating to transmission scheduling such as, for example, order and / or timing. 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 end nodes. The configuration information 1930 affects the operation of the downlink scheduler module 1936 associated with one or more traffic flows and / or end nodes, such as priority, rate bound, latency bound, or shared weight. The note may include configuration information. In some embodiments, the scheduling and / or resource allocation operations performed by the downlink scheduler module 1936 are additionally a function of channel conditions and other factors such as, for example, power cost.

The uplink traffic conditioner module 1938 may be received, for example, by messages, packets, and / or frames, for example, received by the air interface module 1908 from an end node to an access node 1900. For data information such as < RTI ID = 0.0 > e.g., ≪ / RTI > The uplink traffic conditioner module 1938 is a function of, for example, surveying, marking, and / or guarding 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. You can tune traffic as well. The configuration information 1930 may contain configuration information that affects the operation of the uplink traffic conditioner module 1938, such as, for example, a value bound and / or a marking value associated with one or more traffic flows and / or end nodes. It may include.

The uplink classifier module 1940 belongs to specific traffic flows, for example, from the end node to the access node 1900 before being processed by the traffic coordinator module 1938. Control processing regarding the identification of data information received via, for example, messages, packets, and / or frames. In some embodiments, messages, packets, and / or frames received via wireless communication interface module 1908 may be based on uplink classifier module 1940 based on a survey of one or more header and / or payload fields. Are classified as belonging to one of various traflows. The classification by the uplink classifier module 1940 may affect the processing of the classified data information such as, for example, messages, packets, and / or frames by the uplink traffic conditioner module 1938. For example, the results may determine a particular data structure or state machine to which the message, packet, and / or frame is associated and additionally affects subsequent processing such as surveying, marking and / or expense. have. The configuration information 1930 belongs to one or more traffic flows and, for example, specifies one or more criteria used to associate data information, such as messages, packets, and / or frames, for example one or more. It may include configuration information that affects the operation of the uplink classifier module 1940, such as a set of classifier filters.

The uplink LLC (ARQ) module 1942 sends data information, such as, for example, packets and / or frames, by the wireless communication interface module 1908, for example, from the end node to the access node 1900. Control LLC layer information related to receiving. Uplink LLC (ARQ) module 1942 includes processing associated with ARQ capabilities such as, for example, missing packets or frames. In some embodiments, uplink LLC (ARQ) module 1942 additionally includes processing relating to an LLC header and / or trailer that encapsulates higher layer messages, such as, for example, packets, which is included in the checksum field. By means of type field or error detection, for example, to provide additional functionality such as multi-protocol multiplexing / demultiplexing. The uplink LLC (ARQ) module 1942 can also perform reassembly of frames received by the uplink PHY / MAC module 1944 with higher layer messages such as, for example, packets. have. The configuration information 1930 may include configuration information that affects the operation of the uplink LLC (ARQ) module 1942, such as, for example, an ARQ window size, a maximum number of retransmissions, a discard timer, and the like.

The uplink PHY / MAC module 1944 receives data information, such as, for example, packets and / or frames, by the wireless communication interface module 1908, for example, from the end node to the access node 1900. Control PHY layer and MAC layer processing associated with In some embodiments, the operation of the uplink PHY / MAC module 1944 is, for example, to coordinate the reception of data information such as messages, packets, or frames, for example, signals or It includes both sending and receiving control information such as messages. The configuration information 1930 may be associated with the operation of the uplink PHY / MAC module 1944, such as, for example, frequency, band, channel, spreading or hopping code to be used for reception, an identifier associated with the access node 1900, and the like. May contain configuration information that affects.

The downlink classifier module 1946 belongs to a particular traffic flow, for example, from the access node 1900 to the end node before being transmitted through the wireless communication interface module 1908, for example, messages, packets. Control processing for identification of data information such as, and / or frames. In some embodiments, the messages, packets, and / or frames to be sent by the wireless communication interface module 1908 are based on the downlink classifier module 1946 based on a survey of one or more header and / or payload fields. Are classified as belonging to one of various traffic flows. The results of the classification by the downlink classifier module 1946 are determined by the downlink queue management module 1950 and other modules 1948, 1952, and 1954, for example, messages, packets, and / or May affect the processing of the classified data information, such as frames, for example, the result may be that the message, packet, and / or frame is associated with storage and further affects subsequent processing such as scheduling. You can decide on a specific cue. The configuration information 1930 is, for example, one or more classifiers that belong to one or more traffic flows, for example specifying criteria used to associate data information such as messages, packets, and / or frames. It may include configuration information such as, for example, parameter settings that affect the operation of the downlink classifier module 1946, such as a set of filter rules.

The downlink traffic conditioner module 1948 may be transmitted by the air interface module 1908, for example, from the access node 1900 to the end node, eg, messages, packets, and / or frames. For data information such as, control processing relating to traffic coordination such as, for example, surveying, marking, expenses. The downlink traffic conditioner module 1948 may determine traffic according to, for example, surveying, marking and / or guarding according to constraints and / or quality of service requirements associated with one or more traffic flows and / or one or more end nodes. Can be adjusted. The configuration information 1930 can affect the operation of the downlink traffic conditioner module 1948, such as, for example, rate bound and / or marking values associated with one or more traffic flows and / or end nodes. May contain information.

The downlink queue management module 1950 maintains information and may be transmitted by the wireless communication interface module 1908, for example from messages 1 packets to packets, for example, from an access node 1900 to an end node. Controls processing relating to the storage of data information such as frames. The downlink queue management module can control the storage of data information awaiting transmission and maintain state information regarding the data information awaiting transmission for each traffic flow basis, for example associated with each traffic flow. Packets can be stored in separate queues. In some embodiments, downlink queue management module 1950 supports various queue management techniques and / or capabilities such as head drop, tail drop and / or various AQM mechanisms such as RED, for example. The configuration information 1930 may include configuration information that affects the downlink queue management module 1950, such as, for example, queue limits, drop policies, and / or AQM thresholds associated with one or more traffic flows. Can be.

The downlink LLC (ARQ) module 1952 is, for example, accessed by the wireless communication interface module 1908 from the access node 1900 to the end node, for example, messages, packets, and / or frames. Control LLC layer processing for transmitting data information such as Downlink LLC (ARQ) module 1952 includes processing associated with ARQ performance such as, for example, retransmission of lost packets or frames. In some embodiments, downlink LLC (ARQ) module 1952 provides additional functionality such as multi-protocol multiplexing / demultiplexing via type field or error detection by checksum field, eg, packets. It further includes processing relating to the addition of the LLC header and / or trailer to higher layer messages, such as. Downlink LLC (ARQ) module 1952 may also be a higher layer message such as, for example, packets in multiple sub-parts, such as, for example, a frame to be transmitted by downlink PHY / MAC module 1954. Can be fragmented. The configuration information 1930 may include configuration information that affects the operation of the downlink LLC (ARQ) module 1952, such as, for example, an ARQ window size, a maximum number of retransmissions, a discard timer, and the like.

The downlink PHY / MAC module 1954 is, for example, from the access node 1900 to the end node, by the wireless communication interface module 1908, such as, for example, messages, packets, and / or frames. Controls the PHY layer and MAC layer processing for transmitting data information. In some embodiments, the operation of the downlink PHY / MAC module 1954 is, for example, to schedule the transmission of data information such as messages, packets or frames, for example signals or messages. It includes both sending and receiving control information, such as: The configuration information 1930 may operate with the downlink PHY / MAC module 1954, such as, for example, a frequency, band, channel, spreading or hopping code to be used for transmissions, an identifier associated with the access node 1900, and the like. May contain configuration information that affects

20 illustrates example signaling and traffic flows between the various modules included in the example end node 1800 and the example access node 1900. The end node 1800 of FIG. 20 and the access node 1900 of FIG. 20 briefly illustrate the end node 1800 of FIG. 18 and the end node 1900 of FIG. 19, respectively. The example of FIG. 20 illustrates an application module 1828 that receives and transmits data information such as, for example, a traffic flow consisting of a sequence of messages, packets, or frames. In the context of the example system of FIG. 17, the end node 1800 of FIG. 20 may be any one of the end nodes 1702-1712 shown in FIG. 17 and included in the end node 1800 of FIG. 20. The application module 1828 may exchange data information with another node in the system, such as, for example, another end node 1702-1712 or an application server node 1726, as shown in FIG. 17. . In FIG. 20 and the following description, the nodes to which the end node 1800 of FIG. 20 exchanges data information is referred to as corresponding nodes.

Data information, such as traffic flows consisting of a sequence of messages, packets, or frames transmitted from an application module 1828 in the end node 1800, may be included in the modules 1830- It is shown by the sequence 2002-2008 of arrows progressing through the sequence of 1844, after which the data information is accessed from the end node 1800, for example, by the wireless communication interface module 1804. Sent to node 1900. For example, by the wireless communication interface module 1908, following the reception by the access node 1900, transmitted from the application module 1828 at the end node 1800 to the corresponding node, for example, Data information, such as traffic flows consisting of a sequence of messages, packets or frames, may be routed to, for example, an intermediate node connected to the access node by the network / internet interface module 1906. As directed, an arrow proceeds through a sequence of modules 1938-1944 included in the access node 1900 for processing, before forwarding from the access node 1900 towards the corresponding node. It is shown by the sequence 2010-2018.

Data information, such as, for example, traffic flows composed of a sequence of messages, packets, or frames, sent from the corresponding node to the application module 1828 at the end node 1800, may be, for example, network / The arrows are generated by the internetwork interface module 1906, proceeding through a sequence of modules 1946-1954 that are received by the access node 1900 and included in the access node 1900 for further processing. 2020-2028, after the processing, the data information is transmitted from the access node 1900 to the end node 1800, for example, via a wireless communication interface module 1908. For example, transmitted by the wireless communication interface module 1804 following the reception by the end node 1800, from the corresponding node to the application module 1828 at the end node 1800, for example. Data information, such as traffic flows composed of messages, packets, or frames, is passed to the end node 1800 for processing before being passed to the application module 1828 at the end node 1800. Proceeding through the included modules 1846 and 1848 is shown by the sequence of arrows 2030-2034.

In addition to the exchange of data information such as, for example, traffic flows, FIG. 20 also illustrates the exchange of control information such as, for example, signaling flows and / or a communication interface. In particular, FIG. 20 illustrates the exchange of control information between the control signaling module 1926 and the traffic control module 1928 included in the access node 1900. Similarly, the example of FIG. 20 illustrates the exchange of control information between the control signaling module 1826 and the traffic control module 1830 included in the end node 1800. In both the access node 1900 and the end node 1800, the exchange of control information between the two modules, as shown, may occur, for example, to / from an application module 1828 in the end node 1800. If necessary to provide proper quality of service management of data information such as traffic flows, the individual control signaling module 1926/1826 at the access / end node 1900/1800 causes the individual traffic control module 1928 /. 1830, such as setting, modifying, and / or monitoring the operation and / or configuration of the various modules included therein.

For example, the exchange of control information, such as signaling flows and / or communication interfaces, may include a) between a control signaling module 1926 at an access node 1900 and another node, b) at an end node 1800. Between the application module 1828 and the control signaling module 1826 at the end node 1800, and c) between the access node 1900 and the individual control signaling modules 1926/1826 at the end node 1800. Shown. The exchanges of control information, such as, for example, signaling flows and / or communication interfaces, may involve the configuration and / or operation of traffic control modules 1928/1830 in both access node 1900 and end node 1800. a) one or more additional nodes such as, for example, an access control node 1720 and / or an application server node 1726, b) an application module at the end node 1800, or c) at an end node 1800. To be affected by a combination of application modules and one or more additional nodes. Various embodiments of the present invention may support all of the illustrated control information exchanges or only a subset of the illustrated control information exchanges as needed.

What has been described above includes examples of one or more embodiments. Of course, it is not possible to describe all possible combinations of components or methods for the purpose of describing the above-described embodiments, but one of ordinary skill in the art may recognize that many additional combinations and variations of the various embodiments are possible. Accordingly, the described embodiments are intended to embrace all such alterations, modifications and variations that fall within the spirit and scope of the appended claims. Moreover, to the extent that the term "comprises" is used in the description or in the claims, such terms are analogous to the term "comprises" because "compose" is interpreted as a transitional term in the claims. It is intended to be included.

Claims (36)

As a roaming method between networks, Receiving a request for network access at the visited network; Receiving a profile from a home network in response to the request; And Selectively providing services to one or more access terminals based at least in part on the profile, Roaming method. The method of claim 1, The services are associated with Quality of Service (QoS) parameters, Roaming method. The method of claim 1, The visited network modifies, deletes or adds services to the profile, Roaming method. The method of claim 3, The visited network selectively provides a subset of services from the profile, Roaming method. The method of claim 3, The visited network provides additional services in addition to those specified by the profile, Roaming method. The method of claim 1, Receiving the profile when receiving an access grant from the home network, Roaming method. The method of claim 1, Further comprising using a virtual homing component as part of a home network, Roaming method. The method of claim 7, wherein The virtual homing component is associated with a mobile virtual network operator (MVNO), Roaming method. The method of claim 8, The virtual homing component is used with a roaming service, Roaming method. The method of claim 1, Further comprising performing authentication and authorization for devices for the visited network or for the home network, Roaming method. The method of claim 1, The profile provides service differentiation between subscribers or application services authorized by a given subscriber, Roaming method. The method of claim 1, Further comprising the step of modifying the profile according to an XML services description, Roaming method. The method of claim 1, The profile may include QoS parameters associated with the identification of packets as belonging to a traffic flow, parameters associated with traffic coordination of the traffic flow, parameters associated with queuing / scheduling the traffic flow, or an access node may Parameters that characterize the traffic flow that enable to determine an appropriate QoS configuration to provide service of the flow, Roaming method. As a communication device, Memories holding instructions for receiving a profile associated with one or more services, the profile associated with a home network component and modifiable via a visited network component, the profile being used to provide services to a roaming access terminal -; And A processor that executes the instructions; Communication device. The method of claim 14, The visited network component includes an authentication and authorization server in communication with an authentication and authorization server associated with the home network component, Communication device. The method of claim 14, The profile is associated with a quality of service (QoS) data set generated from the home network component, Communication device. The method of claim 16, The QoS data set is associated with one or more latency associated with multiple traffic flows, a minimum data rate associated with the multiple traffic flows, and a maximum data rate associated with the multiple traffic flows. Communication device. As a communication device, Means for receiving a subscriber profile generated from a home network, Means for modifying the subscriber profile; And Means for providing services partially based on the modified subscriber profile, Communication device. The method of claim 18, Means for modifying the subscriber profile further comprises adding or deleting services from the profile, Communication device. A machine-readable medium having machine-executable instructions stored thereon, The commands are Receive a request from an access terminal for network services; Receive a profile at a visited network component in association with the request; And Instructions for analyzing the profile to determine available services for processing the request, Machine-readable medium. The method of claim 20, Further comprising modifying the profile in view of the available services, Machine-readable medium. The method of claim 21, Modifying the profile further includes adding services to the profile, deleting services from the profile, or editing a parameter in the profile, Machine-readable medium. Request a subscriber profile in association with a visited network access request; And In accordance with the profile, executing a command to use the subscriber profile to selectively provide services, either as a subset of the profile, or as a superset of the profile, Processor. As a roaming method between networks, Receiving a profile request for network access in a home network; Sending the profile from the home network in response to the profile request; And When transmitting the profile, generating an access grant signal from the home network; Roaming method. The method of claim 24, The profile includes services associated with Quality of Service (QoS) parameters, Roaming method. The method of claim 24, Further comprising modifying, deleting or adding services to the profile, Roaming method. The method of claim 24, Further comprising using a virtual homing component as part of the home network; Roaming method. The method of claim 27, The virtual homing component is associated with a mobile virtual network operator (MVNO), Roaming method. The method of claim 28, The virtual homing component is used with a roaming service, Roaming method. The method of claim 24, Generating the profile according to an XML service description; Roaming method. As a communication device, Memory holding instructions for creating a profile associated with one or more services, the profile associated with a home network component and modifiable via the services description component, wherein the profile is used to provide services to a roaming access terminal. ; And A processor that executes the instructions; Communication device. The method of claim 31, wherein The service description component includes an XML schema component, Communication device. The method of claim 31, wherein The profile is associated with a quality of service (QoS) data set generated from the home network component, Communication device. As a communication device, Means for generating a subscriber profile from a home network; Means for annotating the subscriber profile to enable modifications to the profile; And Means for granting access to the home network; Communication device. A machine-readable medium having machine-executable instructions stored thereon, The commands are Receive a profile request for network services in a home network, the request being a response to an access terminal request; Create a profile in association with the profile request; And Instructions for sending the profile from the home network upon access authorization; Machine-readable medium. Create a subscriber profile in association with a visited network access request; And Executing instructions that enable modifications in the subscriber profile to facilitate the selective provision of services according to the profile, wherein the modifications are possible for a network other than a home network; Processor.

Images