RU2419250C2 - Selective control of user equipment capabilities - Google Patents

Abstract

FIELD: information technologies.

SUBSTANCE: method of UE operation is proposed in the public land mobile network (PLMN), including the following stages: definition of the fact that UE improperly requests at least one service from PLMN; informing a control object in the home public land mobile network (HPLMN) on the improper request; requesting, through an object of HPLMN control, a server of devices control in HPLMN to disconnect improperly requested service in UE; sending, from HPLMN server, a message to UE to establish a session of control between UE and the server; and applying to a control object of selective disconnection of UE capabilities (SDoUE) in UE, such that the improperly requested service is disconnected. When procedures of general purpose radio communication session management procedures (SM GPRS) initiated by UE are switched off, deactivation of contexts of packet data passing (PDP) is initiated; and the method includes the following stages: receiving DM OMA; issuing the mark on the basis of DM OMA notice; requesting PDP context; and initiation of PDP context activation, if the mark has been issued.

EFFECT: provision of safety in control of basic working criteria of UE and application of notice of the list of selective capabilities and control of devices according to Open mobile alliance to disconnect UE capabilities.

16 cl, 8 dwg, 3 tbl

Description

The present invention relates to electronic communication systems and, more particularly, to electronic communication systems having user equipment configured by various software components.

Currently, several performers are involved in managing the software and hardware of a user equipment (UE), such as a mobile phone or other communication device in a wireless communication system. The software may be applications, services, and modules, including an operating system (OS) stored in and used by the UE. The manufacturer of the UE typically installs a software suite in the UE at the time of manufacture of the device. Then the end user can modify the software of the UE by loading applications into the UE, etc. from various sources, for example, via the Internet. The manufacturer of the UE, the operator of the communication system to which the UE is subscribed, or in which the UE is a guest, and / or an authorized third party, depending on business agreements, can also remotely modify part or all of the software of the UE.

After such modifications and in other cases, the UE may not function properly. From the point of view of the system operator, for example, malfunctioning involves a decrease in the throughput of the communication system due to the UE by increasing the number of control messages or other messages exchanged with the system. UE malfunctioning can occur in various ways, for example, unexpected interaction between software modules in a UE, malicious software modules, etc. The user can download a malicious or malformed application, for example, a Java application that interacts with the network protocol stack through open application programming interfaces (APIs) in the UE. As a result, the UE can repeatedly send operator network service requests.

Type approval is always issued for all radio alarm software. For example, type-approved software in the UE may exhibit functionality similar to an emergency call and Internet Protocol (IP) Multimedia Subsystem (IMS) service, Java environment, and generally the application layer. Compared, for example, with a normal call setup, the request is rejected if there are not enough network resources to satisfy the request, which can be a problem for functionality similar to an emergency call, which is a high priority request. This may not be a big problem today, but more and more functionality is being exposed to the application layer, and more and more UEs can download software. When permitted attributes are exposed to the application layer, they may be misused; for example, a UE application may attempt to register an IMS session 1000 times per minute. If this application is copied to other UEs, a serious problem for the network operator may result.

Methods to address the malfunctioning of a UE by disabling services for a UE have been discussed in standardization organizations such as the 3rd Generation System Partnership Project (3GPP). 3GPP publishes specifications for the Global System for Mobile Communications (GSM) communications system and its enhancements, such as increasing the data rate for the evolution of GSM networks (EDGE), the universal mobile communications system (UMTS), and systems employing code division multiple access (WCDMA) )

For example, Section 4.5 3GPP Technical Specification (TS) 22.011 V7.6.0 (March 2007), Service Accessibility (Release 7) and Section 4.5 3GPP TS 22.011 V8.0.0 (March 2007), Service Accessibility (Release 8) relate to UE capability management . The list of services of the selective capabilities of the UE can be stored in the UE and, if the service in the list is indicated as disabled, the UE does not request a service from the network. Services in the selective capabilities list include Call Control (CC), Extra Services (SS), Emergency Calls, Short Message Service (SMS) via circuit switched (CS) and packet switched (PS) communication lines, Caller ID service location (LCS), general packet radio services based on GSM (GPRS), broadcast and multicast multimedia services (MBMS) and IMS.

3GPP TS 22.011 follows from 3GPP Technical Report (TR) 23.805 V0.3.1 (Sept. 2005), Selective Disabling of UE Capabilities; Report on Technical Options and Conclusion (Release 7) and 3GPP TS 24.305 V0.1.0 (March 2006), Selective Disabling of 3GPP UE Capabilities (SDoUE) Management Object (MO) (Release 7). 3GPP TR 23.805 V0.3.1 and TS 24.305 V0.1.0 introduced a list of selective capabilities and device management (DM) according to the Open Mobile Alliance (OMA) for disabling UE capabilities, but did not describe any of the parameters required for a selective shutdown control object (MO) UE capabilities (SDoUE), or none of the rules and the corresponding functioning of the UE when services or functions are disconnected / connected. OMA has developed specifications for the management of devices (DM) of communication devices, and versions 1.1.2 and 1.2 of these specifications define a protocol for managing the configuration, data and settings of communication devices. OMA standards and other information are available at http://www.openmobilealliance.org.

The OMA DM can be used to control the configuration and the UE of the UE from the point of view of various DM bodies, including setting initial configuration information in the UE, then updating the permanent information in the UE, retrieving the control information from the UE, and processing events and alarms generated by the UE. Using OMA DMs, third parties can configure the UE on behalf of end users. A third party, such as a network operator, service provider, and corporate information management department, can remotely set UE parameters and install or update software using suitable MOs in the UE. MO, as a rule, is a program object that can be written, for example, in accordance with SyncML (markup language for synchronization), which is a specification of a markup language for a data presentation protocol based on an extensible markup language (XML), a synchronization protocol and DM protocol, transport bindings for protocols, and device description structure for DM.

