hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 4.2.1 Single CCA system | The functional architecture for a single CCA system according to the present document is presented in figure 2. Figure 2: Functional architecture NOTE 1: The SIP proxy function may be part of the "application control" interface or may be separate. The Critical Communications Application Server (CCAS) has a number of en... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 4.2.2 Multi-CCAS system | A multi-CCAS system is depicted in figure 3. Figure 3: Multi-CCAS system In the multi-CCAS system each CCAS may be in contact with "home" mobile units, but may also offer access to mobile units that have migrated to that CCAS as visitors. The visited CCAS allows routing of the signalling from a migrated mobile unit to ... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 4.2.3 Interconnection with legacy | Interconnection with legacy networks is outside the scope of the present document. It will be satisfied by interface 8b (8 bis) in figure 1, and its function is described in [i.11]. It may be realized by an existing interface from a legacy technology, for example an inter system interface from the appropriate technolog... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 5 Components | |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 5.0 Functional groups | The following clauses describe the functional groups involved in the implementation of the mission-critical PMR services over broadband. |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 5.1 Mobile unit | The Mobile Unit (MU) is the (mobile) sub-system used by the user to access the mission critical application. The MU contains the CCA client (the client part of the application) and one or several modems able to interface with the access sub-systems which provide IP connectivity for the client application. The access de... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 5.2 Access sub-systems | The access sub-systems provide the link between the CCA client and the infrastructure based application. They are generally based on wireless technologies, particularly the 3GPP Long Term Evolution (LTE) technology, but access may also be based on other type of wireless technologies such as WLAN (IEEE 802.11 [i.5]) or ... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 5.3 Critical Communication Application | |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 5.3.0 General | The CCA comprises a number of functional entities which when combined provide the application service to the MUs. The functional entities are not prescriptive, but illustrate the functionality required in offering the various aspects of the service. The CCA contains both application related services, for example which ... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 5.3.1 Access interfaces | |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 5.3.1.0 General | The CCA provides a number of access interfaces for both application purposes and for access network control, where available. The interfaces described in this clause are logical and do not imply a specific physical implementation. For example, a CCAS may employ more than one interface of each type to distribute the loa... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 5.3.1.1 Application control interface | The application control interface is the access point for signalling, both SIP and non-SIP (e.g. HTTP [22]) for the implementation of mission critical services over broadband. It is not used for the actual media flows. It provides facilities such as user authentication and registration with the CCAS, affiliation to gro... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 5.3.1.2 Media unicast interface | The media interface is the access point for media and media control signalling sent to and from the MU in unicast mode. The discovery of its transport address(es) is derived from service initiation dialogue with the application control interface. Information sent via this interface includes the media which is the conte... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 5.3.1.3 Media multicast interface | The media multicast interface is used by the CCA to transmit media to a group of MUs simultaneously using only a single resource from the underlying access sub-system. An example of a means of transport is the Enhanced Multimedia Broadcast Multicast Service (E-MBMS) offered by 3GPP LTE (see ETSI TS 136 300 [i.9]. The i... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 5.3.1.4 Unicast bearer control interface | The unicast bearer control interface is used by the CCA to set up unicast bearers with the relevant characteristics for control signalling and media exchange. More than one bearer may be established between CCAS and MU at any time, as the quality of service and priority characteristics required for control and various ... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 5.3.1.5 Multicast bearer control interface | The multicast bearer control interface is used by the CCA to set up multicast bearers for carrying control and media information to groups of users using the broadcast service of the underlying access sub-system. Note that, depending on the characteristics of the access sub-system, more than one application layer group... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 5.4 CCAS functional entities | |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 5.4.0 General | The notional functional entities of the CCAS which, when combined, provide the application service to the MUs that are described in the following clauses. The functional entities are not prescriptive, but illustrate the functionality required in offering the various aspects of the service. |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 5.4.1 SIP application server | The SIP application server provides functionality for terminal registration, and additionally provides registration functions for naming, group affiliation and individual call processes. Once the MU has established an IP connection with the application control interface, it performs a registration with the SIP applicat... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 5.4.2 Mobility management | The mobility management entity tracks the location of both individual MUs and the various communication groups of MUs that will participate in the various services. The mobility management entity tracks the following with respect to individuals and affiliated group members: • To the current CCAS which is providing serv... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 5.4.3 Group management | The group management entity is responsible for the definitions and memberships of communication groups within the CCA. For migrating MUs, the visited CCAS co-operates with the home CCAS. Each group has a defined set of parameters, such as priority level, permitted media types and so on, and also the defined membership ... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 5.4.4 Resource management | The resource management entity is responsible for interaction with the access networks for setting up and maintaining the appropriate bearers to and from MUs and groups of MUs in order to carry signalling and media information related to calls. It makes use of the information provided by the mobility management entity ... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 5.4.5 Control server | The control server entity is responsible for managing call related information. When a call is to be placed, the control server receives the call request from the initiator; determines whether the called party or group is available; requests resources from the resource management entity and determines whether the call ... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 5.4.6 Media distribution | The media distribution entity distributes the media within calls from current sourcing party to target party/parties within a call, making use of the various unicast and multicast paths provided by the resource management entity. |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 5.4.7 Security | The security entity is responsible for maintaining all elements of application related security, to ensure that CCA signalling and media is protected even when carried over otherwise unprotected bearers. Its functions include: • Control of encryption of signalling and media flows. • Control of integrity protection for ... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 5.4.8 Identity management | The identity management entity is responsible for authenticating the CCA user and providing the CCA client instance with the information the CCA client requires to obtain service from the CCAS. This information includes: • an access token; • an identity token; • a CCA individual identity; • agreed user profile identiti... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 6 Reference points, identities and protocols | |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 6.0 Reference points | The reference points are defined with reference to figure 4 where an LTE EPS provides the broadband IP connection between MU and CCAS. ETSI ETSI TS 103 269-2 V1.2.1 (2017-06) 24 Figure 4: Reference points A1: is the channel used for communication between the Mobile CCA (which is part of the Mobile Unit) and the Applica... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 6.1 Identities and protocols | |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 6.1.0 CCA User identities | The CCA user identity is specific to an individual user and a CCAS. The CCA user identity is used only for human user log-on and mutual authentication with the user's home CCAS. The CCA user identity is hidden from other users. The format of the CCA user identity is outside the scope of the present document. A user ide... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 6.1.1 CCA application identities | CCA application identities take the form of SIP Universal Resource Identifiers (URIs - see IETF RFC 3261 [2]) which have a format of user@application_domain.org (where the "user@" portion is optional and is called "userinfo"). These SIP URIs are globally usable and identify the user's home CCAS. If the network design p... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 6.1.2 Transport protocols | |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 6.1.2.0 Protocol layers | All transport protocols utilized by the CCA make use of IP (IPv4 [9] or IPv6 [10]), to allow operation over any broadband IP network. The main signalling channel (SIP) is carried over a reliable transport protocol, such as TCP [11] or SCTP [12]. This enables early re-transmission of signalling messages without forcing ... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 6.1.2.1 Unicast transport | Unicast transport will be provided by all types of underlying broadband IP network. Where an LTE EPS is the underlying network, the CCA makes use of the SGi interface for signalling and media. The characteristics of the bearer may be different for different application flows; for example an application signalling flow ... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 6.1.2.2 Multicast transport | For group addressed media and signalling, unicast bearers may be complemented by a broadcast bearer if the access sub-system provides this. Inbound traffic for media and associated signalling related to group addressed media (from MU to CCAS) is always provided by a unicast bearer, while outbound traffic may be provide... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 6.1.2.3 Control of unicast/broadcast transport over LTE | When an MU which is receiving media over a unicast bearer or set of unicast bearers moves into an area where the corresponding media stream(s) are broadcast over a set of broadcast bearers, transmission of this same information over the unicast bearers may be suspended. The CCAS may interact with the LTE EPC to release... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 6.1.3 Network layer protocols | The CCA makes use of SIP [2] for network layer protocols. SIP is used for: • Application level registration and deregistration. • Affiliation to groups for group calls. • Session initiation (individual and group calls). • Messaging and other such services. The parameters of each service such as service type, codec type... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 6.1.4 Application layer protocols | |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 6.1.4.0 Keep alive | Application layer protocols will be based on existing protocols where appropriate and carried over IP. The application layer protocols may include a periodic "keep alive" message which firstly ensures continuous information about the status of the MU to the CCAS, and secondly may be used to maintain lower layer transpo... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 6.1.4.1 Pseudo-broadcast protocol | The purpose of this protocol is to provide an information transmission function of background information from CCAS to its served MUs. Two main types of information may be transmitted using this method: • Service related information: this is information is related to the services provided by the infrastructure, includi... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 6.1.4.2 Group information exchange | A protocol within HTTP (see IETF RFC 7230 [22]) is used by the MU to request and receive information about groups, including lists of affiliated users. |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 6.1.4.3 Priority information requests | Priority information requests from the MU to the CCAS uses a protocol within HTTP (see IETF RFC 7230 [22]). ETSI ETSI TS 103 269-2 V1.2.1 (2017-06) 29 |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 6.1.4.4 Profile and CCA service parameter management | A protocol within HTTP [22] is used by MUs registered to suitably authorized users to read and modify user, device and group profiles and CCA service parameters, and is used by the CCAS to synchronize MUs with modified profiles and service parameters. |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 6.2 Standardized application codecs | |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 6.2.1 Voice Codec | For voice, two categories of vocoder should be considered: • a CCA code: the choice of this codec is outside the scope of the present document; • interoperability codecs: TETRA, Tetrapol, P25 Full Rate, P25 Half Rate. Any CCA codec shall have good intelligibility in noisy conditions. |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 6.2.2 Video Codec | The selection of a CCA video codec is outside the scope of the present document. |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7 Overview of services | |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.0 Introduction | The following clauses provide an overview of the services provided and a brief generic description of the signalling involved when applicable. |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.1 CCA system access | Before user access to a CCAS is possible, the MU has to attach to an access network and the CCA client has to perform SIP registration of the MU (i.e. the device) with a CCAS (see note) to permit an unauthenticated user to gain access to limited services, e.g. emergency calls. Then the CCA client can attempt to connect... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.2 Service registration | |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.2.0 Initial authentication procedure | |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.2.0.1 General | The normal sequence of events following power-on is illustrated in figure 8 (figure 8 does not consider the possibility of authentication or SIP registration failures). ETSI ETSI TS 103 269-2 V1.2.1 (2017-06) 31 Figure 8: Sequence of events in the MU following power up NOTE: Figure 8 shows how emergency calls are made ... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.2.0.2 Authentication | Before the CCA client's users can be granted access to full services, the CCA client has to create a CCA client instance particular to each user and has to create a UUID unique to each user's CCA client instance (e.g. by using the timestamp method of IETF RFC 4122 [26]) The CCA client is then required to register each ... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.2.1 Home network registration | Authentication and SIP registration with the user's home CCAS is possible as soon as the network used to access the Critical Communication Application provides connectivity. This may be achieved when the MU is in its home 3GPP network (e.g. when its LTE modem is attached to its HPLMN) or when the MU is using a non-home... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.2.2 Migration registration | When connected to an access network which provides connectivity to a CCAS that is not the home CCAS of the CCA client, the CCA client may elect to visit that CCAS by performing SIP registration with the non-home CCAS (see figure 10). This decision may be the result of manual selection by the user or may be configured i... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.2.3 SIP registration and access procedure | |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.2.3.1 General | The CCA client needs to register the MU and its users with the CCAS's SIP application server when it powers-up, joins a CCAS after having previously been registered with a different CCAS, changes its access network (e.g. from 3GPP to a non-3GPP network or from one WiFi network to another WiFi network), or after any oth... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.2.3.2 Preparation for SIP registration - the access procedure | The CCA client may be required to present a limited-access token for the MU and access tokens for each of its users during the SIP registrations. These are obtained during initial authentication. The CCA client is required to create and SIP register a separate CCA client instance for the MU and each of its users. The C... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.2.3.3 SIP registration of the CCA client | When performing SIP registration of the CCA client, the CCA client instance shall place its CCA client identity in the From header field of the SIP REGISTER message. If the CCA client has a limited-access token obtained during a previous user authentication, as described in clause 7.2.0.2, the MU should present the lim... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.2.3.4 SIP registration of users | When performing SIP registration of a user, the CCA client instance shall place the user's CCA individual identity in the From header field of the SIP REGISTER message. In order to register a user with a CCAS's SIP application server the CCA client requires a CCA client instance specific to the CCA user and may require... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.2.3.5 Identities used for SIP registration | The CCA client instance shall place its CCA client identity in the Contact header field of the SIP REGISTER message and shall request a GRUU (see IETF RFC 5627 [30]) by including an "instance ID" in the "+sip.instance" Contact header field parameter defined in IETF RFC 5626 [29]. The instance ID shall contain the CCA c... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.2.3.6 Device class and device capabilities | The MU is pre-provisioned with the MU's device class and device capabilities (see clause 9.1). If either of these has changed since they were last sent to the CCAS, they should be sent to the CCAS now in a SIP PUBLISH message. |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.2.3.7 Subscription to event services | On completion of the registration and publication process, the CCA client instance shall subscribe to event services relevant to the CCA using the SIP Specific Event Notification process [4] (SIP SUBSCRIBE) and subscribing to the "reg" event package, and may subscribe to other relevant event packages using further SIP ... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.2.3.8 Service parameters, profiles and security parameters | Following registration, the CCA client instance obtains the CCAS service parameters and the device, user and group profiles that the CCAS has associated with the CCA client instance. Specifically, the CCA client instance sends a request for a particular profile in a SIP SUBSCRIBE message containing the CCA client ident... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.2.3.9 Group affiliations and media paths | Once the MU and the CCA client instance(s) have completed their SIP registrations, exchanged device class, device capabilities, service parameters and profiles, and subscribed to event services, the secure connection is used by the signalling protocols to set up group affiliations and calls as needed. The SIP message e... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.2.4 Periodic update | A periodic registration update procedure allows the maintenance of accurate registration records in the CCAS and purging the database of records corresponding to units which have silently disappeared due to link failures. Timing of the periodic update is determined by a combination of the home and serving CCASs. On ini... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.2.5 Deregistration | When the MU no longer requires service from the CCAS (for example as the result of a user action such as switching off the MU) the MU deregisters from the CCAS. A SIP REGISTER message is sent, with the "expires" header set to zero (i.e. reducing the lifetime of the current registration to zero). The MU may send informa... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.2.6 Remote deregistration | If a user is registered to the CCAS with two or more MUs, the user may use one MU to transmit a request to the CCAS to cancel his user registration on other MUs by using HTTPS (see IETF RFC 2818 [23]) to query the CCAS's identity management entity to obtain references to the relevant authentication instances and then s... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.3 Individual streaming communication | |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.3.0 General | |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.3.0.1 The individual communication process | Individual communications may be established between two MUs or an MU and a fixed unit or external telephony subscriber, both in incoming or outgoing call mode. The individual calls that do not include an external telephony subscriber may use on/off hook signalling with explicit alerting of the call recipient, or may u... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.3.0.2 Media control protocol for individual calls | The Media Control Protocol (MCP) - see annex B - shall be used to control the flow of media during a half-duplex call. Different calls and media types are distinguished by different flow identifications. The first MU to request permission to transmit in a call with a particular media type chooses a flow identification ... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.3.0.3 Individual call states | A simplified state-event diagram for individual call is shown in figure 13. NOTE 1: The CCA client instance may be idle or receiving in a call in the "Session joined" state. NOTE 2: The CCA client instance may receive media in "Active TX" state (full duplex call) and "TX Request" states (half and full duplex calls). NO... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.3.1 Individual unit to unit call with on/off hook signalling | This service is analogous to the normal fixed telephony or cellular telephony service. After dialling by the calling party, the calling MU sends a SIP INVITE containing a parameter indicating that call setup is being requested to initiate call set up signalling to the CCAS and also containing parameters indicating that... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.3.2 Individual unit to unit call with direct signalling | It is possible to shorten the call setup time for individual call by bypassing the alerting step and connecting directly as soon as the called unit is reachable. This also allows the user experience to be more similar to normal (unacknowledged or unconfirmed) group call. In this case, the alerting step of sending SIP R... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.3.3 Individual unit to telephony call (outgoing call) | Mobile units may perform calls to external subscribers (including emergency addresses) using fixed telephony interface. Only the message flows for a SIP based interface are standardized, but legacy ISDN interfaces may be supported through additional (non-standardized) gateways. The calling MU is kept informed by the CC... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.3.4 Individual unit to telephony call (incoming call) | Mobile units may receive calls from external subscribers using a fixed telephony interface. As indicated above, only SIP based message flows are standardized, but legacy ISDN interfaces may be supported through additional (non- standardized) gateways. The receiving user may reject the call. An authorized user may cause... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.4 Group streaming communication | |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.4.0 General | |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.4.0.1 The Group communication process | The group call service is a point to multipoint service, where one MU transmits to a group of MUs who receive the transmitted information almost simultaneously (subject to small variations in delay of the media transport service). In the normal case, group members affiliate to the group before placing calls. This allow... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.4.0.2 Media control protocol for group calls | The Media Control Protocol (MCP - see annex B) shall be used to control the flow of media during the call. Different calls and different media types can be distinguished by different flow identifications. The first MU to request permission to transmit in a call with a particular media type chooses a flow identification... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.4.0.3 Group call states | A simplified state-event diagram for group call is shown in figure 18. NOTE 1: Prior to receiving a SIP NOTIFY, the CCA client instance subscribes to its affiliation document. NOTE 2: Floor control signalling in the "Affiliated, no session joined" state is received over a multicast channel. NOTE 3: State changes in the... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.4.0.4 E-MBMS use | A group call downlink from a 3GPP network may be broadcast using the Enhanced Multimedia Broadcast Multicast Service (E-MBMS) in some areas. The E-MBMS may use a multicast-broadcast single-frequency network (MBSFN) or single-cell point-to-multipoint (SC-PTM). In those areas the 3GPP network may broadcast announcements ... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.4.1 Broadcast and system call | A broadcast call is a group communication to a given group where the receiving parties are not allowed to request transmission. Thus, the authorization to request transmission shall be indicated in an information element of the call setup or TX Granted message. The CCAS may merge multiple groups (see clause 7.11.3) to ... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.4.2 Group communication coverage | The coverage of a group communication may be potentially unlimited, i.e. extended to the location of every affiliated group member, including affiliated members migrating in all or part of any visited networks, or potentially unlimited but only inside the home network, or limited inside a given geographic area defined ... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.4.3 Group provisioning | The group(s) to which an MU may request affiliation are expected to be provisioned in the database of the terminal. The configuration may be programmed statically or may be updated using the individually addressed Dynamic Group Number Assignment supplementary service (DGNA). The CCAS may accept or deny the affiliation(... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.4.4 Group affiliation, mobility and selection | |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.4.4.0 Group affiliation | The group service affiliation procedure allows the CCA client instance and the CCAS to negotiate permission for the CCA client instance to participate in calls to a group of which the CCA client instance's user is a member. The affiliation process supports both CCA client-requested group affiliations and CCAS-directed ... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.4.4.1 Relation between group affiliation and mobility | When the geographic location (reported, for example, by the signalling channel heartbeats) indicates that the MU has moved outside a designated coverage area for a group (see clause 7.4.2), for example due to a change of jurisdiction, the network may modify or suspend the group affiliations of the mobile unit. This may... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.4.4a Group selection | The selected group is the group to which the MU will request a call if the user attempts to transmit when the MU is not in a call. The action of "selecting" a group will cause a change in state at the MU, as the MU will know that pressing the PTT switch when the MU is not in a call should result in a request to transmi... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.4.5 Session join and call start | A group session is joined by an exchange of SIP signalling between MU and CCAS. Once an MU has joined a session, only media control protocol signalling (see annex B) is required to perform call transactions. An MU may join more than one session within the same group in order to send or receive different media types wit... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.4.6 Late entry | The late entry function allows the setup of a group call to a called party when the initial setup message has been missed, for various reasons such as radio conditions, mobility or late affiliation to the corresponding group. The late entry function is implemented through appropriate repetition of the corresponding cal... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.4.7 Message exchanges related to group call | |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.4.7.1 Group subscription and affiliation | Group subscription and affiliation are achieved by exchange of SIP messages. The MU achieves subscription by sending a SIP SUBSCRIBE in order to express an interest in a group and to receive relevant events relating to the group's operating state, according to a defined event package. The MU may subscribe to an individ... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.4.7.2 Joining a session | To join a session, a SIP INVITE is sent. This may be subsequent to the subscription described in clause 7.4.7.1. The INVITE may be sent by MU or CCAS depending on the scenario. If the MU has not affiliated by use of a SIP SUBSCRIBE, the SIP INVITE will cause the CCAS to affiliate the MU to the group for the duration of... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.4.7.3 Non-acknowledged group communication | |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.4.7.3.0 Call setup sequence for group communication | The call setup sequence for normal group communication is similar to unit to unit call with direct signalling as the called parties do not answer to the call setup message but proceed immediately to a reception state. NOTE: As the called parties belong to the same group as the caller, it is assumed that they have negot... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.4.7.3.1 Group call combined with session join | If the affiliated group members are not currently included in a session for that group, the calling party sends a SIP INVITE to join a session for the group, which includes a parameter indicating that the SIP INVITE also is a request to set up a call, and to request transmit permission. Where the CCAS uses unicast down... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.4.7.3.2 Group call in pre-joined session | If the MU has already joined the session at group affiliation time, the SIP signalling has completed with the session establishment phase. Media Control Protocol is used by the calling party to request resources for transmission, to grant transmission to the calling party and to inform the called parties of the commenc... |
66fe6cb8cafb76225bdc5aca69bc6b63 | 103 269-2 | 7.4.7.4 Acknowledged or ringing group communication | The purpose of the acknowledged or confirmed group call is to provide to the calling party information that a number of called parties or specific called parties will be available to receive the call. Several options may be offered depending on network operator requirements. There can be different strategies for confir... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.