hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 3.2.2.1 General
| In the following procedures the UE selects and attempts registration on PLMNs.
In this TS, the term "PLMN Selection" defines a UE based procedure, whereby candidate PLMNs are chosen, one at a time, for attempted registration.
A User Controlled PLMN Selector data field exists on the USIM to allow the user to indicate a preference for network selection. It shall be possible for the user to update the User Controlled PLMN Selector data field, but it shall not be possible to update this data field over the radio interface, e.g. using SIM Application Toolkit.
It shall be possible to have an Operator Controlled PLMN Selector list and a User Controlled PLMN Selector list stored on the SIM/USIM card. Both PLMN Selector lists may contain a list of preferred PLMNs in priority order. It shall be possible to have an associated Access Technology identifier e.g., NG-RAN, satellite NG-RAN, E-UTRAN (WB-S1 mode, NB-S1 mode), satellite E-UTRAN (WB-S1 mode, NB-S1 mode), UTRAN, GERAN or GERAN EC-GSM-IoT associated with each entry in the PLMN Selector lists.
Optionally, it may be possible to have an Operator Controlled Lower Selection-priority PLMN Selector list for PLMN selection. This list may be stored either in the USIM or provisioned in the ME or both. If the list is both stored in the USIM and provisioned in the ME, only the list stored in the USIM shall be used by the UE. This list contains PLMNs and associated Access Technology identifiers combinations, in priority order. The support of Operator Controlled Lower Selection-priority PLMN Selector list in the network selection procedure is optional for the UE.
For UEs supporting any, or a combination, of NB-IoT, GERAN EC-GSM-IoT [18] and Category M1 or M2 of E-UTRA [17], the 5G system shall support a mechanism to have an Operator controlled signal threshold per access technology on the USIM to be used for network selection. The signal threshold is specific for a certain Access Technology and shall apply to all PLMNs with the corresponding access technology combinations.
NOTE 1: The use of the Operator controlled signal threshold per access technology is intended for IoT stationary devices, without user interaction.
NOTE 2: The allowed range of the Operator controlled signal threshold per access technology is between the cell selection criterion and the high quality signal as defined in TS 23.122 [3].
The UE shall utilise the following information stored in the USIM related to network selection, e.g. HPLMN, Operator controlled PLMN Selector list, User Controlled PLMN Selector list, Forbidden PLMN list, Operator controlled signal threshold, and if supported by the UE, Operator Controlled Lower Selection-priority PLMN Selector list.
NOTE 3: A PLMN in a Selector list, including HPLMN, may have multiple occurrences, with different access technology identifiers.
The UE shall ignore those PLMN + access technology entries in the User Controlled PLMN selector and Operator Controlled PLMN selector lists where the associated Access Technology is not supported by the UE. In the case that there are multiple associated Access Technology identifiers in an entry the UE shall not ignore the entry if it includes any associated Access Technology that is supported by the UE.
It shall be possible to handle cases where one network operator accepts access from access networks with different network IDs. It shall also be possible to indicate to the UE that a group of PLMNs are equivalent to the registered PLMN regarding PLMN selection, cell selection/re-selection and handover.
It shall be possible for the home network operator to identify alternative Network IDs as the HPLMN. It shall be possible for the home network operator to store in the USIM an indication to the UE that a group of PLMNs are treated as the HPLMN regarding PLMN selection. Any PLMN to be declared as an equivalent to the HPLMN shall be present within the EHPLMN list and is called an EHPLMN. The EHPLMN list replaces the HPLMN derived from the IMSI. When the EHPLMN list is present, any PLMN in this list shall be treated as the HPLMN in all the network and cell selection procedures.
If registration on a PLMN is successful, the UE shall indicate this PLMN (the "registered PLMN") and be capable of making and receiving calls on it. The identity of the registered PLMN shall be stored on the SIM/USIM. However, if registration is unsuccessful, the UE shall ensure that there is no registered PLMN stored in the SIM/USIM.
If a registration is unsuccessful because the IMSI is unknown in the home network, or the UE is illegal, then the UE shall not allow any further registration attempts on any network, until the UE is next powered‑up or a SIM/USIM is inserted.
If the registration is unsuccessful due to the lack to service entitlement, specific behaviour by the UE may be required, see clause 3.2.2.4.
To avoid unnecessary registration attempts, lists of forbidden PLMNs, TAs and LAs are maintained in the UE, see clause 3.2.2.4 and 3GPP TS 23.122 [3].
Registration attempts shall not be made by UEs without a SIM/USIM inserted.
An UE/ME which has not successfully registered shall nevertheless be able to make emergency call attempts on an available PLMN (which supports the emergency call teleservice), without the need for the user to select a PLMN. An available PLMN is determined by radio characteristics (3GPP TS 23.122 [3]).
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 3.2.2.2 At switch-on or recovery from lack of coverage
| If the Operator controlled signal threshold per access technology is set on the USIM, it shall be used for the selection of the last registered PLMN (and/or EHPLMN/HPLMN) and for the automatic mode network selection steps described in this clause. In particular, if the Operator controlled signal threshold per access technology is set on the USIM the UE shall only select a network if
- the network selection conditions as described below are met and
- the received signal quality of the candidate PLMN/access technology combination is equal to or higher than the Operator controlled signal threshold per access technology.
At switch on, when in coverage of the last registered PLMN as stored in the SIM/USIM, the UE will attach to that network.
As an option, in automatic selection mode, when no EHPLMN list is present, the UE may select the HPLMN. When the EHPLMN list is present, the UE may select the highest priority EHPLMN among the available EHPLMNs. The operator shall be able to control the UE behaviour by USIM configuration.
As an option, if the UE is in manual network selection mode at switch-on
- if the last registered PLMN is unavailable and no equivalent PLMN is available,
- and the UE finds it is in coverage of either the HPLMN or an EHPLMN
then the UE should register on the corresponding HPLMN or EHPLMN. The UE remains in manual mode.
As an option, if the UE is in automatic network selection mode at switch-on, and if the last registered PLMN is identified as Operator Controlled Lower Selection-priority, the UE may skip RPLMN selection and move to the Automatic network selection mode specified below.
If the UE returns to coverage of the PLMN on which it is already registered (as indicated by the registered PLMN stored in the SIM/USIM), the UE shall perform a location update to a new location area if necessary. As an alternative option to this, if the UE is in automatic network selection mode and it finds coverage of the HPLMN or any EHPLMN, the UE may register on the HPLMN (if the EHPLMN list is not present) or the highest priority EHPLMN of the available EHPLMNs (if the EHPLMN list is present) and not return to the last registered PLMN. If the EHPLMN list is present and not empty, it shall be used. The operator shall be able to control by USIM configuration whether an UE that supports this option shall follow this alternative behaviour.
NOTE: At switch-on and at recovery from lack of coverage, a UE in automatic network selection mode can attempt registration once the RPLMN or, if the above option is applicable, the HPLMN or EHPLMN is found on an access technology.
The default behaviour for a UE is to select the last registered PLMN.
If there is no registered PLMN stored in the SIM/USIM, or if this PLMN is unavailable and no equivalent PLMN is available, or the attempted registration fails, the UE shall follow one of the following procedures for network selection:
A) Automatic network selection mode
The UE shall select and attempt registration on other PLMNs, if available and allowable, if the location area is not in the list of "forbidden LAs for roaming" and the tracking area is not in the list of "forbidden TAs for roaming" (see 3GPP TS 23.122 [3]), in the following order:
i) An EHPLMN if the EHPLMN list is present or the HPLMN (derived from the IMSI) if the EHPLMN list is not present for preferred access technologies in the order specified. In the case that there are multiple EHPLMNs present then the highest priority EHPLMN shall be selected. It shall be possible to configure a voice capable UE so that it shall not attempt registration on a PLMN if all cells identified as belonging to the PLMN do not support the corresponding voice service;
ii) each entry in the "User Controlled PLMN Selector with Access Technology" data field in the SIM/USIM (in priority order). It shall be possible to configure a voice capable UE so that it shall not attempt registration on a PLMN if all cells identified as belonging to the PLMN do not support the corresponding voice service;
iii) each entry in the "Operator Controlled PLMN Selector with Access Technology" data field in the SIM/USIM (in priority order). It shall be possible to configure a voice capable UE so that it shall not attempt registration on a PLMN if all cells identified as belonging to the PLMN do not support the corresponding voice service;
iv) other PLMN/access technology combinations with sufficient received signal quality (see 3GPP TS 23.122 [3]) in random order, excluding any PLMN/access technology combination listed in the “Operator Controlled Lower Selection-priority PLMN Selector with Access Technology” list. It shall be possible to configure a voice capable UE so that it shall not attempt registration on a PLMN if all cells identified as belonging to the PLMN do not support the corresponding voice service;
v) all other PLMN/access technology combinations in order of decreasing signal quality, excluding any PLMN/access technology combination listed in the “Operator Controlled Lower Selection-priority PLMN Selector with Access Technology” list. It shall be possible to configure a voice capable UE so that it shall not attempt registration on a PLMN if all cells identified as belonging to the PLMN do not support the corresponding voice service;
vi) each entry (PLMN/access technology combination) in the “Operator Controlled Lower Selection-priority PLMN Selector with Access Technology” list (in priority order);
In the case of a UE operating in UE operation mode A or B, an allowable PLMN is one which is not in the "Forbidden PLMN" data field in the SIM/USIM. This data field may be extended in the ME memory (see clause 3.2.2.4). In the case of a UE operating in UE operation mode C, an allowable PLMN is one which is not in the "Forbidden PLMN" data field in the SIM/USIM or in the list of "forbidden PLMNs for GPRS service" in the ME.
If the UE uses the Operator controlled signal threshold per access technology and no candidate PLMN/access technology combination fulfils the Operator controlled signal threshold criteria, the UE shall repeat the network selection without using the Operator controlled signal threshold per access technology.
If there is no available PLMN except for PLMNs in the "Forbidden PLMN" data field in the SIM/USIM, and the available PLMNs indicate that Disaster Condition applies, this PLMN shall be considered allowable for registration to the UE while the Disaster Condition is applicable.
If successful registration is achieved, the UE shall indicate the selected PLMN.
If registration cannot be achieved on any PLMN and at least one PLMN offering restricted local operator services has been found, the UE shall obtain user consent for restricted local operator services and the UE may use a list of preferred PLMNs for restricted local operator services stored in the ME. If none of the preferred PLMNs for restricted local operator services is available, the UE shall select any available PLMN offering restricted local operator services. If one of these PLMNs for restricted local operator service is chosen, the UE shall indicate the choice. If none are selected, the UE shall wait until a new PLMN is detected, or new location areas or tracking areas of an allowed PLMN are found which are not in the forbidden LA or TA list(s), and then repeat the procedure.
If registration cannot be achieved on any PLMN and no PLMN offering restricted local operator services has been found, the UE shall indicate "no service" to the user, wait until a new PLMN is detected, or new location areas or tracking areas of an allowed PLMN are found which are not in the forbidden LA or TA list(s), and then repeat the procedure. When registration cannot be achieved, different (discontinuous) PLMN search schemes may be used in order to minimize the access time while maintaining battery life, e.g. by prioritising the search in favour of BCCH carriers which have a high probability of belonging to an available and allowable PLMN.
B) Manual network selection mode
The UE shall indicate PLMNs, including "Forbidden PLMNs", which are available. If there are none, this shall also be indicated. The HPLMN of the user may provide on the USIM additional information about the available PLMNs, if this is provided then the UE shall indicate that information to the user. This information, provided as free text may include:
- Preferred partner;
- roaming agreement status;
- supported services.
Furthermore, the UE may indicate whether the available PLMNs are present on one of the PLMN selector lists (e.g. EHPLMN, User Controlled, Operator Controlled or Forbidden) as well as not being present on any of the lists.
For the purpose of presenting the names of the available PLMNs to the user, the ME shall use the USIM defined names if available or other PLMN naming rules in priority order as defined in 3GPP TS 22.101 [7] (Country/PLMN indication).
Any available PLMNs shall be presented in the following order:
i) HPLMN (if the EHPLMN list is not present); or if one or more of the EHPLMNs are available then based on an optional data field on the USIM either the highest priority available EHPLMN is to be presented to the user or all available EHPLMNs are presented to the user in priority order; if the data field is not present, then only the highest priority available EHPLMN is presented;
ii) PLMNs contained in the "User Controlled PLMN Selector" data field in the SIM/USIM (in priority order);
iii) PLMNs contained in the "Operator Controlled PLMN Selector" data field in the SIM/USIM (in priority order);
iv) other PLMN/access technology combinations with sufficient received signal level (see 3GPP TS 23.122 [3]) in random order, excluding any PLMN/access technology combination listed in the “Operator Controlled Lower Selection-priority PLMN Selector with Access Technology” list;
v) all other PLMN/access technology combinations in order of decreasing signal strength, excluding any PLMN/access technology combination listed in the “Operator Controlled Lower Selection-priority PLMN Selector with Access Technology” list.
vi) each entry (PLMN/access technology combination) in the “Operator Controlled Lower Selection-priority PLMN Selector with Access Technology” list (in priority order);
If a PLMN does not support voice services, then this shall be indicated to the user.
The user may select the desired PLMN and the UE shall attempt registration on this PLMN. (This may take place at any time during the presentation of PLMNs.)
If registration cannot be achieved on any PLMN and at least one PLMN offering restricted local operator services has been found, the UE shall obtain user consent for restricted local operator services and offer the user to select one of these networks. If one of these networks is selected, the UE shall indicate the selected PLMN, wait until a new PLMN is detected, or new location areas or tracking areas of an allowed PLMN are found which are not in the forbidden LA or TA list(s), and then repeat the procedure.
If the registration cannot be achieved on any PLMN and no PLMN offering restricted local operator services is selected, the UE shall indicate "No Service". The user may then select and attempt to register on another or the same PLMN following the above procedure. The UE shall not attempt to register on a PLMN which has not been selected by the user.
Once the UE has registered on a PLMN selected by the user, the UE shall not automatically register on a different PLMN unless:
i) The new PLMN is declared as an equivalent PLMN by the registered PLMN;
or,
ii) The user selects automatic mode.
If a PLMN is selected but the UE cannot register on it because registration is rejected with the cause "PLMN not allowed", the UE shall add the PLMN to the “Forbidden PLMN” list (clause 3.2.2.4.1). The UE shall not re-attempt to register on that network unless the same PLMN is selected again by the user.
If a PLMN is selected but the UE cannot register for PS services on it because registration is rejected with the cause "GPRS services not allowed in this PLMN", the UE shall not re-attempt to register for E-UTRAN or UTRAN PS or GERAN PS on that network. The PLMN is added to the list "Forbidden PLMN's for GPRS services". The UE shall not re-attempt to register for E-UTRAN or UTRAN PS or GERAN PS on that network unless the same PLMN is selected again by the user. The reception of the cause "GPRS services not allowed in this PLMN", does not affect the CS service.
For requirements to restrict the access of a UE to one or several specific RATs see section 7.1.
If a PLMN is selected but the UE cannot register on it for other reasons, the UE shall, upon detection of a new LA (not in a forbidden LA list) of the selected PLMN, attempt to register on the PLMN.
If the UE is registered on a PLMN but loses coverage, different (discontinuous) carrier search schemes may be used to minimize the time to find a new valid BCCH carrier and maintain battery life, e.g. by prioritizing the search in favour of BCCH carriers of the registered PLMN.
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 3.2.2.3 User reselection
| At any time, the user may request the UE to initiate reselection and registration onto an alternative available PLMN, according to the following procedures, dependent upon the operating mode.
A) Automatic Network Selection Mode
The UE shall follow the procedure defined in clause 3.2.2.2.A) above, including the use of Operator signal threshold per access technology, if set on the USIM, as described in 3.2.2.2.
B) Manual Network Selection Mode
The procedure of 3.2.2.2 B) is followed.
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 3.2.2.4 Mobile Station reactions to indications of service restriction from the network
| Different types of UE behaviour are required to support, for example, national roaming, regionally provided service and temporary international roaming restrictions. The behaviour to be followed by the UE is indicated by the network.
3.2.2.4.1 "Permanent" PLMN restriction
When a registration attempt by the UE is rejected by a network with an indication of "permanent" PLMN restriction, the PLMN identity shall be written to a list of "Forbidden PLMNs" stored in a data field in the SIM/USIM.
If a successful registration is achieved on a PLMN in the "Forbidden PLMN" list, the PLMN shall be deleted from the list. However, if successful registration is achieved on a PLMN in the "Forbidden PLMN" list while Disaster Condition applies, the PLMN shall not be deleted from "Forbidden PLMN" list.
When in automatic mode, the UE may indicate any PLMNs which will not be selected due to their presence in the "Forbidden PLMN" list.
If a UE receives an equivalent PLMN list containing a PLMN which is included in the “Forbidden PLMN” list, this PLMN shall be removed from the equivalent PLMN list before this is stored by the UE.
3.2.2.4.2 "Partial" and "temporary" PLMN restrictions
When a registration attempt by the UE is rejected by a network due to a "partial" or a "temporary" PLMN restriction, the UE shall perform one of the following procedures determined by the indication in the location update reject cause sent by the network (see 3GPP TS 23.122 [3]):
i) The UE shall store the tracking area identity or location area identity in the list of "5GS forbidden TA, forbidden TAs or forbidden LAs for regional provision of service" respectively and shall enter the limited service state. The UE shall remain in that state until it moves to a cell in a location area where service is allowed;
ii) The UE shall store the tracking area identity or the location area identity in the list of "5GS forbidden TA, forbidden TAs or forbidden LAs for roaming" respectively and shall use one of the following procedures according to the PLMN selection Mode:
A) Automatic network selection mode:
The procedure of 3.2.2.2. A).
B) Manual network selection mode:
The procedure of 3.2.2.2.B).
iii) The UE shall store the tracking area identity or location area identity in the list of "5GS forbidden TA, forbidden TAs or forbidden LAs for roaming" respectively and shall search for a suitable cell in the same PLMN.
NOTE: A suitable cell will belong to a different TA or LA which is not in the "forbidden TAs or LAs for roaming". When a TA supports multiple systems (e.g. 5GS and EPS), a cell of the TA may be a suitable cell for one system while the cell is not a suitable cell for other systems..
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 3.2.2.4.3 PLMN restrictions for PS services
| When a registration attempt for PS services by the UE is rejected by the network with the cause "GPRS services not allowed in this PLMN", the PLMN identity shall be written to a list of "forbidden PLMNs for GPRS service" in the ME. This list is deleted when the UE is switched off or when the SIM/USIM is removed; the maximum number of possible entries in this list is implementation dependent, but must be at least one entry (see 3GPP TS 23.122 [3]).
If a successful registration is achieved on a PLMN in the "forbidden PLMNs for GPRS service" list, the PLMN shall be deleted from the list.
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 3.2.2.5 Periodic network selection attempts
| If the Operator controlled signal threshold per access technology is not set on the USIM, a UE in Automatic Mode shall make periodic attempts to look for a higher priority PLMN including associated Access Technology of the same country as the currently received PLMN including associated Access Technology or for a higher priority PLMN including associated Access Technology that uses a Shared MCC (e.g. MCC=901). If the currently received PLMN including associated Access Technology uses a Shared MCC, also a higher priority PLMN including associated Access Technology using any non-Shared MCC shall be considered. For the ranking of PLMNs the UE shall use the order used in clause 3.2.2.2. In the case that there is no associated Access Technology identifier, the mobile shall assume that all Access Technologies provided by a PLMN are of equal priority. Moreover, periodic network selection shall not lead to change of access technology within the registered PLMN.
When a Disaster Condition is applicable, a UE in Automatic Mode that is registered to a PLMN in the "Forbidden PLMN" data field in the SIM/USIM may make periodic attempts to look for an allowable PLMN of the same country as the currently received PLMN.
In the case that the UE has stored a list of equivalent PLMNs, the UE shall only select a PLMN if it has a higher priority than all the PLMNs, in the list of equivalent PLMNs, which are of the same country as the currently registered PLMN.
NOTE 1: In the context of this 3GPP TS, the term country is to be interpreted not as a political entity but as a single Mobile Country Code (MCC). For example the USA and India have multiple MCC. Such cases are in fact treated as exceptions in the 3GPP specifications. For all other countries, multiple MCCs may be used, however the specifications have not taken this into account and there could be adverse effects such as the UE being unable to detect that multiple MCCs are within the same country.
NOTE 2: There are some situations where one MCC represents multiple political entities or where an MCC is independent of political entities. Examples include Shared MCCs, where international satellite operations typically use the Shared MCC with value 901.
NOTE 3: For the purposes of PLMN selection, the associated Access Technology using a Shared MCC is restricted to the satellite NG-RAN.
In the case that there are multiple EHPLMNs available, the UE shall not attempt to select a higher priority EHPLMN when an EHPLMN has already been selected. The priorities of EHPLMNs are only applicable when the UE is on a VPLMN and multiple EHPLMNs are available.
The UE shall only make reselection attempts while in idle mode. In case of GPRS terminals, the UE shall only make reselection attempts while in Idle or Stand-by mode. In case of terminals operating E-UTRA and/or NR, the UE shall only make reselection attempts while in Idle or RRC-Inactive mode.
In the case of a UE receiving an eMBMS transport service when in idle mode, the UE may postpone the higher priority PLMN search and any reselection attempt until the eMBMS transport service has finished or been stopped.
The interval between attempts shall be stored in the SIM/USIM.
Only the service provider shall be able to select for which of the previous situations, periodic network selection shall be attempted and to set the interval value.
For UEs supporting only Access Technologies other than the following: NB-IoT, GERAN EC-GSM-IoT and Category M1 [17] of E-UTRAN enhanced-MTC the UE shall interpret the interval value to be between 6 minutes and 8 hours, with a step size of 6 minutes.
For UEs only supporting any of the following, or a combination of, NB-IoT, GERAN EC-GSM-IoT [18], and Category M1[13] of E-UTRAN enhanced-MTC, the UE shall interpret the interval value to be between 2 and 240 hours, with a step size of 2 hours between 2 and 80 hours and a step size of 4 hours between 80 and 240 hours.
For UEs supporting a combination of IoT and non-IoT Access Technologies the UE shall interpret the interval value to determine the timer value as above based on the Access Technology currently in use by the UE.
A different interval value may be applied to entries listed in the “Operator Controlled Lower Selection-priority PLMN Selector with Access Technology” list for UEs performing periodic network selection, if this list is supported by the UE.
One interval value shall be designated to indicate that no periodic attempts shall be made.
In the absence of a permitted value in the SIM/USIM, or the SIM/USIM is phase 1 and therefore does not contain the datafield, then a default value of 60 minutes, shall be used by the UE except for those UEs only supporting any of the following, or a combination of: NB-IoT, GERAN EC-GSM-IoT [18], and Category M1 [17] of E-UTRAN enhanced-MTC. For those UEs a default value of 72 hours shall be used.
NOTE 4: Use of values less than 60 minutes may result in excessive UE battery drain.
Periodic network selection based on Operator controlled signal threshold criteria
If the Operator controlled signal threshold per access technology is set on the USIM, the UE shall perform the periodic network selection procedure considering all PLMNs, of higher or lower priority than the current PLMN, in the same order as in clause 3.2.2.2, with the following conditions:
- the UE shall select a higher priority PLMN/access technology combination if the target PLMN’s access technology signal quality is equal to or higher than the Operator controlled signal threshold per access technology;
- the UE shall select a lower priority PLMN/access technology combination only if the RPLMN’s access technology signal quality is lower than the Operator controlled signal threshold per access technology, and the target PLMN’s access technology signal quality is equal or higher than the Operator controlled signal threshold per access technology.
NOTE 5: The UE does not perform the periodic attempts if the RPLMN is a HPLMN or EHPLMN, and the RPLMN’s access technology signal quality is equal or higher than the Operator controlled signal threshold per access technology.
If no PLMN, including the RPLMN, fulfils the Operator controlled signal threshold criteria, the UE shall perform the normal periodic network selection for higher priority PLMNs (as described above), without applying the Operator controlled signal threshold per access technology.
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 3.2.2.6 Investigation PLMN Scan
| The operator shall be able to control by SIM/USIM configuration whether a UE that is capable shall perform an investigation scan. This investigation scan shall be performed after each successful PLMN selection as well as during limited service state. The investigation scan shall search for a higher prioritised PLMN that does not offer CS voice service. If such a PLMN is available, the user shall be informed. This enables the user to switch to such a PLMN using manual selection if the user so prefers. The investigation scan shall not be performed when no SIM/USIM is inserted.
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 3.2.2.7 Void
| |
a842a011dff727c2a113a15b547b0a48 | 22.011 | 3.2.2.8 Steering Of Roaming
| Steering to a specific VPLMN
It shall be possible for the HPLMN at any time to direct a UE, that is in automatic mode, to search for a specific VPLMN and, if it is available, move to that VPLMN as soon as possible. This VPLMN shall then be regarded as the highest priority VPLMN as defined by the operator, though any EHPLMN or PLMN on the User Controlled PLMN list shall have higher priority. This process shall be done transparently and without inconvenience to the user.
If the Operator controlled signal threshold per access technology is set on the USIM, the UE shall only select the VPLMN if the signal quality is equal to or higher than the Operator controlled signal threshold per access technology, otherwise the steering request shall be ignored.
If the UE is in manual mode, the steering request shall be ignored.
If the UE is registered on a VPLMN that is present on the User Controlled PLMN List, the steering request shall be ignored. PLMNs contained on the User Controlled PLMN List shall have priority over the steered-to-PLMN.
The UE shall attempt to register on the specified VPLMN even if the specified VPLMN is present on a Forbidden List.
This mechanism shall be available to the HPLMN even if the VPLMN the UE is registered on is compliant to an earlier release of the 3GPP specifications.
VPLMN Redirection
It shall be possible for the HPLMN to request a UE, that is in automatic mode, to find and register on a different VPLMN from the one it is currently using or trying to register on, if another VPLMN, that is not in a Forbidden List, is available. The original VPLMN shall then be treated as the lowest priority VPLMN and would not be selected by the UE unless it is the only one available to the UE or has been selected in manual mode. This process shall be done transparently and without inconvenience to the user.
If the UE is in manual mode, the redirection request shall be ignored.
If the UE is registered on a VPLMN that is present on the User Controlled PLMN List, the redirection request shall be ignored.
This mechanism shall be available to the HPLMN even if the VPLMN the UE is registered on is compliant to an earlier release of the 3GPP specifications.
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 3.2.3 Network selection for Multi-mode terminals with 3GPP Capability
| Different types of Multi-mode terminals combining different technologies and systems in one terminal can be produced. It is not possible to foresee all possible configurations and provide a detailed technical specification for network and system selection for all possible multi-mode terminal configurations. The following provides the generic requirements for network and system selection for Multi-mode terminals with 3GPP Capability. These requirements are mandatory for a 3GPP capable multi-mode terminal, unless otherwise is explicitly specified elsewhere in the 3GPP Technical Specifications.
- a multi-mode terminal, when in 3GPP mode of operation shall be compliant to the 3GPP specifications, including PLMN selection, cell selection and re-selection, paging reception etc.,
- As consequence, the multi-mode terminal when entering 3GPP mode of operation shall act as if it were a 3GPP only UE which had just been switched-on. Similarly, when leaving the 3GPP mode of operation the multimode terminal shall act as if it were a 3GPP only UE which had just been switched-off
When the multimode terminal is in 3GPP mode, the switching between modes in the multi-mode terminal is considered an overlay functionality selecting mode of operation. For the design of the overlay functionality the following requirements shall be fulfilled:
- The overlay functionality shall include a mechanism to avoid ping-pong between systems, e.g., a timer or hysteresis function;
- The overlay functionality shall not include network priority mechanisms, which conflict with the network priority mechanisms specified in 3GPP specifications, e.g., the Periodic network selection attempts scanning within 3GPP based systems for PLMNs of higher priority than the current serving PLMN;
- Any functionality in the overlay system, such as background scan of other systems, shall not impact the fulfilment of 3GPP protocol requirements (in particular in regard to paging, cell selection, cell re-selection and PLMN selection);
- As specified in this technical specification, the 3GPP technical specification provides the capability for the user to set their own 3GPP PLMN selection preferences; as well as the user can manually select any 3GPP PLMN. This has been done to ensure a fair competition environment. These principles shall be maintained in the design of the overlay functionality.
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 4 Access control
| |
a842a011dff727c2a113a15b547b0a48 | 22.011 | 4.1 Purpose
| Under certain circumstances, it will be desirable to prevent UE users from making access attempts (including emergency call attempts) or responding to pages in specified areas of a PLMN. Such situations may arise during states of emergency, or where 1 of 2 or more co-located PLMNs has failed.
Broadcast messages should be available on a cell by cell basis indicating the class(es) or categories of subscribers barred from network access.
The use of these facilities allows the network operator to prevent overload of the access channel under critical conditions.
It is not intended that access control be used under normal operating conditions.
It should be possible to differentiate access control between CS and PS domains. Details are specified in TS23.122[3] and TS25.304 [10]. Not all RATs need to support this functionality.
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 4.2 Allocation
| All UEs are members of one out of ten randomly allocated mobile populations, defined as Access Classes 0 to 9. The population number is stored in the SIM/USIM. In addition, UEs may be members of one or more out of 5 special categories (Access Classes 11 to 15), also held in the SIM/USIM. These are allocated to specific high priority users as follows. (The enumeration is not meant as a priority sequence):
Class 15 - PLMN Staff;
-"- 14 - Emergency Services;
-"- 13 - Public Utilities (e.g. water/gas suppliers);
-"- 12 - Security Services;
-"- 11 - For PLMN Use.
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 4.3 Operation
| |
a842a011dff727c2a113a15b547b0a48 | 22.011 | 4.3.1 Access Class Barring
| If the UE is a member of at least one Access Class which corresponds to the permitted classes as signalled over the radio interface, and the Access Class is applicable in the serving network, access attempts are allowed. Additionally, in the case of the access network being UTRAN the serving network can indicate that UEs are allowed to respond to paging and perform location registration (see, sec 3.1), even if their access class is not permitted. Otherwise access attempts are not allowed. Also, the serving network can indicate that UEs are restricted to perform location registration, although common access is permitted. If the UE responded to paging it shall follow the normal defined procedures and react as specified to any network command.
NOTE: The network operator can take the network load into account when allowing UEs access to the network.
Access Classes are applicable as follows:
Classes 0 - 9 - Home and Visited PLMNs;
Classes 11 and 15 - Home PLMN only if the EHPLMN list is not present or any EHPLMN;
Classes 12, 13, 14 - Home PLMN and visited PLMNs of home country only. For this purpose the home country is defined as the country of the MCC part of the IMSI.
Any number of these classes may be barred at any one time.
In the case of multiple core networks sharing the same access network, the access network shall be able to apply Access Class Barring for the different core networks individually.
The following are the requirements for enhanced Access control on E-UTRAN.
- The serving network shall be able to broadcast mean durations of access control and barring rates (e.g. percentage value) that commonly applied to Access Classes 0-9 to the UE. The same principle as in UMTS is applied for Access Classes 11-15;
- E-UTRAN shall be able to support access control based on the type of access attempt (i.e. mobile originating data or mobile originating signalling), in which indications to the UEs are broadcasted to guide the behaviour of UE. E-UTRAN shall be able to form combinations of access control based on the type of access attempt e.g. mobile originating and mobile terminating, mobile originating, or location registration. The ‘mean duration of access control’ and the barring rate are broadcasted for each type of access attempt (i.e. mobile originating data or mobile originating signalling);
- The UE determines the barring status with the information provided from the serving network, and perform the access attempt accordingly. The UE draws a uniform random number between 0 and 1 when initiating connection establishment and compares with the current barring rate to determine whether it is barred or not. When the uniform random number is less than the current barring rate and the type of access attempt is indicated allowed, then the access attempt is allowed; otherwise, the access attempt is not allowed. If the access attempt is not allowed, further access attempts of the same type are then barred for a time period that is calculated based on the ‘mean duration of access control’ provided by the network and the random number drawn by the UE;
- The serving network shall be able to indicate whether or not a UE shall apply Access Class Barring for SMS access attempts in SMS over SGs, SMS over IMS (SMS over IP), and SMS over S102. This indication is valid for Access Classes 0-9 and 11-15;
- The serving network shall be able to indicate whether or not a UE shall apply Access Class Barring for MMTEL voice access attempts. This indication is valid for Access Classes 0-9 and 11-15;
- The serving network shall be able to indicate whether or not a UE shall apply Access Class Barring for MMTEL video access attempts. This indication is valid for Access Classes 0-9 and 11-15.
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 4.3.2 Service Specific Access Control
| Additionally to the above requirements in 4.3.1;
- In E-UTRAN it shall be possible to support a capability called Service Specific Access Control (SSAC) to apply independent access control for telephony services (MMTEL) for mobile originating session requests from idle-mode and connected-mode as following:
- The serving network shall be able to indicate (as specified in sub-clause 4.3.1) whether or not a UE subject to SSAC shall also apply Access Class Barring.
- EPS shall provide a capability to assign a service probability factor [13] and mean duration of access control for each of MMTEL voice and MMTEL video:
- assign a barring rate (percentage) commonly applicable for Access Classes 0-9;
- assign a flag barring status (barred /unbarred) for each Access Class in the range 11-15;
- SSAC shall not apply to Access Class 10;
- SSAC can be provided by the VPLMN based on operator policy without accessing the HPLMN;
- SSAC shall provide mechanisms to minimize service availability degradation (i.e. radio resource shortage) due to the mass simultaneous mobile originating session requests and maximize the availability of the wireless access resources for non-barred services;
- The serving network shall be able to broadcast mean durations of access control, barring rates for Access Classes 0-9, barring status for Access class in the range 11-15 to the UE;
- The UE determines the barring status with the information provided from the serving network, and perform the access attempt accordingly. The UE draws a uniform random number between 0 and 1 when initiating connection establishment and compares with the current barring rate to determine whether it is barred or not. When the uniform random number is less than the current barring rate and the type of access attempt is indicated allowed, then the access attempt is allowed; otherwise, the access attempt is not allowed. If the access attempt is not allowed, further access attempts of the same type are then barred for a time period that is calculated based on the ‘mean duration of access control’ provided by the network and the random number drawn by the UE.
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 4.3.3 Access Control for CSFB
| Access control for CSFB provides a mechanism to prohibit UEs to access E-UTRAN to perform CSFB. It minimizes service availability degradation (i.e. radio resource shortage, congestion of fallback network) caused by mass simultaneous mobile originating requests for CSFB and increases the availability of the E-UTRAN resources for UEs accessing other services.
When an operator determines that it is appropriate to apply access control for CSFB, the network may broadcast necessary information to provide access control for CSFB for each class to UEs in a specific area. The network shall be able to separately apply access control for CSFB, SSAC and enhanced Access control on E-UTRAN.
The following requirements apply for CSFB to 1xRTT:
- In E-UTRAN, the network may apply access control for mobile originating session requests on CSFB from 1xRTT/E-UTRAN UE, The parameters received by the UE are dealt with in accordance with CDMA2000 procedures in 3GPP2 C.S0004-A: "Signaling Link Access Control (LAC) Standard for cdma2000 Spread Spectrum Systems – Addendum 2" [15].
For CSFB to UTRAN or GERAN, the necessary information in the broadcast to provide access control for CSFB is the same as that specified in Clause 4.3.1. In addition to those requirements the following apply:
- Access control for CSFB shall apply for Access Class 0-9 and Access Class 11-15.It shall not apply for Access Class 10;
- Access control for CSFB shall be applied for idle mode UE;
- Access control for CSFB shall apply to all CSFB services;
- Access control for CSFB may be provided by the VPLMN based on operator policy without accessing the HPLMN;
- If Access control for CSFB, according to the UE's access class, disallows originating session requests for CSFB then a UE shall not send mobile originating session requests for CSFB;
- If Access control for CSFB is applied by the UE for a mobile originating session request for CSFB, the UE shall bypass enhanced Access control on E-UTRAN for that session.
- The criteria on which a UE determines whether Access control for CSFB allows or disallows originating session requests for CSFB are equivalent to those for enhanced Access control on E-UTRAN, as described in clause 4.3.1;
- If access is not granted for the UE, mobile originating session requests for CSFB shall be restricted for a certain period of time to avoid overload of E-UTRAN due to continuous mobile originating session requests from the same UE. The duration of the period shall be determined using the same operation specified in Clause 4.3.1;
- In case the network does not provide the Access control for CSFB information, the UE shall be subject to access class barring for Access Classes 0-9 and 11-15 as described in Clause 4.3.1.
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 4.3.4 Extended Access Barring
| |
a842a011dff727c2a113a15b547b0a48 | 22.011 | 4.3.4.1 General
| Extended Access Barring (EAB) is a mechanism for the operator(s) to control Mobile Originating access attempts from UEs that are configured for EAB in order to prevent overload of the access network and/or the core network. In congestion situations, the operator can restrict access from UEs configured for EAB while permitting access from other UEs. UEs configured for EAB are considered more tolerant to access restrictions than other UEs. When an operator determines that it is appropriate to apply EAB, the network broadcasts necessary information to provide EAB control for UEs in a specific area. The following requirements apply for EAB:
• The UE is configured for EAB by the HPLMN;
- EAB shall be applicable to all 3GPP Radio Access Technologies used in EPS or UMTS;
NOTE: When a UE configured for EAB is located in 5G system, the UE is considered as configured for delay tolerant service.
- EAB shall be applicable regardless of whether the UE is in a Home or a Visited PLMN;
- A network may broadcast EAB information;
- EAB information shall define whether EAB applies to UEs within one of the following categories:
a) UEs that are configured for EAB;
b) UEs that are configured for EAB and are neither in their HPLMN nor in a PLMN that is equivalent to it;
c) UEs that are configured for EAB and are neither in the PLMN listed as most preferred PLMN of the country where the UE is roaming in the operator-defined PLMN selector list on the SIM/USIM, nor in their HPLMN nor in a PLMN that is equivalent to their HPLMN.
- EAB information shall also include extended barring information for Access Classes 0-9;
- A UE configured for EAB shall use its allocated Access Class(es), as defined in sub-clause 4.2, when evaluating the EAB information that is broadcast by the network, in order to determine if its access to the network is barred;
- If a UE that is configured for EAB answers to paging, initiates an emergency call or, is a member of an Access Class in the range 11-15 and according to clause 4.3.1 that Access Class is permitted by the network, then the UE shall ignore any EAB information that is broadcast by the network;
- If the network is not broadcasting the EAB information, the UE shall be subject to access barring as described in clause 4.3.1;
- If the EAB information that is broadcast by the network does not bar the UE, the UE shall be subject to access barring as described in clause 4.3.1;
- In the case of multiple core networks sharing the same access network, the access network shall be able to apply the EAB for the different core networks individually.
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 4.3.4.2 Overriding extended access barring
| Overriding Extended Access Barring is a mechanism for the operator to allow UEs that are configured for EAB to access the network under EAB conditions. The following requirements apply:
- The UE configured with EAB may be configured by the HPLMN with a permission to override EAB;
- For a UE configured with the permission to override EAB, the user or application (upper layers in UE) may request the UE to activate PDN connection(s) for which EAB does not apply;
- The UE shall override any EAB restriction information that is broadcast by the network as long as it has an active PDN connection for which EAB does not apply.
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 4.3.5 Application specific Congestion control for Data Communication (ACDC)
| |
a842a011dff727c2a113a15b547b0a48 | 22.011 | 4.3.5.1 Service description
| Application specific Congestion control for Data Communication (ACDC) is an access control mechanism for the operator to allow/prevent new access attempts from particular, operator-identified applications in the UE in idle mode. ACDC does not apply to UEs in connected mode. The network can prevent/mitigate overload of the access network and/or the core network. This feature is optional.
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 4.3.5.2 Requirements
| |
a842a011dff727c2a113a15b547b0a48 | 22.011 | 4.3.5.2.1 General
| The following requirements apply:
- This feature shall be applicable to UTRAN PS Domain and E-UTRAN;
- This feature shall be applicable to UEs in idle mode only that are not a member of one or more of Access Classes 11 to 15;
- ACDC shall not apply to MMTEL voice, MMTEL video, SMS over IMS (SMS over IP) emergency call and paging response;
NOTE 1: Even if any of the above services are initiated by application, ACDC does not apply, but they are subject to other applicable access control methods.
- The home network shall be able to configure a UE with at least four and a maximum of sixteen ACDC categories to each of which particular, operator-identified applications are associated. The categories shall be ordered as specified in sub-clause 4.3.5.2.2;
NOTE 2: Provisioning of the ACDC categories in the UE is the responsibility of the home network, and the categorization is outside the scope of 3GPP.
NOTE 3: A mechanism needs to be provided that enables the UE to verify that the provisioning of the configuration originates from a trusted source.
- The serving network shall be able to broadcast, in one or more areas of the RAN, control information, indicating barring information per each ACDC category, and whether a roaming UE shall be subject to ACDC control;
NOTE 4: The barring information may be similar to ACB information, and include mean durations of access control (i.e., barring timer) and barring rates (i.e., percentage value). If the barring timer is running due to a previous access attempt from an application in a certain given matched ACDC category, the UE may only allow access attempts from applications in higher ACDC categories (according to the corresponding barring information for those higher categories). If the barring timer is running due to a previous access attempt from an application in a certain given unmatched ACDC category or a uncategorised application, the UE may only allow access attempts from applications in higher ACDC categories than the lowest ACDC category broadcast (according to the corresponding barring information for those higher categories).
- The UE shall be able to control whether or not an access attempt for a certain application is allowed, based on this broadcast barring information and the configuration of ACDC categories in the UE;
- The serving network shall be able to simultaneously indicate ACDC with other forms of access control;
- When both ACDC and ACB controls are indicated, ACDC shall override ACB;
- If a UE is configured for both EAB and ACDC, and the serving network simultaneously broadcasts EAB information and ACDC barring information:
- If the UE determines as specified in sub-clause 4.3.4.1 that access to the network is not barred or as specified in sub-clause 4.3.4.2 that it is permitted to override an EAB restriction, then access to the network is subject to ACDC;
- If the UE determines as specified in sub-clause 4.3.4.1 that access to the network is barred and as specified in sub-clause 4.3.4.2 that it is not permitted to override the EAB restriction, then access to the network is barred.
- In the case of multiple core networks sharing the same access network, the access network shall be able to apply ACDC for the different core networks individually. For the mitigation of congestion in a shared RAN, barring rates should be set equal for all Participating Operators.
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 4.3.5.2.2 ACDC Categories
| When configuring the UE with categories of applications, the home network shall proceed as follows:
- Applications whose use is expected to be restricted the least shall be assigned the highest ACDC category; and
- Applications whose use is expected to be restricted more than applications in the highest category shall be assigned the second-to-highest ACDC category, and so on; and
- Applications whose use is expected to be restricted the most shall either be assigned the lowest ACDC category, or not be categorised at all.
For a UE with ACDC categories configured, the applications on the UE that are not assigned to any ACDC category shall be treated by the UE as part of the lowest ACDC category broadcast by the serving network. If the operator requires differentiation with respect to these uncategorized applications, the operator should avoid assigning applications to the lowest ACDC category. When applying ACDC, the serving network broadcasts barring information starting from the highest to the lowest ACDC category. The home network and the serving network may use different categorisation. The serving network decides if ACDC applies to roaming UEs.
The number of ACDC categories in the UE may not be the same as the number of ACDC categories broadcast by the serving network. This may happen, e.g. when the UE is roaming and the number of categories broadcast by the serving network is different from the home network. Therefore, the following rules shall apply:
- If the serving network broadcasts more ACDC categories than the UE's configuration, the UE shall use barring information for the matching ACDC category and shall bar uncategorised applications using the barring information for the lowest category broadcast by the serving network, and shall ignore barring information for unmatched categories.
- If the serving network broadcasts barring information for fewer ACDC categories than the UE's configuration, the UE shall use barring information for the matching ACDC category and shall bar other applications using the barring information for the lowest category broadcast by the serving network.
NOTE: A matching ACDC category is an ACDC category for which barring information is broadcast by the serving network and that has the same rank as the rank of a configured ACDC category in the UE. An unmatched ACDC category is either an ACDC category for which barring information is broadcast by the serving network but with no corresponding ACDC category configured in the UE, or an ACDC category configured in the UE but with no corresponding barring information broadcast by the serving network.
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 4.3.6 Access Control for Indirect 3GPP Communications
| For the case where an Evolved ProSe Remote UE is trying to access the network via an Evolved ProSe UE-to-Network Relay, the following requirements apply:
- Access control for CSFB shall not apply to an Indirect 3GPP Communication;
- ACB, EAB and ACDC shall apply when the Evolved ProSe UE-to-Network Relay is in IDLE mode and when the access control information for the respective access control is broadcast by the network;
- SSAC shall apply when the Evolved ProSe UE-to-Network Relay is either in IDLE or CONNECTED mode and when the access control information for SSAC is broadcast by the network;
- The interaction between ACDC, EAB and ACB (defined in paragraph 4.3.5.2.1) shall be based on the Evolved ProSe Remote UE’s configuration;
- During the access control procedure, the requirements in subsections of 4.3.1, 4.3.2, 4.3.4 and 4.3.5 shall be performed by Evolved Prose Remote UE using the following parameters:
- Access control parameters broadcast by the cell where the Evolved ProSe UE-to-Network Relay is camped on or connected to shall be used in all access control procedures;
- Access Class of the Evolved ProSe Remote UE shall be used;
- For ACB, the type of access attempt (i.e. mobile originating data, mobile originating signalling, response to paging or emergency call) of the Evolved ProSe Remote UE shall be used;
- For EAB, the following information shall be used:
- Whether or not the Evolved ProSe Remote UE is configured with EAB;
- Whether or not the Evolved ProSe Remote UE is configured with a permission to override EAB;
- Whether the PLMN is the Evolved ProSe Remote UE’s Home PLMN, equivalent PLMN or preferred PLMN. The PLMN where the Evolved ProSe UE-to-Network Relay is camped/connected shall be used to make this determination.
- For SSAC, the type of access attempt (MMTEL voice or MMTEL video) of the Evolved ProSe Remote UE shall be used;
- For ACDC, the ACDC category of the application that triggered the access attempt in the Evolved ProSe Remote UE shall be used.
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 4.4 Emergency Calls
| An additional control bit known as "Access Class 10" is also signalled over the radio interface to the UE. This indicates whether or not network access for Emergency Calls is allowed for UEs with access classes 0 to 9 or without an IMSI. For UEs with access classes 11 to 15, Emergency Calls are not allowed if both "Access class 10" and the relevant Access Class (11 to 15) are barred. Otherwise, Emergency Calls are allowed.
4.4a Multimedia Priority Service
Multimedia Priority Service (TS 22.153 [16]) shall be assigned its own unique access class value (i.e., one of the special access classes 11 to 15). The assigned access class value for Multimedia Priority Service is based on regional/national regulatory requirements and operator policy.
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 4.5 Control of UE Capabilities
| To protect the user from the effects of a misbehaving UE (e.g. causing additional charges, degraded performance) and to protect the network operator's network capacity, including radio resources and network signalling and processing, means shall be provided for the HPLMN/EHPLMN and the VPLMN to provide an indication to the UE as to which network provided services or functions it is not allowed to use.
The Selective UE Capabilities list shall be maintained in the UE and the UE shall not request any services indicated as disabled. At registration the HPLMN/EHPLMN or VPLMN may interrogate the status of the list and provide a new list.
The Selective UE Capabilities list shall not be deleted at switch off and will remain valid until a new list is provided by the network. The Selective UE Capabilities list relates to the ME and not to the subscription.
It should be ensured that UEs are not maliciously disabled, including malicious disabling by a VPLMN, or accidentally disabled, or kept disabled, and there shall be a mechanism for restoring disabled UEs in all situations (e.g. in the case that the serving network does not support the control of UE Capabilities).
The UE should use the indications given in the Selective UE Capabilities list to inform the user of the non-availability of services or functions.
There shall be a means for the network to provide an optional customer service number(s) which can be used, by the user, to assist in determining the cause of non-availability of specific services. The specifications should also provide the capability for the network to include an optional text string that will be displayed by the UE.
The UE Capabilities list shall take precedence over subscribed services.
The services to be included in the list are:
- Call Control functions;
- Supplementary Services;
- Emergency Calls (including the (U)SIM-less case and subject to regional regulatory requirements, i.e. emergency calls shall not be disabled in regions where support of them is required);
- SMS, via CS and PS;
- LCS, via CS and PS;
- GPRS based services;
- MBMS;
- IMS.
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 4.6 Prevention of mobile-originating signalling and/or data traffic
| The network shall be able to control the behavior of UEs in E-UTRAN in connected mode to prevent mobile originating signalling and/or data traffic, while the access barring mechanisms specified under Clause 4.3 are being applied to UEs in idle mode.
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 5 Support of Localised Service Area (SoLSA)
| SoLSA consists of a set of service features that give the operator a basis to offer subscribers different services (e.g. tariffs or access rights) depending on the location of the subscriber. (3GPP TS 22.043 [5]). The following section is only applicable to the support of SoLSA functionality in GERAN.
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 5.1 Network selection
| The standard automatic and manual network selection procedures will be used.
Manual network selection may be required when the PLMN providing the users SoLSA service is not the one on which the user is currently registered.
At manual network selection the UE shall provide the means to present the subscribers LSA(s) for each PLMN presented.
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 5.2 The Idle-mode operation
| The UE shall always select a valid LSA with the highest priority.
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 5.2.1 Subscriber moving from a normal environment to his localised service area
| The UE shall have the ability to prioritise allowed LSA cells in reselection, making it possible to camp on a LSA cell earlier (the function shall be network controlled).
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 5.2.2 Subscriber moving away from his localised service area to a normal environment
| The UE shall have the ability to prioritise allowed LSA cells in reselection, making it possible to camp on a LSA cell longer (the function shall be network controlled).
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 5.2.3 Subscriber staying in his localised service area
| The UE shall have the ability to prioritise allowed LSA cells in reselection by being more persistent (the function shall be network controlled).
NOTE: Typically in indoor environments there are occasional reflections and "disturbances" due to macro cells, e.g. near the windows. In such a case LSA cells should be favoured even though there is higher field strength available from the outdoor cells.
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 5.3 LSA only access
| It shall be possible to allow LSA user to access PLMN only within his LSAs. A LSA user is not allowed to receive and/or originate a call outside the allowed LSA area.
When UE is out of the allowed LSA area it shall be registered in PLMN but indicate subscriber/service specific "out of LSA area" notification. It shall be a network-controlled function to prevent terminated or/and originated calls. Emergency calls are however always allowed.
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 5.4 Exclusive access
| Access to exclusive access cells is restricted to defined LSA subscribers.
Non-LSA subscriber shall consider exclusive access cells as not suitable, only allowing to camp for emergency calls (limited service state 3GPP TS 23.122 [3]).
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 5.5 Preferential access
| As a network-controlled function, it shall be possible in LSA to allocate resources at call setup and during the active mode to LSA users compared to non-LSA users.
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 6 Support of 3GPP - WLAN Interworking
| Support of 3GPP-WLAN interworking and network selection is captured in TS 22.234 [6]
NOTE: The requirement specification 22.234 is no longer maintained from Release 12 onwards.
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 6.1 Void
| |
a842a011dff727c2a113a15b547b0a48 | 22.011 | 6.2 Void
| |
a842a011dff727c2a113a15b547b0a48 | 22.011 | 6.3 Void
| 7 Administrative restriction of subscribers’ access
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 7.1 Allowed Location and Routing Area identities access
| Means shall be standardised for an administrative restriction of subscribers’ access without the need of having explicit Tracking/Location/Routing Area identities in the individual subscription profiles.
To achieve this it shall be possible to indicate per subscriber, in subscription data, allowed categories of Tracking/ Location/Routing Areas. It shall be possible to use this subscription information to restrict subscribers’ access to categories of Tracking/Location/Routing Areas in serving networks accordingly.
As a minimum, at least one of the following categories shall be available:
a) GERAN;
b) UTRAN;
c) E-UTRAN;
d) NG-RAN.
There might be cases where the visited network has not separated the Location/Routing area categories, in which case the administrative restriction of subscribers' access to only GERAN or UTRAN will not be possible.
In EPS, an operator may introduce subscriptions supporting the 5G NR Dual Connectivity in E-UTRAN. It shall be possible to indicate in subscription data that a subscriber´s access to the 5G NR Dual Connectivity in E-UTRAN service is restricted.
This administrative restriction of subscribers’ access shall be an optional feature.
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 7.2 Void
| |
a842a011dff727c2a113a15b547b0a48 | 22.011 | 7.3 UE configured radio technology restriction
| A UE shall support a Man Machine Interface setting for the user to disable use of one or more of the UE’s radio technologies, regardless of PLMNs. Radio technologies that individually can be disabled is dependent on supported radio technology of the UE such as GSM/EDGE, WCDMA, E-UTRA, and NR.
A UE shall support a Man Machine Interface setting enabling the user to re-enable use of one or more of the ME’s radio technologies for access to a radio access network, regardless of PLMNs. The user can only re-allow a radio technology that the user has previously disallowed.
NOTE: The described MMI user setting is a proprietary function of most legacy UE products to allow a user of a UE to change the radio capabilities of the UE. Legacy radio technologies may lack means to mitigate some security attack. If severe enough, the home operator may want to disallow their subscribers to access a radio access network with such radio technology. This configuration of the UE is valid for all PLMNs.
A UE shall support a secure mechanism for the home operator to disallow selection of one or more of the UE’s radio technologies for access to a radio access network, regardless of PLMNs. Radio technologies that individually can be disallowed are at least GSM/EDGE, WCDMA, E-UTRA, and NR.
A UE shall support a secure mechanism for the home operator to re-allow selection of one or more of the UE’s radio technologies for access to a radio access network, regardless of PLMNs. Radio technologies that individually can be re-allowed are at least GSM/EDGE, WCDMA, E-UTRA, and NR. The home operator can only re-allow a radio technology that the home operator has previously disallowed.
For a prioritized service (e.g., Emergency Services, MPS, Mission Critical Services), the UE shall support a mechanism to automatically override user and network disallowed RATs when there are no PLMNs on the allowed radio technologies identified that the UE is able to access.
Upon power-cycle or when the USIM is disabled, the UE configuration of enabled/disabled radio technologies configured by the user shall remain as it was before such events happen. The radio technologies disallowed by the HPLMN shall remain as it was before a power cycle. The radio technologies disallowed by the HPLMN shall be bound to the USIM
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 8 Support of Home NodeB and Home E-NodeB
| The service requirements for Home NodeB and Home eNodeB can be found in [14].
9 Control of traffic from UE-based applications toward associated server
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 9.1 Description
| This feature allows operators to control traffic from UEs to an application on a third-party server or the third-party server itself. When an application on a third-party server or the third-party server itself becomes congested or fails the traffic towards that server need to be controlled to avoid/mitigate potential issues caused by resulting unproductive use of 3GPP network resource. This will also make it possible to allow 3GPP network to help third party servers to handle overload and recover from failures (see [7]).
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 9.2 Requirements
| Under network control, the UE shall be able to control (i.e. block and/or prioritize) traffic from UEs to an application on a third-party server or the third-party server itself without affecting traffic to other applications on the third-party server or to other third-party servers.
For this purpose, the UE shall be able to identify the traffic towards the third-party server or the application on the third-party server.
When congestion or failure of the application on the third-party server or the third-party server abates, the control shall be applied in a phased manner to gradually restore traffic according to operator policy.
This feature and other forms of access control shall be able to be applied simultaneously.
In case of simultaneous application of ACDC and this feature, this feature shall take precedence over ACDC to control traffic from applications in the UE, only when such traffic is allowed by ACDC.
This feature shall be applicable both to new connections being set up and to existing connections from the UE towards an application on a third-party server or the third-party server.
10 3GPP PS Data Off
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 10.1 Description
| 3GPP PS Data Off is a feature which, when configured by the HPLMN and activated by the user, prevents transport via PDN connections or PDU sessions in 3GPP access networks of all data packets except IP packets required by 3GPP PS Data Off Exempt Services.
|
a842a011dff727c2a113a15b547b0a48 | 22.011 | 10.2 Requirements
| The 3GPP system shall provide a mechanism by which an operator can configure which operator services are defined as 3GPP PS Data Off Exempt Services for their own subscribers.
When 3GPP PS Data Off is activated in the UE, in order to preserve charging consistency:
- the UE shall inform the network that 3GPP PS Data Off is activated;
- the UE shall cease the sending of uplink IP Packets of all services that are not 3GPP PS Data Off Exempt Services via PDN connections in 3GPP access networks;
- the network shall cease the sending of downlink IP Packets to the UE for all services that are not 3GPP PS Data Off Exempt Services via PDN connections in 3GPP access networks;
- the UE shall cease the sending of uplink traffic over non-IP PDN types via PDN connections in 3GPP access networks; and
- the network shall cease the sending of downlink traffic over non-IP PDN types via PDN connections in 3GPP access networks;
- the UE shall cease the sending of uplink IP packets of all services that are not 3GPP PS data Off Exempt Services via PDU sessions in 3GPP access networks;
- the network shall cease the sending of downlink IP packets to the UE for all services that are not 3GPP PS data Off Exempt Services via PDU sessions in 3GPP access networks;
- the UE shall cease the sending of uplink unstructured and ethernet data via PDU sessions in 3GPP access networks;
- the network shall cease the sending of downlink unstructured and ethernet data via PDU sessions in 3GPP access networks.
NOTE 1: Disabling of traffic on both the uplink and downlink is needed in order to provide consistency of charging between HPLMN and VPLMN, as well as consistency between what the user expects and what the user may be billed for.
Each of the following operator services shall be configurable by the HPLMN operator to be part of the 3GPP PS Data Off Exempt Services:
- MMTel Voice;
- SMS over IMS;
- USSD over IMS (USSI);
- MMTel Video;
- Services over IMS Data Channel;
- Particular IMS services not defined by 3GPP, where each such IMS service is identified by an IMS communication service identifier;
- Device Management over PS;
- Management of USIM files over PS (e.g. via Bearer Independent Protocol); and
- IMS Supplementary Service configuration via the Ut interface using XCAP.
- User plane location services protocol (LCS-UPP).
NOTE 1a: IMS Data Channel is defined in 3GPP TS 26.114[20].
NOTE 1b: Services over IMS Data Channel are treated as a whole to be exempt or not to be exempt. Usage of individual applications on the data channel can be controlled by operators when the PS Data Off Exempt of services over IMS Data Channel is on.
NOTE 1c: 3GPP PS Data Off Exempt for LCS-UPP in roaming is subject to agreement between operators.
3GPP PS Data Off may be activated based on roaming status, and the HPLMN may configure up to two sets of 3GPP PS Data Off Exempt Services for its subscribers: one is used when in HPLMN and another when roaming.
NOTE 2: The updating to the sets of configured 3GPP Data Off Exempt Services in the VPLMNs and HPLMN is not guaranteed to take effect in real time. The updating to the sets of configured 3GPP Data Off Exempt Services in the UEs is not guaranteed take effect in real time.
The user should be made aware of the operator services that are 3GPP PS Data Off Exempt Services.
NOTE 3: The system can support falling back to operate over the CS domain in case an operator service is not configured to be a 3GPP PS Data Off Exempt Service and an equivalent CS domain operator service exists for the operator service.
Annex A (informative):
Change history
Change history
TSG SA#
SA Doc.
SA1 Doc
Spec
CR
Rev
Rel
Cat
Subject/Comment
Old
New
Work Item
Jun 1999
02.04
Transferred to 3GPP SA1
7.0.0
3.0.0
SA#04
02.04
3.0.0
SP-05
SP-99479
S1-99610
22.011
0001
R99
D
Editorial changes for alignment
3.0.0
3.0.1
SP-06
SP-99524
S1-991032
22.011
0002
R99
B
COMPACT Cell Selection Part 2
3.0.1
3.1.0
SP-06
SP-99606
22.011
0003
1
R99
B
Network Selection
3.0.1
3.1.0
SP-06
SP-99607
22.011
0004
1
R99
B
Control of user preference field
3.0.1
3.1.0
SP-07
SP-000055
S1-000138
22.011
0012
R99
F
Corrections to 22.011
3.1.0
3.2.0
SP-07
SP-000055
S1-000139
22.011
0013
R99
C
Removal of "Home Environment Specific Network Selection Procedure"
3.1.0
3.2.0
SP-07
SP-000071
S1-000161
22.011
0014
R00
B
Network Selection
3.1.0
4.0.0
SP-08
SP-000211
S1-000335
22.011
0016
R00
B
Reselection attempts of GPRS terminals
4.0.0
4.1.0
SP-09
SP-000372
S1-000549
22.011
0018
R4
F
Alignment with 23.122 on selection procedure
4.1.0
4.2.0
SP-11
SP-010036
S1-010245
22.011
0021
Rel-4
A
CR to 02.11 on Roaming restrictions for GPRS (Release4)
4.2.0
4.3.0
GPRS
SP-11
SP-010151
22.011
0023
Rel-4
A
Equivalent handling of PLMNs with different PLMN codes
4.2.0
4.3.0
GSM / UMTS inter-working
SP-12
SP-010244
S1-010495
22.011
0025
Rel-4
A
Partial PLMN access restriction
4.3.0
4.4.0
SP-12
SP-010244
S1-010514
22.011
0027
Rel-4
A
Periodic Network Selection Attempt improvement
4.3.0
4.4.0
SP-12
SP-010244
S1-010517
22.011
0029
Rel-4
A
Default value for background scanning timer
4.3.0
4.4.0
SP-14
SP-010685
S1-011341
22.011
0031
Rel-4
A
CR to 22.011 R4 'Interaction between equivalent PLMN list and periodic network selection attempts'
4.4.0
4.5.0
SP-14
SP-010684
S1-011334
22.011
0035
Rel-4
A
CR to 22.011 R4 'Editorial improvements'
4.4.0
4.5.0
SP-14
SP-010688
S1-011336
22.011
0037
Rel-4
A
CR to 22.011 R4 'Clarification on the UE behaviour when receiving a registration rejection'
4.4.0
4.5.0
SP-14
SP-010687
S1-011338
22.011
0039
Rel-4
A
CR to 22.011 R4 'Simplification of the procedure for user PLMN reselection'
4.4.0
4.5.0
SP-14
SP-010686
S1-011339
22.011
0041
Rel-4
A
CR to 22.011 R4 'Interaction between “equivalent PLMN” list and “Forbidden PLMN” list'
4.4.0
4.5.0
SP-14
SP-010757
---
22.011
0042
2
Rel-4
A
Interaction between ePLMN and manual mode
4.4.0
4.5.0
SP-15
SP-010158
---
22.011
0045
1
Rel-4
A
CR to 22.011 Rel-4: clarification of the term 'country'
NOTE: special dispensation was given by SA #15 to allow some leeway on the position of the note.
4.5.0
4.6.0
SP-16
SP-020238
S1-021058
22.011
0046
Rel-4
F
Editorial corrections on 22.011
4.6.0
4.7.0
CORRECT
SP-16
SP-020267
S1-021043
22.011
Rel-5
Updated from Rel-4 to Rel5
4.7.0
5.0.0
SP-17
SP-020547
S1-021826
22.011
0049
Rel-5
A
CR to 22.011 Rel 5 - correction to periodic PLMN scan
5.0.0
5.1.0
TEI4
SP-19
SP-030035
S1-030236
22.011
0050
-
Rel-6
B
Netshare CR to TS 22.011
5.1.0
6.0.0
NTShar-CR
SP-20
SP-030249
S1-030504
22.011
0051
Rel-6
B
Network Selection requirements for WLAN Interworking
6.0.0
6.1.0
WLAN-CR
SP-20
SP-030248
S1-030532
22.011
0052
Rel-6
B
Network selection in shared networks
6.0.0
6.1.0
NTshar-CR
SP-22
SP-030774
-
22.011
0053
1
Rel-6
B
Administrative restriction of subscribers’ access
6.1.0
6.2.0
TEI
SP-23
SP-040088
S1-040200
22.011
0054
-
Rel-6
C
Periodic network selection attempts enhancement
6.2.0
6.3.0
TEI
SP-23
SP-040089
S1-040257
22.011
0056
-
Rel-6
F
Priority usage of UICC parameters for I-WLAN
6.2.0
6.3.0
WLAN
SP-23
SP-040101
S1-040260
22.011
0057
-
Rel-6
D
Extraction of redundant WLAN network selection information [– now in WLAN TS22.234]
6.2.0
6.3.0
WLAN
SP-24
SP-040287
S1-040438
22.011
0058
-
Rel-6
F
Behaviour of Single Mode mobiles with regards to the use of access technology in the PLMN selector lists
6.3.0
6.4.0
TEI6
SP-24
SP-040287
S1-040442
22.011
0060
-
Rel-6
F
Use of access technology in Periodic Network Selection attempts
6.3.0
6.4.0
TEI6
SP-24
SP-040287
S1-040443
22.011
0061
-
Rel-6
F
Clarification on the use of the RAT during network selection
6.3.0
6.4.0
TEI6
SP-24
SP-040295
S1-040526
22.011
0064
-
Rel-6
F
Priority usage of UICC parameters for I-WLAN
6.3.0
6.4.0
WLAN-CR
SP-24
SP-040299
S1-040445
22.011
0062
-
Rel-7
F
Multimode terminals with 3GPP capability
6.3.0
7.0.0
TEI7
SP-24
SP-040298
S1-040448
22.011
0063
-
Rel-7
B
Support of multiple HPLMN codes
6.3.0
7.0.0
TEI7
SP-27
SP-050063
S1-050233
22.011
0066
-
Rel-7
B
Addition of "Network Control of UE Capabilities"
7.0.0
7.1.0
Network Protection
SP-27
SP-050063
S1-050245
22.011
0067
-
Rel-7
B
Reinstate CR016 for GPRS Terminal PLMN Reselection
7.0.0
7.1.0
TEI-4
SP-29
SP-050521
S1-050903
22.011
0068
-
Rel-7
C
Enhancement of the EHPLMN feature to allow load balancing
7.1.0
7.2.0
TEI7
SP-31
SP-060221
-
22.011
0069
2
Rel-7
C
The Last RPLMN
7.2.0
7.3.0
NSP-CR
SP-31
SP-060033
S1-060330
22.011
0070
-
Rel-7
B
Confirmed Roaming
7.2.0
7.3.0
NSP-CR
SP-31
SP-060033
S1-060331
22.011
0071
-
Rel-7
F
Capability of UE to read USIM information for Network Selection
7.2.0
7.3.0
NSP-CR
SP-31
SP-060033
S1-060332
22.011
0072
-
Rel-7
C
Displaying all available EHPLMNs in Manual Mode
7.2.0
7.3.0
NSP-CR
SP-31
SP-060033
S1-060333
22.011
0073
-
Rel-7
B
Requirement for presentation of additional information in manual mode
7.2.0
7.3.0
NSP-CR
SP-31
SP-060033
S1-060335
22.011
0074
-
Rel-7
B
Network selection mode at switch-on
7.2.0
7.3.0
NSP-CR
SP-31
SP-060033
S1-060352
22.011
0075
-
Rel-7
B
Steering of Roaming
7.2.0
7.3.0
NSP-CR
SP-32
SP-060311
S1-060630
22.011
0076
-
Rel-7
C
Clarification on confirmed roaming applicability
7.3.0
7.4.0
NSP-CR
SP-32
SP-060311
S1-060632
22.011
0077
-
Rel-7
C
Incomplete PLMN list for manual mode information
7.3.0
7.4.0
NSP-CR
SP-32
SP-060426
-
22.011
0078
1
Rel-7
C
Exception in Manual network selection mode when HPLMN is available at power-on
7.3.0
7.4.0
NSP-CR
SP-32
SP-060451
S1-060649
22.011
0079
3
Rel-7
C
Interaction of steering of roaming with User controlled and forbidden PLMN list
7.3.0
7.4.0
NSP-CR
SP-34
SP-060762
S1-061314
22.011
0080
-
Rel-7
F
Additional Information in Manual Mode
7.4.0
7.5.0
NSP-CR
SP-35
SP-070119
S1-070182
22.011
0081
1
Rel-7
F
Removal of "Confirmed Roaming" enhancement (section 3.2.2.7)
7.5.0
7.6.0
NSP-CR
SP-35
SP-070119
S1-070294
22.011
0083
2
Rel-7
C
Single EHPLMN Display Name in Manual Mode (CR to 22.011)
7.5.0
7.6.0
NSP-CR
SP-35
SP-070129
S1-070285
22.011
0082
2
Rel-8
C
Administrative restriction of subscribers’ access
7.6.0
8.0.0
SAE-R
SP-36
SP-070474
22.011
0085
-
Rel-8
A
Clarification on User Controlled PLMNs in SoR
8.0.0
8.1.0
NSP-CR
SP-38
SP-070855
S1-071842
22.011
0091
-
Rel-8
C
EPS Alignment - References and Definitions
8.1.0
8.2.0
AIPN-SAE-R
SP-38
SP-070855
S1-071910
22.011
0092
1
Rel-8
C
EPS Alignment - 3.2.2 Procedures
8.1.0
8.2.0
AIPN-SAE
SP-38
SP-070855
S1-071911
22.011
0093
1
Rel-8
C
EPS Alignment - 7 Administrative restriction of subscribersÆ access
8.1.0
8.2.0
AIPN-SAE
SP-38
SP-070855
S1-071925
22.011
0099
1
Rel-8
B
Additional requirement for location registration
8.1.0
8.2.0
AIPN-SAE
SP-38
SP-070859
S1-071943
22.011
0098
2
Rel-8
F
Correction to EHPLMN terminology and editorials
8.1.0
8.2.0
TEI8
SP-38
SP-070913
-
22.011
0090
2
Rel-8
A
EHPLMN case added to the optimisation for automatic network selection
8.1.0
8.2.0
NSP-CR
SP-38
SP-070934
-
22.011
0095
2
Rel-8
F
DSAC requirement in UMTS
8.1.0
8.2.0
TEI8
SP-38
SP-070942
-
22.011
0094
4
Rel-8
B
PPAC requirement
8.1.0
8.2.0
PPACR
SP-39
SP-080026
S1-080155
22.011
0101
1
Rel-8
A
EHPLMN recovery lack of coverage
8.2.0
8.3.0
NSP-CR
SP-39
SP-080034
S1-080351
22.011
0102
2
Rel-8
B
HNB/HeNB - Closed Subscriber Group (CSG) definitions for UTRA and E-UTRA
8.2.0
8.3.0
HomeNB
SP-39
SP-080042
S1-080326
22.011
0107
1
Rel-8
C
basic access control enhancement for EPS
8.2.0
8.3.0
AIPN-SAE
SP-39
SP-080041
S1-080331
22.011
0108
1
Rel-8
C
Barring of inbound roamers of previous release networks from E-UTRAN
8.2.0
8.3.0
TEI8
SP-39
SP-080188
-
22.011
0109
4
Rel-8
B
HNB/HeNB - Closed Subscriber Group (CSG) requirements for UTRA and E-UTRA
8.2.0
8.3.0
HomeNB
SP-40
SP-080301
S1-080655
22.011
0114
1
Rel-8
D
Delete CSGs related access restriction requirements
8.3.0
8.4.0
HomeNB
SP-40
SP-080301
S1-080656
22.011
0115
2
Rel-8
F
Introduction of length for HNBID
8.3.0
8.4.0
HomeNB
SP-40
SP-080301
S1-080767
22.011
0116
3
Rel-8
F
HNB/HeNB - Closed Subscriber Group (CSG) requirements for UTRA and E-UTRA
8.3.0
8.4.0
HomeNB
SP-40
SP-080432
-
22.011
0117
3
Rel-8
F
Relation between EPS Services and GPRS Services
8.3.0
8.4.0
SAE
SP-40
SP-080301
S1-080663
22.011
0118
-
Rel-8
C
Removal of GERAN - E-UTRAN connected mode handover requirement from HeNB
8.3.0
8.4.0
HomeNB
SP-40
SP-080453
-
22.011
0119
4
Rel-8
C
PPAC restriction to UTRAN
8.3.0
8.4.0
PPACR
Corrects typos in previous line of history table.
8.4.0
8.4.1
SP-41
SP-080493
S1-082333
22.011
0122
2
Rel-8
F
Correction on definition of length for HNBID
8.4.1
8.5.0
HomeNB
SP-41
SP-080493
S1-082354
22.011
0120
2
Rel-8
F
Essential correction to manual CSG selection
8.4.1
8.5.0
HomeNB
SP-41
SP-080493
S1-082389
22.011
0123
2
Rel-8
F
Additional HNB/HeNB operator requirements
8.4.0
8.5.0
HomeNB
SP-41
SP-080493
S1-082393
22.011
0128
2
Rel-8
F
Terminology alignment and generalization of requirements
8.4.1
8.5.0
HomeNB
SP-42
SP-080771
S1-083443
22.011
132
2
Rel-8
F
Correction to the maximum limit requirement of CSG members
8.5.0
8.6.0
HomeNB
SP-42
SP-080771
S1-083250
22.011
0133
1
Rel-8
F
HNB/HeNB and pre-release 8 USIM
8.5.0
8.6.0
HeNB
SP-42
SP-080773
S1-083380
22.011
0134
1
Rel-8
F
PPAC CR alignment with CT1
8.5.0
8.6.0
PPAC
SP-42
SP-080771
S1-084409
22.011
0137
2
Rel-8
F
Correction of HNB/HeNB display requirements and manual CSG selection
8.5.0
8.6.0
HomeNB
SP-42
SP-080874
S1-084408
22.011
0139
2
Rel-8
C
Home network independent support of roamers in CSG
8.5.0
8.6.0
HomeNB
SP-42
SP-080771
S1-084410
22.011
0140
1
Rel-8
B
HNB mobility
8.5.0
8.6.0
HomeNB
SP-42
SP-080785
S1-084389
22.011
0136
2
Rel-9
B
SSAC Services Specific Access Control Requirements
8.6.0
9.0.0
SSACR
SP-43
SP-090195
S1-090161
22.011
0142
1
Rel-9
D
Removing the content of chapter 8 and add a reference instead.
9.0.0
9.1.0
EHNB
SP-45
SP-090669
-
22.011
0156
1
Rel-9
F
Description Alignment of Access Class Barring for E-UTRAN with Stage 3
9.1.0
9.2.0
TEI9
SP-46
SP-090841
S1-094330
22.011
0158
1
Rel-9
F
Alignment between SSAC and Common AC
9.2.0
9.3.0
SSAC
SP-48
SP-100442
S1-101221r
22.011
0161
4
Rel-10
B
Access control for CSFB
9.3.0
10.0.0
TEI10
SP-49
SP-100580
S1-102153
22.011
0166
-
Rel-10
F
Clarification on roaming in shared networks
10.0.0
10.1.0
TEI10
SP-49
SP-100580
S1-102178
22.011
0163
1
Rel-10
F
Clarification of ACB for CSFB
10.0.0
10.1.0
TEI10
SP-49
SP-100580
S1-102178
22.011
0163
1
Rel-10
F
Clarification of ACB for CSFB
10.0.0
10.1.0
TEI10
SP-50
SP-100893
S1-103336
22.011
0168
12
Rel-10
B
Access Control for Machine Type Communications
10.1.0
10.2.0
NIMTC
SP-50
SP-100805
S1-103328
22.011
0171
-
Rel-10
F
Clarification of Access Class Barring for CSFB
10.1.0
10.2.0
TEI10
-
LTE logo changed into LTE Advanced logo
10.2.0
10.2.1
-
SP-51
SP-110162
S1-110409
22.011
0175
3
Rel-10
F
Clarifications for Extended Access Barring
10.2.1
10.3.0
NIMTC
SP-52
SP-110374
S1-111118
22.011
0181
-
Rel-11
F
Clarification on applicability of EAB
10.3.0
11.0.0
SIMTC
SP-52
SP-110374
S1-111376
22.011
0178
2
Rel-11
B
Clarification on how EAB is applied in Shared Network
10.3.0
11.0.0
SIMTC
SP-53
SP-110582
S1-112243
22.011
0182
2
Rel-11
F
Support of countries with multiple MCC values
11.0.0
11.1.0
TEI11
SP-54
SP-110813
S1-113443
22.011
0186
1
Rel-11
F
Applicability of Access Class Barring in a FULL-MOCN configuration
11.1.0
11.2.0
TEI11
SP-59
SP-130123
S1-131287
22.011
0191
2
Rel-11
F
Overriding extended access barring
11.2.0
11.3.0
TEI11
SP-59
SP-130110
S1-131279
22.011
0194
2
Rel-12
B
Prevention of mobile-originating signalling and/or data traffic of UEs in E-UTRAN in connected mode based on the criteria for the access barring mechanisms
11.2.0
12.0.0
PMOC
SP-63
SP-140064
S1-140057
22.011
200
-
Rel-12
C
Requirement for SSAC in CONNECTED
12.0.0
12.1.0
TEI12
SP-63
SP-140065
S1-140154
22.011
0202
-
Rel-12
B
Prioritization of MO-SMS for ACB
12.0.0
12.1.0
TEI12
SP-63
SP-140065
S1-140329
22.011
0198
5
Rel-12
B
Prioritization of MMTEL for ACB
12.0.0
12.1.0
TEI12
SP-64
SP-140233
S1-141306
22.011
0203
2
Rel-13
B
Access control mechanism for operator-identified applications
12.1.0
13.0.0
ACDC
SP-65
SP-140507
S1-143622
22.011
0206
2
Rel-13
C
Number and usage of ACDC categories
13.0.0
13.1.0
ACDC
SP-65
SP-140523
S1-143484
22.011
0205
1
Rel-13
A
I-WLAN clean up
13.0.0
13.1.0
TEI12
SP-68
SP-150267
S1-151621
22.011
214
2
Rel-13
F
Number of ACDC categories and ACDC in idle mode
13.1.0
13.2.0
ACDC-ST1
SP-68
SP-150270
S1-151546
22.011
213
2
Rel-13
A
Access Class for MPS (Rel-13 Mirror)
13.1.0
13.2.0
ePRIOR-St1
SP-69
SP-150535
S1-152405
22.011
217
1
Rel-13
F
Handling of uncategorized ACDC applications
13.2.0
13.3.0
ACDC
SP-69
SP-150539
S1-152456
22.011
215
1
Rel-14
B
Enhancements for control of traffic from UE-based applications toward associated server
13.2.0
14.0.0
CATS
SP-70
SP-150747
S1-154542
22.011
0225
1
Rel-14
A
Corrections of ACDC Requirements
14.0.0
14.1.0
ACDC-ST1
SP-70
SP-150758
S1-154589
22.011
0224
3
Rel-14
B
Requirements to support a defined set of services when 3GPP PS Data Off is configured by the HPLMN
14.0.0
14.1.0
PS_DATA_OFF
SP-71
SP-160111
S1-160526
22.011
0224
7
Rel-14
B
3GPP PS Data Off
14.1.0
14.2.0
PS_DATA_OFF
SP-71
SP-160091
S1-160283
22.011
0229
1
Rel-14
A
Correction of ACDC requirement for IMS services
14.1.0
14.2.0
ACDC-ST1
SP-71
SP-160091
S1-160311
22.011
0233
Rel-14
A
Barring of applications in unmatched ACDC categories
14.1.0
14.2.0
ACDC
SP-71
SP-160111
S1-160322
22.011
0234
1
Rel-14
F
Removal of non-approved CR#0224rev3 on 3GPP PS Data Off
14.1.0
14.2.0
PS_DATA_OFF
SP-72
SP-160352
S1-161087
22.011
0236
Rel-14
A
Extension of periodic network selection attempts interval
14.2.0
14.3.0
TEI13
SP-74
SP-160894
S1-163439
22.011
0239
2
Rel-14
F
Enable CS equivalent services for PS Data Off exempted services
14.3.0
14.4.0
PS_Data_Off
SP-75
SP-170151
S1-170350
22.011
0246
1
Rel-14
F
PS Data Off handling of services supported by BIP
14.4.0
14.5.0
PS_Data_Off
SP-75
SP-170153
S1-170354
22.011
0242
2
Rel-14
B
Access Control for Evolved ProSe Remote UE
14.4.0
14.5.0
REAR
SP-75
SP-170154
S1-171441
22.011
0251
1
Rel-14
F
Access Technology differentiation
14.4.0
14.5.0
TEI14
SP-75
SP-170155
S1-170124
22.011
0244
Rel-15
B
Administrative restriction of subscribers’ access to 5G-RAN
14.4.0
15.0.0
SMARTER
SP-75
SP-170155
S1-170233
22.011
0243
1
Rel-15
B
Add support of 5G in PLMN Selection
14.4.0
15.0.0
SMARTER
SP-75
SP-170155
S1-171184
22.011
0249
Rel-15
B
Administrative restriction of subscribers’ access to E-UTRAN with NR DC
14.4.0
15.0.0
SMARTER
SP-75
SP-170160
S1-171467
22.011
0248
4
Rel-15
C
Optimisation of network selection in case of an operator supporting only a subset of specific access technologies
14.4.0
15.0.0
HORNS
SP-76
SP-170450
S1-172210
22.011
0257
1
Rel-15
F
Adding missing abbreviations and reference
15.0.0
15.1.0
TEI15
SP-76
SP-170446
S1-172379
22.011
0256
1
Rel-15
F
Alignment of PLMN selection with stage 3
15.0.0
15.1.0
HORNS
SP-76
SP-170442
S1-172423
22.011
0255
2
Rel-15
A
Correction to ACDC access control
15.0.0
15.1.0
ACDC-ST1
SP-76
SP-170440
S1-172207
22.011
0260
Rel-15
A
Removal of ACB-skip
15.0.0
15.1.0
REAR
SP-76
SP-170446
S1-172016
22.011
0253
Rel-15
F
Removal of Optimisation of network selection requirements not Agreed at SA#75
15.0.0
15.1.0
HORNS
SP-76
SP-170439
S1-172209
22.011
0261
Rel-15
A
Removal of VPLMN-specific 3GPP PS Data Off Exempt services
15.0.0
15.1.0
PS_Data_Off
SP-77
SP-170689
S1-173273
22.011
0263
1
Rel-15
A
CR on REAR
15.1.0
15.2.0
REAR
SP-77
SP-170695
S1-173551
22.011
0268
2
Rel-15
F
RAT identifiers for PLMN selection in 5G
15.1.0
15.2.0
TEI15
SP-78
SP-170987
S1-174600
22.011
0270
2
Rel-16
B
Selective Legacy Radio Disabling
15.2.0
16.0.0
TEI16
SP-79
SP-180142
S1-180635
22.011
0275
3
Rel-16
C
Selective Legacy Radio Disabling
16.0.0
16.1.0
TEI16
SP-79
SP-180228
-
22.011
277
Rel-16
A
Addition of RLOS availability into Automatic PLMN Selection
16.0.0
16.1.0
PARLOS
SP-80
SP-180305
S1-181395
22.011
0283
1
Rel-16
F
Alignment of RLOS availability into Automatic PLMN Selection
16.1.0
16.2.0
PARLOS
SP-80
SP-180308
S1-181566
22.011
0281
2
Rel-16
A
Clarification to forbidden TA
16.1.0
16.2.0
TEI15
SP-80
SP-180308
S1-181678
22.011
0287
1
Rel-16
A
IoT periodic network selection attempt timers
16.1.0
16.2.0
TEI15
SP-81
SP-180751
S1-182254
22.011
0296
Rel-16
A
Correction to EAB
16.2.0
16.3.0
TEI14
SP-81
SP-180751
S1-182655
22.011
0300
Rel-16
A
PS Data Off handling of non-IP PDN types
16.2.0
16.3.0
PS_Data_Off
SP-81
SP-180752
S1-182096
22.011
0291
Rel-16
A
Clarification to Delay Tolerant
16.2.0
16.3.0
SMARTER
SP-81
SP-180756
S1-182633
22.011
0289
1
Rel-16
C
Delaying periodic higher priority PLMN searches and reselection attempts when receiving eMBMS service in idle mode
16.2.0
16.3.0
TEI16
SP-81
SP-180907
-
22.011
0297
5
Rel-16
F
Clarification on the PLMN selection mode for RLOS
16.2.0
16.3.0
PARLOS
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2018-12
SP-82
SP-180999
0301
4
F
correction on PLMN selection in RLOS
16.4.0
2018-12
SP-82
SP-180999
0302
3
F
Clarification on disabling of legacy radio
16.4.0
2019-12
SP-86
SP-191032
0307
2
B
On PLMN selection for MINT
17.0.0
2020-03
SP-87
SP-200123
0310
1
F
Clarification on the traffic handling over non-3GPP access for PS DATA Off
17.1.0
2020-09
SA#89e
SP-200794
315
1
F
Corrections to Service accessibility specification
17.2.0
2020-12
SA#90e
SP-201029
319
0
F
Satellite access RAT identifier for PLMN selection
17.3.0
2020-12
SA#90e
SP-201029
321
1
F
Requirement Alignment related to PLMN reselection
17.3.0
2021-09
SA#93e
SP-211096
0324
D
Correction of 'air interface' terminology
17.4.0
2021-09
SA#93e
SP-211068
0322
4
B
Signal level Enhanced Network Selection
18.0.0
2021-12
SP#94e
SP-211487
0327
1
A
Periodic network selection with shared MCC
18.1.0
2022-03
SP#95e
SP-220082
0330
D
Clean-up of the references for quality improvement
18.2.0
2022-06
SA#96
SP-220433
340
1
A
Clarifications on PLMN search for FPLMN Registered UEs
18.3.0
2022-06
SA#96
SP-220428
336
1
A
Clarification of Shared MCC definition
18.3.0
2022-12
SA#98
SP-221258
0342
F
Clarification of SENSE requirement under disaster roaming condition
18.4.0
2022-12
SA#98
SP-221258
0344
2
F
Clarification on the periodic network selection for SENSE
18.4.0
2023-03
SA#99
SP-230228
0348
3
B
PS Data Off for IMS Data Channel Service
19.0.0
2023-06
SA#100
SP-230530
0351
1
A
Clarification on selection of Forbidden PLMN during Disaster Conditions when Operator controlled signal threshold applies
19.1.0
2023-09
SA#101
SP-231041
0352
D
Quality improvements for TS22.011 Release 19
19.2.0
2024-03
SA#103
SP-240202
0359
3
F
Clarification on the PS Data Off exemption for services over Data Channel
19.3.0
2024-09
SA#105
SP-241145
0363
1
F
Location services user plane protocol and 3GPP PS data off
19.4.0
2024-12
SA#106
SP-241760
0370
2
A
Alignment on Satellite E-UTRA
19.5.0
2024-12
SA#106
SP-241762
0364
3
F
Clarification on support of 3GPP PS data off for 5G
19.5.0
2025-09
SA#109
SP-250979
0373
3
B
Lower Selection-priority for PLMN Selection
19.6.0
|
162c3f0c36a54745dc509a8130708d2d | 22.104 | 1 Scope | The present document provides Stage 1 normative service requirements for 5G systems, in particular service requirements for cyber-physical control applications in vertical domains and requirements for auxiliary applications. In the context of the present document, cyber-physical systems are to be understood as systems that include engineered, interacting networks of physical and computational components; control applications are to be understood as applications that control physical processes. Examples for auxiliary applications are distributed sensing and asset monitoring.
Communication services supporting cyber-physical control applications need to be ultra-reliable and, in some cases, the end-to-end latency must be very low. Communication for cyber-physical control applications supports operation in various vertical domains, for instance industrial automation, Smart Grid .
The aspects addressed in the present document include:
- end-to-end service performance requirements and network performance requirements related to these end-to-end service performance requirements;
- support for Ethernet services specific to industrial/high performance use cases. Related Ethernet functionalities include, for example, those in IEEE 802.1Qbv;
- direct device connection and indirect network connection for cyber-physical applications. |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 22.261: "Service requirements for the 5G system".
[3] IEC 61784-3: "Industrial communication networks – profiles – part 3: functional fieldbuses – general rules and profile definitions".
[4] BZKI, "Aspects of dependability assessment in ZDKI", June 2017.
[5] BZKI, "Requirement Profiles in ZDKI", 2017.
[6] IEC 61158: "Industrial communication networks – fieldbus specification", 2014.
[7] IEC 61907, "Communication network dependability engineering".
[8] Richard C. Dorf and Robert H. Bishop, "Modern Control Systems", Pearson, Harlow, 13th Edition, 2017.
[9] Ernie Hayden, Michael Assante, and Tim Conway, "An Abbreviated History of Automation & Industrial Controls Systems and Cybersecurity", SANS Institute, https://ics.sans.org/media/An-Abbreviated-History-of-Automation-and-ICS-Cybersecurity.pdf {accessed: 2017-05-23}, 2014.
[10] IEC 61512 "Batch control - Part 1: Models and terminology".
[11] RESERVE project, Deliverable D1.3, ICT Requirements,
http://www.re-serve.eu/files/reserve/Content/Deliverables/D1.3.pdf, September 2017.
[12] RESERVE project, Deliverable D1.2, Energy System Requirements
http://www.re-serve.eu/files/reserve/Content/Deliverables/D1.2.pdf, September 2017.
[13] G. Garner, "Designing Last Mile Communications Infrastructures for Intelligent Utility Networks (Smart Grids)", IBM Australia Limited, 2010.
[14] B. Al-Omar, B., A. R. Al-Ali, R. Ahmed, and T. Landolsi, "Role of Information and Communication Technologies in the Smart Grid", Journal of Emerging Trends in Computing and Information Sciences, Vol. 3, pp. 707-716, 2015.
[15] H. Kagermann, W. Wahlster, and J. Helbig, "Recommendations for implementing the strategic initiative INDUSTRIE 4.0", Final report of the Industrie 4.0 working group, acatech – National Academy of Science and Engineering, Munich, April 2013.
[16] IEC 62443-3-2: "Security for industrial automation and control systems - Part 3-2: Security risk assessment and system design", in progress.
[17] IEC 62657-2: "Industrial communication networks - Wireless communication networks - Part 2: Coexistence management", 2017.
[18] IEC 62657-1: "Industrial communication networks – Wireless communication networks – Part 1: Wireless communication requirements and spectrum considerations".
[19] IEEE Std 802.1Q: "IEEE Standard for Local and Metropolitan Area Networks---Bridges and Bridged Networks".
NOTE: IEEE Std 802.1Qbv-2015 "IEEE Standard for Local and Metropolitan Area Networks--Bridges and Bridges Networks - Amendment 25: Enhancements for Scheduled Traffic" has been included into IEEE Std 802.1Q-2018.
[20] IEEE, Use Cases IEC/IEEE 60802, 2018.
[21] (void)
[22] IEEE Std 802.1AS: "IEEE Standard for Local and Metropolitan Area Networks--Timing and Synchronization for Time-Sensitive Applications".
[23] 3GPP TS 22.289: "Mobile Communication System for Railways".
[24] IEEE P802.1CS: "IEEE Standard for Local and Metropolitan Area Networks--Link-local Registration Protocol".
[25] IEEE P802.1Qdd: "IEEE Draft Standard for Local and Metropolitan Area Networks--Bridges and Bridged Networks -- Amendment: Resource Allocation Protocol (RAP) ".
[26] IEC/IEEE 60802: "Time-Sensitive Networking Profile for Industrial Automation".
[27] 3GPP TS 22.263: "Service requirements for Video, Imaging and Audio for Professional Applications (VIAPA)".
[28] IEC TR 61850-90-1:2010, Communication Networks and Systems for Power Utility automation – Part 90-1: Use of IEC61850 for the communication between substations.
[29] 5G DNA White Paper: "5GDN@Smart Grid White Paper: Requirements, Technologies, and Practices" https://www.5gdna.org/
[30] IEC 61850-9-3-2016 – IEC/IEEE International Standard - Communication Networks and Systems for Power Utility automation – Part 9-3: Precision time protocol profile for power utility automation.
[31] IEEE Std C37.238-2017 , IEEE Standard Profile for Use of IEEE Std 1588™ Precision Time Protocol in Power System Applications.
[32] IEC 61850-90-5:2012, Use of IEC 61850 to transmit Synchrophasors information according to IEEE C37.118.
[33] IEEE Std C37.118.2-2011, IEEE Standard for Synchrophasor Data Transfer for Power Systems.
[34] IEEE Std 1588-2019: "IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control". |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 3 Definitions, symbols and abbreviations | |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
characteristic parameter: numerical value that can be used for characterising the dynamic behaviour of communication functionality from an application point of view.
clock synchronicity: the maximum allowed time offset within a synchronisation domain between the sync master and any sync device.
NOTE 1: Clock synchronicity (or synchronicity) is used as KPI of clock synchronisation services.
NOTE 2: Clock synchronicity is also referred to as clock (or time) synchronization precision.
clock synchronisation service: the service to align otherwise independent user-specific UE clocks.
communication service availability: as defined in TS 22.261 [2].
communication service reliability: ability of the communication service to perform as required for a given time interval, under given conditions.
NOTE 3: Given conditions would include aspects that affect reliability, such as: mode of operation, stress levels, and environmental conditions.
NOTE 4: Reliability may be quantified using appropriate measures such as mean time between failures, or the probability of no failure within a specified period of time.
NOTE 5: This definition is based on IEC 61907 [7].
direct device connection: as defined in TS 22.261 [2].
end-to-end latency: as defined in TS 22.261 [2].
error: discrepancy between a computed, observed or measured value or condition and the true, specified or theoretically correct value or condition.
NOTE 6: This definition was taken from IEC 61784-3 [3].
factory automation: automation application in industrial automation branches typically with discrete characteristics of the application to be automated with specific requirements for determinism, low latency, reliability, redundancy, cyber security, and functional safety.
NOTE 7: Low latency typically means below 10 ms delivery time.
NOTE 8: This definition is taken from IEC 62657-1 [18].
global clock: a user-specific synchronization clock set to a reference timescale such as the International Atomic Time.
indirect network connection: as defined in TS 22.261 [2].
influence quantity: quantity not essential for the performance of an item but affecting its performance.
process automation: automation application in industrial automation branches typically with continuous characteristics of the application to be automated with specific requirements for determinism, reliability, redundancy, cyber security, and functional safety.
NOTE 9: This definition is taken from IEC 62657-1 [18].
service area: as defined in TS 22.261 [2].
survival time: as defined in TS 22.261 [2].
sync device: device that synchronizes itself to the master clock of the synchronization domain.
sync master: device serving as the master clock of the synchronization domain.
transfer interval: time difference between two consecutive transfers of application data from an application via the service interface to 3GPP system.
NOTE 10: This definition is based on subclause 3.1.85 in IEC 62657-2 [17].
user experienced data rate: as defined in TS 22.261 [2].
vertical domain: an industry or group of enterprises in which similar products or services are developed, produced, and provided.
working clock: a user-specific synchronization clock for a localized set of UEs collaborating on a specific task or work function. |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 3.2 Symbols | For the purposes of the present document, the following symbols apply:
<symbol> <Explanation> |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
AV Audio-Visual
AVPROD AV Production
CSIF Communication Service Interface
EPON Ethernet Passive Optical Network
FIFO First In, First Out
GOOSE Generic Object-Oriented Substation Event
HCL Higher Communication Layer
HMI Human Machine Interface
IMU Inertial Measurement Unit
LCL Lower Communication Layer
PMU Phasor Measurement Unit |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 4 Overview | |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 4.1 Introduction | For the purpose of this document, a vertical domain is a particular industry or group of enterprises in which similar products or services are developed, produced, and provided. Automation refers to the control of processes, devices, or systems in vertical domains by automatic means. The main control functions of automated control systems include taking measurements, comparing results, computing any detected or anticipated errors, and correcting the process to avoid future errors. These functions are performed by sensors, transmitters, controllers, and actuators.
In the context of this document, cyber-physical systems are referred to as systems that include engineered, interacting networks of physical and computational components. Cyber-physical control applications are to be understood as applications that control physical processes. Cyber-physical control applications in automation follow certain activity patterns, which are open-loop control, closed-loop control, sequence control, and batch control (see Clause 4.2).
Communication services supporting cyber-physical control applications need to be ultra-reliable, dependable with a high communication service availability, and often require low or (in some cases) very low end-to-end latency.
Communication in automation in vertical domains follows certain communication patterns. The most well-known is periodic deterministic communication, others are aperiodic deterministic communication and non-deterministic communication (see Clause 4.3).
Communication for cyber-physical control applications supports operation in various vertical domains, for instance industrial automation and energy automation. This document addresses service requirements for cyber-physical control applications and supporting communication services from the vertical domains of factories of the future (smart manufacturing), electric power distribution, and central power generation. Service requirements for cyber-physical control applications and supporting communication services for rail-bound mass transit are addressed in TS 22.289 [23]. |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 4.2 Activity patterns in automation | Open-loop control: The salient aspect of open-loop control is the lack of feedback from the output to the control; when providing commands to an actuator, it is assumed that the output of the influenced process is predetermined and within an acceptable range. This kind of control loop works if the influences of the environment on process and actuator are negligible. Also, this kind of control is applied in case unwanted output can be tolerated [8].
Closed-loop control: Closed-loop control enables the manipulation of processes even if the environment influences the process or the performance of the actuator changes over time. This type of control is realised by sensing the process output and by feeding these measurements back into a controller [8].
Sequence control: Sequence control may either step through a fixed sequence or employ logic that performs different actions based on various system states and system input [8]. Sequence control can be seen as an extension of both open-loop and closed-loop control, but instead of achieving only one output instance, an entire sequence of output instances can be produced [9].
Batch control: Batch processes lead to the production of finite quantities of material (batches) by subjecting input materials to a defined order of processing actions by use of one or more pieces of equipment [10]. |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 4.3 Communication attributes | Communication in automation can be characterised by two main attributes: periodicity and determinism.
Periodicity means that a transmission interval is repeated. For example, a transmission occurs every 15 ms. Reasons for a periodical transmission can be the periodic update of a position or the repeated monitoring of a characteristic parameter. Most periodic intervals in communication for automation are rather short. The transmission is started once and continuous unless a stop command is provided.
An aperiodic transmission is, for example, a transmission which is triggered instantaneously by an event, i.e., events are the trigger of the transmission. Events are defined by the control system or by the user. Example events are:
- Process events: events that come from the process when thresholds are exceeded or fallen below, e.g., temperature, pressure, level, etc.
- Diagnostic events: events that indicate malfunctions of an automation device or module, e.g., power supply defective; short circuit; too high temperature; etc.
- Maintenance events: events based on information that indicates necessary maintenance work to prevent the failure of an automation device.
Most events, and especially alarms, are confirmed. In this context, alarms are messages that inform a controller or operator that an event has occurred, e.g., an equipment malfunction, process deviation, or other abnormal condition requiring a response. The receipt of the alarm is acknowledged usually within a short time period by the application that received the alarm. If no acknowledgment is received from the target application after a preset time, the so-called monitoring time, the alarm is sent again after a preset time or some failure response action is started.
Determinism refers to whether the delay between transmission of a message and receipt of the message at the destination address is stable (within bounds). Usually, communication is called deterministic if it is bounded by a given threshold for the latency/transmission time. In case of a periodic transmission, the variation of the interval is bounded. |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 4.4 Control systems and related communication patterns | There are preferences in the mapping between the type of control and the communication pattern. Open-loop control is characterised by one or many messages sent to an actuator. These can be sent in a periodic or an aperiodic pattern. However, the communication means used need to be deterministic since typically an activity response from the receiver and/or the receiving application is expected.
Closed-loop control produces both periodic and aperiodic communication patterns. Closed-loop control is often used for the control of continuous processes with tight time-control limits, e.g., the control of a printing press. In this case, one typically relies on periodic communication patterns. Note that in both the aperiodic and periodic case, the communication needs to be deterministic.
Logging of device states, measurements, etc. for maintenance purposes and such typically entails aperiodic communication patterns. In case the transmitted logging information can be time-stamped by the respective function, determinism is often not mandatory.
In practice, vertical communication networks serve a large number of applications exhibiting a wide range of communication requirements. In order to facilitate efficient modelling of the communication network during engineering and for reducing the complexity of network optimisation, traffic classes or communication patterns have been identified [6]. There are three typical traffic classes or communication patterns in industrial environments [6], i.e.,
- deterministic periodic communication: periodic communication with stringent requirements on timeliness of the transmission.
- deterministic aperiodic communication: communication without a preset sending time. Typical activity patterns for which this kind of communication is suitable are event-driven actions.
- non-deterministic communication: subsumes all other types of traffic, including periodic non-real time and aperiodic non-real time traffic. Periodicity is irrelevant in case the communication is not time-critical.
Some communication services exhibit traffic patterns that cannot be assigned to one of the above communication patterns exclusively (mixed traffic). |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 4.5 Implications for 5G systems | In order to be suitable for automation in vertical domains, 5G systems need to be dependable and flexible to meet specific KPIs to serve specific applications and use cases. They need to come with the system properties of reliability, availability, maintainability, safety, and integrity. What particular requirements each property needs to meet depends on the particularities of the domain and the use case. Annex F discusses the difference between reliability and communication service availability. The requirements in this document provide various sets of performance criteria that need to be met to satisfactorily support different use cases of cyber-physical control applications used by various vertical markets. |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 5 Performance requirements | |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 5.1 Overview | There are two fundamental perspectives concerning dependable communication in 5G systems: the end-to-end perspective of the communication services and the network perspective (see Figure 5.1-1).
Figure 5.1-1: Network perspective of 5G system
The Communication Service in Figure 5.1-1 may be implemented as a logical communication link between a UE on one side and a network server on the other side, or between a UE on one side and a UE on the other side.
In some cases, a local approach (e.g. network edge) is preferred for the communication service on the network side in order to reduce the latency, to increase communication service availability, or to keep sensitive data in a non-public network on the factory site.
The tables in Clauses 5.2 through 5.5 below provide sets of requirements where periodicity and determinism are critical to meeting cyber-physical control application needs in various vertical scenarios. While many use cases have similar KPI values, the important distinction is that in order to meet the needs of different verticals and different uses, the 5G system will need to be sufficiently flexible to allow deployment configurations that can meet the different sets of KPIs specific to each use.
Communication service availability is considered an important service performance requirement for cyber-physical applications, especially for applications with deterministic traffic. The communication service availability depends on the latency and reliability (in the context of network layer packet transmissions, as defined in TS 22.261 [2]) of the logical communication link, as well as the survival time of the cyber-physical application (see Annex C.3 for further details on these relations).
The communication service reliability requirements also depend on the operation characteristics of the corresponding cyber-physical applications. Typically, the communication services critical for the automation application also come with stringent communication service reliability requirements. Note that the communication service reliability requirement has no direct relationship with the communication service availability requirement.
The "# of UEs" in the tables in clauses 5.2 to 5.5 is intended to give an indication of the UE density that would need to be served within a given service area.
Clock synchronisation is needed in many "vertical" use cases. The requirements and tables in Clause 5.6 provide specific criteria for managing time sensitive communications in an industrial environment.
High accuracy positioning is becoming essential for Factories of the Future. The reason for this is that tracking of mobile devices as well as mobile assets is becoming increasingly important in improving processes and increasing flexibility in industrial environments, Clause 5.7 provides positioning requirements for horizontal and vertical accuracy, availability, heading, latency and UE speed in an industrial use case scenario.
An example of the relationship between reliability (in the context of network layer packet transmissions, as defined in TS 22.261 [2]), survival time and communication service availability of a logical communication link is illustrated in the following Table 5.1-1. This is done for a special case where packet errors are uncorrelated, which in many cases is an unrealistic assumption.
Table 5.1-1: Example of relationship between reliability (as defined in TS 22.261) and communication service availability when the survival time is equal to the transfer interval.
Communication service availability
Reliability
( as defined in TS 22.261)
1 - p
99.999 9 %
99.9 %
99.999 999 %
99.99 %
99.999 999 99 %
99.999 %
99.999 999 999 9 %
99.999 9 %
99.999 999 999 999 %
99.999 99 % |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 5.2 Periodic deterministic communication | Periodic deterministic communication is periodic with stringent requirements on timeliness and availability of the communication service. A transmission occurs every transfer interval. A description of periodic deterministic communication can be found in Clauses 4.3 and 4.4. Additional information on the underlying use cases of the sets of requirements in Table 5.2-1 can be found in Annex A. Further information on characteristic parameters and influence quantities used in Table 5.2-1 can be found in Annex C.
The 5G system shall be able to provide periodic deterministic communication with the service performance requirements for individual logical communication links that realise the communication services reported in Table 5.2‑1.
Process and asset monitoring using industrial wireless sensors is a special case of periodic deterministic communication with more relaxed requirements on timeliness and availability. These use cases put a slightly different set of requirements on the 5G system due to the specific constraints of industrial wireless sensors. These requirements for individual logical communication links are listed in Table 5.2-2 and additional information on the underlying use cases can be found in Annex A.
Smart-Grid use case information can be found in Annex A.
Table 5.2-1: Periodic deterministic communication service performance requirements
Characteristic parameter
Influence quantity
Communication service availability: target value (note 1)
Communication service reliability: mean time between failures
End-to-end latency: maximum (note 2) (note 12a)
Service bit rate: user experienced data rate (note 12a)
Message size [byte] (note 12a)
Transfer interval: target value (note 12a)
Survival time (note 12a)
UE
speed (note 13)
# of UEs
Service area
(note 3)
Remarks
99.999 % to 99.999 99 %
~ 10 years
< transfer interval value
–
50
500 μs
500 μs
≤ 75 km/h
≤ 20
50 m x 10 m x 10 m
Motion control (A.2.2.1)
99.999 9 % to 99.999 999 %
~ 10 years
< transfer interval value
–
40
1 ms
1 ms
≤ 75 km/h
≤ 50
50 m x 10 m x 10 m
Motion control (A.2.2.1)
99.999 9 % to 99.999 999 %
~ 10 years
< transfer interval value
–
20
2 ms
2 ms
≤ 75 km/h
≤ 100
50 m x 10 m x 10 m
Motion control (A.2.2.1)
99.999 9 %
–
< 5 ms
1 kbit/s (steady state)
1.5 Mbit/s (fault case)
< 1,500
< 60 s
(steady state)
≥ 1 ms (fault case)
transfer interval
stationary
20
30 km x 20 km
Electrical Distribution – Distributed automated switching for isolation and service restoration (A.4.4); (note 5)
99.999 9 % to 99.999 999 %
~ 10 years
< transfer interval value
1 k
≤ 10 ms
10 ms
-
5 to 10
100 m x 30 m x 10 m
Control-to-control in motion control (A.2.2.2); (note 9)
99.999 9 % to 99.999 999 %
~ 10 years
< transfer interval value (note 5)
50 Mbit/s
≤ 1 ms
3 x transfer interval
stationary
2 to 5
100 m x 30 m x 10 m
Wired-2-wireless 100 Mbit/s link replacement (A.2.2.4)
99.999 9 % to 99.999 999 %
~ 10 years
< transfer interval value (note 5)
250 Mbit/s
≤ 1 ms
3 x transfer interval
stationary
2 to 5
100 m x
30 m x 10 m
Wired-2-wireless 1 Gbit/s link replacement (A.2.2.4)
99.999 9 % to 99.999 999 %
~ 10 years
< transfer interval value
1 k
≤ 50 ms
50 ms
-
5 to 10
1,000 m x 30 m x 10 m
Control-to-control in motion control (A.2.2.2); (note 9)
> 99.999 9 %
~ 10 years
< transfer interval value
–
40 to 250
1 ms to 50 ms (note 6) (note 7)
transfer interval value
≤ 50 km/h
≤ 2,000
≤ 1 km2
Mobile robots (A.2.2.3)
99.999 9 % to 99.999 999 %
~ 1 month
< transfer interval value
–
40 to 250
4 ms to 8 ms (note 7)
transfer interval value
< 8 km/h (linear movement)
TBD
50 m x 10 m x 4 m
Mobile control panels – remote control of e.g. assembly robots, milling machines (A.2.4.1); (note 9)
99.999 999 %
1 day
< 8 ms
(note 14)
250 kbit/s
40 to 250
8 ms
16 ms
quasi-static; up to 10 km/h
2 or more
30 m x 30 m
Mobile Operation Panel: Emergency stop (connectivity availability) (A.2.4.1A)
99.999 99 %
1 day
< 10 ms
(note 14)
< 1 Mbit/s
< 1024
10 ms
~10 ms
quasi-static; up to 10 km/h
2 or more
30 m x 30 m
Mobile Operation Panel: Safety data stream (A.2.4.1A)
99.999 999 %
1 day
10 ms to 100 ms
(note 14)
10 kbit/s
10 to 100
10 ms to 100 ms
transfer interval
stationary
2 or more
100 m² to 2,000 m²
Mobile Operation Panel: Control to visualization (A.2.4.1A)
99.999 999 %
1 day
< 1 ms
(note 14)
12 Mbit/s to 16 Mbit/s
10 to 100
1 ms
~ 1 ms
stationary
2 or more
100 m²
Mobile Operation Panel: Motion control (A.2.4.1A)
99.999 999 %
1 day
< 2 ms
(note 14)
16 kbit/s (UL)
2 Mbit/s (DL)
50
2 ms
~ 2 ms
stationary
2 or more
100 m²
Mobile Operation Panel: Haptic feedback data stream (A.2.4.1A)
99.999 9 % to 99.999 999 %
~ 1 year
< transfer interval
–
40 to 250
< 12 ms (note 7)
12 ms
< 8 km/h (linear movement)
TBD
typically 40 m x 60 m; maximum 200 m x 300 m
Mobile control panels -remote control of e.g. mobile cranes, mobile pumps, fixed portal cranes (A.2.4.1); (note 9)
99.999 9 % to 99.999 999 %
≥ 1 year
< transfer interval value
–
20
≥ 10 ms (note 8)
0
typically stationary
typically 10 to 20
typically ≤ 100 m x 100 m x 50 m
Process automation – closed loop control (A.2.3.1)
99.999 %
TBD
~ 50 ms
–
~ 100
~ 50 ms
TBD
stationary
≤ 100,000
several km2 up to 100,000 km2
Primary frequency control (A.4.2); (note 9)
99.999 %
TBD
~ 100 ms
–
~ 100
~ 200 ms
TBD
stationary
≤ 100,000
several km2 up to 100,000 km2
Distributed Voltage Control (A.4.3) (note 9)
> 99.999 9 %
~ 1 year
< transfer interval value
–
15 k to 250 k
10 ms to 100 ms (note 7)
transfer interval value
≤ 50 km/h
≤ 2,000
≤ 1 km2
Mobile robots – video-operated remote control (A.2.2.3)
> 99.999 9 %
~ 1 year
< transfer interval value
–
40 to 250
40 ms to 500 ms (note 7)
transfer interval value
≤ 50 km/h
≤ 2,000
≤ 1 km2
Mobile robots (A.2.2.3)
99.99 %
≥ 1 week
< transfer interval value
–
20 to 255
100 ms to 60 s (note 7)
≥ 3 x transfer interval value
typically stationary
≤ 10,000 to 100,000
≤ 10 km x 10 km x 50 m
Plant asset management (A.2.3.3)
>99.999 999 %
> 10 years
< 2 ms
2 Mbit/s to 16 Mbit/s
250 to 2,000
1 ms
transfer interval value
stationary
1
< 100 m2
Robotic Aided Surgery (A.6.2)
>99.999 9 %
> 1 year
< 20 ms
2 Mbit/s to 16 Mbit/s
250 to 2,000
1 ms
transfer interval value
stationary
2 per 1,000 km2
< 400 km (note 12)
Robotic Aided Surgery (A.6.2)
>99.999 %
>> 1 month
(< 1 year)
< 20 ms
2 Mbit/s to 16 Mbit/s
80
1 ms
transfer interval value
stationary
20 per 100 km2
< 50 km (note 12)
Robotic Aided Diagnosis (A.6.3)
99.999 9 % to 99.999 999 %
~ 10 years
< 0.5 x transfer interval
2.5 Mbit/s
250
500 with localisation information
> 5 ms
> 2.5 ms
> 1.7 ms
(note 10)
0
transfer interval
2 x transfer interval
(note 10)
≤ 6 km/h (linear movement)
2 to 8
10 m x 10 m x 5 m;
50 m x 5 m x 5 m
(note 11)
Cooperative carrying – fragile work pieces; (ProSe communication) (A.2.2.5)
99.999 9 % to 99.999 999 %
~ 10 years
< 0.5 x transfer interval
2.5 Mbit/s
250
500 with localisation information
> 5 ms
> 2.5 ms
> 1.7 ms (note 10)
0
transfer interval
2 x transfer interval
(note 10)
≤ 12 km/h (linear movement)
2 to 8
10 m x 10 m x 5 m;
50 m x 5 m x 5 m
(note 11)
Cooperative carrying – elastic work pieces; (ProSe communication) (A.2.2.5)
> 99.9 %
DL: < 10 ms
UL: < 10 ms
UL: > 16 Mbit/s (urban), 640 Mbit/s (rural)
DL: > 100 kbit/s
(note 15)
UL: 800 kbyte
UL: 10 ms
> 10/km2 (urban),
> 100/km2 (rural)
(note 16)
Distributed energy storage ‒ monitoring (A.4.6)
> 99.9 %
DL: < 10 ms
UL: < 1 s
UL: > 128 kbit/s (urban), 10.4 Mbit/s (rural);
DL: > 100 kbit/s
(note 15)
UL: 1.3 Mbyte
DL: > 100 kbyte
UL: 1000 ms
> 10/km2 (urban),
> 100/km2 (rural)
(note 16)
Distributed energy storage ‒ data collection (A.4.6)
> 99.99 %
General information data collection: < 3 s
(note 17)
UL: < 2 Mbit/s
DL: < 1 Mbit/s
< 10,000/km2 (note 18)
Advanced metering (A.4.7)
99.999 %
< 10 ms
2 Mbit/s to 10 Mbit/s
normal: 1 s;
fault: 2 ms
(note 24)
54/km²
(note 19),
78/km2 (note 20)
Intelligent distributed feeder automation (A.4.4.3)
> 99.99 %
10 ms, 100 ms, 3 s (note 22)
> 2 Mbit/s (note 21)
500 in the service area (note 23)
Communication distance is from 100 m to 500 m, outdoor, indoor / deep indoor
Smart distribution ‒transformer terminal (A.4.8)
99.999 %
5 ms, 10 ms, 15 ms (note 25)
1.2 Mbit/s to 2.5 Mbit/s
< 245 byte
≤ 1 ms
≤ 2 ms
(note 26)
≤ 100/km2
several km2
High speed current differential protection (note 12a) (A.4.4.4)
99.999 9 %
3 ms
5.4 Mbit/s
140 byte
≤ 1 ms
stationary
Distributed Energy Resources (DER) and micro-grids (A.4.9)
99.999 9 %
100 ms
(note 12a and note 5)
< 1 kbit/s per DER
stationary
Ensuring uninterrupted communication service availability during emergencies (A.4.10)
NOTE 1: One or more retransmissions of network layer packets may take place in order to satisfy the communication service availability requirement.
NOTE 2: Unless otherwise specified, all communication includes 1 wireless link (UE to network node or network node to UE) rather than two wireless links (UE to UE).
NOTE 3: Length x width (x height).
NOTE 4: (void)
NOTE 5: Communication includes two wireless links (UE to UE).
NOTE 6: This covers different transfer intervals for different similar use cases with target values of 1 ms, 1 ms to 10 ms, and 10 ms to 50 ms.
NOTE 7: The transfer interval deviates around its target value by < ±25 %.
NOTE 8: The transfer interval deviates around its target value by < ±5 %.
NOTE 9: Communication may include two wireless links (UE to UE).
NOTE 10: The first value is the application requirement, the other values are the requirement with multiple transmission of the same information (two or three times, respectively).
NOTE 11: Service Area for direct communication between UEs. The group of UEs with direct communication might move throughout the whole factory site (up to several km²).
NOTE 12: Maximum straight-line distance between UEs.
NOTE 12a: It applies to both UL and DL unless stated otherwise.
NOTE 13: It applies to both linear movement and rotation unless stated otherwise.
NOTE 14: The mobile operation panel is connected wirelessly to the 5G system. If the mobile robot/production line is also connected wirelessly to the 5G system, the communication includes two wireless links.
NOTE 15: Service bit rate for one energy storage station.
NOTE 16: Activity storage nodes/km2. This value is used for deducing the data volume in an area that features multiple energy storage stations. The data volume can be calculated with the following formula (current service bit rate per storage station) x (activity storage nodes/km2) + (video service bit rate per storage station) x (activity storage nodes/km2).
NOTE 17: One-way delay from 5G IoT device to backend system. The distance between the two is below 40 km (city range).
NOTE 18: Typical connection density in today’s city environment. With the evolution from centralised meters to socket meters in the home, the connection density is expected to increase 5 to 10 times.
NOTE 19: When the distributed terminals are deployed along an overhead line, there are about 54 terminals per square kilometre.
NOTE 20: When the distributed terminals are deployed in power distribution cabinets, there are about 78 terminals per square kilometre.
NOTE 21: Service bit rate of the smart metering application between the smart distribution transformer terminal and the energy end equipment. Once there are multiple smart grid applications, the required service bit rate will be higher.
NOTE 22: The end-to-end latency depends on the applications supported by the smart distribution transformer terminal. The lower the end-to-end latency, the more applications can be supported.
NOTE 23: The service area is circular with a radius between 100 m and 500 m (0.031 km2 to 0.79 km2).
NOTE 24: During the normal working phase of the feeder system, the heartbeat packet is transmitted periodically with a 1 s transfer interval. When a fault occurs, the heartbeat is sent with a 2 ms transfer interval.
NOTE 25: The maximum allowed delay between two protection relays would be between 5 ms and 10 ms, depending on the voltage (see IEC 61850-90-1 for more details [aa]). For some legacy systems, the end-to-end latency is usually set to 15 ms.
NOTE 26: For a sampling rate of 600 Hz, the transfer interval is 1.7 ms. For 1200 Hz, the transfer interval is 0.83 ms.
Table 5.2-2: Communication service performance requirements for industrial wireless sensors
Characteristic parameter
Influence quantity
Communication service availability: target value
Communication service reliability: mean time between failure
End-to-end latency (note 6)
Transfer interval
(note 1) (note 7)
Service bit rate: user experienced data rate
(note 2) (note 7)
Battery lifetime [year]
(note 3)
Message
Size
[byte] (note 7)
Survival time
(note 7)
UE speed
UE density [UE / m²]
Range
[m]
(note 4)
Remarks
99.99 %
≥ 1 week
< 100 ms
100 ms to 60 s
≤ 1 Mbit/s
≥ 5
20
(note 5)
3 x transfer interval
stationary
Up to 1
< 500
Process monitoring, e.g. temperature sensor (A.2.3.2)
99.99 %
≥ 1 week
< 100 ms
≤ 1 s
≤ 200 kbit/s
≥ 5
25 k
3 x transfer interval
stationary
Up to 0.05
< 500
Asset monitoring, e.g. vibration sensor (A.2.3.2)
99.99 %
≥ 1 week
< 100 ms
≤ 1 s
≤ 2 Mbit/s
≥ 5
250 k
3 x transfer interval
stationary
Up to 0.05
< 500
Asset monitoring, e.g. thermal camera (A.2.3.2)
NOTE 1: The transfer interval deviates around its target value by < ± 25 %.
NOTE 2: The traffic is predominantly mobile originated.
NOTE 3: Industrial sensors can use a wide variety of batteries depending on the use case, but in general they are highly constrained in terms of battery size.
NOTE 4: Distance between the gNB and the UE.
NOTE 5: The application-level messages in this use case are typically transferred over Ethernet. For small messages, the minimum Ethernet frame size of 64 bytes applies and dictates the minimum size of the PDU sent over the air interface.
NOTE 6: It applies to both UL and DL unless stated otherwise.
NOTE 7: It applies to UL. |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 5.3 Aperiodic deterministic communication | Aperiodic deterministic communication is without a pre-set sending time, but still with stringent requirements on timeliness and availability of the communication service. A description of aperiodic deterministic communication can be found in Clauses 4.3 and 4.4. Additional information on the underlying use cases of the sets of requirements in Table 5.3-1 can be found in Annex A. Further information on characteristic parameters and influence quantities used in Table 5.3-1 can be found in Annex C.
The 5G system shall be able to provide aperiodic deterministic communication with the service performance requirements for individual logical communication links that realise the communication services reported in Table 5.3-1.
Table 5.3-1: Aperiodic deterministic communication service performance requirements
Characteristic parameter (KPI)
Influence quantity
Communication service availability
Communication service reliability: mean time between failures
Max Allowed End-to-end latency (note 1)
(note 5)
Service bit rate: user-experienced data rate (note 5)
Message size [byte] (note 5)
Survival time
UE speed (note 6)
# of UEs
Service Area (note 3)
Remarks
> 99.999 9 %
~ 1 week
10 ms
UL: > 10 Mbit/s
–
–
≤ 50 km/h
≤ 2,000
≤ 1 km2
Mobile robots – video streaming (A.2.2.3)
99.999 9 % to 99.999 999 %
~ 1 month
< 30 ms
> 5 Mbit/s
–
–
< 8 km/h (linear movement)
TBD
TBD
Mobile control panels - parallel data transmission (A.2.4.1)
99.999 999 %
1 day
<8 ms
(note 8)
250 kbit/s
40 to 250
16 ms
quasi-static; up to 10 km/h
2 or more
30 m x 30 m
Mobile Operation Panel: Emergency stop (emergency stop events) (A.2.4.1A)
99.999 9 %
–
< 50 ms
0.59 kbit/s
28 kbit/s
< 100
–
stationary
10 km‑² to 100 km‑²
TBD
Smart grid millisecond level precise load control (A.4.5)
> 99.9 %
~ 1 month
< 10 ms
–
–
–
< 8 km/h (linear movement)
≥ 3
20 m x 20 m x 4 m
Augmented reality; bi-directional transmission to image processing server (A.2.4.2)
99.999 9 % to 99.999 999 %
~ 10 years
< 1 ms
(note 4)
25 Mbit/s
–
–
stationary
2 to 5
100 m x
30 m x 10 m
Wired-2-wireless 100 Mbit/s link replacement (A.2.2.4)
99.999 9 % to 99.999 999 %
~ 10 years
< 1 ms
(note 4)
500 Mbit/s
–
–
stationary
2 to 5
100 m x
30 m x 10 m
Wired-2-wireless 1 Gbit/s link replacement (A.2.2.4)
> 99.9 %
–
DL: < 10 ms
UL:<1 s
(rural)
DL: > 100 kbit/s UL: > 5 Gbit/s
(note 9)
–
–
stationary
> 100
Distributed energy storage; energy storage station video (A.4.6)
> 99.99 %
–
< 100 ms (note 10);
DL:<1 Mbit/s
–
–
–
–
–
Advanced metering (A.4.7)
> 99.999 %
–
20 ms
–
< 100 byte
–
–
–
several km2
Distributed automated switching for isolation and service restoration (A.4.4.1) (note 7)
> 99.999 9 %
< 3 ms
–
160 byte
–
–
–
–
Distributed Energy Resources (DERs) and micro-grids (A.4.9) (note 7)
NOTE 1: Unless otherwise specified, all communication includes 1 wireless link (UE to network node or network node to UE) rather than two wireless links (UE to UE).
NOTE 2: (void)
NOTE 3: Length x width x height.
NOTE 4: Scheduled aperiodic traffic with transfer interval (max end-to-end allowed latency < transfer interval).
NOTE 5: It applies to both UL and DL unless stated otherwise.
NOTE 6: It applies to both linear movement and rotation unless stated otherwise.
NOTE 7: Communication includes two wireless links (UE to UE).
NOTE 8: The mobile operation panel is connected wirelessly to the 5G system. If the mobile robot/production line is also connected wirelessly to the 5G system, the communication includes two wireless links.
NOTE 9: The service bit rate in one energy storage station can be calculated as follows:12.5 Mbytes/s x 50 containers x 8 = 5 Gbit/s.
NOTE 10: The maximum allowed end-to-end latency is for accuracy fee control. It is the delay for one-way communication between the backend system and the 5G IoT device. The distance between the two is 40 km or lower (city range). |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 5.4 Non-deterministic communication | Non-deterministic communication subsumes all other traffic types than periodic/aperiodic deterministic communication. This includes periodic/aperiodic non-real-time traffic. A description of non-deterministic communication can be found in Clauses 4.3 and 4.4. Additional information on the underlying use cases of the sets of requirements in Table 5.4‑1 can be found in Annex A. Further information on characteristic parameters and influence quantities used in Table 5.4-1 can be found in Annex C.
The 5G system shall be able to provide non-deterministic communication with the service performance requirements for individual logical communication links that realise the communication services reported in Table 5.4-1.
Table 5.4-1: Non-deterministic communication service performance requirements
Characteristic parameter (KPI)
Influence quantity
Communication service reliability: mean time between failures
Service bit rate: user-experienced data rate
UE speed (note 2)
# of UEs
Service area (note 1)
Remarks
~ 1 month
DL: ≥ 1 Mbit/s
~ 0 km/h
≤ 75 km/h
≤ 100
50 m x 10 m x 10 m
Motion control - software updates (A.2.2.1)
UL: > 10 Mbit/s
≤ 50 km/h (linear movement)
≤ 2,000
≤ 1 km2
Mobile robots; real-time video stream (A.2.2.3)
NOTE 1: Length x width x height
NOTE 2: It applies to both linear movement and rotation unless stated otherwise. |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 5.5 Mixed traffic | Mixed traffic cannot be assigned to one of the other communication patterns exclusively. Additional information on the underlying use cases of the sets of requirements in Table 5.5-1 can be found in Annex A. Further information on characteristic parameters and influence quantities used in Table 5.5-1 can be found in Annex C.
The 5G system shall be able to provide mixed traffic communication with the service performance requirements for individual logical communication links that realise the communication services reported in Table 5.5-1.
Table 5.5-1: Mixed traffic communication service performance requirements
Characteristic parameter (KPI)
Influence quantity
Remarks
Communication service availability
Communication service reliability: mean time between failures
Max Allowed End-to-end latency (note 1)
(note 3)
Service bit rate: aggregate user-experienced data rate
Message
Size
[byte]
Survival time
UE speed
# of UEs
Service Area
99.999 999 9 %
~ 10 years
16 ms
stationary
< 1,000
several km²
Wind power plant – control traffic (A.5.2)
99.999 9 % to 99.999 99 %
1 day
(note 4)
12 Mbit/s
250 to 1,500
quasi-static; up to 10 km/h
2 or more
30 m x 30 m
Mobile Operation Panel: Manufacturing data stream (A.2.4.1A)
NOTE 1: Unless otherwise specified, all communication includes 1 wireless link (UE to network node or network node to UE) rather than two wireless links (UE to UE).
NOTE 2: (void)
NOTE 3: It applies to both UL and DL unless stated otherwise.
NOTE 4: The mobile operation panel is connected wirelessly to the 5G system. If the mobile robot/production line is also connected wirelessly to the 5G system, the communication includes two wireless links. |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 5.6 Clock synchronisation requirements | |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 5.6.0 Description | Clock synchronicity, or time synchronization precision, is defined between a sync master and a sync device. The requirement on the synchronicity budget for the 5G system is the time error contribution between ingress and egress of the 5G system on the path of clock synchronization messages.
Clock synchronisation requirements specific for direct device connection and indirect network connection are captured in section 7.2.3 and 8.2.3. |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 5.6.1 Clock synchronisation service level requirements | The 5G system shall support a mechanism to process and transmit IEEE 1588v2 / Precision Time Protocol messages to support 3rd-party applications which use this protocol.
The 5G system shall support a mechanism to synchronise the user-specific time clock of UEs with a global clock.
The 5G system shall support a mechanism to synchronize the user-specific time clock of UEs with a working clock.
The 5G system shall support two types of synchronization clocks, the global time domain and the working clock domains.
The 5G system shall support networks with up to 128 working clock domains (with different synchronization domain identifiers / domain numbers), including for UEs connected through the 5G network.
NOTE 1: The domain number (synchronization domain identifier) is defined with one octet in IEEE 802.1AS [22].
The 5G system shall be able to support up to four simultaneous synchronization domains on a UE.
NOTE 1A: The four synchronization domains are used, for example, as two synchronization domains for global time and two working clock domains. One pair of global time and working clock is used as redundant synchronization domains for zero failover time.
The synchronicity budget for the 5G system within the global time domain shall not exceed 900 ns.
NOTE 2: The global time domain requires in general a precision of 1 µs between the sync master and any device of the clock domain. Some use cases require only a precision of ≤ 100 µs for the global time domain if a working clock domain with precision of ≤ 1 µs is available.
NOTE 3: (void)
The synchronicity budget for the 5G system within a working clock domain shall not exceed 700 ns.
NOTE 4: The working clock domains require a precision of ≤ 1 µs between the sync master and any device of the clock domain.
NOTE 5: Different working clock domains are independent and can have different precision.
NOTE 6: The synchronicity budget for the 5G system is also applicable when the flow of clock synchronization messages traverses the air interface twice.
The 5G system shall provide a media-dependent interface for one or multiple IEEE 802.1AS sync domains [22].
The 5G system shall provide an interface to the 5G sync domain which can be used by applications to derive their working clock domain or global time domain (Reference Clock Model).
The 5G system shall provide an interface at the UE to determine and to configure the precision and time scale of the working clock domain.
The 5G system shall be able to support arbitrary placement of sync master functionality and sync device functionality in integrated 5G / non-3GPP TSN networks.
The 5G system shall be able to support clock synchronization through the 5G network if the sync master and the sync devices are served by different UEs. (Flow of clock synchronization messages is in either direction, UL and DL.)
The 5G system shall provide a suitable means to support the management of the merging and separation of working clock domains, that is interoperable with the corresponding mechanisms of TSN and IEEE 802.1AS.
The 5G system shall provide a suitable means to support precise time distribution, clock synchronization and synchrophasor communication functionalities specific to smart grid applications, e.g.:
- IEC 61850-9-3 [30] profile and IEEE Std C37.238-2017 [31].
- at least one of the two profiles for synchrophasor communications: IEC 61850-90-5:2012 [32], or IEEE Std C37.118.2-2011 [33].
7NOTE 7: The requirement above assumes the ability to support all main clock synchronization functionalities defined in the respective references, unless explicitly indicated. Support of IEC 61850-90-5 can entail supporting multiple profiles (e.g. A-profile, T-profile, KDC-profile and IEEE 802.1Q QoS profiles can be applicable for support of synchrophasor communications). |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 5.6.2 Clock synchronisation service performance requirements | Table 5.6.2-1: Clock synchronization service performance requirements for 5G System
User-specific clock synchronicity accuracy level
Number of devices in one communication group for clock synchronisation
5GS synchronicity budget requirement
(note 1)
Service area
Scenario
1
up to 300 UEs
≤ 700 ns (note 4)
≤ 100 m x 100 m
• Motion control (A.2.2.1)
• Control-to-control communication for industrial controller (A.2.2.2)
2
up to 300 UEs
≤ 700 ns (note 4)
≤ 1,000 m x 100 m
• Control-to-control communication for industrial controller (A.2.2.2)
3
up to 10 UEs
< 10 µs
≤ 2,500 m2
• High data rate video streaming
3a
up to 100 UEs
< 1 µs
≤ 10 km2
• AVPROD synchronisation and packet timing
4
up to 100 UEs
< 1 µs
< 20 km2
• Smart Grid: synchronicity between PMUs
4a
up to 100 UEs
< 250 ns to 1 µs
< 20 km²
Smart Grid: IEC 61850-9-2 Sampled Values
4b
up to 100 UEs
<10-20 µs
< 20 km²
Smart Grid: IEC 61850-9-2 Sampled Values – Power system protection in digital substation
4c
54/km² (note 2)
78/km2 (note 3)
< 10 µs
several km²
Smart Grid: Intelligent Distributed Feeder Automation (A.4.4.3)
4d
up to 100 UEs
<1 ms
< 20 km²
Smart Grid: IEC 61850-9-2 Sampled Values – Event reporting and Disturbance recording
5
up to 10 UEs
< 50 µs
400 km
• Telesurgery (A.6.2) and telediagnosis (A.6.3)
NOTE 1: The clock synchronicity requirement refers to the clock synchronicity budget for the 5G system, as described in Clause 5.6.1.
NOTE 2: When the distributed terminals are deployed along overhead line, about 54 terminals will be distributed along overhead lines in one square kilometre. The resulting power load density is 20 MW/km2.
NOTE 3: When the distributed terminals are deployed in power distribution cabinets, there are about 78 terminals in one square kilometre. The resulting power load density is 20 MW/km2.
NOTE 4: 5GS synchronicity budget requirement refers to working clock domain for a localized set of UEs callaborating on a specific task or work function.
5.6A Time-sensitive communication requirements
The 5G system shall support the fully distributed model for configuration of time-sensitive networking.
The 5G system shall support the fully distributed model for configuration of time-sensitive networking that is aligned with Multiple Stream Registration Protocol (MSRP, IEEE 802.1Q [19] clause 35.1), IEEE P802.1CS Link-local Registration Protocol (LRP) [24], and IEEE P802.1Qdd Resource Allocation Protocol (RAP) [25].
The 5G system shall support the user-network / network-network interface for the dynamic configuration of the fully distributed model for time-sensitive networking.
5.6B 5G Timing Resiliency
To enable support of many critical services within the 5G network, additional requirements and KPIs that enhance the 5G system with timing resiliency are specified in TS 22.261 [2] clauses 6.36 and 7.8. Those enhancements enable use of the 5G system for time critical services in collaboration with or as a backup to other timing solution such as loss or degradation of GNSS reference timing.
5.6C Support for infrastructure protection of electrical transmission
5.6C.1 Description
Transmission infrastructure is a key component of the energy system. Communication enables protection of this infrastructure. The algorithms involved depend on certain constraints must be met, particularly concerning the end-to-end latency.
5.6C.2 Requirements
The 5G system shall support an end-to-end latency of less than 5 ms or 10 ms, as requested by the UE initiating the communication.
NOTE 1: Whether the end-to-end latency is 5 ms or 10 ms depends on the applied voltage level.
NOTE 2: The end-to-end latency is between two UEs, including two wireless links.
The 5G system shall support communication channel symmetry in terms of end-to-end latency (latency from UE1 to UE2, and end-to-end latency from UE2 to UE1), with an asymmetry of < 2ms. |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 5.7 Positioning performance requirements | |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 5.7.1 General requirements | High accuracy positioning is becoming essential for Factories of the Future. The reason for this is that tracking of mobile devices as well as mobile assets is becoming increasingly important in improving processes and increasing flexibility in industrial environments.
The 5G system shall provide positioning information for a UE that is out of coverage of the network, with accuracy of < [1 m] relative to other UEs that are in proximity and in coverage of the network.
Table 5.7.1-1 below lists typical scenarios and the corresponding high positioning requirements for horizontal and vertical accuracy, availability, heading, latency, and UE speed.
NOTE: The column on "Corresponding Positioning Service Level in TS 22.261" maps the scenarios listed in Table 5.7.1-1 to the service levels defined in TS 22.261 [2].
Table 5.7.1-1: Positioning performance requirements
Scenario
Horizontal accuracy
Vertical accuracy
Availability
Heading
Latency for position estimation of UE
UE speed
Corresponding Positioning Service Level in TS 22.261
Mobile control panels with safety functions (non-danger zones)
< 5 m
< 3 m
90 %
n/a
< 5 s
n/a
Service Level 2
Process automation – plant asset management
< 1 m
< 3 m
90 %
n/a
< 2 s
< 30 km/h
Service Level 3
Flexible, modular assembly area in smart factories (for tracking of tools at the work-place location)
< 1 m (relative positioning)
n/a
99 %
n/a
1 s
< 30 km/h
Service Level 3
Augmented reality in smart factories
< 1 m
< 3 m
99 %
< 0.17 rad
< 15 ms
< 10 km/h
Service Level 4
Mobile control panels with safety functions in smart factories (within factory danger zones)
< 1 m
< 3 m
99.9 %
< 0.54 rad
< 1 s
n/a
Service Level 4
Flexible, modular assembly area in smart factories (for autonomous vehicles, only for monitoring purposes)
< 50 cm
< 3 m
99 %
n/a
1 s
< 30 km/h
Service Level 5
Inbound logistics for manufacturing (for driving trajectories (if supported by further sensors like camera, GNSS, IMU) of indoor autonomous driving systems))
< 30 cm (if supported by further sensors like camera, GNSS, IMU)
< 3 m
99.9 %
n/a
10 ms
< 30 km/h
Service Level 6
Inbound logistics for manufacturing (for storage of goods)
< 20 cm
< 20 cm
99 %
n/a
< 1 s
< 30 km/h
Service Level 7 |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 5.7.2 Energy efficiency requirements for high accuracy positioning | The 5G system shall support low power high accuracy positioning mechanisms that allow a battery-constrained UE to sustain a long lifetime without changing battery. Some corresponding use cases and example scenarios are captured in Annex A.7.2. |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 5.8 Network operation requirements | For use by Industry 4.0, the 5G system needs to meet various operational options that are not typical in a traditional mobile operator setting. Additional system requirements that enable a 5G system to support those options are included in this clause.
5G system shall provide support for reliable communications when a UE serves as a TSN talker or listener so there is no single point of service failure. |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 6 Ethernet applications | |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 6.1 Description | This section lists the requirements applicable to the 5G system for supporting cyber-physical applications using Ethernet.
For requirements pertaining to common, fundamental Ethernet transport requirements, and any requirements necessary to support the 5G LAN-type service, see Clause 6.24 in TS 22.261 [2]. |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 6.2 Requirements | For infrastructure dedicated to high performance Ethernet applications, the 3GPP system shall support clock synchronisation defined by IEEE 802.1AS across 5G-based Ethernet links with PDU-session type Ethernet.
For infrastructure dedicated to high performance Ethernet applications, the 3GPP system shall support clock synchronisation defined by IEEE 802.1AS across 5G-based Ethernet links and other ethernet transports such as wired and optical (EPON.)
For infrastructure dedicated to high performance Ethernet applications, the accuracy of clock synchronisation should be better than 1µs.
For infrastructure dedicated to high performance Ethernet applications, the 3GPP system shall support enhancements for time-sensitive networking as defined by IEEE 802.1Q, e.g. time-aware scheduling with absolute cyclic time boundaries defined by IEEE 802.1Qbv [19], for 5G-based Ethernet links with PDU sessions type Ethernet.
For infrastructure dedicated to high performance Ethernet applications, absolute cyclic time boundaries shall be configurable for flows in DL direction and UL direction.
For infrastructure dedicated to high performance Ethernet applications, the 3GPP system shall support coexistence of hard-RT traffic following a time-aware schedule and lower priority traffic. The lower priority traffic cannot have a performance degrading impact on the hard-RT traffic.
The Ethernet transport service shall support routing based on information extracted from the Ethernet header information created based on IEEE 802.1Qbv. |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 7 Direct device connection for cyber-physical control applications | |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 7.1 Description | This section lists the requirements applicable to the 5G system for supporting cyber-physical control applications using wireless direct device connection. |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 7.2 Requirements | |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 7.2.1 General | The 5G system shall allow UEs to use direct device connection when the UEs are not served by a RAN.
The 5G system shall be able to support direct device connection between UEs in close proximity using spectrum different than the spectrum being used for the 5GC-based communication.
The 5G system shall be able to support direct device connection for 5G LAN-type private communication.
The 5G system shall be able to support multicast communication between the UEs within the group of UEs using direct device connection . |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 7.2.2 Network performance | The 5G system shall be able to support direct device connection between a group of UEs for periodic deterministic communication (both unicast and multicast) with respective service performance requirements in Table 5.2-1 related to cooperative carrying.
The 5G system shall be able to support mobility of the group of UEs using direct device connections with respective service performance requirements in Table 5.2-1 related to cooperative carrying.
The 5G system shall be able to support direct device connection with respective service performance requirements in Table 5.2-1 related to cooperative carrying between UEs up to 50 m distance. |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 7.2.3 Clock synchronization | |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 7.2.3.1 Description | This clause lists the service level requirements and performance requirements applicable to the 5G system for supporting clock synchronization for direct device connection, building on the description already provided in Clause 5.6.0. |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 7.2.3.2 Clock synchronization requirements | The 5G system shall be able to support clock synchronization (working clock domain) between the UEs within the group of UEs using direct device connection ProSe communication.
The 5G system shall be able to support Precision Time Protocol-based (IEEE 802.1AS [22] or another applicable IEEE Std 1588 [34] profile) or 5G sync domain-based clock synchronization among the group of UEs using direct device connection.
The 5G system shall be able to support the sync master of the working clock domain being connected to one of the UEs or being hosted at one of the UEs in the group of UEs using direct device connection.
The 5G system shall be able to support up to four simultaneous synchronization domains on a UE using direct device connection.
The 5G system using direct device connection shall support one or multiple time domains (IEEE 802.1AS [22] or another applicable IEEE Std 1588 [34] profile or 5G sync domain configuration).
The 5G system shall provide a suitable means to support the merging and separation of working clock domains at the UEs within the group of UEs connected by direct device connection, that is interoperable with the corresponding mechanisms of IEEE 802.1AS [22], IEEE Std 1588 [34], or 5G sync domain.
For direct device connection, the 5G system shall be able to support a 5GS synchronicity budget for clock synchronization according to Table 7.2.3.2-1. In this case, the sync master and sync device are located at or connected to two UEs which are connected via direct device connection.
Table 7.2.3.2-1: Direct device connection clock synchronization service performance requirements for 5G System
Number of devices in one communication group for clock synchronization
5GS synchronicity budget requirement
(note 1)
Service area
(note 2)
Scenario
2 to 16
≤ 700 ns
10 m x 10 m x 5 m;
50 m x 5 m x 5 m
Cooperative carrying – fragile work pieces; (A.2.2.5)
2 to 16
≤ 700 ns
10 m x 10 m x 5 m;
50 m x 5 m x 5 m
Cooperative carrying – elastic work pieces; (A.2.2.5)
NOTE 1: 5G synchronicity budget is the time error between ingress and egress of the 5G system on the path of clock synchronization messages (as described in Clause 5.6.0). For direct device connection, the ingress is one UE and the egress the other directly connected UE.
NOTE 2: Service Area for direct device connections between UEs (length x width x height). The group of UEs with direct device connections might move throughout the whole factory site (up to several km²). |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 7.2.4 Service Continuity | The 5G system shall be able to minimize service disruption for a group of UEs using direct device connection with respective service performance requirements in Table 5.2-1 related to cooperative carrying, when the group moves between a non-public network and a PLMN (subject to operator policies and agreement between the operators and service providers). |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 7.2.5 Direct device connection via UE to UE relay | The 5G system shall be able to support direct device connection via an UE to UE relay with respective service performance requirements in Table 5.2-1 related to cooperative carrying between UEs out of transmission range of each other. |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 8 Indirect network connection for cyber-physical control applications | |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 8.1 Description | This section lists the requirements applicable to the 5G system for supporting cyber-physical control applications using wireless indirect network connection. |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 8.2 Requirements | |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 8.2.1 General | The 5G system shall be able to support multicast communication between the UEs within the group of UEs using indirect network connection. |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 8.2.2 Communication via indirect network connection | The 5G system shall be able to provide service to an out-of-coverage UE via indirect network connection using one relay UE while meeting the performance requirements specified for the process automation use cases in Table 5.2-1 (related to Annex A.2.3.1 and A.2.3.2). |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 8.2.3 Clock synchronization | |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 8.2.3.1 Description | This clause lists the service level requirements and performance requirements applicable to the 5G system for supporting clock synchronization for indirect network connection, building on the description already provided in Clause 5.6.0. |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 8.2.3.2 Clock synchronization requirements | The 5G system shall be able to support clock synchronization (working clock domain) for UEs using indirect network connection.
The 5G system shall be able to support Precision Time Protocol-based (IEEE 802.1AS [22] or another applicable IEEE Std 1588 [34] profile) or 5G sync domain-based clock synchronization for UEs using indirect network connection.
The 5G system shall be able to support the sync master of the working clock domain being connected to one of the UEs or being hosted at one of the UEs using indirect network connection.
The 5G system shall be able to support up to four simultaneous synchronization domains on a UE using indirect network connection.
The 5G system shall provide a suitable means to support the merging and separation of working clock domains at the UEs connected by indirect network connection, that is interoperable with the corresponding mechanisms of IEEE 802.1AS [22] or another applicable IEEE Std 1588 [34] profile or 5G sync domain.
For indirect network connection between UEs using one UE-to-network relay, the 5G system shall be able to support a 5GS synchronicity budget for clock synchronization according to Table 8.2.3.2-1.
Table 8.2.3.2-1: Indirect network connection clock synchronization service performance requirements for 5G System
Number of devices in one communication group for clock synchronization
UE density [UE / m²]
5GS synchronicity budget requirement
(note 1)
Service area
(note 2)
Scenario
10 to 20 UEs
-
< 1 ms
≤ 100 m x 100 m x 50 m
Process automation – closed loop control (A.2.3.1)
≤ 10,000 to 100,000
-
≤ 1 ms
≤ 10 km x 10 km x 50 m
Process and asset monitoring (A.2.3.2)
NOTE 1: 5G synchronicity budget is the time error between ingress and egress of the 5G system on the path of clock synchronization messages (as described in Clause 5.6.0). For indirect network connection, 3 cases are considered:
1) If the path of clock synchronization messages is between device and network side, ingress and egress of the 5G system are the remote UE and the corresponding UPF on the network side.
2) If ingress and egress of the 5G system are at the device side, the 5G synchronicity budget is the time error between the involved remote UE and the 5G sync master.
3) If the sync master is inside the 5G system, the 5G synchronicity budget ingress is the sync master in the 5G system and egress is the remote UE.
NOTE 2: Service Area for indirect network connections between UEs (length x width x height). |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 8.2.4 Service Continuity | The 5G system shall be able to minimize service disruption for a UE using indirect network connection with respective service performance requirements in Table 5.2-1 related to process automation, when the UE moves between a non-public network and a PLMN (subject to operator policies and agreement between the operators and service providers). |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 9 Recovery of infrastructure for electrical distribution | |
162c3f0c36a54745dc509a8130708d2d | 22.104 | 9.1 Description | The robustness of the infrastructure for electrical power distribution may depend upon the possibility to operate telecommunication networks even during an energy system incident, in which electricity cannot be delivered to some network operator facilities. Through coordination between the network operator and the energy system operator, increases in the ability to recover the energy system operation can be achieved. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.