As shown in FIG. 1, the DM control unit (MA) 102 issues a request to the DM server 104, for example, to prepare for operation of the parameters in one or more UEs. The DM server 104 sends a server-initiated notification to the UE 106, which establishes a DM session with the DM server 104, which requests the UE for current settings (which may include UE-specific extensions). The DM server 104 sends DM commands to configure the UE to meet the requirements set by the MA 102 of the DM. The UE 106 and the DM server 104 terminate their DM session, and the UE gains access to network data services using the configured connectivity parameters. The DM MA or the DM server can store connectivity parameters on a smart card or the like, so that the UE can use them when the UE uses the parameters.

The UE, for example, can use the MO connectivity for application-independent settings to connect to the network. Network Connectivity MoE provides connectivity information that relates to the parameters and tools needed to access the network infrastructure, including network channels, protocols, network access point (NAP) addresses, and proxy addresses. According to the OMA specifications, the connectivity connector MO processes the connectivity control for wireless data transmission by defining a set of DM object circuits that can be set by the DM client and routed by the DM server. The object diagram has three parts: the top-level control object, which is neutral for the channel; a set of channel-specific parameters; and a subtree for setting manufacturer-specific parameters. The connectivity parameters, which are bootable using the client preparation standard (CP), can then be addressed and controlled using the DM server, which can add new intermediaries and network access points using the standardized DM package. Preparing for work is the process by which a client is configured on the device, and basically covers both preparing for work on the radio (OTA) and other preparations for work, for example, using a Subscriber Identity Module (SIM) card.

However, it is difficult to use OMA DM to remotely disconnect and connect services in order to deal with the UE operating mode according to 3GPP TS 22.011. Among the problems that arise is the fact that the services to be disconnected / connected operate at protocol stack levels that are lower than usual for a DM session. Another problem involves the need for acceptable security when managing such basic operational features of the UE. Thus, it is not obvious to use DM OMA to disable the capabilities of the UE.

SUMMARY OF THE INVENTION

According to aspects of the present invention, there is provided a method of operating a UE in a Public Land Mobile Network (PLMN). The method includes the steps of determining that the UE is incorrectly requesting at least one service from the PLMN; informing the management entity in the home PLMN (HPLMN) about the wrong request; request, through the HPLMN management object, the computer device management server in the HPLMN, to disable the incorrectly requested service in the UE; sending, from the HPLMN server, a message to the UE to establish a control session between the UE and the server; and accessing the SDoUE management object in the UE, so that the incorrectly requested service is disabled.

According to other aspects of the present invention, there is provided a UE capable of communicating with a device management server. The UE includes a processor configured to execute software components residing in the UE and manage the services of the UE. The software component includes an SDoUE control object that is configured by the processor to disable UE services based on a control session established between the UE and the server.

According to other aspects of the present invention, there is provided a computer-readable medium having instructions that, when executed by a processor in a UE in a PLMN, cause the processor to perform the steps of: determining that the UE is incorrectly requesting at least one service from the PLMN; informing the management object in HPLMN about the wrong request; request, through the HPLMN management object, the computer device management server in HPLMN to disable the incorrectly requested service in the UE; sending, from the HPLMN server, a message to the UE to establish a control session between the UE and the server; and accessing the SDoUE management object in the UE, so that the incorrectly requested service is disabled.

Brief Description of the Drawings

Various objects, features and advantages of the present invention are understood as a result of reading this description together with the drawings, in which:

Figure 1 depicts a device control device;

2 is a flowchart of a method for operating a UE and a communication network;

FIG. 3 is a flowchart of another operation method of a UE and a communication network; FIG.

4 is a block diagram of a user equipment;

5 illustrates valve control in user equipment;

6 is a flowchart of a method for controlling activation of a packet data protocol (PDP) context;

7 is a block diagram of a communication system including user equipment and part of a network; and

Fig.8 depicts a network.

Detailed description

The present application focuses on wireless communication systems that meet the specifications published by 3GPP to reduce the explanation, but it is understood that the principles described in this application can be implemented in other communication systems. It is also understood that this description is written based on DM OMA, but this description should not be interpreted as limited to DM OMA. Regardless of the mechanism used to disable or enable services in the UE, it is advantageous for the UE to be selectively managed in a standardized manner.

The inventors recognized that DM OMA can be used to disconnect and connect a given service or function (or a set of services or functions), even if some of these services / functions are needed when DM OMA is again used to connect these services / functions. This application describes a suitable MO SDoUE and the operation of a UE using MO SDoUE in a communication system. One skilled in the art will understand that MO SDoUE is basically a software module that includes parameters that can be used to selectively disable and enable the capabilities of the UE.

Currently, it is considered beneficial to use the standardized DM OMA access control list (ACL) property mechanism to grant or revoke access to DM OMA servers to modify the nodes and objects of MO SDoUE sheets. The ACL property mechanism is currently described in the Enabler Release Definition OMA-ERELD-DM-V1_2, which is incorporated herein by reference. For security reasons, the HPLMN UE operator can use the ACL mechanism to enable or disable other network operators (for example, guest PLMN operators (VPLMN)) to access the MO SDoUE UE through the VPLMN DM server when the UE roams, as described below.

