Nokia test mode problem solution ways
, -, F, R99, , -, Removal of Iu Release Failure, -, -, -, S2, S .. SP‑ , approved, Nokia, S, S2‑, agreed, ‑11‑19, TEI6, -, ‑ 12‑09 , 1, F, Rel-8, , -, Local address and address type in the TFT filter , -, Relationship between LIPA permissions and SIPTO permissions. (not a patent) license as the basis of his royalty rate, and failure to . On July 7, , IV moved to compel answers to interrogatories regarding the relationship .. (Fed. Cir.). The Federal Circuit affirmed on January, Microsoft Corp., Nokia Inc. and Saitek Industries, Ltd., Civil Action. No. GridNets local organization chair. (invited and peer-reviewed paper). . "Flexible TDMA access optical networks enabled by burst-mode software . "QoT-Aware RWA Algorithms for Fast Failure Recovery in All-Optical .
The control logic may also be referred to herein as the data server software Memory may also store data used in performance of one or more aspects described herein, including a first database and a second database In some embodiments, the first database may include the second database e. That is, the information can be stored in a single database, or separated into different logical, virtual, or physical databases, depending on system design.
Devices, may have similar or different architecture as described with respect to device Those of skill in the art will appreciate that the functionality of data processing device or device, as described herein may be spread across multiple data processing devices, for example, to distribute processing load across multiple computers, to segregate transactions based on geographic location, user access level, quality of service QoSetc. Generally, program modules include routines, programs, objects, components, data structures, etc.
Various aspects described herein may be embodied as a method, a data processing system, or a computer program product. Particular data structures may be used to more effectively implement one or more aspects described herein, and such data structures are contemplated within the scope of computer executable instructions and computer-usable data described herein.
With further reference tosome aspects described herein may be implemented in a cloud-based environment. As seen in FIG. Management server may be implemented on one or more physical servers. Management server may manage various computing resources, including cloud hardware and software resources, for example, host computersdata storage devicesand networking devices In other embodiments, public clouds or hybrid public-private clouds may be used by other customers over an open or hybrid networks.
Nokia Local Test Mode And Contact Service Problem Solution | mobile manual
Management server may be configured to provide user interfaces through which cloud operators and cloud customers may interact with the cloud system. Client computers may connect to management server via the Internet or other communication network, and may request access to one or more of the computing resources managed by management server In response to client requests, the management server may include a resource manager configured to select and provision physical resources in the hardware layer of the cloud system based on the client requests.
For example, the management server and additional components of the cloud system may be configured to provision, create, and manage virtual machines and their operating environments e. Cloud systems also may be configured to provide various specific services, including security systems, development environments, user interfaces, and the like. Certain clients may be related, for example, different client computers creating virtual machines on behalf of the same end user, or different users affiliated with the same company or organization.
In other examples, certain clients may be unrelated, such as users affiliated with different companies or organizations. For unrelated clients, information on the virtual machines or storage of any one user may be hidden from other users.
Referring now to the physical hardware layer of a cloud computing environment, availability zones or zones may refer to a collocated set of physical computing resources. Zones may be geographically separated from other zones in the overall cloud of computing resources.
For example, zone may be a first cloud datacenter located in California, and zone may be a second cloud datacenter located in Florida. Management sever may be located at one of the availability zones, or at a separate location. Each zone may include an internal network that interfaces with devices that are outside of the zone, such as the management serverthrough a gateway.
End users of the cloud e. For example, an end user may request the creation of a virtual machine having a specified amount of memory, processing power, and network capabilities. The management server may respond to the user's request and may allocate the resources to create the virtual machine without the user knowing whether the virtual machine was created using resources from zone or zone In other examples, the cloud system may allow end users to request that virtual machines or other cloud resources are allocated in a specific zone or on specific resources within a zone.
In this example, each zone may include an arrangement of various physical hardware components or computing resourcesfor example, physical hosting resources or processing resourcesphysical network resources, physical storage resources, switches, and additional hardware resources that may be used to provide cloud computing services to customers.
The physical hosting resources in a cloud zone may include one or more computer serverssuch as virtualization servers, which may be configured to create and host virtual machine instances. The physical network resources in a cloud zone or may include one or more network elements e. The storage resources in the cloud zone may include storage disks e.
The example cloud computing environment shown in FIG. The virtualization layer may include one or more hypervisors, along with other components to provide network virtualizations, storage virtualizations, etc. For example, the virtualization layer may include a hypervisor installed in each of the virtualization servers with the physical computing resources.
Known cloud systems may alternatively be used, e. The architecture enables a user of a mobile device e. The user may access such enterprise resources or enterprise services using a mobile device that is purchased by the user or a mobile device that is provided by the enterprise to the user.
local mode failed - GSM-Forum
The user may utilize the mobile device for business use only or for business and personal use. The enterprise may choose to implement policies to manage the mobile device The policies may be implanted through a firewall or gateway in such a way that the mobile device may be identified, secured or security verified, and provided selective or full access to the enterprise resources.
The policies may be mobile device management policies, mobile application management policies, mobile data management policies, or some combination of mobile device, application, and data management policies. A mobile device that is managed through the application of mobile device management policies may be referred to as an enrolled device or managed device. In some embodiments, the operating system of the mobile device may be separated into a managed partition and an unmanaged partition The managed partition may have policies applied to it to secure the applications running on and data stored in the managed partition.
Stated differently, by enforcing policies on managed apps, those apps may be restricted to only be able to communicate with other managed apps and trusted enterprise resources, thereby creating a virtual partition that is impenetrable by unmanaged apps and devices.
The applications running on the managed partition may be secure applications. The secure applications may be email applications, web browsing applications, software-as-a-service SaaS access applications, Windows Application access applications, and the like.
The secure applications may be secure native applicationssecure remote applications executed by a secure application launchervirtualization applications executed by a secure application launcherand the like.
The secure native applications may be wrapped by a secure application wrapper The secure application wrapper may include integrated policies that are executed on the mobile device when the secure native application is executed on the device.
The secure application wrapper may include meta-data that points the secure native application running on the mobile device to the resources hosted at the enterprise that the secure native application may require to complete the task requested upon execution of the secure native application The secure remote applications executed by a secure application launcher may be executed within the secure application launcher application The virtualization applications executed by a secure application launcher may utilize resources on the mobile deviceat the enterprise resourcesand the like.
The resources used on the mobile device by the virtualization applications executed by a secure application launcher may include user interaction resources, processing resources, and the like. The user interaction resources may be used to collect and transmit keyboard input, mouse input, camera input, tactile input, audio input, visual input, gesture input, and the like. The processing resources may be used to present a user interface, process data received from the enterprise resourcesand the like.
The resources used at the enterprise resources by the virtualization applications executed by a secure application launcher may include user interface generation resources, processing resources, and the like.
The user interface generation resources may be used to assemble a user interface, modify a user interface, refresh a user interface, and the like. The processing resources may be used to create information, read information, update information, delete information, and the like. For example, the virtualization application may record user interactions associated with a GUI and communicate them to a server application where the server application will use the user interaction data as an input to the application operating on the server.
In this arrangement, an enterprise may elect to maintain the application on the server side as well as data, files, etc. For example, while some applications may be secured for use on the mobile device, others may not be prepared or appropriate for deployment on the mobile device so the enterprise may elect to provide the mobile user access to the unprepared applications through virtualization techniques.
As another example, the enterprise may have large complex applications with large and complex data sets e. As yet another example, the enterprise may have an application that maintains highly secured data e.
An enterprise may elect to provide both fully secured and fully functional applications on the mobile device as well as a virtualization application to allow access to applications that are deemed more properly operated on the server side.
In an embodiment, the virtualization application may store some data, files, etc. An enterprise, for example, may elect to allow certain information to be stored on the phone while not permitting other information. The application may communicate the user interactions to the server side to be used by the server side application as user interactions with the application.
In response, the application on the server side may transmit back to the mobile device a new GUI. For example, the new GUI may be a static page, a dynamic page, an animation, or the like, thereby providing access to remotely located resources. The secure applications may access data stored in a secure data container in the managed partition of the mobile device.
The data secured in the secure data container may be accessed by the secure wrapped applicationsapplications executed by a secure application launchervirtualization applications executed by a secure application launcherand the like.
The data stored in the secure data container may include files, databases, and the like. The data stored in the secure data container may include data restricted to a specific secure applicationshared among secure applicationsand the like. Data restricted to a secure application may include secure general data and highly secure data Secure general data may use a strong form of encryption such as AES bit encryption or the like, while highly secure data may use a very strong form of encryption such as AES bit encryption.
Data stored in the secure data container may be deleted from the device upon receipt of a command from the device manager The secure applications may have a dual-mode option The dual mode option may present the user with an option to operate the secured application in an unsecured mode.
In an unsecured mode, the secure applications may access data stored in an unsecured data container on the unmanaged partition of the mobile device The data stored in an unsecured data container may be personal data The data stored in an unsecured data container may also be accessed by unsecured applications that are running on the unmanaged partition of the mobile device The data stored in an unsecured data container may remain on the mobile device when the data stored in the secure data container is deleted from the mobile device This operation may be referred to as a selective wipe.
With the enterprise and personal data arranged in accordance to the aspects described herein, an enterprise may perform a selective wipe. The mobile device may connect to enterprise resources and enterprise services at an enterprise, to the public Internetand the like. The mobile device may connect to enterprise resources and enterprise services through virtual private network connections. The virtual private network connections also referred to as microVPN or application-specific VPN may be specific to particular applicationsparticular devices, particular secured areas on the mobile device, and the like e.
For example, each of the wrapped applications in the secured area of the phone may access enterprise resources through an application specific VPN such that access to the VPN would be granted based on attributes associated with the application, possibly in conjunction with user or device attribute information.
The virtual private network connections may support and enable single-sign-on authentication processes The single-sign-on processes may allow a user to provide a single set of authentication credentials, which are then verified by an authentication service The authentication service may then grant to the user access to multiple enterprise resourceswithout requiring the user to provide authentication credentials to each individual enterprise resource The virtual private network connections may be established and managed by an access gateway The access gateway may include performance enhancement features that manage, accelerate, and improve the delivery of enterprise resources to the mobile device The access gateway may also re-route traffic from the mobile device to the public Internetenabling the mobile device to access publicly available and unsecured applications that run on the public Internet The mobile device may connect to the access gateway via a transport network The transport network may be a wired network, wireless network, cloud network, local area network, metropolitan area network, wide area network, public network, private network, and the like.
The enterprise resources may include email servers, file sharing servers, SaaS applications, Web application servers, Windows application servers, and the like. Email servers may include Exchange servers, Lotus Notes servers, and the like. SaaS applications may include Salesforce, and the like. Windows application servers may include any application server that is built to provide applications that are intended to run on a local Windows operating system, and the like.
The enterprise resources may be premise-based resources, cloud based resources, and the like. The enterprise resources may be accessed by the mobile device directly or through the access gateway The enterprise resources may be accessed by the mobile device via a transport network The enterprise services may include authentication servicesthreat detection servicesdevice manager servicesfile sharing servicespolicy manager servicessocial integration servicesapplication controller servicesand the like.
Authentication services may include user authentication services, device authentication services, application authentication services, data authentication services and the like. Authentication services may use certificates. The certificates may be stored on the mobile deviceby the enterprise resourcesand the like. The certificates stored on the mobile device may be stored in an encrypted location on the mobile device, the certificate may be temporarily stored on the mobile device for use at the time of authentication, and the like.
Threat detection services may include intrusion detection services, unauthorized access attempt detection services, and the like.
Unauthorized access attempt detection services may include unauthorized attempts to access devices, applications, data, and the like. Device management services may include configuration, provisioning, security, support, monitoring, reporting, and decommissioning services. File sharing services may include file management services, file storage services, file collaboration services, and the like.
Policy manager services may include device policy manager services, application policy manager services, data policy manager services, and the like. Social integration services may include contact integration services, collaboration services, integration with social networks such as Facebook, Twitter, and LinkedIn, and the like. Application controller services may include management services, provisioning services, deployment services, assignment services, revocation services, wrapping services, and the like.
All sites are provided with a shared function for mapping transitive graphs to a selected node in that graph designated as the primary copy. The site of the primary copy is referred to as the primary site. The identity of the primary copy will change as the graph changes due to individual model objects joining and leaving the collaboration, as noted above.
Any model object can potentially be the primary copy at some time. When a model object serves as the primary copy, its history is augmented with a reservation list, shown in FIGS.
Each model object in the relationship has instance variables for recording VTg and VTr during a particular transaction, detailed below to insure that the VT values set by the primary copy will be respected. The concurrency control system is predicated on the fact that the results of executing reads and updates at all sites must be the same as if they had executed in VT order at the primary site.
Whenever the originating site of the transaction is not the primary site of some of the objects read or written by a transaction, the transaction executes optimistically, with update notifications to all related entities. If these guesses are confirmed, the transaction is able to commit. Section III Method of Operation for Collaboration Manager The remainder of the ensuing description will involve the operations of the present inventive system, the apparatus of which has been the subject of the preceding portion of the description and which will be referred to throughout.
As will be understood by one having skill in the relevant art, the process flow charts are representatively created to elucidate the description, and should not be interpreted as providing the necessary order of operations for a parallel processing environment. The Collaboration Manager 70 will respond to the user requests in accordance with the following descriptions.
Create Model Object A user request to create a model object will specify the model object type e. If the model object is an association object, the new association object 60 is initialized to be a primary association object with an empty set of relationships, of FIG.
Create from Invitation In a request to the Collaboration Manager to create an association object from an invitation, the invitation will contain an encoding of the OID of the primary association object at another site. The encoding can be done by any one of a number of encoding techniques which have been used in the past to externalize remote object references e. The Collaboration Manager responds to the invitation by creating an association model object, together with an OID as above.
The primary site OID is referred to in the newly created, but as yet unregistered, association object and is stored in location If the current context is view context or transaction context, then the transaction is a dependent transaction. If the current context is view context, the context object is a VP.
If the current context is transaction context, the context object will be a TI, which is notified of the new LocalTI at In response to such notification, the notified object either ViewTI or LocalTI will create a guessid and will retain the guessid and a reference to the new LocalTI on its ControlDependency listas shown at steps and The guessid is then returned to the new LocalTI object atwhich completes its initialization by saving the guessid on its MyGuesses listat step This operation records the fact that the new LocalTI will commit only if the originating transaction i.
The Collaboration Manager will schedule TIs from its work queue whenever the queue is non-empty. The TI object then invokes an execute method of the user transaction object denoted as its user transaction reference at stepincluding one or more of the operations detailed in Section IV below. The user transaction, in response, invokes operations on the model objects. The exact behavior of each operation will depend upon the data type of the model object, with local computation being the same as the local computation performed by a conventional non-collaborative object.
After all of the operations of a transaction have been performed i. Each model object then executes a concurrency control and distribution protocol, stepas further detailed below in Section V. Each updated model object, in turn, notifies any attached VP objects on its VP list of the update and the VP objects perform a view notification protocol as detailed in Section VI below.
Messages The Collaboration Manager at each site receives messages resulting from execution of various protocols at other sites. The messages are queued in the message queue so that they can be executed serially with transactions. When the message is a Request or a Response of a protocol initiated at a model object as detailed in Section V belowthe Collaboration Manager simply routes the message to the appropriate model object, as determined from the OID, by referring to table The RemoteTI, whether newly-created or pre-existing, is given the message atwith the OID translated into a model object reference according to table from The RemoteTI then checks its state in step If it is Aborted, the message is discarded at If the state is Committed, the message is delivered to the model object at and a commit notification is sent to that model object at Finally, if the state is Waiting, the RemoteTI appends the reference to the model object on the Notify listat stepand the message is routed to the model object at The model object responds by updating its history at step and issuing a NotifyUpdate to each VP on its list at step If no RemoteTI exists, one is created having a Waiting state and an empty Notifylist as at above.
The execute method may read, write, and update model objects within the application. Any changes to model objects will be propagated to their replicas. In addition to performing the execute function, one or more of the following will be performed: After processing the transaction, the TI will be in one of three states, recorded atAborted, Committed, or Waiting.
If the state is Aborted, because the concurrency control protocol aborted the transaction, the LocalTI performs an Abort action — comprising the steps of 1 sending an Abort notification to all of the model objects on the Notify list ; 2 sending an external Abort message containing the VT to all Collaboration Managers at sites on the Site list ; and, 3 sending a DenyGuess for each guessid to the corresponding TI object on its ControlDependency list The TI is then rescheduled for execution on the queue and the transaction retried when the Collaboration Manager finds it at the top of the queue.
If the state is Committed, because the transaction was not aborted and there are no guesses on the MyGuesses list, a Commit action — is performed by the LocalTI. In performing a Commit action, the LocalTI does the following: Finally, if the state is Waiting, because the transaction has not been aborted, but there are guesses on the MyGuesses list which have not yet been confirmed or denied, the concurrency control protocol guarantees that a future event will occur which will either send a ConfirmGuess or a DenyGuess method call to the TI.
Upon receiving a ConfirmGuess method call atthe TI removes the designated guessid from the MyGuesses list at If this results in the condition that the MyGuesses list is now empty, then the TI performs a Commit action —unless the TI is in the Aborted state. Upon receiving a DenyGuess method call atthe TI enters the Aborted state at and performs an Abort action at — Read or Modify When a model object receives a user request to read or modify its value determined atthe model object executes that request and performs additional actions, as follows.
The model object checks the context atdue to the fact that state-changing operations must only be performed from transaction context. For operations arising out of a view context, an exception is raised at with an error signalled to the user. From controller context, either an exception is raised at or an implicit transaction is created and scheduled.
In addition, the current TI is determined at from the context objecteither as a LocalTI if in the transaction context or from the VP's current view TI,if in the view context. The virtual time is computed from the current TI's virtual time at step The model object additionally records the identity at of each updated model object in the Notify list of the current TI. In one implementation of the invention all reads may be recorded as well.
Any read of the state of the object is performed as of the VT of the current context, such that the value which is read is the latest value of a write moment whose VT, at b, is earlier than the current TI's VT. If the write moment, at c, associated with the state read is currently not committed, as determined atthan a new guess is created on the MomentGuess list in stepand the id of that guess is communicated to the LocalTI, at stepwhich places that guess on it MyGuesses list Finally, attached VPs on the list are notified of the updated value with the method NotifyUpdate at and Further view notification is performed in accordance with the description found in Section VI.
Commit When a commit notification is received at a model object, as determined atthe model object performs the following: Abort When an Abort notification is received at the model object, as determined atthe model object does the following: Attachview In response to a user AttachView request, as determined atthe model object interrogates the Collaboration Manager 70 at to determine whether a VP already exists for the specified view object.
The Collaboration Manager makes this determination by performing a lookup at table If a VP already exists, the model object notifies the VP at that the model object is being attached. The VP updates its list of attached model objects atand performs an AttachView operation at to invoke the view notification protocols of Section VI. The model object updates its VP list by adding a reference to the VP at If a VP does not exist, a VP is created and given a reference to the user view, with the particular implementation of VP being selected based upon the view notification mechanism, below.
The Collaboration manager updates it table by appending a mapping between the user view object a and the new VP object b. Detachview In response to a DetachView user request, as determined atthe model object requests at that the Collaboration Manager perform a lookup of its table to ascertain which VP object corresponds to the detached user view object.
The model object then notifies, atthe attached view object that the model object is being detached.
The VP updates its list by removing the detached model object reference atand invokes the DetachView operation at resulting in execution of the view notification protocol in accordance with Section VI. The model object updates its VP list by removing the reference to the VP, at Site 1 holds M, which is replicated at Site 2 as MR. The representative communications among the entities are illustrated along the arrows. As the ensuing description details, the other protocols will parallel the illustrated Join and Leave protocols.
CreateInvitation In response to a user CreateInvitation request, if the association model object is a primary association object see FIG. The invitation is an external object reference which can be created using any of a number of well-known distributed object implementations, such as the aforementioned CORBA.
If the association model object is not a primary association object, then the invitation is created referring to the OID of the primary association object saved in slot Register In response to a Register user request, a primary association model object needn't perform any functions, since it is already registered. If the association model object is not primary and it is not registered, then it invokes a Register protocol to assure that a when the transaction containing the Register operation commits, the value of the association model object is a copy of the component and FIGS.
The Register protocol for a non-primary, non-registered includes the following steps: If the relationship name is omitted, a new relationship is created containing the single model object. The association object additionally invokes a specific Join protocol to actively notify all model objects in the relationship of the fact that the designated model object has joined the relationship, and, where necessary, to update the values of the model objects and their graphs to reflect the change in relationship.
The association object additionally invokes a specific Leave protocol to actively notify all model objects in the relationship of the fact that the requesting model object has left the relationship and to update their graphs. If, however, the originating site is not the site of the primary association object, the originating association object updates its value, registers a guess with the LocalTI, saving the guessid in a slot associated with the write moment VTn, and sends a Request-Join or a Request-Leave request to the primary association object, specifying its own OID, the time VT, the time of the most recent previous graph write moment VTg, and the request parameters.
The primary association responds to this message by checking that no intervening write moment occurred between the time VTn and the VTg, reserving that interval so that subsequent attempts to update that association object will abort.
The primary association object also checks that VT itself does not lie in any previously reserved interval. If all of the foregoing checks succeed, then the primary object updates the association data, distributes it to all registered association objects, except for the requesting object, via a Distribute message, and sends a Response-Confirmed message to the requesting association object.
If a check fails, the primary sends a Response-Denied message to the requesting association object. When the requesting association object receives a Request-confirmed message, it retrieves the guessid from the slot associated with write moment VT and sends a guess confirmed confirmation notice to the LocalTI.
In the alternative, if a Response-Denied message is received at the requesting object, it retrieves the guessid and sends a guess deny notification to the LocalTI. In response to receipt of the request, the association object first checks to determine if the designated relationship currently exists.
If it does not exist, an exception is raised, unless no relationship was specifically identified, in which case a new relation is created in the association object at of FIG. The association object registers five guesses with the LocalTI, receiving five guessid's for these five assumptions including guessid1—meaning that data read from the joined model object is committed; guessid2 meaning that the data and graph written are writable at the primary copy of the joining model object; guessid3 meaning that the graph read from the joining model object is committed; guessid4 meaning that the graph read from the joined model object is committed; and, guessid 5 meaning that the data and graph written are writable at the primary copy of the joined model object.
If the current value of the graph of the requesting model object is uncommitted, then guessid3 is placed on the Momentguess list of the graph history of the model object. If committed, then guessid3 is confirmed at the LocalTI with a message sent containing the VT of the join operation, the current value of the graph of the model object, the virtual time VTg that the graph was modified, the requesting OID of the model object, the new pairing of the primary association object and the OID of the requesting model object, and guessids 1, 2, 4 and 5.
The arbitrarily selected model object which receives the Request-DelegateJoin message checks to see if the VT associated with the last change to the current graph is committed. If not committed, it inserts guessid4 on the MomentGuess list of the history write moment associated with the last change to the current graph.
If the VT associated with the last change to the model data is committed, then a ConfirmGuess message is sent specifying the VT of the Request-DelegateJoin message, and guessid1. If not, guessid1 is inserted on the MomentGuess list of the history write moment associated with the last change to the model data. Next, the model object creates an augmented graph cf: The augmented graph along with the data is propagated to all model objects on the augmented graph via the message DistributeGraphAndData, containing the VT, the graph and the data.
The selected model object also sends Request-ConfirmUpdateGraph to the primary copy of the original graph prior to merging, specifying guessid5, VT, and the time VTo that the original graph was last written. Finally, the selected object sends a Request-ConfirmUpdateGraph message to the primary copy of the graph, the identity of which was received in the Request-DelegateJoin message specifying guessid2, and VTg.
Model objects respond to the DistributeGraphAndData message from the selected model object by creating new uncommitted write moments in their data history and graph history associated with the given VT and by notifying the attached VP objects. The concurrency control mechanism is augmented for Join situations whereby model objects at the primary site respond to the message Request-ConfirmChangeGraph, specifying a VT, a graph virtual time VTg, and a guessid by performing the GL and GNC operations and the NC operations detailed below.
If the checks succeeds, then a Response-ConfirmGuess is sent to the originating site corresponding to the VT, containing that guessid. If the checks do not both succeed, a Response-DenyGuess is generated to the originating site corresponding to the VT and containing that guessid. When a transaction is committed or aborted, and the guesses on the MomentGuess list are confirmed or denied, remaining guesses may be remote guesses, associated with a RemoteTI rather than a LocalTI.
If it did not exist, an exception is raised. Assuming that the entry is found, the entry is updated to remove the model object which is leaving.