This application claims the benefit under 35 U.S.C. §119(a) of Korean patent applications filed in the Korean Industrial Property Office on Mar. 6, Apr. 8, Apr. 17, Apr. 21, and May 9, 2008 and respectively assigned Serial Nos. 10-2008-0021107, 10-2008-0032879, 10-2008-0035839, 10-2008-0036781, and 10-2008-0043670, the entire disclosures of all of which are hereby incorporated by reference.
1. Field of the Invention
The present invention relates to a Convergence of Broadcasting and Mobile Service (CBMS) system. More particularly, the present invention relates to a method and an apparatus for Electronic Service Guide (ESG) selection in a CBMS system.
2. Description of the Related Art
With the development of communication and broadcast technologies, broadcast systems and mobile communication systems are able to provide a mobile Broadcast, which includes transmission of packet data through a broadcast channel. The capability of the mobile Broadcast is beyond that of the typical broadcast service which is limited to voice and image services. Establishing such a mobile Broadcast may include the discovery of a service by a mobile terminal capable of receiving the mobile broadcast, such as a mobile phone, a notebook, or a Personal Digital Assistant (PDA), subscription of the mobile terminal to the service, provision of various pieces of control information for reception of the service, transmission of the service and reception of the service by the mobile terminal.
The Open Mobile Alliance (OMA), which is an organization studying standards for interaction between individual mobile solutions, has determined standards for various applications mainly relating to mobile games, Internet services, etc. Among the working groups of the OMA, the sub working group of the Browser and Content (OMA BAC) Mobile Broadcast (BCAST) is studying technologies for convergence of a broadcast service and a mobile communication service by using a mobile terminal capable of communicating with an interactive network. Further, the Digital Video Broadcasting-Convergence of Broadcasting and Mobile Service (DVB-CBMS), which is an organization for mobile broadcast terminal standards, also defines system structures, interfaces, etc. for convergence of a broadcast service and a mobile communication service.
Referring to
The broadcast network 107 is a network that transmits broadcast service data, an example of which is the DVB-H system. In general, the interactive network 109 refers to a cellular mobile communication network, such as the Universal Mobile Telecommunications system (UMTS) according to the 3rd Generation Partnership Project (3GPP), the International Mobile Telecommunications (IMT)-2000 according to the 3GPP2, and the Wireless Local Area Network (WLAN) or Wireless Broadband internet (WiBro). Also, the interactive network 109 may include all types of mobile communication networks capable of receiving information or a request from the terminal 111 and transmitting a response to the information or the request. The broadcast network 107 and the interactive network 109 operate as transmission bearers in a Convergence of Broadcasting and Mobile Service (CBMS) system.
The terminal 111 refers to a user terminal or receiver capable of accessing the interactive network 109 and receiving a broadcast service supplied from the broadcast network 107. In a CBMS system, the terminal 111 receives service data and signaling information from the broadcast network 107 and bi-directionally exchanges service data and signaling information with the interactive network 109.
Hereinafter, interfaces between individual entities including the logical entities will be described. In
The interfaces of X-1, X-2 and X-3 refer to reference points between the broadcast network 107 and other entities, and they are typically not used in interactive standards based on the DVB-H. The X-1 interface interconnects the content creation block 101 and the service application block 103, the X-2 interface interconnects the interactive network 109 and the terminal 111, and the X-3 interface interconnects the service management block 105 and the interactive network 109.
The CBMS-1 interface carries broadcast-related signaling, i.e. Program Specific Information/Service Information (PSI/SI), from the broadcast network 107 to the terminal 111, and the CBMS-2 interface transfers content including audio, video, and files, from the service application block 103 to the terminal 111. The CBMS-3 interface transfers an Electronic Service Guide (ESG) from the service management block 105 to the terminal 111 through the broadcast network 107 in the form of Point-To-Multipoint (PTM) transmission. The CBMS-4 interface is used for Point-To-Point (PTP) transmission of ESG metadata and access control for service applications of the service application block 103 between the service management block 105 and the terminal 111. The CBMS-5 interface, which is an interface for PTP transmission service between the service application block 103 and the terminal 111, transfers a Short Message Service (SMS), a Multimedia Message Service (MMS), etc. through the interactive network 109. The CBMS-6 interface carries configuration parameters, which include allocated bandwidths and the number of services for DVB-H transmission, between the service management block 105 and the broadcast network 107. The CBMS-7 interface is used for description of a service application including metadata and content description or declaration of a service application between the service application block 103 and the service management block 105.
In order to receive a broadcast service in a mobile broadcast system such as the CBMS system, the terminal receives a Service Guide (SG), which includes description information of the service itself, charging information for the service, and information on a method of receiving the service. Then, by using the SG, the terminal can receive a service that it desires.
According to the conventional art as described above, in order to receive the ESG bootstrap information and receive a desired service through selection of an ESG, the terminal has to select an ESG bootstrap entry point from the PSI/SI in the broadcast network. Therefore, there is a need for the ability to select an ESG in an interactive network using an OMA Device Management (DM) without using the broadcast network.
An aspect of the present invention is to address at least the above-mentioned problems and/or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the present invention is to provide a method and an apparatus for discovering an Electronic Service Guide (ESG) bootstrap entry point for selection of an ESG in an interactive network.
Another aspect of the present invention is to provide a method and an apparatus for discovering roaming partner information within a roaming coverage area of a mobile station and an ESG bootstrap entry point corresponding to the roaming partner information.
In accordance with an aspect of the present invention, a method of providing discovery information of an ESG bootstrap entry point, which is a point for requiring ESG bootstrap information for selection of an ESG, by a server in a Convergence of Broadcasting and Mobile Service (CBMS) system, is provided. The method includes listing at least one piece of ESG bootstrap characteristic information for an ESG bootstrap appropriate for a status of a terminal, creating a Management Object (MO), which connects the ESG bootstrap entry point with said at least one piece of ESG bootstrap characteristic information and transmitting the created MO to the terminal through an interactive channel.
Other aspects, advantages, and salient features of the invention will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses exemplary embodiments of the invention.
The above and other aspects, features and advantages of certain exemplary embodiments of the present invention will be more apparent from the following description taken in conjunction with the accompanying drawings, in which:
Throughout the drawings, it should be noted that like reference numbers are used to depict the same or similar elements, features, and structures.
The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of exemplary embodiments of the invention as defined by the claims and their equivalents. It includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. In addition, descriptions of well-known functions and constructions are omitted for clarity and conciseness.
The terms and words used in the following description and claims are not limited to the bibliographical meanings, but, are merely used by the inventor to enable a clear and consistent understanding of the invention. Accordingly, it should be apparent to those skilled in the art that the following description of exemplary embodiments of the present invention are provided for illustration purpose only and not for the purpose of limiting the invention as defined by the appended claims and their equivalents.
It is to be understood that the singular forms “a,” “an,” and “the” include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to “a component surface” includes reference to one or more of such surfaces
By the term “substantially” it is meant that the recited characteristic, parameter, or value need not be achieved exactly, but that deviations or variations, including for example, tolerances, measurement error, measurement accuracy limitations and other factors known to skill in the art, may occur in amounts that do not preclude the effect the characteristic was intended to provide.
Exemplary embodiments of the present invention propose mechanisms, which enable a terminal to either select a new Electronic Service Guide (ESG) bootstrap entry point based on the Open Mobile Alliance (OMA) Device Management (DM) or select an ESG based on provisioning. As used herein, the term “ESG bootstrap entry point” denotes a point at which a terminal can access an ESG bootstrap in order to search for ESG bootstrap information.
First, Management Object (MO), which is ESG bootstrap entry point information used in searching for an ESG bootstrap entry point by using the OMA DM, is defined. According to exemplary embodiments of the present invention, the MO may have various configurations, and may provide useful information, which enables a terminal to select an appropriate ESG bootstrap entry point information. Therefore, the MO can be properly modified according to its use.
Referring to
The tables below provide a description of each node, which is provided through a description of the OMA DM. Therefore, a more detailed description of the tables below can be obtained by referring to detailed descriptions of OMA DMs.
Table 1 below shows the above-mentioned node <x> in more detail.
Table 2 shows the above-mentioned node <x>/IPDC/ in more detail.
Table 3 below shows the above-mentioned node <x>/IPDC/ESG/ in more detail.
Table 4 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPointURL/ in more detail.
Based on the representative MO described above, a terminal can search for an ESG bootstrap entry point URL by using the following OMA DM mechanisms.
Table 5 shows ideas of exemplary embodiments of the present invention.
A terminal can register in a particular Internet Protocol Data Cast Key Management System (IPDC KMS) and IPDC operator, and has a right to access a service possessed by the IPDC KMS and IPDC operator. A service described in the ESG may belong to a particular single IPDC KMS and IPDC operator, and the IPDC KMS and IPDC operator information is given within an acquisition fragment.
When a service is given within an acquisition fragment as described above, a terminal may not be aware of which IPDC operator each service belongs to, before selecting and searching for an ESG.
Meanwhile, a current IPDC operator can be identified by the IPDCKMSID and IPDCOperatorID. In exemplary embodiments of the present invention, the IPDCKMSID and IPDCOperatorID are used as an IPDC operator identifier. If the IPDC operator identifier is changed later, related identifiers also should be replaced by new identifiers.
When the IPDCKMSID and IPDCOperatorID are used as an IPDC operator identifier as described above, indication information reading “which ESG is proper for a terminal registered in a particular IPDC KMS and IPDC operator” in an OMA DM mechanism according to the first exemplary embodiment of the present invention can achieve optimization of the OMA DM mechanism, and helps the terminal to more easily and rapidly find a proper ESG bootstrap entry point for selection of an ESG belonging to the IPDC KMS and IPDC operator.
Referring to
Through nodes 301 to 311 as described above, the terminal can search for an ESG bootstrap entry point URL, and can find an ESG having corresponding IPDCKMSID and IPDCOperatorID from the ESG bootstrap entry point URL obtained through the search.
A second OMA DM mechanism according to the first exemplary embodiment of the present invention provides a bootstrap entry point for a particular ESG KMS system. All bootstrap information for an IPDC operator belonging to a particular IPDC KMS system using a bootstrap entry point is described below.
Referring to
Based on the second OMA DM mechanism according to the first exemplary embodiment of the present invention as described above, the terminal can search for an ESG bootstrap entry point URL. From the ESG bootstrap entry point URL obtained through the search, the terminal can find an ESG having an IPDCKMSID which the terminal itself has registered.
The following description of mechanisms based on the OMA DM mechanism according to the first exemplary embodiment of the present invention will use the first OMA DM mechanism according to the first exemplary embodiment of the present invention as an example. Of course, the mechanisms described below can be applied to similar examples using the second OMA DM mechanism according to the first exemplary embodiment of the present invention. However, for convenience of description, the present specification discusses only the examples using the first OMA DM mechanism according to the first exemplary embodiment of the present invention.
In some circumstances, there may be multiple ESG providers within each ESG bootstrap, and each ESG provider can provide multiple ESGs. Therefore, a single ESG bootstrap entry point may include multiple pieces of ESG information. When a single ESG bootstrap entry point may include multiple pieces of ESG information as described above, an OMA DM mechanism according to the second exemplary embodiment of the present invention indicates an ESG Universal Resource Identifier (ESGURI), so as to provide a solution enabling a terminal to find a proper ESG bootstrap entry point.
Referring to
A second OMA DM mechanism according to the second exemplary embodiment of the present invention is a mechanism based on the OMA DM mechanism according to the first exemplary embodiment of the present invention as described above.
Referring to
Through the OMA DM mechanism according to the second exemplary embodiment of the present invention as described above, the terminal can find the ESG bootstrap entry point related to only the desired ESG. For example, the terminal accesses an ESG1 in one network and then moves to another network. However, the change of the network causes a change of bootstrap information for the ESG1. At this time, without using the OMA DM mechanism according to the second exemplary embodiment of the present invention, the terminal must search all bootstrap information for the bootstrap information relating to ESG1. However, by using the OMA DM mechanism according to the second exemplary embodiment of the present invention, the terminal can find the bootstrap information relating to ESG1.
Multiple available ESGs may exist within multiple areas. When there are multiple available ESGs within multiple areas as described above, the OMA DM mechanism according to a third exemplary embodiment of the present invention enables a terminal located within a particular area to acquire bootstrap information for an ESG usable within the particular area through an ESG bootstrap entry point.
Referring to
In the OMA DM mechanism according to the first exemplary embodiment of the present invention described above, the ESG bootstrap entry point is a point for a particular terminal from particular IPDCKMSID and IPDCOperatorID in a particular area.
Referring to
Using the OMA DM mechanism according to the third exemplary embodiment of the present invention as described above, the terminal can obtain an ESG bootstrap entry point for only a particular area. For example, when there exist two cells each having an ESG, it is possible to prepare two different ESG bootstrap entry points for the two cells, so as to use the two different ESG bootstrap entry points according to the position of the terminal.
Each network may have available a plurality of ESGs, each of which is different according to the network. For example, each network may have its own ESG for satellite, ESG for DVB-H, ESG for an interactive network and the like. In the case where available ESGs are different according to the network as described above, an OMA DM mechanism according to a fourth exemplary embodiment of the present invention enables a terminal having accessed a particular network to acquire bootstrap information for an ESG usable in the network through an ESG bootstrap entry point.
Referring to
In the OMA DM mechanism according to the first exemplary embodiment of the present invention described above, the ESG bootstrap entry point is a point for a particular terminal from particular IPDCKMSID and IPDCOperatorID in a particular area.
Referring to
In an OMA DM mechanism according to the fourth exemplary embodiment of the present invention, a terminal can obtain an ESG bootstrap entry point for a particular network. For example, a Digital Video Broadcasting-Satellite service to Handheld (DVB-SH) terminal can use a satellite ESG bootstrap entry point when it receives a satellite signal, and use a terrestrial ESG bootstrap entry point when it receives a terrestrial signal.
There exists a large amount of detailed information about each ESG bootstrap and ESG. The above description relating to the first to fourth exemplary embodiments of the present invention discusses characteristic information, which includes a mechanism for an ESG bootstrap entry point relating to particular IPDCKMSID and IPDCOperatorID, an ESG bootstrap relating to a particular area, and an ESG bootstrap relating to a particular network. An OMA DM mechanism according to a fifth exemplary embodiment of the present invention provides a scheme for indicating the above-described characteristic information together with detailed information on the characteristic information. That is to say, according to the fifth exemplary embodiment of the present invention, detailed information relating to the ESG is included in the MO in order to help proper ESG bootstrap entry point selection by a terminal. By combining all or a part of the detailed information relating to the ESG, it is possible to indicate attributes of the ESG bootstrap entry point. Further, the related detailed information is not limited to the IPDCKMSID, IPDCOperatorID, area parameter, and network information, and may include more information for describing attributes of the ESG bootstrap entry point as application requirements.
Referring to
Further, the NetworkType field 1123 is a node indicating network type-related information, such as satellite, terrestrial network, Digital Video Broadcasting-Satellite (DVB-S), Digital Video Broadcasting-Handheld (DVB-H), DVB-SH, 3rd Generation Partnership Project (3GPP), Wimax, and the like, the NetworkID field 1125 is a node carrying a network ID capable of accessing the ESG, the CellID field 1127 is a node carrying a cell ID capable of accessing the ESG, the AreaParameter field 1129 is a node carrying area-related parameters, such as network ID, cell ID, MCC, MNC, GPS, and nation code, the Ext field 1131 is a node carrying other access range parameters relating to application requirements, the Tuning parameters field 1133 is a node carrying related tuning parameters, and the Ext field 1135 is a node for addition or extension.
As illustrated in
Referring to
By the OMA DM mechanism according to the fifth exemplary embodiment of the present invention as described above, a terminal can select a proper ESG bootstrap entry point based on detailed information relating to each ESG bootstrap entry point. The detailed information described above is optional and can be selected by the network or the terminal according to the requirements.
In a mobility scenario, proper management targets include main parameters of the roaming concept. One proper management range corresponds to the roaming of handover, because subscription and roaming agreement occurs in the roaming of handover.
In the current CBMS, an IPDC operator (more specifically, an IPDC KMS and IPDC operator) performs subscription and proper management. In the future, the subject performing the subscription and proper management may be changed. However, the concept and mechanisms of exemplary embodiments of the present invention can be applied to a partial modification in which the IPDC KMS system and IPDC operator are replaced by new parameters.
Within a home coverage, the terminal can search for an ESG bootstrap entry point and then access an ESG relating to the IPDC KMS system and IPDC operator ESG. Even when the terminal is located out of the home coverage, the terminal still has the right to access the service, because there is a kind of roaming agreement between the exterior and home IPDC KMS system and the IPDC operator.
Each local IPDCKMSID and IPDCOperatorID may have a roaming partner.
As shown in
When detailed roaming partner information is not indicated, and if entry points for the local and roaming IPDC KMS system and IPDC operator are simultaneously provided, it is possible to use mechanism 1. In this case, a local terminal, whose home operator is, for example, (IPDCKMSID=1 and IPDCOperator=1), can use an entry point for the (IPDCKMSID=1 and IPDCOperator=1). Further, a roaming terminal, whose home operator is, for example, (IPDCKMSID=1 and IPDCOperator=2), can use an entry point for the (IPDCKMSID=1 and IPDCOperator=2). In the case of a local terminal, it is possible to obtain the entry point information from its home DM server. In the case of a roaming terminal, it is possible to obtain its own entry point information from its home DM server. However, when the roaming terminal is located out of the home DM server coverage, the entry point information can be obtained from the local DM server through negotiation between and support by the local DM server and its own roaming DM server. Therefore, according to mechanism 1, an entry point for the local and roaming terminal is provided based on the IPDCKMSID and IPDCOperatorID. There is no indication for the roaming relation information.
Further, mechanisms 2 to 5 relating to mechanism 1 can be used for both the local and roaming terminal in the manner described above.
An entry point for the local and roaming IPDC KMS and IPDC operator may be separated by an indication within the MO.
An OMA DM mechanism according to the sixth exemplary embodiment of the present invention provides a scheme for indicating ESG bootstrap entry points for the roaming terminal by corresponding IPDCKMSID and IPDCOperatorID.
Referring to
By an OMA DM mechanism according to the sixth exemplary embodiment of the present invention as described above, the terminal can obtain an ESG bootstrap entry point for the roaming terminal. By using the ESG bootstrap entry point, the terminal can search for ESGbootstrap information, and select an ESG having an available service for the roaming user.
An OMA DM mechanism according to a seventh exemplary embodiment of the present invention provides a relation between the local and roaming IPDC KMS system and the IPDC operator, together with ESG bootstrap entry point information of each roaming terminal.
A first OMA DM mechanism according to the seventh exemplary embodiment of the present invention provides a scheme for enumerating roaming partners of each local IPDCKMSID and IPDCOperatorID as roamingIPDCKMSID and roamingIPDCOperatorID, and indicating a corresponding ESG bootstrap entry point of each roaming partner.
Referring to
In the first OMA DM mechanism according to the seventh exemplary embodiment of the present invention described above, if the ESG bootstrap entry point has common bootstrap information for both the local and roaming users, the terminal can select an ESG and can find a service usable by itself based on the roaming partner information described in the MO. If the ESG bootstrap entry point has particular bootstrap information for only a particular partner, the terminal can obtain all proper ESG information by using the ESG bootstrap entry point.
Referring to
According to the second OMA DM mechanism according to the seventh exemplary embodiment of the present invention described above, the roaming terminal can search for the IPDCKMSID and IPDCOperatorID of the roaming terminal itself in the RoamingIPDCKMSID and RoamingIPDCOperatorID. When the roaming terminal cannot find its own IPDCKMSID and IPDCOperatorID through the search, the roaming terminal cannot obtain proper information. In contrast, when the roaming terminal can find its own IPDCKMSID and IPDCOperatorID through the search, the terminal can find a roaming find of the roaming terminal in the LocalIPDCKMSID and LocalIPDCOperatorID, and indicates the ESG bootstrap entry point also.
An OMA DM mechanism according to an eighth exemplary embodiment provides a scheme of additionally providing roaming partner information based on an OMA DM mechanism according to the fifth exemplary embodiment of the present invention.
A first OMA DM mechanism according to the eighth exemplary embodiment is based on the first OMA DM mechanism according to the fifth exemplary embodiment of the present invention.
Referring to
Based on the OMA DM illustrated in
Table 7 below shows the above-mentioned node <x>/IPDC/ in more detail.
Table 8 shows the above-mentioned node <x>/IPDC/ESG/ in more detail.
Table 9 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/ in more detail.
Table 10 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x> in more detail.
Table 11 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/ESGBootstrapEntryPointURL/ in more detail.
Table 12 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/IPPlatform/ in more detail.
Table 13 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/ESGProviderURI/ in more detail.
Table 14 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/ESGURI/ in more detail.
Table 15 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/ESGURI/IPDCKMSID/ in more detail.
Table 16 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/ESGURI/IPDCKMSID/IPDCOperatorID/ in more detail.
Table 17 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/ESGURI/IPDCKMSID/IPDCOperator ID/RoamingPartner/ in more detail.
Table 18 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/ESGURI/IPDCKMSID/IPDCOperator ID/RoamingPartner/<x> in more detail.
Table 19 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/ESGURI/IPDCKMSID/IPDCOperator ID/RoamingPartner/<x>/RoamingIPDCKMSID/ in more detail.
Table 20 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/ESGURI/IPDCKMSID/IPDCOperator ID/RoamingPartner/<x>/RoamingIPDCKMSID/RoamingIPDCOperatorID/ in more detail.
Table 21 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/ESGURI/NetworkType/ in more detail.
Table 22 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/ESGURI/NetworkID/ in more detail.
Table 23 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/ESGURI/NetworkID/CellID/ in more detail.
Table 24 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/ESGURI/AreaParameter/ in more detail.
Table 25 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/ESGURI/Ext/ in more detail.
Table 26 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/Ext/ in more detail.
Based on the OMA DM illustrated in
Table 28 shows the above-mentioned node <x>/IPDC/ in more detail.
Table 29 shows the above-mentioned node <x>/IPDC/ESG/ in more detail.
Table 30 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/ in more detail.
Table 31 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x> in more detail.
Table 32 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/ESGBootstrapEntryPointURL/ in more detail.
Table 33 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/IPPlatform/ in more detail.
Table 34 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/ESGProviderURI/ in more detail.
Table 35 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/ESGURI/ in more detail.
Table 36 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/IPDCKMSID/ in more detail.
Table 37 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/IPDCKMSID/IPDCOperatorID/ in more detail.
Table 38 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/IPDCKMSID/IPDCOperatorID/RoamingPartner/ in more detail.
Table 39 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/IPDCKMSID/IPDCOperatorID/RoamingPartner/<x> in more detail.
Table 40 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/IPDCKMSID/IPDCOperatorID/RoamingPartner/<x>/RoamingIPDCKMSID/ in more detail.
Table 41 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/IPDCKMSID/IPDCOperatorID/RoamingPartner/<x>/RoamingIPDCKMSID/RoamingIPDCOperatorID/ in more detail.
Table 42 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/NetworkType/ in more detail.
Table 43 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/NetworkID/ in more detail.
Table 44 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/NetworkID/CellID/ in more detail.
Table 45 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/AreaParameter/ in more detail.
Table 46 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/Ext/ in more detail.
A second OMA DM mechanism according to the eighth exemplary embodiment is based on the second OMA DM mechanism according to the fifth exemplary embodiment of the present invention.
Referring to
Table 47 below shows the above-mentioned node <x> in more detail.
Table 48 shows the above-mentioned node <x>/IPDC/ in more detail.
Table 49 shows the above-mentioned node <x>/IPDC/ESG/ in more detail.
Table 50 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/ in more detail.
Table 51 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x> in more detail.
Table 52 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/GeneralESGEntryPoint/ in more detail.
Table 53 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/GeneralESGBootstrapEntryPoint/<x> in more detail.
Table 54 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/GeneralESGEntryPoint/<x>/GenESGBootstrapEntryPointURL/ in more detail.
Table 55 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/IPDCESGEntryPoint/ in more detail.
Table 56 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/IPDCESGBootstrapEntryPoint/<x> in more detail.
Table 57 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/IPDCESGEntryPoint/<x>/IPDCKMSID/ in more detail.
Table 58 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/IPDCESGEntryPoint/<x>/IPDCKMSID/IPDCOperatorID/ in more detail.
Table 59 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/IPDCESGEntryPoint/<x>/IPDCKMSID/IPDCOperatorID/IPDCESGEntryPointURL/ in more detail.
Table 60 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/AreaESGEntryPoint/ in more detail.
Table 61 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/AreaESGEntryPoint/<x> in more detail.
Table 62 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/AreaESGEntryPoint/<x>/AreaParameter/ in more detail.
Table 63 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/AreaESGEntryPoint/<x>/AreaParameter/AreaESGBootstrapEntryPointURL/ in more detail.
Table 64 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/NetworkESGEntryPoint/ in more detail.
Table 65 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/NetworkESGEntryPoint/<x> in more detail.
Table 66 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/NetworkESGEntryPoint/<x>/NetworkInfo/ in more detail.
Table 67 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/NetworkESGEntryPoint/<x>/NetworkInfo/NetworkESGBootstrapEntryPointURL/ in more detail.
Table 68 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/ProviderESGEntryPoint/ in more detail.
Table 69 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/ProviderESGEntryPoint/<x> in more detail.
Table 70 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/ProviderESGEntryPoint/<x>/ESGProviderURI/ in more detail.
Table 71 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/ProviderESGEntryPoint/<x>/ESGProviderURI/ProviderESGBootstrapEntryPointURL/ in more detail.
Table 72 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/ESGIdenESGEntryPoint/ in more detail.
Table 73 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/ESGIdenESGEntryPoint/<x> in more detail.
Table 74 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/ESGIdenESGEntryPoint/<x>/ESGURI/ in more detail.
Table 75 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/ESGIdenESGEntryPoint/<x>/ESGURI/ESGIdenESGBootstrapEntryPointURL/ in more detail.
Table 76 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/PlatformESGEntryPoint/ in more detail.
Table 77 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/PlatformESGEntryPoint/<x> in more detail.
Table 78 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/PlatformESGEntryPoint/<x>/IPPlatformID/ in more detail.
Table 79 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/PlatformESGEntryPoint/<x>/IPPlatformID/PlatformESGBootstrapEntryPointURL/ in more detail.
Table 80 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/RoamingESGEntryPoint/ in more detail.
Table 81 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/RoamingESGEntryPoint/<x>in more detail.
Table 82 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/RoamingESGEntryPoint/<x>/RoamingIPDCKMSID/ in more detail.
Table 83 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/RoamingESGEntryPoint/<x>/RoamingIPDCKMSID/Roaming IPDCOperatorID/ in more detail.
Table 84 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/RoamingESGEntryPoint/<x>/RoamingIPDCKMSID/RoamingIPDCOperatorID/ESGBootstrapEntryPointURL/ in more detail.
Table 85 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/KMSESGEntryPoint/ in more detail.
Table 86 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/KMSESGEntryPoint/<x> in more detail.
Table 87 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/KMSESGEntryPoint/<x>/IPDCKMSID/ in more detail.
Table 88 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/KMSESGEntryPoint/<x>/IPDCKMSID/KMSESGBootstrapEntryPointURL/ in more detail.
Table 89 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/tuning parameters/ in more detail.
Table 90 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/Ext/ in more detail.
Referring to
Table 91 below shows the above-mentioned node <x> in more detail.
Table 92 below shows the above-mentioned node <x>/IPDC/ in more detail.
Table 93 shows the above-mentioned node <x>/IPDC/ESG/ in more detail.
Table 94 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/ in more detail.
Table 95 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x> in more detail.
Table 96 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/GeneralESGEntryPoint/ in more detail.
Table 97 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/GeneralESGBootstrapEntryPoint/<x> in more detail.
Table 98 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/GeneralESGEntryPoint/<x>/GenESGBootstrapEntryPointURL/ in more detail.
Table 99 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/IPDCESGEntryPoint/ in more detail.
Table 100 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/IPDCESGBootstrapEntryPoint/<x> in more detail.
Table 101 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/IPDCESGEntryPoint/<x>/IPDCKMSID/ in more detail.
Table 102 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/IPDCESGEntryPoint/<x>/IPDCKMSID/IPDCOperatorID/ in more detail.
Table 103 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/IPDCESGEntryPoint/<x>/IPDCKMSID/IPDCOperatorID/IPDCESGEntryPointURL/ in more detail.
Table 104 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/AreaESGEntryPoint/ in more detail.
Table 105 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/AreaESGEntryPoint/<x> in more detail.
Table 106 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/AreaESGEntryPoint/<x>/AreaParameter/ in more detail.
Table 107 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/AreaESGEntryPoint/<x>/AreaParameter/AreaESGBootstrapEntryPointURL/ in more detail.
Table 108 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/NetworkESGEntryPoint/ in more detail.
Table 109 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/NetworkESGEntryPoint/<x> in more detail.
Table 110 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/NetworkESGEntryPoint/<x>/NetworkInfo/ in more detail.
Table 111 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/NetworkESGEntryPoint/<x>/NetworkInfo/NetworkESGBootstrapEntryPointURL/ in more detail.
Table 112 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/ProviderESGEntryPoint/ in more detail.
Table 113 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/ProviderESGEntryPoint/<x> in more detail.
Table 114 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/ProviderESGEntryPoint/<x>/ESGProviderURI/ in more detail.
Table 115 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/ProviderESGEntryPoint/<x>/ESGProviderURI/ProviderESGBootstrapEntryPointURL/ in more detail.
Table 116 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/ESGIdenESGEntryPoint/ in more detail.
Table 117 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/ESGIdenESGEntryPoint/<x> in more detail.
Table 118 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/ESGIdenESGEntryPoint/<x>/ESGURI/ in more detail.
Table 119 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/ESGIdenESGEntryPoint/<x>/ESGURI/ESGIdenESGBootstrapEntryPointURL/ in more detail.
Table 120 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/PlatformESGEntryPoint/ in more detail.
Table 121 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/PlatformESGEntryPoint/<x> in more detail.
Table 122 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/PlatformESGEntryPoint/<x>/IPPlatformID/ in more detail.
Table 123 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/PlatformESGEntryPoint/<x>/IPPlatformID/PlatformESGBootstrapEntryPointURL/ in more detail.
Table 124 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/RoamingESGEntryPoint/ in more detail.
Table 125 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/RoamingESGEntryPoint/<x> in more detail.
Table 126 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/RoamingESGEntryPoint/<x>/LocalIPDCKMSID/ in more detail.
Table 127 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/RoamingESGEntryPoint/<x>/LocalIPDCKMSID/LocalIPDCOperatorID/ in more detail.
Table 128 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/RoamingESGEntryPoint/<x>/RoamingPartner/ in more detail.
Table 129 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/RoamingESGEntryPoint/<x>/RoamingPartner/<x> in more detail.
Table 130 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/RoamingESGEntryPoint/<x>/RoamingPartner/<x>RoamingIPDCKMSID/ in more detail.
Table 131 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/RoamingESGEntryPoint/<x>/RoamingPartner/<x>RoamingIPDCKMSID/Roaming IPDCOperatorID/ in more detail.
Table 132 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/RoamingESGEntryPoint/<x>/RoamingPartner/<x>RoamingESGBootstrapEntryPointURL in more detail.
Table 133 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/KMSESGEntryPoint/ in more detail.
Table 134 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/KMSESGEntryPoint/<x> in more detail.
Table 135 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/KMSESGEntryPoint/<x>/IPDCKMSID/in more detail.
Table 136 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/KMSESGEntryPoint/<x>/IPDCKMSID/KMSESGBootstrapEntryPointURL/ in more detail.
Table 137 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/tuning parameters in more detail.
Table 138 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/Ext/ in more detail.
Referring to
Table 139 below shows the above-mentioned node <x> in more detail.
Table 140 below shows the above-mentioned node <x>/IPDC/ in more detail.
Table 141 below shows the above-mentioned node <x>/IPDC/ESG/ in more detail.
Table 142 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/ in more detail.
Table 143 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/ in more detail.
Table 144 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/GeneralESGEntryPoint/ in more detail.
Table 145 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/GeneralESGBootstrapEntryPoint/<x> in more detail.
Table 146 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/GeneralESGEntryPoint/<x>/GenESGBootstrapEntryPointURL/ in more detail.
Table 147 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/IPDCESGEntryPoint/ in more detail.
Table 148 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/IPDCESGBootstrapEntryPoint/<x> in more detail.
Table 149 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/IPDCESGEntryPoint/<x>/IPDCKMSID/ in more detail.
Table 150 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/IPDCESGEntryPoint/<x>/IPDCKMSID/IPDCOperatorID/ in more detail.
Table 151 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/IPDCESGEntryPoint/<x>/IPDCKMSID/IPDCOperatorID/IPDCESGEntryPointURL/ in more detail.
Table 152 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/AreaESGEntryPoint/ in more detail.
Table 153 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/AreaESGEntryPoint/<x> in more detail.
Table 154 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/AreaESGEntryPoint/<x>/AreaParameter/ in more detail.
Table 155 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/AreaESGEntryPoint/<x>/AreaParameter/AreaESGBootstrapEntryPointURL/ in more detail.
Table 156 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/NetworkESGEntryPoint/ in more detail.
Table 157 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/NetworkESGEntryPoint/<x> in more detail.
Table 158 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/NetworkESGEntryPoint/<x>/NetworkInfo/ in more detail.
Table 159 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/NetworkESGEntryPoint/<x>/NetworkInfo/NetworkESGBootstrapEntryPointURL/ in more detail.
Table 160 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/ProviderESGEntryPoint/ in more detail.
Table 161 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/ProviderESGEntryPoint/<x> in more detail.
Table 162 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/ProviderESGEntryPoint/<x>/ESGProviderURI/ in more detail.
Table 163 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/ProviderESGEntryPoint/<x>/ESGProviderURI/ProviderESGBootstrapEntryPointURL/ in more detail.
Table 164 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/ESGIdenESGEntryPoint/ in more detail.
Table 165 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/ESGIdenESGEntryPoint/<x> in more detail.
Table 166 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/ESGIdenESGEntryPoint/<x>/ESGURI/ in more detail.
Table 167 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/ESGIdenESGEntryPoint/<x>/ESGURI/ESGIdenESGBootstrapEntryPointURL/ in more detail.
Table 168 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/PlatformESGEntryPoint/ in more detail.
Table 169 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/PlatformESGEntryPoint/<x> in more detail.
Table 170 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/PlatformESGEntryPoint/<x>/IPPlatformID/ in more detail.
Table 171 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/PlatformESGEntryPoint/<x>/IPPlatformID/PlatformESGBootstrapEntryPointURL/ in more detail.
Table 172 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/RoamingESGEntryPoint/ in more detail.
Table 173 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/RoamingESGEntryPoint/<x> in more detail.
Table 174 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/RoamingESGEntryPoint/<x>/RoamingIPDCKMSID/ in more detail.
Table 175 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/RoamingESGEntryPoint/<x>/RoamingIPDCKMSID/LocalIPDCOperatorID/ in more detail.
Table 176 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/RoamingESGEntryPoint/<x>/RoamingPartner/ in more detail.
Table 177 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/RoamingESGEntryPoint/<x>/RoamingPartner/<x> in more detail.
Table 178 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/RoamingESGEntryPoint/<x>/RoamingPartner/<x>LocalIPDCKMSID/ in more detail.
Table 179 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/RoamingESGEntryPoint/<x>/RoamingPartner/<x>LocalIPDCKMSID/LocalIPDCOperatorID/ in more detail.
Table 180 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/RoamingESGEntryPoint/<x>/RoamingPartner/<x>RoamingESGBootstrapEntryPointURL/ in more detail.
Table 181 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/KMSESGEntryPoint/ in more detail.
Table 182 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/KMSESGEntryPoint/<x> in more detail.
Table 183 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/KMSESGEntryPoint/<x>/IPDCKMSID/ in more detail.
Table 184 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/KMSESGEntryPoint/<x>/IPDCKMSID/KMSESGBootstrapEntryPointURL/ in more detail.
Table 185 below shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/tuning parameters/ in more detail.
Table 186 shows the above-mentioned node <x>/IPDC/ESG/ESGBootstrapEntryPoint/<x>/Ext in more detail.
Referring to
Table 187 below shows the above-mentioned node <x> in more detail.
Table 188 shows the above-mentioned node <x>/IPDC/ in more detail.
Table 189 shows the above-mentioned node <x>/IPDC/<x> in more detail.
Table 190 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/ in more detail.
Table 191 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x> in more detail.
Table 192 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/ESGBootstrapEntryPointURL/ in more detail.
Table 193 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/ in more detail.
Table 194 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/EntryPointAttri/<x> in more detail.
Table 195 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/EntryPointAttri/<x>/Operator/ in more detail.
Table 196 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/EntryPointAttri/<x>/Operator/<x> in more detail.
Table 197 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/Operator/<x>/LocalIPDCKMSID/ in more detail.
Table 198 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/Operator/<x>/LocalIPDCKMSID/LocalIPDCOperatorID/ in more detail.
Table 199 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/EntryPointAttri/<x>/Operator/<x>RoamingPartner/ in more detail.
Table 200 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/EntryPointAttri/<x>/Operator/<x>RoamingPartner/<x> in more detail.
Table 201 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/EntryPointAttri/<x>/Operator/<x>RoamingPartner/<x>/RoamingIPDCKMSID/ in more detail.
Table 202 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/Operator/<x>/LocalIPDCKMSID/LocalIPDCOperatorID/ in more detail.
Table 203 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/IPPlatform/ in more detail.
Table 204 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/IPPlatform/<x> in more detail.
Table 205 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/IPPlatformID/ in more detail.
Table 206 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESGProvider/ in more detail.
Table 207 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESGProvider/<x> in more detail.
Table 208 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESGProvider/<x>/ESGProviderURI/ in more detail.
Table 209 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESG/ in more detail.
Table 210 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESG/<x> in more detail.
Table 211 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESG/<x>/ESGURI/ in more detail.
Table 212 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/AreaParameters/ in more detail.
Table 213 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/AreaParameters/<x> in more detail.
Table 214 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/AreaParameters/<x>/AreaParameter/ in more detail.
Table 215 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/NetworkInfos/ in more detail.
Table 216 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/NetworkInfos/<x> in more detail.
Table 217 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/NetworkInfos/<x>/NetworkInfo/ in more detail.
Table 218 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/Tuningparameters/ in more detail.
Table 219 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/Tuningparameters/<x> in more detail.
Table 220 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/Tuningparameters/<x>/Tuningparameter/ in more detail.
Table 221 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/Ext/ in more detail.
Table 222 below shows the above-mentioned node <x>/IPDC/<x>/Ext in more detail.
The fifth OMA DM mechanism according to the eighth exemplary embodiment of the present invention provides characteristics of each ESG bootstrap entry point. Therefore, a local terminal may select an ESG bootstrap entry point for a home operator, and a roaming terminal may receive the MO information from a home DM server or a local DM server. Further, the terminal may search for home operator information from the RoamingIPDCKMSID and RoamingIPDCOperatorID. If the terminal finds the home operator information, a related entry point has bootstrap information for the terminal.
The 6.1st OMA DM mechanism according to the eighth exemplary embodiment of the present invention relates to one ESG bootstrap for an IP platform, in view of the above-described exemplary embodiments. That is, the 6.1st OMA DM mechanism according to the eighth embodiment of the present invention as illustrated in
In
In the 6.2nd OMA DM mechanism according to the eighth exemplary embodiment of the present invention, an ESG bootstrap entry point for each IPDC operator is provided. That is, in the 6.2nd OMA DM mechanism according to the eighth exemplary embodiment of the present invention as illustrated in
In
In the 6.3rd OMA DM mechanism according to the eighth exemplary embodiment of the present invention, each IP platform provides an ESG bootstrap entry point for each IPDC operator. That is, in the 6.3rd OMA DM mechanism according to the eighth exemplary embodiment of the present invention as shown in
In
Hereinafter, operations of a DM server and a terminal according to the eighth exemplary embodiment of the present invention will be described with reference to
Referring to
Referring to
After receiving the ESG bootstrap entry point information, the terminal may search for an entry point expected according to requirements for a desired bootstrap as illustrated in
That is, in step 2607, if the terminal wants a typical bootstrap, the terminal determines a typical ESG bootstrap entry point in the MO. Then, the terminal selects a typical ESG bootstrap entry point from the determined ESG bootstrap entry point in step 2609, and requests ESG bootstrap information from the selected ESG bootstrap entry point in step 2611. Then, in step 2613, the terminal receives the requested ESG bootstrap information and selects an ESG.
Meanwhile, in step 2615, if the terminal wants a bootstrap relating to the IPDC KMS and IPDC operator of the terminal, the terminal determines an ESG bootstrap entry point for the IPDC KMS and IPDC operator of the terminal in the MO. Then, the terminal selects the ESG bootstrap entry point for the IPDC KMS and IPDC operator of the terminal through the determined ESG bootstrap entry point in step 2617, and requests ESG bootstrap information from the selected ESG bootstrap entry point in step 2619. Then, in step 2621, the terminal receives the requested ESG bootstrap information and selects an ESG.
In step 2623, if the terminal wants a bootstrap at the location of the terminal, the terminal determines an ESG bootstrap entry point for an area in the MO. Then, the terminal selects the ESG bootstrap entry point for the area through the determined ESG bootstrap entry point in step 2625, and requests ESG bootstrap information from the selected ESG bootstrap entry point in step 2627. Then, in step 2629, the terminal receives the requested ESG bootstrap information and selects an ESG.
In step 2631, if the terminal wants a bootstrap through a network, the terminal determines an ESG bootstrap entry point for the network of the terminal in the MO. Then, the terminal selects the ESG bootstrap entry point based on the determined ESG bootstrap entry point in step 2633, and requests ESG bootstrap information from the selected ESG bootstrap entry point in step 2635. Then, in step 2637, the terminal receives the requested ESG bootstrap information and selects an ESG.
In step 2639, if the terminal wants a bootstrap relating to an ESG, the terminal determines an ESG bootstrap entry point for ESGURI in the MO. Then, the terminal selects the ESG bootstrap entry point through the determined ESG bootstrap entry point in step 2641, and requests ESG bootstrap information from the selected ESG bootstrap entry point in step 2643. Then, in step 2645, the terminal receives the requested ESG bootstrap information and selects an ESG.
In step 2647, if a roaming terminal wants a bootstrap appropriate for a roaming user, the terminal determines an ESG bootstrap entry point for the roaming user in the MO. Then, the terminal selects the ESG bootstrap entry point for the roaming user through the determined ESG bootstrap entry point in step 2649, and requests ESG bootstrap information from the selected ESG bootstrap entry point in step 2651. Then, in step 2653, the terminal receives the requested ESG bootstrap information and selects an ESG.
In step 2655, the terminal selects a service to be accessed through the selected ESG, and accesses or subscribes to the selected service.
An OMA DM mechanism according to a ninth exemplary embodiment of the present invention provides each home (local) terminal with a scheme for preliminarily providing information on a roaming partner of a roaming terminal (itself) in an outer network. When an ESG bootstrap entry point is known, a server can preliminarily provide information on a roaming partner of a roaming terminal. At this time, the terminal has a large amount of roaming information in advance in a home network of the terminal, and uses the roaming information when it moves to an outer area.
Referring to
Table 223 below shows the above-mentioned node <x> in more detail.
Table 224 shows the above-mentioned node <x>/IPDC/ in more detail.
Table 225 shows the above-mentioned node <x>/IPDC/<x> in more detail.
Table 226 below shows the above-mentioned node <x>/IPDC/<x>/LocalIPDCKMSID/ in more detail.
Table 227 below shows the above-mentioned node <x>/IPDC/<x>/LocalIPDCKMSID/LocalIPDCOperatorID/ in more detail.
Table 228 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/ in more detail.
Table 229 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x> in more detail.
Table 230 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/OutsideRoamingIPDCKMSID/ in more detail.
Table 231 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/OutsideRoamingIPDCKMSID/OutsideRoaming IPDCOperatorID/ in more detail.
Table 232 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESG/ in more detail.
Table 233 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESG/ESGBootstrapEntryPointURL/ in more detail.
A second OMA DM mechanism according to the ninth exemplary embodiment of the present invention provides a scheme capable of indicating more detailed information on an outer coverage.
Referring to
Table 234 shows the above-mentioned node <x> in more detail.
Table 235 shows the above-mentioned node <x>/IPDC/ in more detail.
Table 236 below shows the above-mentioned node <x>/IPDC/<x> in more detail.
Table 237 below shows the above-mentioned node <x>/IPDC/<x>/LocalIPDCKMSID/ in more detail.
Table 238 below shows the above-mentioned node <x>/IPDC/<x>/LocalIPDCKMSID/LocalIPDCOperatorID/ in more detail.
Table 239 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/ in more detail.
Table 240 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x> in more detail.
Table 241 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/OutsideRoamingIPDCKMSID/ in more detail.
Table 242 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/OutsideRoamingIPDCKMSID/OutsideRoaming IPDCOperatorID/ in more detail.
Table 243 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESG/ in more detail.
Table 244 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESG/ESGBootstrapEntryPointURL/ in more detail.
Table 245 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/AreaParameter/ in more detail.
Table 246 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/NetworkInfo/ in more detail.
Table 247 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGProviderURI/ in more detail.
Table 248 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGURI/ in more detail.
Table 249 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/IPPlatformID/ in more detail.
Table 250 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/Tuningparameter/ in more detail.
Table 251 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/Ext/ in more detail.
In the second OMA DM mechanism according to the ninth exemplary embodiment of the present invention as described above, since a roaming partner for each local IPDC KMS and IPDC operator is provided to the terminal, the terminal can find a proper ESG having a roaming partner of the terminal when the terminal roams in an outer network and accesses outer bootstrap-related information. If a bootstrap entry point in a roaming situation is also provided, the terminal can request bootstrap information by using the entry point at the time of roaming. If a roaming ESG is provided, the terminal can find a roaming ESG in the roaming situation. As presented in the above Tables, if other related information is also provided, the terminal can request a particular entry point based on its roaming partner, location, network type, etc.
Referring to
Table 252 shows the above-mentioned node <x> in more detail.
Table 253 below shows the above-mentioned node <x>/IPDC/ in more detail.
Table 254 shows the above-mentioned node <x>/IPDC/<x> in more detail.
Table 255 shows the above-mentioned node <x>/IPDC/<x>/LocalIPDCKMSID/ in more detail.
Table 256 below shows the above-mentioned node <x>/IPDC/<x>/LocalIPDCKMSID/LocalIPDCOperatorID/ in more detail.
Table 257 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/ in more detail.
Table 258 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x> in more detail.
Table 259 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/OutsideRoamingIPDCKMSID/ in more detail.
Table 260 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/OutsideRoamingIPDCKMSID/OutsideRoaming IPDCOperatorID/ in more detail.
Table 261 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/ in more detail.
Table 262 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x> in more detail.
Table 263 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/ESGBootstrapEntryPointURL in more detail.
Table 264 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/ in more detail.
Table 265 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x> in more detail.
Table 266 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/IPPlatform/ in more detail.
Table 267 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/IPPlatform/<x>/ in more detail.
Table 268 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/IPPlatform/<x>/IPPlatformID/ in more detail.
Table 269 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESGProvider/ in more detail.
Table 270 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESGProvider/<x> in more detail.
Table 271 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESGProvider/<x>/ESGProviderURI/ in more detail.
Table 272 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESG/ in more detail.
Table 273 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESG/<x> in more detail.
Table 274 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESG/<x>/ESGURI/ in more detail.
Table 275 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/AreaParameters/ in more detail.
Table 276 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/AreaParameters/<x> in more detail.
Table 277 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/AreaParameters/<x>/AreaParameter/ in more detail.
Table 278 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/NetworkInfos/ in more detail.
Table 279 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/NetworkInfos/<x> in more detail.
Table 280 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/NetworkInfos/<x>/NetworkInfo in more detail.
Table 281 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/Tuningparameters/ in more detail.
Table 282 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/Tuningparameters/<x> in more detail.
Table 283 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/Tuningparameters/<x>/Tuningparameter/ in more detail.
Table 284 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/Ext/ in more detail.
Table 285 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/Ext/ in more detail.
Referring to
Table 286 below shows the above-mentioned node <x> in more detail.
Table 287 below shows the above-mentioned node <x>/IPDC/ in more detail.
Table 288 below shows the above-mentioned node <x>/IPDC/<x> in more detail.
Table 289 shows the above-mentioned node <x>/IPDC/<x>/LocalIPDCKMSID/ in more detail.
Table 290 below shows the above-mentioned node <x>/IPDC/<x>/LocalIPDCKMSID/LocalIPDCOperatorID/ in more detail.
Table 291 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/ in more detail.
Table 292 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x> in more detail.
Table 293 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/ in more detail.
Table 294 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x> in more detail.
Table 295 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/ESGBootstrapEntryPointURL/ in more detail.
Table 296 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/ in more detail.
Table 297 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x> in more detail.
Table 298 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/Operator/ in more detail.
Table 299 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/Operator/<x> in more detail.
Table 300 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/Operator/<x>/OutsideRoamingIPDCKMSID/ in more detail.
Table 301 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/Operator/<x>/OutsideRoamingIPDCKMSID/OutsideRoaming IPDCOperatorID in more detail.
Table 302 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/IPPlatform/ in more detail.
Table 303 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/IPPlatform/<x> in more detail.
Table 304 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/IPPlatform/<x>/IPPlatformID in more detail.
Table 305 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESGProvider/ in more detail.
Table 306 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESGProvider/<x> in more detail.
Table 307 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESGProvider/<x>/ESGProviderURI/ in more detail.
Table 308 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESG/ in more detail.
Table 309 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESG/<x> in more detail.
Table 310 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESG/<x>/ESGURI in more detail.
Table 311 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/AreaParameters/ in more detail.
Table 312 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/AreaParameters/<x> in more detail.
Table 313 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/AreaParameters/<x>/AreaParameter/ in more detail.
Table 314 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/NetworkInfos/ in more detail.
Table 315 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/NetworkInfos/<x> in more detail.
Table 316 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/NetworkInfos/<x>/NetworkInfo/ in more detail.
Table 317 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/Tuningparameters/ in more detail.
Table 318 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/Tuningparameters/<x> in more detail.
Table 319 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/Tuningparameter s/<x>/Tuningparameter in more detail.
Table 320 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/Ext/ in more detail.
Table 321 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/Ext/ in more detail.
A fifth OMA DM mechanism according to the ninth exemplary embodiment of the present invention may provide an ESG entry point for a local IPDC operator. The fifth OMA DM mechanism according to the ninth exemplary embodiment of the present invention is based on an MO for a local IPDC operator similarly to the third exemplary embodiment of the present invention.
Referring to
Table 322 shows the above-mentioned node <x> in more detail.
Table 323 below shows the above-mentioned node <x>/IPDC/ in more detail.
Table 324 shows the above-mentioned node <x>/IPDC/<x> in more detail.
Table 325 shows the above-mentioned node <x>/IPDC/<x>/LocalIPDCKMSID/ in more detail.
Table 326 below shows the above-mentioned node <x>/IPDC/<x>/LocalIPDCKMSID/LocalIPDCOperatorID/ in more detail.
Table 327 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/ in more detail.
Table 328 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x> in more detail.
Table 329 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/ESGBootstrapEntryPointURL in more detail.
Table 330 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/ in more detail.
Table 331 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x> in more detail.
Table 332 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/IPPlatform/ in more detail.
Table 333 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/IPPlatform/<x> in more detail.
Table 334 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/IPPlatform/<x>/IPPlatformID/ in more detail.
Table 335 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESGProvider/ in more detail.
Table 336 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESGProvider/<x> in more detail.
Table 337 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESGProvider/<x>/ESGProviderURI/ in more detail.
Table 338 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESG/ in more detail.
Table 339 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESG/<x> in more detail.
Table 340 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESG/<x>/ESGURI/ in more detail.
Table 341 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/AreaParameters/ in more detail.
Table 342 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/AreaParameters/<x> in more detail.
Table 343 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/AreaParameters/<x>/AreaParameter/ in more detail.
Table 344 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/NetworkInfos/ in more detail.
Table 345 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/NetworkInfos/<x> in more detail.
Table 346 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/NetworkInfos/<x>/NetworkInfo/ in more detail.
Table 347 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/Tuningparameters/ in more detail.
Table 348 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/Tuningparameters/<x> in more detail.
Table 349 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/Tuningparameters/<x>/Tuningparameter/ in more detail.
Table 350 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/Ext in more detail.
Table 351 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/Ext in more detail.
A sixth OMA DM mechanism according to the ninth exemplary embodiment of the present invention provides an ESG entry point for a local IPDC operator in a similar way to that of the third or fourth OMA DM mechanism according to the ninth exemplary embodiment of the present invention.
Referring to
Table 352 shows the above-mentioned node <x> in more detail.
Table 353 below shows the above-mentioned node <x>/IPDC/ in more detail.
Table 354 shows the above-mentioned node <x>/IPDC/<x> in more detail.
Table 355 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/ in more detail.
Table 356 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x> in more detail.
Table 357 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/ESGBootstrapEntryPointURL in more detail.
Table 358 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/ in more detail.
Table 359 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/EntryPointAttri/<x> in more detail.
Table 360 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/EntryPointAttri/<x>/Operator/ in more detail.
Table 361 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/EntryPointAttri/<x>/Operator/<x> in more detail.
Table 362 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/Operator/<x>/IPDCKMSID/ in more detail.
Table 363 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/Operator/<x>/IPDCKMSID/IPDCOperatorID/ in more detail.
Table 364 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/IPPlatform/ in more detail.
Table 365 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/IPPlatform/<x> in more detail.
Table 366 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/IPPlatformID/ in more detail.
Table 367 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESGProvider/ in more detail.
Table 368 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESGProvider/<x> in more detail.
Table 369 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESGProvider/<x>/ESGProviderURI/ in more detail.
Table 370 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESG/ in more detail.
Table 371 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESG/<x> in more detail.
Table 372 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESG/<x>/ESGURI/ in more detail.
Table 373 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/AreaParameters/ in more detail.
Table 374 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/AreaParameters/<x> in more detail.
Table 375 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/AreaParameters/<x>/AreaParameter/ in more detail.
Table 376 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/NetworkInfos/ in more detail.
Table 377 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/NetworkInfos/<x> in more detail.
Table 378 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/NetworkInfos/<x>/NetworkInfo/ in more detail.
Table 379 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/Tuningparameters/ in more detail.
Table 380 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/Tuningparameters/<x> in more detail.
Table 381 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/Tuningparameters/<x>/Tuningparameter/ in more detail.
Table 382 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/Ext/ in more detail.
Table 383 below shows the above-mentioned node <x>/IPDC/<x>/Ext/ in more detail.
A seventh OMA DM mechanism according to the ninth exemplary embodiment of the present invention corresponds to a combination of the third OMA DM mechanism and the fifth OMA DM mechanism according to the ninth exemplary embodiment of the present invention or the fourth OMA DM mechanism and the fifth OMA DM mechanism according to the ninth exemplary embodiment of the present invention.
Referring to
The RoamingPartnerOutside field 3359 is a node carrying roaming partner-related information for the local IPDC KMS system and IPDC operator in an area out of the home coverage area, the OutsideRoamingIPDCKMSID field 3363 is a node carrying a roaming IPDC KMS system having an IPDCKMSID for a local terminal and indicates the IPDC KMS system having made a roaming agreement with the home (local) IPDC KMS system and operator, the OutsideRoamingIPDCOperatorID field 3365 is a node carrying a roaming IPDC operator having an IPDCOperatorID for a local terminal and indicates the IPDC operator having made a roaming agreement with the home (local) IPDC operator, the ESGBootstrapEntryPointout field 3367 is a node carrying ESG bootstrap entry point-related information, the ESGBootstrapEntryPointoutURL field 3371 is a node indicating an entry point URL for requiring ESG bootstrap information through and interactive network.
Table 384 shows the above-mentioned node <x> in more detail.
Table 385 shows the above-mentioned node <x>/IPDC/ in more detail.
Table 386 below shows the above-mentioned node <x>/IPDC/<x> in more detail.
Table 387 below shows the above-mentioned node <x>/IPDC/<x>/LocalIPDCKMSID/ in more detail.
Table 388 below shows the above-mentioned node <x>/IPDC/<x>/LocalIPDCKMSID/LocalIPDCOperatorID/ in more detail.
Table 389 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/ in more detail.
Table 390 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x> in more detail.
Table 391 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/ESGBootstrapEntryPointURL/ in more detail.
Table 392 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/ in more detail.
Table 393 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x> in more detail.
Table 394 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/IPPlatform/ in more detail.
Table 395 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/IPPlatform/<x> in more detail.
Table 396 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/IPPlatform/<x>/IPPlatformID/ in more detail.
Table 397 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESGProvider/ in more detail.
Table 398 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESGProvider/<x> in more detail.
Table 399 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESGProvider/<x>/ESGProviderURI/ in more detail.
Table 400 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESG/ in more detail.
Table 401 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESG/<x> in more detail.
Table 402 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESG/<x>/ESGURI/ in more detail.
Table 403 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/AreaParameters/ in more detail.
Table 404 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/AreaParameters/<x> in more detail.
Table 405 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/AreaParameters/<x>/AreaParameter/ in more detail.
Table 406 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/NetworkInfos/ in more detail.
Table 407 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/NetworkInfos/<x> in more detail.
Table 408 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/NetworkInfos/<x>/NetworkInfo/ in more detail.
Table 409 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/Tuningparameters/ in more detail.
Table 410 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/Tuningparameters/<x> in more detail.
Table 411 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/Tuningparameters/<x>/Tuningparameter/ in more detail.
Table 412 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/Ext/ in more detail.
Table 413 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/Ext/ in more detail.
Table 414 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/ in more detail.
Table 415 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x> in more detail.
Table 416 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/OutsideRoamingIPDCKMSID/ in more detail.
Table 417 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/OutsideRoamingIPDCKMSID/OutsideRoamingIPDCOperatorID/ in more detail.
Table 418 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/ in more detail.
Table 419 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x> in more detail.
Table 420 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/ESGBootstrapEntryPointOutURL/ in more detail.
Table 421 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointOutAttri/ in more detail.
Table 422 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointOutAttri/<x>/ in more detail.
Table 423 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointOutAttri/<x>/IPPlatform/ in more detail.
Table 424 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointOutAttri/<x>/IPPlatform/<x> in more detail.
Table 425 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointOutAttri/<x>/IPPlatform/<x>/IPPlatformID/ in more detail.
Table 426 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointOutAttri/<x>/ESGProvider/ in more detail.
Table 427 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointOutAttri/<x>/ESGProvider/<x> in more detail.
Table 428 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointOutAttri/<x>/ESGProvider/<x>/ESGProviderURI/ in more detail.
Table 429 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointOutAttri/<x>/ESG/ in more detail.
Table 430 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointOutAttri/<x>/ESG/<x> in more detail.
Table 431 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointOutAttri/<x>/ESG/<x>/ESGURI/ in more detail.
Table 432 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointOutAttri/<x>/AreaParameters/ in more detail.
Table 433 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointOutAttri/<x>/AreaParameters/<x> in more detail.
Table 434 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointOutAttri/<x>/AreaParameter s/<x>/AreaParameter/ in more detail.
Table 435 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointOutAttri/<x>/NetworkInfos/ in more detail.
Table 436 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointOutAttri/<x>/NetworkInfos/<x> in more detail.
Table 437 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointOutAttri/<x>/NetworkInfos/<x>/NetworkInfo/ in more detail.
Table 438 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointOutAttri/<x>/Tuningparameters/ in more detail.
Table 439 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointOutAttri/<x>/Tuningparameters/<x> in more detail.
Table 440 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointOutAttri/<x>/Tuningparameters/<x>/Tuningparameter/ in more detail.
Table 441 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointOutAttri/<x>/Ext/ in more detail.
Table 442 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutOutside/<x>/Ext/ in more detail.
An eighth OMA DM mechanism according to the ninth exemplary embodiment of the present invention corresponds to a combination of the fourth OMA DM mechanism and the fifth OMA DM mechanism according to the ninth exemplary embodiment of the present invention.
Referring to
The RoamingPartnerOutside field 3477 is a node carrying roaming partner-related information for the local IPDC KMS system and IPDC operator in an area out of the home coverage, the ESGBootstrapEntryPointout field 3481 is a node carrying ESG bootstrap entry point-related information, and the ESGBootstrapEntryPointoutURL field 3485 is a node indicating an entry point URL for requiring ESG bootstrap information through and interactive network.
The Operator field 3491 is a node carrying operator information, the OutsideRoamingIPDCKMSID field 3495 is a node carrying a roaming IPDC KMS system having an IPDCKMSID for a local terminal and indicates the IPDC KMS system having made a roaming agreement with the home (local) IPDC KMS system and operator, and the OutsideRoamingIPDCOperatorID field 3497 is a node carrying a roaming IPDC operator having an IPDCOperatorID for a local terminal and indicates the IPDC operator having made a roaming agreement with the home (local) IPDC operator.
Table 443 below shows the above-mentioned node <x> in more detail.
Table 444 shows the above-mentioned node <x>/IPDC/ in more detail.
Table 445 shows the above-mentioned node <x>/IPDC/<x> in more detail.
Table 446 below shows the above-mentioned node <x>/IPDC/<x>/LocalIPDCKMSID/ in more detail.
Table 447 below shows the above-mentioned node <x>/IPDC/<x>/LocalIPDCKMSID/LocalIPDCOperatorID/ in more detail.
Table 448 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/ in more detail.
Table 449 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x> in more detail.
Table 450 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/ESGBootstrapEntryPointURL/ in more detail.
Table 451 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/ in more detail.
Table 452 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x> in more detail.
Table 453 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/IPPlatform/ in more detail.
Table 454 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/IPPlatform/<x> in more detail.
Table 455 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/IPPlatform/<x>/IPPlatformID/ in more detail.
Table 456 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESGProvider/ in more detail.
Table 457 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESGProvider/<x> in more detail.
Table 458 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESGProvider/<x>/ESGProviderURI/ in more detail.
Table 459 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESG/ in more detail.
Table 460 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESG/<x> in more detail.
Table 461 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESG/<x>/ESGURI/ in more detail.
Table 462 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/AreaParameters/ in more detail.
Table 463 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/AreaParameters/<x> in more detail.
Table 464 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/AreaParameters/<x>/AreaParameter/ in more detail.
Table 465 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/NetworkInfos/ in more detail.
Table 466 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/NetworkInfos/<x> in more detail.
Table 467 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/NetworkInfos/<x>/NetworkInfo/ in more detail.
Table 468 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/Tuningparameters/ in more detail.
Table 469 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/Tuningparameters/<x> in more detail.
Table 470 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/Tuningparameters/<x>/Tuningparameter/ in more detail.
Table 471 below shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/Ext/ in more detail.
Table 472 shows the above-mentioned node <x>/IPDC/<x>/ESGBootstrapEntryPoint/<x>/Ext/ in more detail.
Table 473 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/ in more detail.
Table 474 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x> in more detail.
Table 475 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/ in more detail.
Table 476 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x> in more detail.
Table 477 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/ESGBootstrapEntryPointOutURL/ in more detail.
Table 478 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointOutAttri/ in more detail.
Table 479 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointOutAttri/<x> in more detail.
Table 480 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointOutAttri/<x>/Operator/ in more detail.
Table 481 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointOutAttri/<x>/Operator/<x> in more detail.
Table 482 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointOutAttri/<x>/Operator/<x>/OutsideRoamingIPDCKMSID/ in more detail.
Table 483 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointOutAttri/<x>/Operator/<x>/OutsideRoamingIPDCKMSID/OutsideRoamingIPDCOperatorID/ in more detail.
Table 484 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointOutAttri/<x>/IPPlatform/ in more detail.
Table 485 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointOutAttri/<x>/IPPlatform/<x> in more detail.
Table 486 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointOutAttri/<x>/IPPlatform/<x>/IPPlatformID/ in more detail.
Table 487 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointOutAttri/<x>/ESGProvider/ in more detail.
Table 488 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointOutAttri/<x>/ESGProvider/<x> in more detail.
Table 489 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointOutAttri/<x>/ESGProvider/<x>/ESGProviderURI/ in more detail.
Table 490 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointOutAttri/<x>/ESG/ in more detail.
Table 491 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointOutAttri/<x>/ESG/<x> in more detail.
Table 492 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointAttriOut/<x>/ESG/<x>/ESGURI/ in more detail.
Table 493 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointAttriOut/<x>/AreaParameters/ in more detail.
Table 494 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointAttriOut/<x>/AreaParameters/<x> in more detail.
Table 495 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointAttriOut/<x>/AreaParameters/<x>/AreaParameter/ in more detail.
Table 496 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointOutAttri/<x>/NetworkInfos/ in more detail.
Table 497 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointOutAttri/<x>/NetworkInfos/<x> in more detail.
Table 498 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointOutAttri/<x>/NetworkInfos/<x>/NetworkInfo/ in more detail.
Table 499 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointOutAttri/<x>/Tuningparameters/ in more detail.
Table 500 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointOutAttri/<x>/Tuningparameters/<x> in more detail.
Table 501 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointOutAttri/<x>/Tuningparameter s/<x>/Tuningparameter/ in more detail.
Table 502 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPointOut/<x>/EntryPointAttriOut/<x>/Ext/ in more detail.
Table 503 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/Ext/ in more detail.
Hereinafter, operations of a DM server and a terminal according to the ninth exemplary embodiment of the present invention will be described with reference to
Referring to
Referring to
In step 3607, if an operator wants a proper bootstrap when it moves to another coverage area, the terminal determines a particular ESG bootstrap entry point for a roaming partner in the MO. In step 3609, the terminal selects the ESG bootstrap entry point for the roaming partner. In step 3611, the terminal requests ESG bootstrap information from the selected ESG bootstrap entry point. In step 3613, the terminal receives proper ESG bootstrap information for the roaming situation and selects an ESG. As a result, in step 3615, the terminal selects a service that the terminal will access through the selected ESG.
The OMA DM mechanism according to the first to ninth exemplary embodiments of the present invention as described above provides an ESG bootstrap entry point by using an OMA DM. However, it is also possible to provide an ESG bootstrap entry point in the same manner using an OMA DM. To this end, the “ESGBootstrapEntryPoint” in the first to ninth exemplary embodiments of the present invention can be replaced by “ESGEntryPoint,” and the “ESGBootstrapEntryPointURL” can be replaced by “ESGEntryPointURL.” Further, the terminal can directly request an ESG by using an entry point provided by the OMA DM.
The following description on an OMA DM mechanism according to the tenth exemplary embodiment of the present invention presents an example of an ESG entry point for a roaming partner based on the OMA DM mechanism. Meanwhile, it is also possible to provide an ESG entry point for a local operator in a similar way.
Referring to
Table 504 shows the above-mentioned node <x> in more detail.
Table 505 shows the above-mentioned node <x>/IPDC/ in more detail.
Table 506 below shows the above-mentioned node <x>/IPDC/<x> in more detail.
Table 507 below shows the above-mentioned node <x>/IPDC/<x>/LocalIPDCKMSID/ in more detail.
Table 508 below shows the above-mentioned node <x>/IPDC/<x>/LocalIPDCKMSID/LocalIPDCOperatorID/ in more detail.
Table 509 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/ in more detail.
Table 510 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x> in more detail.
Table 511 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/OutsideRoamingIPDCKMSID/ in more detail.
Table 512 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/OutsideRoamingIPDCKMSID/OutsideRoaming IPDCOperatorID/ in more detail.
Table 513 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGEntryPoint/ in more detail.
Table 514 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x> in more detail.
Table 515 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/ESGEntryPointURL/ in more detail.
Table 516 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/ in more detail.
Table 517 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x> in more detail.
Table 518 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESG/ in more detail.
Table 519 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESG/<x> in more detail.
Table 520 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESG/<x>/ESGURI/ in more detail.
Table 521 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESGProvider/ in more detail.
Table 522 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESGProvider/<x> in more detail.
Table 523 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/ESGProvider/<x>/ESGProviderURI/ in more detail.
Table 524 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/AreaParameters/ in more detail.
Table 525 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/AreaParameters/<x> in more detail.
Table 526 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/AreaParameters/<x>/AreaParameter/ in more detail.
Table 527 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/NetworkInfos/ in more detail.
Table 528 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/NetworkInfos/<x> in more detail.
Table 529 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/NetworkInfos/<x>/NetworkInfo/ in more detail.
Table 530 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/IPPlatform/ in more detail.
Table 531 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/IPPlatform/<x> in more detail.
Table 532 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/IPPlatform/<x>/IPPlatformID/ in more detail.
Table 533 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/Tuningparameters/ in more detail.
Table 534 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/Tuningparameters/<x> in more detail.
Table 535 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/Tuningparameter/<x>/Tuningparameter in more detail.
Table 536 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/ESGBootstrapEntryPoint/<x>/EntryPointAttri/<x>/Ext/ in more detail.
Table 537 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/Ext/ in more detail.
Hereinafter, operations of a DM server and a terminal according to the tenth exemplary embodiment of the present invention will be described with reference to
The operation of the DM server according to the tenth exemplary embodiment of the present invention, which will be described below, is similar to the operation of the DM server according to the eighth or ninth exemplary embodiment of the present invention
Referring to
Referring to
In step 3907, if an operator wants a proper bootstrap when it moves into another coverage area, the terminal determines a particular ESG bootstrap entry point for a roaming partner in the MO. In step 3909, the terminal selects the ESG bootstrap entry point for the roaming partner. In step 3911, the terminal requests ESG information from the selected ESG entry point. In step 3913, the terminal receives proper ESG information for the roaming situation and selects an ESG. As a result, in step 3915, the terminal selects a service that the terminal will access through the selected ESG.
The OMA DM can be used either for the bootstrap as described above or for provisioning according to an eleventh exemplary embodiment of the present invention.
An ESG finding mechanism based on stage 1 specification is as follows:
Since the information on which IP platform, ESG provider, or ESG is proper is omitted, it is possible to provide the terminal with provisioning information. Based on the provisioning information, the terminal can make a decision and can select a proper object to access.
In a roaming scenario, the provisioning information is more important. Therefore, it is possible to provide a provisioning for a roaming scenario also.
Hereinafter, an example of signaling provisioning information by an OMA DM will be described with reference to
Referring to
Table 538 below shows the above-mentioned node <x> in more detail.
Table 539 shows the above-mentioned node <x>/IPDC/ in more detail.
Table 540 below shows the above-mentioned node <x>/IPDC/<x> in more detail.
Table 541 below shows the above-mentioned node <x>/IPDC/<x>/LocalIPDCKMSID/ in more detail.
Table 542 shows the above-mentioned node <x>/IPDC/<x>/LocalIPDCKMSID/LocalIPDCOperatorID/ in more detail.
Table 543 below shows the above-mentioned node <x>/IPDC/<x>/LocalOperatorAttri/ in more detail.
Table 544 shows the above-mentioned node <x>/IPDC/<x>/LocalOperatorAttri/<x> in more detail.
Table 545 shows the above-mentioned node <x>/IPDC/<x>/LocalOperatorAttri/<x>/IPPlatform/ in more detail.
Table 546 below shows the above-mentioned node <x>/IPDC/<x>/LocalOperatorAttri/<x>/IPPlatform/<x> in more detail.
Table 547 below shows the above-mentioned node <x>/IPDC/<x>/LocalOperatorAttri/<x>/IPPlatform/<x>/IPPlatformID in more detail.
Table 548 below shows the above-mentioned node <x>/IPDC/<x>/LocalOperatorAttri/<x>/ESGProvider/ in more detail.
Table 549 shows the above-mentioned node <x>/IPDC/<x>/LocalOperatorAttri/<x>/ESGProvider/<x> in more detail.
Table 550 below shows the above-mentioned node <x>/IPDC/<x>/LocalOperatorAttri/<x>/ESGProvider/<x>/ESGProviderURI in more detail.
Table 551 below shows the above-mentioned node <x>/IPDC/<x>/LocalOperatorAttri/<x>/EntryPointAttri/<x>/ESG/ in more detail.
Table 552 shows the above-mentioned node <x>/IPDC/<x>/LocalOperatorAttri/<x>/EntryPointAttri/<x>/ESG/<x> in more detail.
Table 553 below shows the above-mentioned node <x>/IPDC/<x>/LocalOperatorAttri/<x>/EntryPointAttri/<x>/ESG/<x>/ESGURI in more detail.
Table 554 shows the above-mentioned node <x>/IPDC/<x>/LocalOperatorAttri/<x>/EntryPointAttri/<x>/AreaParameter/ in more detail.
Table 555 shows the above-mentioned node <x>/IPDC/<x>/LocalOperatorAttri/<x>/EntryPointAttri/<x>/AreaParameter/<x> in more detail.
Table 556 below shows the above-mentioned node <x>/IPDC/<x>/LocalOperatorAttri/<x>/EntryPointAttri/<x>/AreaParameter/<x>/AreaParameter/ in more detail.
Table 557 below shows the above-mentioned node <x>/IPDC/<x>/LocalOperatorAttri/<x>/EntryPointAttri/<x>/NetworkInfo/ in more detail.
Table 558 shows the above-mentioned node <x>/IPDC/<x>/LocalOperatorAttri/<x>/EntryPointAttri/<x>/NetworkInfo/<x> in more detail.
Table 559 below shows the above-mentioned node <x>/IPDC/<x>/LocalOperatorAttri/<x>/EntryPointAttri/<x>/NetworkInfo/<x>/NetworkInfo/ in more detail.
Table 560 below shows the above-mentioned node <x>/IPDC/<x>/LocalOperatorAttri/<x>/EntryPointAttri/<x>/Tuningparameter/ in more detail.
Table 561 shows the above-mentioned node <x>/IPDC/<x>/LocalOperatorAttri/<x>/EntryPointAttri/<x>/Tuningparameter/<x> in more detail.
Table 562 below shows the above-mentioned node <x>/IPDC/<x>/LocalOperatorAttri/<x>/EntryPointAttri/<x>/Tuningparameter/<x>/Tuningparameter/ in more detail.
Table 563 shows the above-mentioned node <x>/IPDC/<x>/LocalOperatorAttri/<x>/EntryPointAttri/<x>/Ext/ in more detail.
Table 564 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/ in more detail.
Table 565 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x> in more detail.
Table 566 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/OutsideRoamingIPDCKMSID/ in more detail.
Table 567 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/OutsideRoamingIPDCKMSID/OutsideRoamingIPDCOperatorID/ in more detail.
Table 568 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerAttri/ in more detail.
Table 569 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerAttri/<x> in more detail.
Table 570 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerAttri/<x>/IPPlatform/ in more detail.
Table 571 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerAttri/<x>/IPPlatform/<x> in more detail.
Table 572 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerAttri/<x>/IPPlatform/<x>/IPPlatformID in more detail.
Table 573 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerAttri/<x>/ESGProvider/ in more detail.
Table 574 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerAttri/<x>/ESGProvider/<x> in more detail.
Table 575 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerAttri/<x>/ESGProvider/<x>/ESGProviderURI in more detail.
Table 576 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerAttri/<x>/EntryPointAttri/<x>/ESG/ in more detail.
Table 577 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerAttri/<x>/EntryPointAttri/<x>/ESG/<x> in more detail.
Table 578 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerAttri/<x>/EntryPointAttri/<x>/ESG/<x>/ESGURI in more detail.
Table 579 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerAttri/<x>/EntryPointAttri/<x>/AreaParameter/ in more detail.
Table 580 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerAttri/<x>/EntryPointAttri/<x>/AreaParameter/<x> in more detail.
Table 581 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerAttri/<x>/EntryPointAttri/<x>/AreaParameter/<x>/AreaParameter in more detail.
Table 582 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerAttri/<x>/EntryPointAttri/<x>/NetworkInfo/ in more detail.
Table 583 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerAttri/<x>/EntryPointAttri/<x>/NetworkInfo/<x> in more detail.
Table 584 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerAttri/<x>/EntryPointAttri/<x>/NetworkInfo/<x>/NetworkInfo in more detail.
Table 585 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerAttri/<x>/EntryPointAttri/<x>/Tuningparameter/ in more detail.
Table 586 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerAttri/<x>/EntryPointAttri/<x>/Tuningparameter/<x> in more detail.
Table 587 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerAttri/<x>/EntryPointAttri/<x>/Tuningparameter/<x>/Tuningparameter/ in more detail.
Table 588 shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerAttri/<x>/EntryPointAttri/<x>/Ext/ in more detail.
Table 589 below shows the above-mentioned node <x>/IPDC/<x>/RoamingPartnerOutside/<x>/Ext/ in more detail.
Table 590 below shows the above-mentioned node <x>/IPDC/<x>/Ext/ in more detail.
Based on the provisioning information described above, the terminal may query a proper ESG bootstrap entry point, ESG bootstrap information, ESG bootstrap descriptor, ESG, ESG subset, ESG fragment, service bundle, service, etc.
If a terminal or user ID is provided, and if the provisioning for another terminal or user is different, an MO of a mechanism with respect to the different provisioning for another terminal or user may have a construction as illustrated in
Referring to
Hereinafter, operations of a DM server and a terminal according to the eleventh exemplary embodiment of the present invention will be described with reference to
Referring to
Referring to
An OMA DM mechanism according to a twelfth exemplary embodiment of the present invention enables discovery of an ESG entry point using an OMA DM. One MO is defined for ESG discovery from a roaming partner.
Referring to
Referring to
In the second OMA DM mechanism according to the twelfth exemplary embodiment of the present invention, the MO is defined for discovery of an entry point in a broadcast network.
The IPVersion6 4508 indicates if the SourceIPAddress and the DestinationIPAddress are signals according to IPVersion6. Here, the SourceIPAddress 4509 is a source IP address of a FLUTE session transmitting an ESG, and the DestinationIPAddress 4510 is a target IP address of the FLUTE session transmitting the ESG. Further, the Port 4511 is a port number of an IP stream of the FLUTE session transmitting the ESG, the TSI 4512 is a transport session identifier of the FLUTE session transmitting the ESG, the ESGURI 4517 indicates transmission of the ESG, the IPPlatformID 4529 is an IP platform identifier transmitting the ESG. Further, nodes designated by reference numerals 4501 to 4535 perform the same operations as those of the nodes provided by the OMA DM according to the tenth exemplary embodiment of the present invention described above.
Referring to
In the second or third OMA DM mechanism according to the twelfth exemplary embodiment of the present invention, the terminal can search for an ESG directly in a broadcast without parsing ESG bootstrap information. Further, the second and third OMA DM mechanisms according to the twelfth exemplary embodiment of the present invention described above correspond to examples for the home (local) case. Similarly, an ESG of a roaming partner discovery MO can be defined by the fourth and the fifth OMA DM mechanisms according to the twelfth exemplary embodiment of the present invention described below.
Referring to
Referring to
In the home IPDC operator scope and the roaming partner scope, the MO for a terminal may have a configuration obtained by combining both scopes. Further, for the URL and the IP address/port/TSI/IPPlatformID, the MO may have a configuration corresponding to a combination for discovery of both entry points in bi-directions and in the broadcast network. Further, for the entry points of all other MOs, the URL may be an IPPlatform, TSI, or both of them. Further, the MO can be modified in a way similar to that described above in the OMA DM mechanism according to the twelfth exemplary embodiment of the present invention.
The OMA DM mechanisms according to the tenth to twelfth exemplary embodiments of the present invention are used for ESG search. The mechanism according to the eleventh exemplary embodiment of the present invention is used for supply of configuration information, while the others are used for ESG bootstrap search. For example, these mechanisms can be combined for at least one object for supply of configuration information and ESG bootstrap search.
The configuration may have various forms due to different applications. Therefore, the MO, ESG bootstrap entry point, and ESG entry point, which are defined in order to provide the configuration, also may have various forms. Further, in an exemplary implementation, the mechanisms defined in the present specification can be combined or modified in various ways.
Referring to reference numeral 4938 of
In the MO described above, different ESG bootstrap entry point URLs are prepared for local and roaming cases, and one URL may be provided for both of them. When a common URL is used for the local and the roaming cases, the terminal should notify the server of the object to which the terminal queries between the local and roaming cases when the terminal requests bootstrap information using the URL.
Based on the configuration and the entry point information described above, the terminal can select an IP platform for bootstrap, and can select an ESG that is proper for access through a broadcast network or query them through an interactive network. If the ESG entry point information is provided as in the OMA DM mechanism according to the ninth to twelfth exemplary embodiments of the present invention, the terminal can directly access or query the ESG without parsing the bootstrap information.
In
In the first OMA DM mechanism according to the thirteenth exemplary embodiment of the present invention described above, one bootstrap entry point URL is provided for each home and roaming configuration. However, a home or roaming configuration may have at least two entry points having different characteristics, for example, one bootstrap entry point for each IP platform. Such characteristics have been described in the previous mechanisms. The characteristics information relates to the configuration information. In the second OMA DM mechanism according to the thirteenth exemplary embodiment of the present invention, the configuration information can be used for both the characteristics and configuration supply of an entry point.
In
If it is desired to provide configuration information and ESG bootstrap entry point information while discriminating between them, some entry point characteristic information overlaps with the configuration information, and the MO can define the overlapping information by different subnodes. Therefore, it is possible to use various schemes for combining mechanisms for various purposes. Although the third OMA DM mechanism according to the thirteenth exemplary embodiment of the present invention provides several examples of the configuration, the present invention is not limited to these examples and includes modification of the configuration based on another application.
In
A terminal can access a service based on a registered IPDC operator of the terminal and a roaming partner of the operator. Except for this service, there is a service that cannot be scrambled. Even if the service is not based on a registered IPDC operator of the terminal or a roaming partner of the operator, the terminal can access their service. This type of service is referred to as a “clear to air” service.
The following MO corresponds to an example of searching for a clear to air service.
The ESGBootstrapEntryPointURL is a URL which enables a terminal to query bootstrap information for the clear to air service. The IPPlatformID appoints the IP platform having the clear to air service. The ESGURI appoints the ESG having the clear to air service. The ESGEntryPoint appoints an entry point of an ESG having the clear to air service. For details thereof, it is possible to refer to the mechanisms according to the tenth and twelfth exemplary embodiments of the present invention. There may exist a URL by which a terminal queries an ESG. The URL may be an IP address indicating the location of the ESG, port number, TSI, or IPPlatformID. Other related information can be obtained by referring to the description on other mechanisms.
In the exemplary embodiments described above, when a terminal ID or user ID is provided, the ESG bootstrap entry point, ESG access point, provisioning or any other information may be different according to another terminal or user. Further, nodes relating to the terminal information or user information and the terminal ID or user ID may be added or modified. The ESG bootstrap entry point, access point, provisioning or any other information is provided based on another terminal or user.
Further, the exemplary OMA DM of the present specification uses the ESG bootstrap entry point, access point, and provisioning, the used ESG bootstrap entry point, access point, and provisioning do not limit the described exemplary embodiments.
Further, the definition of the MO in the present specification can be used for the used bootstrap information, ESG bootstrap descriptor, ESG subset, ESG container, ESG fragment, service bundle, service, etc.
Hereinafter, a DM server and a terminal according to an exemplary embodiment of the present invention will be described with reference to
Referring to
The service application block 5310 is an interacting endpoint for a terminal, which aggregates content from multiple sources and metadata necessary for service configuration in order to provide a particular service application, generates service description metadata to be used in the electronic service guide, and interacts with the service application. Further, the service application block 5310 can provide a head end application logic and service protection and include the applications provided to the IP datacast, and has a responsibility to provide content encoded in a format which the terminal understands through streaming or file carousel transfer. Further, the service application block 5310 provides service protection and may include a service application entity for each application provided in the IP datacast.
The service management block 5330 includes sub-entities of a service guide provisioning application block 5331, a service configuration & resource allocation block 5333, a security/service protection provision block 5335, and a location services block 5337.
The service configuration & resource allocation block 5333 allocates competing service applications for a bandwidth of a broadcast bearer. That is, one DVB-H IP platform is allocated to one DVB transport stream. Further, the service configuration & resource allocation block 5333 allocates resources to the service location (e.g. broadcast network topology) and a schedule service over bandwidth and time. The service provisioning application block 5331 collects parameters of roaming ESG information from the service application block 5310. The security/service protection provision block 5335 manages user access to the service application block 5310. Further, the location services block 5337 provides a location service to a service application by, for example, an interactive bearer network function or a GPS function.
Referring to
The broadcast receiver 5401 receives service data or signaling (including roaming ESG information) from the broadcast network. The interactive adaptor 5403 transmits and receives the service data or signaling (including roaming ESG information) through an interactive network. The control block 5405 performs the mobility process and performs a control for selection of the ESG bootstrap entry point according to the requirements of the desired bootstrap as described above. The subscription management block 5407 controls rights acquisition, traces the acquired rights and controls the parsing process of the service content. The content consumption block 5409 consumes content and provides the roaming ESG information to the user.
This apparatus may be separately configured between the service application block 103 and the interactive network 109 of
The ESG bootstrap entry point discovery information providing apparatus as described above includes an MO creation block 5501 and a transmission block 5502. The MO creation block 5501 lists at least one piece of ESG bootstrap characteristic information for an ESG bootstrap proper for the status of the terminal, and creates a Management Object (MO) connecting the ESG bootstrap entry point with said at least one piece of ESG bootstrap characteristic information. The transmission block 5502 transmits the generated MO to the terminal through an interactive channel.
According to exemplary embodiments of the present invention, it is possible to select an ESG bootstrap entry point according to requirements of a desired bootstrap, request ESG bootstrap information from the selected ESG bootstrap entry point, receive the requested ESG bootstrap information, select an ESG, and access a service through the selected ESG.
Further, according to exemplary embodiments of the present invention, it is possible to select an ESG by selecting an ESG bootstrap entry point according to requirements of a desired bootstrap by using an OMA DM in a digital broadcast system.
Further, according to exemplary embodiments of the present invention, it is possible to select an ESG based on provisioning information by using an OMA DM in a digital broadcast system. Moreover, according to exemplary embodiments of the present invention, it is possible to discover roaming partner information within a roaming coverage area of a terminal and an ESG bootstrap entry point corresponding to the roaming partner information.
While the invention has been shown and described with reference to certain exemplary embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims and their equivalents.
Number | Date | Country | Kind |
---|---|---|---|
10-2008-0021107 | Mar 2008 | KR | national |
10-2008-0032879 | Apr 2008 | KR | national |
10-2008-0035839 | Apr 2008 | KR | national |
10-2008-0036781 | Apr 2008 | KR | national |
10-2008-0043670 | May 2008 | KR | national |