The following table 1 describes an exemplary logical tree structure including nodes and sheet objects, MO SDoUE.

Table 1

Sample logical structure MO SDoUE

As is common with the DM OMA notation, < X > in Table 1 is a placeholder symbol node that takes any of two values, for example, 0 or 1, and one or more nodes and sheet objects are provided under this node. For a person skilled in the art it is clear that according to DM OMA, MO SDoUE has an associated MO identifier that makes it possible for DM MO SDoUE servers to search for a particular device. The other nodes and sheet objects of MO SDoUE shown in Table 1 are as follows, and it is understood that some nodes and objects of sheets may be omitted, other nodes and objects of sheets may be provided, and nodes and objects of sheets may have different names if required :

Name , which is a sheet for MO SDoUE settings;

CS_Calls , which is a sheet that indicates a preference — enable or disable UE-initiated CS call control procedures, except for emergency calls;

CS_EmergencyCalls , which is an internal node that indicates the preference of the operator to enable or disable CS emergency call procedures (for example, disable when CS_EmergencyCalls is set to 1), which are set, for example, in 3GPP TS 24.008.

Country , which is a sheet that represents a country that can be identified by a mobile country code (MCC) and allows the inclusion of information that indicates in which MSS CS emergency call CC procedures are disabled (for example, in which CS_EmergencyCalls is set to 1 );

Network , which is a sheet that can represent a network that can be identified by a mobile network code (MNC), and can enable, with a Country sheet, the inclusion of information that indicates in which MSS and MNC the CS emergency call CC procedures are disabled;

SupplementaryServices , which is a leaf that enables or disables UE-initiated SS operations;

CS_SMS , which is a sheet that enables or disables UE-initiated SMS over the CS link;

PS_SMS , which is a sheet that connects or disconnects initiated UE SMS via communication lines with PS;

CS_LCS , which is a sheet that enables or disables UE-initiated LCS operations over CS links;

PS_LCS , which is a sheet that enables or disables UE-initiated LCS operations over PS links;

GPRS_SM_PDP , which is a sheet that enables or disables UPR- initiated GPRS session management (SM) procedures for packet data protocol (PDP) contexts, for example, activating, deactivating, and modifying a PDP context;

GPRS_SM_MBMS , which is a sheet that enables or disables SM GPRS procedures for MBMS contexts, for example, activating and deactivating an MBMS context;

IMS , which is a sheet that enables or disables IMS procedures for sending IMS registration requests;

Text , which is a sheet that includes information that can be displayed by the UE to the user;

CustomerCareNumbers , which is an internal node that enables or disables the link to the list of customer support service numbers;

CustomerCareNumbers / <X> / CustomerCareNumber , which is a sheet that represents the number of customer support services that the user can use to determine the reason for the unavailability of the specified services;

AlertServerID , which is a sheet that indicates the ID of the DM server and enables the DM server to be informed about the MO SDoUE that has been modified;

IMS_EmergencyCalls , which is an internal node that indicates the preference of the network operator - to enable or disable IMS emergency call procedures that are defined, for example, in 3GPP TS 24.229;

IMS_EmergencyCalls / <X> / Country , which is a sheet that represents a country that can be identified by the MCC, and connects, with the Network sheet, the inclusion of information that indicates in which the MMS and MNC emergency call procedures are disabled by IMS;

IMS_EmergencyCalls / <X> / Country / Network , which is a sheet that represents a network that can be identified by the MNC, and connects, with the Country sheet, the inclusion of information that indicates in which the MMS and MNC have emergency IMS calls disabled; and

Ext , which is an internal node that can be used for information about MO SDoUE, for example, an application manufacturer, a UE manufacturer, etc.

The sheet usually takes either of two values, for example, either 0, or 1, and it is clear that a particular value is not critical, only the action of a specific value requires a preliminary definition.

For example, when the value of the CS_Calls sheet is set to 1, the UE initiates the end of all active calls except emergency calls and enters a “zero” state, such as described in 3GPP TS 24.008. The UE does not use CC initiated procedures by the UE, except for emergency calls, and the customer support service number (s), if indicated by the Text sheet, until the value of the CS_Calls sheet is set to 0.

When the value of the CS_EmergencyCalls sheet is set to 1, and the UE detects a predefined public land mobile network (PLMN) that can be identified by the MCC and MNC, then the UE initiates a signaling procedure to end all emergency calls. In addition, the UE may not use the CC procedures to establish emergency calls until the CS_EmergencyCalls sheet is set to 0 or the UE detects an MCC and MNC that does not match any of its stored code pairs.

When the value of the SupplementaryServices sheet is set to 1, the UE terminates all active SS operations and does not start the SS operations and their responses until the value of the SupplementaryServices sheet is set to 0.

When the CS_SMS sheet is set to 1, the UE does not use the CS domain for the initiated SMS forwarding UE until the value of the CS_SMS sheet is set to 0. Similarly, when the PS_SMS sheet is set to 1, the UE does not use the PS domain for the initiated SMS forwarding until the value of the PS_SMS sheet is set to 0.

When the value of the CS_LCS sheet is set to 1, the UE does not use the CS domain for UE-initiated LCS service operations until the value of the CS_LCS sheet is set to “0”. Similarly, when the value of the PS_LCS sheet is set to 1, the UE does not use the PS domain for LCS service operations initiated by the UE until the value of the PS_LCS sheet is set to 0.

