APN 情報または CarrierConfig を更新するには、会社の有効なメールアドレスを用いた Google アカウントを使用してリクエストを送信する必要があります（たとえば、Acme Company からの APN 更新リクエストは、「foobar@acme.com」というメールアドレスなどから送信する必要があります）。
会社のメールアドレスに関連付けられた Google アカウントがない場合は、ブラウザですべての Gmail アカウントからサインアウトし（他のアカウントとの混乱を避けるために、シークレット ウィンドウなどのプライベート ブラウジング機能を使用することをおすすめします）、会社のメールアドレスで Google アカウントを作成します。
[Example - "Add VVM settings for CarrierXYZ"]
[Example - "Updated <mccmnc> carrier config file to include VVM settings
as defined by CarrierXYZ."]
Bug: [Issue ID from Google Issue Tracker]
Test: [Testing notes]
[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["必要な情報がない","missingTheInformationINeed","thumb-down"],["複雑すぎる / 手順が多すぎる","tooComplicatedTooManySteps","thumb-down"],["最新ではない","outOfDate","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["サンプル / コードに問題がある","samplesCodeIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-03-26 UTC。"],[],[],null,["# APN and CarrierConfig\n\nCarriers can update their Access Point Name (APN) information and their\ncarrier-specific configuration settings\n([CarrierConfig](/docs/core/connect/carrier))\nin the Android Open Source Project (AOSP).\n\nGoogle Account with your corporate email address\n------------------------------------------------\n\nTo update APN information or your CarrierConfig, you need\nto submit the request using a Google Account with an active corporate email\naddress (for example, an APN update request from Acme Company should come from an\nemail address such as *foobar@acme.com*).\n\nIf you do not have a Google Account that links to your corporate email\naddress, sign out of all Gmail accounts from your browser (we recommend using\na private browsing feature, such as an incognito window, to avoid confusion with\nyour other accounts) and then\n[create a Google\naccount with your corporate email address](https://accounts.google.com/SignUpWithoutGmail?hl=en).\n| **Caution:** Do NOT associate any Gmail accounts with this newly created account.\n\nPrepare a local development environment\n---------------------------------------\n\n| **Note:** Instead of using a local development environment, for small changes, you can use the browser-based [Git source editor](/docs/setup/contribute/source-editor) tool.\n\nIf you've never submitted code to AOSP before, you will\nneed to initialize your build environment, become familiar with the tools, and\nunderstand how to submit patches:\n\n- [Establishing a build environment](/docs/setup/start/initializing)\n- [Getting familiar with Git and Repo](/docs/setup/download)\n- [Downloading the source](/docs/setup/download/downloading)\n- [Submitting patches](/docs/setup/contribute/submit-patches)\n\nIn addition, we strongly recommend that you use the\n[Google Issue Tracker](https://developers.google.com/issue-tracker/)\nto track changes.\n\nFile a bug\n----------\n\n1. Go to [issuetracker.google.com](https://issuetracker.google.com) and sign in using your corporate email address (see [Google Account with your corporate email address](#create-account)).\n| **Note:** If this is your first time logging in, you need to accept a license.\n2. After logging in, click **Create issue** on the left side of the screen.\n3. In **Component** , select [**Android Public Tracker \\\u003e Framework**](https://issuetracker.google.com/issues/new?component=192705&template=845803)\n4. Continue to [APN update](#apn-update1) or [CarrierConfig update](#carrierconfig-update1), as appropriate, to enter the Title and Description.\n\n### APN bug\n\nSet the bug attributes as follows:\n\n**Title:** *Add* /*Modify* /*Remove* APNs for CarrierXYZ\n\n**Description:** Add a detailed description of the changes you're\nrequesting, including the APN settings themselves.\n\n### CarrierConfig bug\n\nSet the bug attributes as follows:\n\n**Title:** Config changes for CarrierXYZ\n\n**Description:** Add a detailed description of the changes you're\nrequesting.\n\nSubmit changes\n--------------\n\nTo make changes:\n\n1. Identify which file to change.\n2. Make changes to the file.\n3. Commit the changes to your local repository by following the instructions for [submitting patches](/docs/setup/contribute/submit-patches#make-your-change), paying attention to the commit message guidelines, including recommended format.\n4. After you commit your change to your personal history, upload it to Gerrit using the `repo upload` command.\n5. Following a successful upload, repo provides the URL of a new page on Gerrit. Use this URL to:\n - View your patch on the review server\n - Add comments\n - Request specific reviewers for your patch\n\n| **Note:** Submission of APN and CarrierConfig changes to AOSP doesn't guarantee that OEMs will pick up the change. Carriers should work with OEMs so that the required changes are made on their devices.\n\n### APN syntax\n\n**Android project name** - device/sample\n\n**File name(s)** - etc/apns-full-conf.xml\n([Google\nGit main link](https://android.googlesource.com/device/sample/+/android16-release/etc/apns-full-conf.xml))\n\nThe file contains APN settings in XML format and serves as a sample file\nso there is no change in the behavior of Android devices.\n\nA typical APN config looks like this: \n\n```carbon\n\u003capn carrier=\"CarrierXYZ\"\n mcc=\"123\"\n mnc=\"123\"\n apn=\"carrierxyz\"\n type=\"default,supl,mms,ims,cbs\"\n mmsc=\"http://mms.carrierxyz.com\"\n mmsproxy=\"0.0.0.0\"\n mmsport=\"80\"\n bearer_bitmask=\"4|5|6|7|8|12\"\n/\u003e\n```\n\n#### Testing\n\n1. Connect any Android device for which you have root access.\n2. Add settings to /etc/apns-conf.xml.\n3. Reset APN settings.\n4. In APN settings, confirm that profiles are loaded correctly.\n5. For each profile, test data connectivity, Wi-Fi hotspot, and MMS to make sure they work correctly.\n\n#### Commit message\n\n```\n[Example - \"Add CarrierXYZ apns to sample apns\"]\nBug: [Issue ID from Google Issue Tracker]\nTest: No change to behavior as this is only a sample file\n```\n\n#### Sample CL\n\nSee [Sample BICS APNs](https://android-review.googlesource.com/c/device/sample/+/532609) for an example CL.\n\n### CarrierConfig syntax\n\n**Project name** - platform/packages/apps/CarrierConfig\n\n**File name(s)** - assets/carrier_config_.xml ([Google\nGit main link](https://android.googlesource.com/platform/packages/apps/CarrierConfig/+/android16-release/assets))\n\nIdentify the relevant XML file(s) in the assets folder by the relevant MCC/MNC\ntuple(s). The file contains the carrier config object in XML format. The\nattribute names are defined as keys under the\n[CarrierConfigManager](https://developer.android.com/reference/android/telephony/CarrierConfigManager.html), and the type of value (int/string/bool) is indicated\nby the suffixes.\n\nTypical int/string/bool attributes look like this: \n\n```carbon\n\u003cint name=\"vvm_port_number_int\" value=\"5499\" /\u003e\n\u003cstring name=\"vvm_type_string\"\u003evvm_type_omtp\u003c/string \u003e\n\u003cboolean name=\"vvm_cellular_data_required_bool\" value=\"true\" /\u003e\n```\n\n#### Commit message\n\n```\n[Example - \"Add VVM settings for CarrierXYZ\"]\n\n[Example - \"Updated \u003cmccmnc\u003e carrier config file to include VVM settings\nas defined by CarrierXYZ.\"]\n\nBug: [Issue ID from Google Issue Tracker]\nTest: [Testing notes]\n```\n\n#### Sample CL\n\nSee an [updated carrier config file](https://android-review.googlesource.com/c/platform/packages/apps/CarrierConfig/+/625835) for an example CL.\n\nRequest a review\n----------------\n\nTo request a review:\n\n- Go to the Gerrit URL of your change and add *android-carrier-config-review@google.com* as a reviewer.\n- You can also add your Google contact to the CC list on Gerrit.\n- For tracking purposes, you can change the assignee of the issue to *android-carrier-config-review@google.com*.\n\nAfter a submission makes it through the review and verification process,\nGerrit automatically merges the change into the public repository. Other users\ncan run ` repo sync ` to pull the update into their local client.\n| **Note:** Changes to the APN file don't automatically take effect because the changes are in device/sample folder. If you are working with key OEMs, make sure they take the latest information from AOSP. Typically OEMs have a regular schedule where they pick the latest information, but if you are in a hurry, reach out to OEMs to encourage them to update their list sooner rather than later."]]
