Some considerations on FMC.Req

1. Some considerations on FMC.Req Alcatel Shanghai Bell

2. FMC Definition (3.1) • FMC.Req • FMC are the capabilities and mechanisms that provide services and applications to the end-user irrespective of the fixed or mobile access technologies and user’s location. • Capabilities requires mechanisms to support it, we only need to define capabilities as the general FMC requirements. Different mechanisms are suitable for different FMC environment. • FMC services should be provide anytime, anywhere through any access technology and network, there is no need to emphasize the location of the user.

3. General Objectives of FMC (5.2) • Cost reduction, convergence services or bundling services could reduce the cost for basic communications. • Abundant services • Cost reduction (network deployment and operation) • Cost reduction, abundant services are all common requirements for the operators. These could be removed from the requirements

4. Characteristics of FMC(6) • Consistency of user experience • Service are offered in accordance with the network capabilities. For example, an ongoing call could be downgraded for some reason such as, change of access technology or terminal capability, e.g. a Video Communication can be downgraded to Voice Communication when the user/terminals migrate to the mobile only coverage. • It shall be possible for an operator to define the preferred access network for service delivery in case the user has dual coverage. • It shall be a network policy when the handover is executed, for example, an ongoing call over the mobile access network may be switched to the Fixed access network when the terminal enters the Fixed coverage. • It shall be possible for an user/terminal to define the preferable access network to access its services.

5. Characteristics of FMC(6) • Common user profile (This contribution will be submitted to SG13 Q.user_data) • Supporting multiple user identities and authentication/authorization mechanisms. • Should maintain a single data record for each subscriber. There is no user data duplication and then data consistency can be reached naturally; • Should separate the database function and control logic function; • Should support all existed mobility management protocols, and the interworking function between different mobility management protocols, e.g. GSM, ASNI-41, Diameter; • Should support terminal mobility as well as user mobility across different access technologies; • Should support multiple public user IDs or phone numbers and devices per user • Should support a common database access mechanism, this database access mechanism can be interpreted into mobility management protocol.

6. FMC network capabilities (8.2) • FMC network should provide unified authentication and authorization mechanism. • For different user, the data relating to authentication and authorization may be varied, and the parameters in the related messages may be also different, but the procedure handling of these data and parameters should be unified. • ISIM/AKA and other mechanisms should be supported , it’s not unified • FMC network should provide multiple authentication and authorization mechanism

7. Convergence Network (8.11) In the NGN environment there are different types of networks to be considered. The network can be a circuit-based network or a packet-based network as well as it can be connected to a convergence network. The convergence network should be able to support all kinds of networks. • It’s not a clear requirement. • It’s hard to understand the concept of convergence network.