When the value of the GPRS_SM_PDP sheet is set to 1, the UE releases all resources allocated for active PDP contexts, and the UE can erase the PDP context data and enter the idle state or the idle state. The UE does not use the UPR- initiated SM GPRS procedures until the value of the GPRS_SM_PDP sheet is set to 0, although the UE may advantageously be allowed to use the UPR- initiated SM GPRS procedures to activate the PDP context in specific cases. For example, UPR-initiated SM GPRS procedures for activating a PDP context can be used when receiving an OMA DM notification message indicating that the UE should initiate an OMA DM session with a DM server that has set the disconnect value of the GPRS_SM_PDP sheet. Another example, SM GPRS UE-initiated procedures for activating a PDP context can be used when they are needed either to set up an emergency call via IMS (for example, if IMS_EmergencyCalls is set to 0) or to send a generic DM OMA warning message.

When the value of the GPRS_SM_MBMS sheet is set to 1, the UE frees resources allocated for active MBMS contexts and can erase the MBMS context data. The UE does not use SM GPRS procedures for MBMS contexts until the value of the GPRS_SM_MBMS sheet is set to 0.

When the IMS sheet value is set to 1, the UE initiates a user-initiated unregistration procedure for IMS and does not send an IMS registration request until the IMS sheet value is set to 0. It is noted that disabling the GPRS_SM_PDP contexts is the second step to disable the incorrect the operation of repeatedly sending the IMS registration IMS application.

The information contained in the Text sheet should be in the language selected by the UE and may help determine the reason for the unavailability of the specified services and what to do. For example, a Text sheet may include a text string indicating a disabled service (s) and one or more phone numbers, Internet addresses, etc. for customer support.

The value of the AlertServerID sheet can be used by the UE to send a generic DM warning message at any time when the MO SDoUE is modified by the OMA DM server, which is different from the server indicated by the value of the AlertServerID sheet.

Table 2 is an exemplary definition of a suitable generalized DM alert message.

table 2

Example DM Generalized Warning Message

It is noted that the Type element of the generalized DM warning message, such as that shown in Table 2, can advantageously be set to "Reserved-Domain-Name: org.3gpp.SDoUE.changesperformedalert". It is also understood, however, that the specific names and structure shown are not essential, since the methods described in this application can be implemented with other names and tree structures.

When the value of the IMS_EmergencyCalls sheet is set to 1, and the UE detects PLMN coverage (identified by MCC and MNC), as indicated by any of the stored pairs of Country and Network nodes, then the UE initiates a signaling procedure to clear all emergency calls by IMS. In addition, the UE does not use IMS procedures to establish emergency calls until the value of the IMS_EvergencyCalls sheet is set to 0 or the UE detects MCCs and MNCs that do not match any of the stored pairs of Country and Network nodes.

An example of a device description structure (DDF) that implements the above-described logical structure of MO SDoUE is presented in table 3 below. For a person skilled in the art, it is understood that features can be reordered, added to, omitted from, and renamed to DDF without leaving the scope of the present invention.

MO SDoUE is advantageously capable of disconnecting and connecting services when the UE is located either in its home PLMN (HPLMN), which is a PLMN that stores the subscription of the UE, or in the guest PLMN (VPLMN). It is also advisable for both HPLMN and VPLMN to provide guidance to the UE as to which features of the UE are allowed to be used or not allowed to be used. Two alternative ways of operating the UE and the network are described below.

In the first method, MO SDoUE is completely controlled by the user's home operator (HPLMN), and only HPLMN can disable / enable services in the UE. This first method is described in the flowchart of FIG. 2 and includes the following steps.

The VPLMN, or HPLMN for this case, notifies (step 202) that one or more UEs repeatedly act to request services / connections to the network and (exclusively) are not detected and disabled by application level preventative measures, i.e. HPLMN or VPLMN reports a malfunctioning UE.

Depending on the architecture of HPLMN and VPLMN and the services provided, various network nodes participate in the notification of a malfunctioning UE. For example, for a service based on a CS domain, a Mobile Switching Center (MSC), a Visitor Location Register (VLR), and a Home Network Subscriber Server (HSS) are typically involved. For PS-based services, a Serving GPRS Support Node (SGSN) is usually involved. For the IMS, a Session / Call Serving Management Function (S-CSCF) may be involved. Thus, these network nodes, or more specifically the processors in such nodes, include programming suitable for detecting abnormal operation of the UE. From a functional point of view, the detected malfunctioning can be reported to the policy management node, which can be hosted with the DM server or integrated into it for the corresponding action. A network having such objects is described in more detail below.

If abnormal operation is notified by the VPLMN, the VPLMN informs HPLMN, for example, the HPLMN customer support center, of the abnormally functioning UE (step 204). This transfer can take place in various ways, for example, through interfaces with Internet services that connect the HPLMN and VPLMN customer support centers.

The HPLMN Customer Support Center requests the HPLMN DM server 104 to disable a service that is not being used correctly by a malfunctioning UE (step 206). The HPLMN DM server 104 sends a suitable message, such as a notification triggered session message, to a malfunctioning UE to establish a DM control session with a malfunctioning UE (step 208). Messages triggered by a notification session are described, for example, in OMA TS-DM-Protocol-V1_2-20060424-C. In the established management session, the HPLMN DM server accesses the MO SDoUE (step 210), disabling the misused service by setting the value of the corresponding parameter to MO SDoUE.

When a service or function is disabled through PLMN, a text string is usually displayed for the user of the UE, which contains contact paths for the corresponding customer support center to receive information, for example, about the disabled service / function, help with determining the reason for the unavailability of the service / function, and about repeated connecting a service / function.

