Name,Description,Reference
g.3gpp.iut-focus,This feature-capability indicator when used in a Feature-Caps header field of a SIP request or a SIP response indicates that the function which inserted the Feature-Caps header field supports anchoring an IUT session.,[3GPP TS 24.337 10.7.0]
g.3gpp.mid-call,"This feature-capability indicator when used in a Feature-Caps header field of a SIP request or a SIP response indicates that:
1. the functional entity including the feature-capability indicator in the SIP message supports the MSC server assisted mid-call feature; and
2. all entities of which the functional entity including the feature-capability indicator in the SIP message is aware of being requested to
support the feature do support the MSC server assisted mid-call feature.",[3GPP TS 24.237 10.10.0]
g.3gpp.atcf,This feature-capability indicator when included in a Feature-Caps header field as specified in IETF [RFC6809] in a SIP REGISTER request or a SIP response to the SIP REGISTER request indicates presence and support of a resource which is an Access Transfer Control Function (ATCF) and also the session transfer number allocated to the ATCF.,[3GPP TS 24.237 10.10.0]
g.3gpp.srvcc-alerting,"This feature-capability indicator when used in a Feature-Caps header field of a SIP request or a SIP response indicates that:
1. the functional entity including the feature-capability indicator in the SIP message supports access transfer for calls in alerting phase; and
2. all entities of which the functional entity including the feature-capability indicator in the SIP message is aware of being requested to support
the feature do support access transfer for calls in alerting phase.",[3GPP TS 24.237 10.10.0]
g.3gpp.atcf-mgmt-uri,This feature-capability indicator when used in a Feature-Caps header field as specified in IETF [RFC6809] [60] in SIP REGISTER request indicates presence and support of performing as a UAS for SIP requests for ATCF management received at this URI.,[3GPP TS 24.237 10.10.0]
g.3gpp.srvcc,"This feature-capability indicator when included in a Feature-Caps header field as specified in IETF [RFC6809] of:
- a SIP INVITE request; or
- a SIP INVITE response;
indicates presence and support of a resource capable of performing the SRVCC access transfer procedure as specified in 3GPP TS 24.237.",[3GPP TS 24.237 10.10.0]
g.3gpp.atcf-path,This feature-capability indicator when used in a Feature-Caps header field as specified in IETF [RFC6809] in SIP REGISTER request indicates capability of identifying the registration path and binding SRVCC related information to it.,[3GPP TS 24.237 10.10.0]
g.3gpp.cs2ps-srvcc,This feature-capability indicator when included in Feature-Caps header field as specified in IETF [RFC6809] [60] indicates support of the CS to PS single radio voice call continuity as specified in 3GPP TS 24.237.,[3GPP TS 24.237 11.10.0][Frederic_Firmin]
g.3gpp.ti,This feature-capability indicator when used in a Feature-Caps header field as specified in IETF [RFC6809] in SIP INVITE request or SIP response to the SIP INVITE request indicates the capability of associating a CS call with dialog created by the SIP INVITE request.,[3GPP TS 24.237 11.10.0][Frederic_Firmin]
g.3gpp.loopback,"This feature-capability indicator, when included in a Feature-Caps header field as specified in [RFC6809] in a SIP INVITE request, indicates the support of the roaming architecture for voice over IMS with local breakout.",[3GPP TS 24.229][Frederic_Firmin]
g.3gpp.trf,"This feature-capability indicator, when included in a Feature-Caps header field as specified in [RFC6809] in a SIP INVITE request, indicates that in a roaming scenario, the visited network supports a transit and roaming functionality in order to allow loopback of session requests to the visited network from the home network. When used, it may indicate the URI of the transit and roaming functionality.",[3GPP TS 24.229 11.11.0][Frederic_Firmin]
g.3gpp.home-visited,"This feature-capability indicator, when included in a Feature-Caps header field as specified in [RFC6809] in a SIP INVITE request, indicates that the home network supports loopback to the identified visited network for this session. The loopback is expected to be applied at some subsequent entity to the insertion point. The feature-capability indicator carries a parameter value which indicates the visited network.",[3GPP TS 24.229][Frederic_Firmin]
g.3gpp.mrb,"This feature-capability indicator when included in a Feature-Caps header field as specified in [RFC6809] in a SIP INVITE request indicates that in a roaming scenario, the visited network supports media resource broker functionality for the allocation of multimedia resources in the visited network. When used, it indicates the URI of the visited network MRB.",[3GPP TS 24.229 11.11.0][Frederic_Firmin]
g.3gpp.icsi-ref,"Each value of the Service Reference feature-capability indicator indicates the software applications supported by the entity. The values for this feature-capability indicator equal the IMS communication Service Identifier (ICSI) values supported by the entity.
Multiple feature-capability indicator values can be included in the Service
Reference feature-capability indicators.
When included in the Feature-Caps header field, according to [RFC6809], the value
of this feature-capability indicator contains the IMS communication service
identifier (ICSI) of the IMS communication service supported for use 1) in the
standalone transaction (if included in a request for a standalone transaction or
a response associated with it) or 2) in the dialog (if included in an initial request for dialog or a response associated with it) by the entity which included the Feature-Caps header field.",[3GPP TS 24.229 11.12.0][Frederic_Firmin]
g.3gpp.drvcc-alerting,This feature-capability indicator when included in a Feature-Caps header field as specified in IETF [RFC6809] in a SIP INVITE request or a SIP response to the SIP INVITE request indicates support of PS to CS dual radio access transfer for calls in alerting phase.,[3GPP TS 24.237 12.8.0][Frederic_Firmin]
g.3gpp.dynamic-stn,"This feature-capability indicator g.3gpp.dynamic-stn, when included in a Feature-Caps header field as specified in IETF [RFC6809] in a SIP INVITE request or a SIP response to the SIP INVITE request, indicates support to transfer the session to the circuit switched (CS) domain using the dynamic STN (session transfer number) digit string.",[3GPP TS 24.237 12.8.0][Frederic_Firmin]
g.3gpp.ps2cs-drvcc-orig-pre-alerting,"This feature-capability indicator g.3gpp.ps2cs-srvcc-orig-pre-alerting when used in a Feature-Caps header field of a SIP request or a SIP response indicates that:
1. the functional entity including the feature-capability indicator in the SIP
message supports the PS to CS SRVCC for originating calls in pre-alerting phase; and
2. all entities of which the functional entity including the feature-capability
indicator in the SIP message is aware of being requested to support the feature
do support the PS to CS SRVCC for originating calls in pre-alerting phase.",[3GPP TS 24.237 12.8.0][Frederic_Firmin]
g.3gpp.ps2cs-srvcc-orig-pre-alerting,"This feature-capability indicator g.3gpp.ps2cs-srvcc-orig-pre-alerting when used in a Feature-Caps header field of a SIP request or a SIP response indicates that:
1. the functional entity including the feature-capability indicator in the SIP
message supports the PS to CS SRVCC for originating calls in pre-alerting phase;
and
2. all entities of which the functional entity including the feature-capability
indicator in the SIP message is aware of being requested to support the feature
do support the PS to CS SRVCC for originating calls in pre-alerting phase.",[3GPP TS 24.237 12.8.0][Frederic_Firmin]
g.3gpp.cs2ps-drvcc-alerting,"This feature-capability indicator, when included in a Feature-Caps header field as specified in IETF [RFC6809] in a SIP request or a SIP response to the SIP request, indicates support of CS to PS dual radio access transfer for calls in alerting phase.",[3GPP TS 24.237 12.9.0][Frederic_Firmin]
g.3gpp.cs2ps-drvcc-orig-pre-alerting,This feature-capability indicator when included in a Feature-Caps header field as specified in IETF [RFC6809] in a SIP request or a SIP response to the SIP request indicates support of CS to PS dual radio access transfer for originating calls in pre-alerting phase.,[3GPP TS 24.237 12.9.0][Frederic_Firmin]
g.3gpp.ics,This feature-capability indicator when included in a Feature-Caps header field as specified in IETF [RFC6809] in a SIP initial request for dialog or a response associated with the SIP initial request indicates support of IMS Centralized Services (ICS).,[3GPP TS 24.292 12.8.0][Frederic_Firmin]
g.3gpp.registration-token,"This feature-capability indicator, when included in a Feature-Caps header field as specified in [RFC6809] [190] in a SIP REGISTER request, indicates the support of using a token to identify the registration used for the request.
This feature-capability indicator can be included in an originating initial INVITE request to identify which registration was used for this request by setting the indicator to the same value as in the +g.3gpp.registration-token media feature tag in the Contact header field of the REGISTER request.
This feature-capability indicator can be included in any response to a terminating INVITE request to identify which registration was used for the response by setting the indicator to the same value as in the +g.3gpp.registration-token media feature tag in the Contact header field of the REGISTER request.",[3GPP TS 24.229 12.16.0][Frederic_Firmin]
g.3gpp.verstat,"This feature-capability indicator, when included in a Feature-Caps header field as specified in
[RFC6809] in a 200 (OK) response to a REGISTER request, indicates that the home network supports calling party number verification, as described in [RFC8224].",[3GPP TS 24.229 v14.7.0][Frederic_Firmin]
g.3gpp.mcvideo.ambient-viewing-call-release,"This feature-capability indicator when included in a Feature-Caps header field as specified in IETF
[RFC6809] in a SIP INVITE request or a SIP 200 (OK) response to a SIP INVITE request indicates that the MCVideo server is capable of receiving a SIP BYE from an MCVideo client to release an ambient-viewing call.",[3GPP TS 24.281 Rel-15][Frederic_Firmin]
g.3gpp.mcptt.ambient-listening-call-release,"This feature-capability indicator when included in a Feature-Caps header field as specified in IETF
[RFC6809] in a SIP INVITE request or a SIP 200 (OK) response to a SIP INVITE request indicates that the MCPTT server is capable of receiving a SIP BYE from an MCPTT client to release an ambient-listening call.",[3GPP TS 24.379 v14.5.0][Frederic_Firmin]
g.3gpp.dynamic-e-stn-drvcc,"This feature-capability indicator, when included in a Feature-Caps header field as specified in IETF
[RFC6809] in a SIP response to a SIP INVITE request, indicates support to transfer the session to the circuit switched (CS) domain using the Emergency Session Transfer Number for DRVCC digit string.",[3GPP TS 24.237][Frederic_Firmin]
g.3gpp.ps2cs-srvcc-term-pre-alerting,This feature-capability indicator when used in a Feature-Caps header field of a SIP request or a SIP response indicates that: 1. the functional entity including the feature-capability indicator in the SIP message supports the PS to CS SRVCC for terminating calls in pre-alerting phase; and 2. all entities of which the functional entity including the feature-capability indicator in the SIP message is aware of being requested to support the feature do support the PS to CS SRVCC for terminating calls in pre-alerting phase.,[3GPP TS 24.237][Frederic_Firmin]
g.3gpp.priority-share,"When included in a Feature-Caps header field in SIP requests or SIP responses, the sender indicates that priority sharing is supported.",[3GPP TS 24.229 13.16.0][Frederic_Firmin]
g.3gpp.thig-path,"This feature-capability indicator when included in a Feature-Caps header field as specified in [RFC6809] in a 200 (OK) response to the REGISTER request indicates that in a roaming scenario, the visited network IBCF supports topology hiding of a Path header field.",[3GPP TS 24.229]
g.3gpp.anbr,"This feature-capability indicator, when included in a Feature-Caps header field as specified in [RFC6809] in a 200 (OK) response to a REGISTER request, indicates that the network supports ANBR as specified in 3GPP TS 26.114.",[3GPP TS 24.229]
g.3gpp.in-call-access-update,"This feature-capability indicator, when included in a Feature-Caps header field as specified in [RFC6809] in a SIP INVITE request or a response to a SIP INVITE, indicates that the entity supports in-call access update procedure specified in 3GPP TS 24.229. The value of this feature capability indicator is a SIP URI to where the entity can be reached.",[3GPP TS 24.229]
g.3gpp.datachannel,"This feature-capability indicator indicates the support of data channel capability in the network, and can be included in a Feature-Caps header field as specified in [RFC6809]
in a 200 (OK) response to the REGISTER request.",[3GPP TS 24.186]
Presently we were in a very dark road, and at a point where it dropped suddenly between steep sides we halted in black shadow. A gleam of pale sand, a whisper of deep flowing waters, and a farther glimmer of more sands beyond them challenged our advance. We had come to a "grapevine ferry." The scow was on the other side, the water too shoal for the horses to swim, and the bottom, most likely, quicksand. Out of the blackness of the opposite shore came a soft, high-pitched, quavering, long-drawn, smothered moan of woe, the call of that snivelling little sinner the screech-owl. Ferry murmured to me to answer it and I sent the same faint horror-stricken tremolo back. Again it came to us, from not farther than one might toss his cap, and I followed Ferry down to the water's edge. The grapevine guy swayed at our side, we heard the scow slide from the sands, and in a few moments, moved by two videttes, it touched our shore. Soon we were across, the two videttes riding with us, and beyond a sharp rise, in an old opening made by the swoop of a hurricane, we entered the silent unlighted bivouac of Ferry's scouts. Ferry got down and sat on the earth talking with Quinn, while the sergeants quietly roused the sleepers to horse. Plotinus is driven by this perplexity to reconsider the whole theory of Matter.477 He takes Aristotle¡¯s doctrine as the groundwork of his investigation. According to this, all existence is divided into Matter and Form. What we know of things¡ªin other words, the sum of their differential characteristics¡ªis their Form. Take away this, and the unknowable residuum is their Matter. Again, Matter is the vague indeterminate something out of which particular Forms are developed. The two are related as Possibility to Actuality, as the more generic to the more specific substance through every grade of classification and composition. Thus there are two Matters, the one sensible and the other intelligible. The former constitutes the common substratum of bodies, the other the common element of ideas.478 The general distinction between Matter and Form was originally suggested to Aristotle by Plato¡¯s remarks on the same subject; but he differs325 from his master in two important particulars. Plato, in his Timaeus, seems to identify Matter with space.479 So far, it is a much more positive conception than the ?λη of the Metaphysics. On the other hand, he constantly opposes it to reality as something non-existent; and he at least implies that it is opposed to absolute good as a principle of absolute evil.480 Thus while the Aristotelian world is formed by the development of Power into Actuality, the Platonic world is composed by the union of Being and not-Being, of the Same and the Different, of the One and the Many, of the Limit and the Unlimited, of Good and Evil, in varying proportions with each other. The Lawton woman had heard of an officer's family at Grant, which was in need of a cook, and had gone there. [See larger version] On the 8th of July an extraordinary Privy Council was summoned. All the members, of whatever party, were desired to attend, and many were the speculations as to the object of their meeting. The general notion was that it involved the continuing or the ending of the war. It turned out to be for the announcement of the king's intended marriage. The lady selected was Charlotte, the second sister of the Duke of Mecklenburg-Strelitz. Apart from the narrowness of her education, the young princess had a considerable amount of amiability, good sense, and domestic taste. These she shared with her intended husband, and whilst they made the royal couple always retiring, at the same time they caused them to give, during their lives, a moral air to their court. On the 8th of September Charlotte arrived at St. James's, and that afternoon the marriage took place, the ceremony being performed by the Archbishop of Canterbury. On the 22nd the coronation took place with the greatest splendour. Mother and girls were inconsolable, for each had something that they were sure "Si would like," and would "do him good," but they knew Josiah Klegg, Sr., well enough to understand what was the condition when he had once made up his mind. CHAPTER V. THE YOUNG RECRUITS Si proceeded to deftly construct a litter out of the two guns, with some sticks that he cut with a knife, and bound with pawpaw strips. His voice had sunk very low, almost to sweetness. A soft flurry of pink went over her face, and her eyelids drooped. Then suddenly she braced herself, pulled herself taut, grew combative again, though her voice shook. HoME²Ô¾®Ïè̫ʲôÐÇ×ù
ENTER NUMBET 0016mallbao.com.cn
hunlizhe.com.cn
www.jipbcd.com.cn
www.jjhgcme.com.cn
scchain.com.cn
tlchain.com.cn
smarttrip.net.cn
www.mtwu.com.cn
www.topnic.com.cn
www.tealove.com.cn