In the second mode of operation of the UE and the network, the MO SDoUE is controlled by HPLMN, but the VPLMN can also disable / enable services and, thus, access and modify the MO SDoUE. In this second method, the information necessary to access the MO SDoUE is made available to the VPLMN for accessing and disconnecting / connecting the services of the UE roaming on the VPLMN. The necessary information for VPLMN access to the UE and MO SDoUE is preferably configured in the UE by HPLMN.

The information that HPLMN needs to provide in the UE for VPLMN is the DM account MO, which is preferably one of the standardized OMA DM objects described in OMA-TS-DM-StdObj-V1_2-20060424-C, and the necessary connectivity ( for example, the connectivity requirement MO) for the UE to connect to the VPLMN, which is also preferably one of the standardized OMA DM entities. It is understood that “connectivity” in this case is the connectivity information required by the UE to establish IP connectivity with the HPLMN DM server, for example, the name “telia-online.se” as the access point name (APN) when GPRS connection to Telia network.

The provision of necessary information can occur at any time, for example, during the production of the UE, when the UE is first turned on, and when the UE roams according to VPLMN. The OMA HPLMN DM server configures the access rights of the UE so that the MO SDoUE part is managed by the VPLMN. HPLMN, for example, can use the OMA DM ACL mechanism to determine which VPLMN can access MO SDoUE. The necessary information can be uploaded to the UE using the established DM control session.

The second method of operation of the UE and the communication system are described in the flowchart of FIG. 3. At step 302, the VPLMN notifies the malfunctioning UE, in the same manner as in the first method depicted in FIG. 2. At step 304, the VPLMN customer support center requests the VPLMN DM server 104 to disable a service that is being misused by a malfunctioning UE. The VPLMN DM server sends a corresponding message, such as a notification triggered OMA session message, to a malfunctioning UE to establish a DM control session with a malfunctioning UE (step 306). If the UE receives an access request to modify the MO SDoUE, the VPLMN has the ability to enable / disable the functions specified by the MO SDoUE parameters. The established control session allows the VPLMN DM server 104 to access the MO SDoUE to disable the misused service (block 308).

HPLMN may wish to be informed of any change made to MO SDoUE UE. In this case, the method further comprises notifying the HPLMN when the VPLMN has made changes to the MO SDoUE (step 310). For example, a malfunctioning UE may notify the HPLMN that changes to its MO SDoUE have been made by sending a generic DM alert message to the HPLMN DM server. The DM server receives the notification, and, as usual, the DM authority decides what to do when the notification arrives. It is clear that VPLMN, instead of or even in addition to the UE, can notify HPLMN about changes made to the MO SDoUE UE, but at the moment a protocol is not set for this purpose.

In order to implement the method described in FIG. 3, the structure of the MO SDoUE described in Table 1 must be modified by adding a parameter that contains the identifier of the HPLMN DM server 104 to which a generic alert message is sent when the MO SDoUE UE changes.

It will be appreciated that the first and second methods include features that support MO SDoUE security aspects, such as resistance to wildcard attack. Currently, OMA DM uses the transport layer security protocol in wireless networks / version 3 secure communications protocol (WTLS / SSL3) with a minimum of 128-bit encryption and allows for implementation with more reliable encryption and encryption sets.

The channel between the UE and the DM server is usually over IP and the GPRS channel (or PS domain). Thus, when the GPRS service and PDP context activation are disabled, the problem of activating the PDP context for communication with the DM-UE server must be resolved. According to the present invention, the problem is solved by conceptually considering activation as a network-initiated channel request. The inventors recognized that a complete UE SMS never needs to be disconnected, and thus DM OMA can use the WAP Push mechanism for sending link messages to establish the GPRS channel required for communication with the DM-UE server. The WAP Push application is allowed to selectively trigger PDP context activation, in particular to the DM server, when other applications in the UE are blocked from requesting PDP context activation by disabling the GPRS service and activating the PDP context.

It is understood that the UE, for example, can use the MO connectivity for application-independent installations to connect to the WAP network, which would provide connectivity information that relates to the parameters and tools needed to access the WAP infrastructure, including network channels, protocols , network access point (NAP) addresses, and proxy addresses. A WAP proxy is an endpoint for a Wireless Access Protocol (WTP), a wireless session protocol (WSP), and a WTLS protocol, as well as a proxy that can access WAP content. A WAP proxy may have functionality, such as, for example, a WSP proxy or a wireless telephony application (WTA) proxy. A physical intermediary is a specified address with the functionality of an intermediary, for example, the IP address plus port for an IP-accessible intermediary and the address of a short message system (SME) plus a port for an intermediary accessible via SMS. A logical intermediary is a set of physical intermediaries that can share the same WSP and WTLS context (shared session identification value space).

According to the OMA specifications, the connectivity connector MO processes the connectivity control for wireless data transmission by defining a set of DM object circuits that can be set by the DM client and routed by the DM server. The object diagram has three parts: the top-level control object, which is neutral for the channel; a set of channel-specific parameters; and a subtree for setting manufacturer-specific parameters. The connectivity parameters, which are bootable using Client Preparation for Work (CP), can then be addressed and managed using the DM server, which can add new intermediaries and NAPs using the standardized DM package. Preparing for work is the process by which a client is configured, such as the WAP client in the device, and mainly covers both preparing for work on the radio (OTA) and other preparations for work, for example, using a SIM card.

It is understood that DM OMA requires the UE to establish the SM GPRS initiated UE procedure (for example, the PDP context) so that the DM OMA server has the ability to contact and configure MO SDoUE to enable / disable services. As described in this application, the UE is allowed to establish an UE initiated SM GPRS procedure for this case. Furthermore, when UE-initiated SM GPRS procedures for PDP contexts are disabled, the UE needs to initiate a signaling procedure to deactivate the PDP context of all PDP contexts according to 3GPP TS 24.008, and the UE is not allowed to use UE-initiated SM GPRS procedures for PDP contexts until UE-initiated SM GPRS procedures for PDP contexts will be connected. The UE, however, is allowed to use UE-initiated SM GPRS procedures to activate the PDP context in the following cases:

- upon receipt of a DM OMA notification message indicating that the UE will initiate a DM OMA session with the DM OMA server that has set the disconnect value of the GPRS_SM_PDP sheet; and

- when a PDP context activation procedure initiated by the UE is needed to either set up an IMS emergency call (if IMS_EmergencyCalls is set to 0) or send a generic DM OMA warning message.

Another example is the case of emergency calls with CS and IMS. In order not to turn off emergency call procedures in regions where support is required, the network operator can specify in which country and / or network (s) the emergency call control procedures are turned off. Emergency call procedures can then be disabled until it is indicated otherwise, or until the UE determines that it has entered a country or network that is not indicated as disconnected. If emergency call management procedures are disabled and the UE enters coverage again in the country or network identified as disconnected, the emergency call service is no longer available. The Country and Network nodes in MO SDoUE, if present, can be considered as a pair of nodes, where MCC + MNC = network operator, but you can specify the country / region by setting only the value of the Country node (for example, setting the MCC to a numerical value that indicates Sweden ) Thus, the disconnection of the emergency call will be valid throughout the country, Sweden.

The operation of the logic in the UE favorably follows the rules, such as the following when the UE-initiated PDP context activations were disabled, but the UE is allowed to perform PDP context activation to use the DM:

1) the feature is activated in the UE, which has been bootstrapped and configured by the DM server;

2) the DM client UE only requests activation of the PDP context when it has received the OMA DM notification via the WAP Push mechanism; and

3) The DM notification transmits the DM server ID and a suitable indicator or security integrity label, such as the MD5 hash function (Message Digest - Message Profile).

FIG. 4 is a block diagram of a typical UE 106 including a transceiver 402 that is suitable for exchanging radio signals with base stations (BSs) in a network (not shown in FIG. 4). The information carried by these signals is processed by a processor 404, which may include one or more sub-processors, and which executes one or more software modules and applications, including MO SDoUE, described in this application, to perform operations of UE 106 in accordance with MO, described above. The user is entered into the terminal using a keypad or other device, and the information presented to the user is presented on the display 406. The software applications can be stored in the corresponding application memory 408, and the device can also download and / or cache the required information in the corresponding memory 410. The device 106 also includes an interface 412 that can be used to connect other components, such as a computer, keyboard, etc., to the UE 106.

To protect against improperly triggered PDP context activations by a malfunctioning application, the implementation of the selective shutdown flag in the UE 106 may apply the internal gate control, which is shown in FIG. 5. 5, the software in UE 106 is shown divided into an application part supporting the DM client 502 and an access part supporting SMS functionality 504 and GPRS functionality 506. Software in the parts of applications and access can communicate via API 508, 510. The 512-valve control, which is advantageously implemented by appropriate programming or logic in both SMS 504 and GPRS 506, works in such a way that the PDP context activation request arriving at API 508, 510, is only sent when a proper WAP Push notification has previously been received to DM client 502. Gate 512 may use the application ID in the WAP Push notification message as a label. The gate 512 is opened by making the tag available, and the PDP context request from the DM client 502 is only accepted when the tag is available on the GPRS 506, when the request is received by API 510. In addition to generating the tag, the gate functionality may include a timer that limits the duration of the validity of the label.

FIG. 6 is a flowchart of an example method for controlling PDP context activation using a gate 512, which may be included in the methods of FIGS. 2 and 3. At step 602, a WAP Push notification transmitted in an SMS message is received by SMS 504 from 104 DM server. As noted above, the WAP Push notification includes the corresponding application ID and, in response to the notification (step 604), the gate functionality in the SMS 504 issues a label, and optionally, a timer starts. The DM client 502 receives a WAP Push notification, and if it is from an authorized DM server, i.e. it has the proper ID, the DM client 502 requests the PDP context from the GPRS functionality 506 (step 606). GPRS 506 receives the DM client request, if a label is available (step 608), and initiates a PDP context activation procedure (step 610). It is understood that the functionality of gate 512 can be implemented in various ways, for example, by software tools included in SMS 504 and / or GPRS 506.

In addition to using MO SDoUE to protect its network bandwidth from improper functioning of the UE, network operators may find other uses for it. For example, when the end user has not paid for the requested service or subscribed to the service, and then stopped paying for the service, the operator can use MO SDoUE to disable the software or functionality of the UE associated with the service.

It is understood that in an OMA DM environment, decision making is not performed at the DM server level; MA makes decisions and then the DM servers perform operations. A UE may also have multiple MAs and corresponding DM servers. For example, a mobile phone can be controlled by a wireless network operator’s MA using several operator’s DM OMA servers and by a telephone user's MA employer using other DM OMA servers. The operator may be responsible for managing connectivity for the operator’s network, including maintaining a roaming list of the cheapest roaming settings that are valid for subscribing the user to the operator. The employer may be responsible for tracking and managing all corporate applications on the device. The phone user can also make a decision, completely unaware of any DM OMA servers, regarding the download and installation of other software on the device.

7 is a block diagram of a communication system 700 that includes part of a typical network 702 and UE 106, which has the ability that its services can be selectively disconnected and connected using MO SDoUE, as described in this application. It will be appreciated that many devices of network entities other than those described in FIG. 7 can be used, that the UE can also connect to a network such as the Internet using a wireless local area network (WLAN) such as IEEE (Institute of Electrical Engineers and electronics) 802.11, WiMAX (IEEE 802.16), etc., and that the UE can use 3GPP WLAN interworking.

7, the UE 106 communicates with a network 702, which typically includes a radio access network (RAN) 704, such as a 3GPP or GSM / EDGE network, and core network entities including SGSN 706, a GPRS support gateway node 708 ( GGSN) and home location register 710 (HLR). GGSN 708 communicates with other networks, such as the Internet and VPLMN, and other entities, such as WAP infrastructure 712 and DM server 104.

RAN 704 typically includes one or more BSs and base station controllers, or Node Bs and Radio Network Controllers (RNCs), which are common. The RNC manages various radio network functions, including, for example, setting up a radio access channel, handover with channel diversity between BSs, etc. In most cases, each RNC routes calls to and from the UE through corresponding BSs that communicate with each other via downlink channels (i.e., from a base station to a mobile device or in a straight line) and uplink (i.e. from a mobile device to a base station or vice versa). Each BS serves a geographic area that is divided into one or more cells, and is usually connected to its corresponding RNC via leased telephone lines, fiber optic communication lines, microwave communication lines, etc.

The core network objects (SGSN, GGSN, etc.) are designed to handle many types of data. In a typical GSM \ EDGE network, PDP contexts for administering data streams are established, or activated, in the GGSN 608 in response to requests from the UE 106. It is understood that the UE can also connect to the network via WLAN access.

For easier understanding, the network 702 may be organized based on functionality into a control level or plane, a connectivity level or plane, and an application layer or plane, as shown in FIG. In this image, the UEs and radio access networks are depicted by “clouds”, and other network objects are depicted by other clouds. Such an organization is described in more detail, for example, in H. Hameleers et al., “IP Technology in WCDMA / GSM Core Networks”, Ericsson Review No. 1, pp. 14-27 (2002). The management layer hosts network management servers, such as DM servers 104, which include programmable processors that are responsible for establishing, modifying, and ending a call or session. Management servers can also handle mobility management, security, billing, and interoperability functions that relate to external networks at the management plane level. The connectivity layer hosts routers, switches, signaling gateways, media gateways (MGWs), and other user plane functions. Routers and switches provide transport capabilities for traffic on the control and user planes. The MGW facilitates user plane interaction, which includes the interaction between various radio access technologies and multimedia formats.

The interface between the control layer and the connectivity layer consists mainly of gateway control protocols. Network management servers use these interfaces to manipulate MGW resources at the connectivity level. The application layer, which is implemented as part of a service network, hosts application and content servers.

There are two interfaces between the core network and the service network: the horizontal interface and the vertical interface. The horizontal interface between the core network and the service network refers to the normal peer-to-peer mode or client / server operation mode for typical end-user applications such as web browsing, email, and audio / video services. These applications are usually called by the end user, but can also be called by the application server. The vertical interface allows applications that reside on specified application servers to supplement or modify the normal procedures for establishing calls or sessions over the core network. These applications interact with the core network through a set of standardized APIs.

In the CS domain, the servers of the mobile service center (MSC), gateway MSC (GMSC) and transit center switching services (TSC) are part of the control level. The corresponding MGW belongs to the connectivity layer. In the PS domain, both SGSN and GGSN can be considered as part of the connectivity level - they contain some management functionality - but their predominant functionality is to provide IP connectivity. With 3GPP, the “domain” added to the core mobile communication network is an IMS that has the main network entities: session / call control function (CSCF); Media Gateway Control Function (MGCF); Switching Gateway Control Function (BGCF) a media resource function control (MRF) node, or MRFC; MRF Processing Node (MRFP); Media Gateway (MG) and signaling gateway (SG). The subscriber’s master database, called the Home Network Subscriber Server (HSS), is common to the CS domain, PS domain, and IMS.

Table 3

DDF example in MO SDoUE

It is understood that the UE can implement the methods described in this application without using the above tree structure and DDF, which are simply concrete examples that have given host names, etc. The exemplary DDF is in a machine readable format that can be read by suitable tools that create a tree structure with little additional help. Implementations that use different names use different DDFs.

It is believed that the invention described herein can be fully embodied on a computer-readable storage medium of any kind having an appropriate set of instructions stored thereon for use with or in connection with a system, device or device for executing instructions, such as a computer system containing a processor system or other system, which can retrieve instructions from the media and execute instructions. As used in this case, a “computer-readable medium” can be any means that can contain, store, transmit, distribute or transport a program for use or in connection with a system, device, or device for executing instructions. A computer-readable medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, device, or propagation medium. More specific examples (non-exhaustive list) of computer-readable media include an electrical connection having one or more wires, a portable computer diskette, random access memory (RAM), read-only memory (ROM), and erasable programmable read-only memory (EPROM or flash memory).

It is expected that the present invention can be implemented in numerous environments, including, for example, mobile communication devices. It is also understood that the above procedures are performed repeatedly when necessary. To facilitate understanding, aspects of the invention are described in terms of sequences of actions that can be performed, for example, by elements of a programmable computer system. It is recognized that various actions can be performed by specialized circuits (for example, discrete logic gates interconnected to perform a specialized function, or specialized integrated circuits), program instructions executed by one or more processors, or a combination of both.

Thus, the invention can be embodied in many different forms, not all of which are described above, and all such forms are considered to be within the scope of the invention. For each of the various aspects of the invention, any such kind may be referred to as “logic configured to” perform the described action, or alternatively, as “logic that” performs the described action. It is emphasized that the terms “contains” and “comprising” when used in this application determine the presence of the declared features, integers, steps or components, and do not exclude the presence or addition of one or more other features, integers, steps, components or their groups.

The above specific embodiments are merely illustrative and should in no way be construed as limiting. The scope of the invention is defined by the following claims, and it is intended that all changes and equivalents that fall within the scope of the claims are covered in this document.

Claims (16)

1. A method of operating a user equipment (UE) in a public land mobile network (PLMN), comprising the steps of:
determining that the UE is incorrectly requesting at least one service from the PLMN;
informing the management entity in the home land mobile network of general use (HPLMN) about the wrong request;
requesting, through the HPLMN management entity, a computer device management server in HPLMN to disable the incorrectly requested service in the UE;
sending a message from the HPLMN server to the UE to establish a control session between the UE and the server; and
accessing the control object for selectively disabling the capabilities of the UE (SDoUE) in the UE, such that the incorrectly requested service is disabled, characterized in that at least one of the following is disabled: call control procedures, emergency calls with circuit switched channels, emergency calls via the Internet protocol multimedia system, and UE-initiated General Packet Radio Service (GPRS) Session Management Procedures (SM);
further comprising the step of: when the UE-initiated SM GPRS procedures are disabled, triggering the deactivation of the packet data protocol (PDP) contexts; and wherein the method further comprises the steps of:
receiving notification of a list of selective capabilities and device management according to an open mobile alliance (DM OMA);
issuing tags based on DM OMA notification;
PDP context request; and initiating PDP context activation if a label is issued. 2. The method according to claim 1, further comprising initiating a control session using the activated PDP context for the server that caused the SM GPRS procedures to be disabled. 3. The method according to claim 1, further comprising at least one of the following steps using the activated PDP context: making an emergency call on the Internet Protocol Multimedia Subsystem service and sending an alert message. 4. The method according to claim 1, further comprising the step of activating a timer based on the DM OMA notification, wherein activation of the PDP context is initiated if the timer does not time out. 5. The method of claim 1, wherein the OMA DM notification includes application identification. 6. A user equipment (UE) capable of communicating with a device management server, comprising:
a processor configured to execute software components residing in the UE and manage the services of the UE;
moreover, the software components include a UE Selective Disable (SDoUE) control object, which is configured by the processor to disable UE services based on a control session established between the UE and the server, characterized in that at least one of the emergency call control procedures is disabled circuit-switched calls, an emergency call over the Internet Protocol multimedia system, and General-Purpose General Packet Radio Service (GPRS) session management (SM) initiated UEs,
however, when the UE-initiated SM GPRS procedures are disabled, the processor initiates the deactivation of the packet data protocol (PDP) contexts. 7. The user equipment (UE) according to claim 6, in which the software components include a device management client in terms of application software components and GPRS in terms of access to software components and notification OM OMA; wherein the device management client requests a PDP context; and GPRS initiates activation of the PDP context if a label is issued. 8. The user equipment (UE) according to claim 7, in which the processor is configured to initiate a control session using the activated PDP context with the server that caused SM GPRS to be disabled. 9. The user equipment (UE) according to claim 7, wherein the processor is configured to make an emergency call on the Internet Protocol Multimedia Subsystem service or send an alert message using the activated PDP context. 10. The user equipment (UE) according to claim 7, further comprising a timer that is activated based on the DM OMA notification, wherein activation of the PDP context is initiated if the timer does not time out. 11. A computer-readable medium having instructions that, when executed by a processor in a user equipment (UE) in a public land mobile network (PLMN), cause the processor to perform the steps:
determining that the UE is incorrectly requesting at least one service from the PLMN;
informing the management entity in the home land mobile network of general use (HPLMN) about the wrong request;
requesting, through the HPLMN management entity, a computer device management server in HPLMN to disable the incorrectly requested service in the UE;
sending a message from the HPLMN server to the UE to establish a control session between the UE and the server; and
access to the control object for selective disconnection of UE capabilities (SDoUE) in the UE, such that the incorrectly requested service is turned off, characterized in that at least one of the following is disabled: call control procedures, emergency calls with circuit switching, emergency calls via the Internet protocol multimedia system and UE-initiated General Packet Radio Service (GPRS) Session Control (SM) Procedures,
moreover, the processor additionally performs the stage when the UE-initiated SM GPRS procedures are disabled, initiating deactivation of packet data protocol (PDP) contexts. 12. The medium of claim 11, wherein the processor further performs the steps of: receiving a DM OMA notification; issuing a label based on the DM OMA notification; PDP context request; and initiating PDP context activation if a label is issued. 13. The medium of claim 12, wherein the processor further performs the step of initiating a control session using the activated PDP context with the server that caused the SM GPRS to be disabled. 14. The medium of claim 12, wherein the processor additionally performs at least one of the following steps using the activated PDP context: making an emergency call on the Internet Protocol Multimedia Subsystem service and sending an alert message. 15. The medium of claim 12, wherein the processor further performs a step of activating a timer based on the DM OMA notification, wherein activation of the PDP context is initiated if the timer does not time out. 16. The medium of claim 12, wherein the OM OMA notification includes application identification.

Images