public class ConferenceParticipant implements Parcelable {  //自定义数据结构
  private static final String ANONYMOUS_INVALID_HOST
  private final Uri mHandle;
   private final String mDisplayName;
  private final Uri mEndpoint;
  private final int mState;
   private long mConnectTime;
   private long mConnectElapsedTime;
  private int mCallDirection;}

public class DisconnectCause implements Parcelable { ...}
participant: ConferenceParticipantConnection.java

   public void handleConferenceParticipantsUpdate(
          TelephonyConnection parent, List<ConferenceParticipant> participants) {

      //不支持会议管理,return
          if (parent != null && !parent.isManageImsConferenceCallSupported()) {
            Log.i(this, "handleConferenceParticipantsUpdate: manage conference is disallowed");
            return;
          }
          Log.i(this, "handleConferenceParticipantsUpdate: size=%d", participants.size());

         // 以同步方式执行更新。IMS framework可以快速连续地触发两次onConferenceParticipantsChanged callbacks。         //  第一次更新添加新的参与者,第二次更新其中一个参与者的状态。
         synchronized (mUpdateSyncRoot) {   //private final Object
            int oldParticipantCount = mConferenceParticipantConnections.size();
            boolean newParticipantsAdded = false;
            boolean oldParticipantsRemoved = false;
            ArrayList<ConferenceParticipant> newParticipants = new ArrayList<>(participants.size());
            HashSet<Pair<Uri,Uri>> participantUserEntities   = new HashSet<>(participants.size());

            // Determine if the conference event package represents a single party conference.
            // A single party conference :除了host外,只有1个会议成员.         // Note: We consider 0 to still be a single party conference since some carriers will
          // send a conference event package with JUST the host in it when the conference is
         // disconnected.  We don't want to change back to conference mode prior to disconnection
         // or we will not log the call.
         boolean isSinglePartyConference = participants.stream()  //1.后面在解析
                   .filter(p -> {
                    Pair<Uri, Uri> pIdent = new Pair<>(p.getHandle(), p.getEndpoint());
                       return !Objects.equals(mHostParticipantIdentity, pIdent);
                }).count() <= 1;

        if ((mIsEmulatingSinglePartyCall && !isSinglePartyConference) ||
               !mIsEmulatingSinglePartyCall) {
             // Add any new participants and update existing.
           for (ConferenceParticipant participant : participants) {
                Pair<Uri, Uri> userEntity = new Pair<>(participant.getHandle(),participant.getEndpoint());
                       participantUserEntities.add(userEntity);
              if (!mConferenceParticipantConnections.containsKey(userEntity)) { //不存在 userEntity
                         // Some carriers will also include the conference host in the CEP.  We will filter that out here.
                if (!isParticipantHost(mConferenceHostAddress, participant.getHandle())) {
                    createConferenceParticipantConnection(parent, participant);
                               newParticipants.add(participant);
                               newParticipantsAdded = true;
                         } else {
                             // Track the identity of the conference host; its useful to know when
                             // we look at the CEP in the future.
                             mHostParticipantIdentity = userEntity;
                         }
                      } else { //存在 userEntity
                       ConferenceParticipantConnection connection = mConferenceParticipantConnections.get(userEntity);
                       Log.i(this,"handleConferenceParticipantsUpdate: updateState, participant = %s",participant);
                connection.updateState(participant.getState());
                connection.setVideoState(parent.getVideoState());
             }
                }

                 // Set state of new participants.
                  if (newParticipantsAdded) {
                    // Set the state of the new participants at once and add to the conference
                    for (ConferenceParticipant newParticipant : newParticipants) {
                         ConferenceParticipantConnection connection =
                       mConferenceParticipantConnections.get(new Pair<>(
                                          newParticipant.getHandle(),newParticipant.getEndpoint()));
                         connection.updateState(newParticipant.getState());
                         connection.setVideoState(parent.getVideoState());
                     }
                  }

        //最后,从会议中删除不再存在于会议事件包数据中的任何参与者。
                 Iterator<Map.Entry<Pair<Uri, Uri>, ConferenceParticipantConnection>> entryIterator =
                          mConferenceParticipantConnections.entrySet().iterator();
                 while (entryIterator.hasNext()) {
                      Map.Entry<Pair<Uri, Uri>, ConferenceParticipantConnection> entry = entryIterator.next();

                      if (!participantUserEntities.contains(entry.getKey())) {
                          ConferenceParticipantConnection participant = entry.getValue();
                          participant.setDisconnected(new DisconnectCause(DisconnectCause.CANCELED));
                          participant.removeConnectionListener(mParticipantListener);
                          mTelephonyConnectionService.removeConnection(participant);
                          removeConnection(participant);
                          entryIterator.remove();
                          oldParticipantsRemoved = true;
                      }
                 }
             }

             int newParticipantCount = mConferenceParticipantConnections.size();
             Log.v(this, "handleConferenceParticipantsUpdate: oldParticipantCount=%d, "
                              + "newParticipantcount=%d", oldParticipantCount, newParticipantCount);
             // If the single party call emulation fature flag is enabled, we can potentially treat
             // the conference as a single party call when there is just one participant.
             if (mFeatureFlagProxy.isUsingSinglePartyCallEmulation()) {
                  if (oldParticipantCount > 1 && newParticipantCount == 1) {
                     // If number of participants goes to 1, emulate a single party call.
                     startEmulatingSinglePartyCall();
                 } else if (mIsEmulatingSinglePartyCall && !isSinglePartyConference) {
                     // Number of participants increased, so stop emulating a single party call.
                     stopEmulatingSinglePartyCall();
                 }
            }
             // If new participants were added or old ones were removed, we need to ensure the state
             // of the manage conference capability is updated.
             if (newParticipantsAdded || oldParticipantsRemoved) {
                 updateManageConference();
             }
          }
     }
handleConferenceParticipantsUpdate:  1.ImsConferenceCallSupported判断  2.isSinglePartyConference判断  3.不EmulatingSinglePartyCall或EmulatingSinglePartyCall且SinglePartyConference条件下,添加成员,更新成员信息  4.新成员被添加到ConferenceParticipant中,更新信息  5.remove,从会议中删除不再存在于会议事件包数据中的任何参与者  6.startEmulatingSinglePartyCall()或stopEmulatingSinglePartyCall()  7.新成员增加或就成员remove, updateManageConference()
 /**
      a single party call:会议电话成员只有1名与会者。      * 1. Set the name/address to that of the single participant.
      * 2. Remove the participant from Telecom and from local tracking; when we get a new CEP in
      *    the future we'll just re-add the participant anyways.
      * 3. Tell telecom we're not a conference.
      * 4. Remove {@link Connection#CAPABILITY_MANAGE_CONFERENCE} capability.

     *注意:如果会议是通过sim call manager进行的,单方呼叫模拟将被禁用。模拟单方呼叫需要更改会议的属性(连接时间、地址、会议状态),       sim call manager 不能保证将这些属性正确地转发到Telecom。
      */
      private void startEmulatingSinglePartyCall() {
          if (mIsUsingSimCallManager) {
             Log.i(this, "startEmulatingSinglePartyCall: using sim call manager; skip.");
            return;
          }

          Log.i(this, "startEmulatingSinglePartyCall: conference has a single "
                  + "participant; downgrade to single party call.");

         mIsEmulatingSinglePartyCall = true;
         Iterator<ConferenceParticipantConnection> valueIterator =
                 mConferenceParticipantConnections.values().iterator();
         if (valueIterator.hasNext()) {
             ConferenceParticipantConnection entry = valueIterator.next();

             // Set the conference name/number to that of the remaining participant.
            setAddress(entry.getAddress(), entry.getAddressPresentation());
            setCallerDisplayName(entry.getCallerDisplayName(),entry.getCallerDisplayNamePresentation());
            setConnectionStartElapsedRealTime(entry.getConnectElapsedTimeMillis());
            setConnectionTime(entry.getConnectTimeMillis());
            mLoneParticipantIdentity = new Pair<>(entry.getUserEntity(), entry.getEndpoint());

             // Remove the participant from Telecom.  It'll get picked up in a future CEP update again anyways.
            entry.setDisconnected(new DisconnectCause(DisconnectCause.CANCELED,DisconnectCause.REASON_EMULATING_SINGLE_CALL));
            entry.removeConnectionListener(mParticipantListener);
            mTelephonyConnectionService.removeConnection(entry);
            removeConnection(entry);
            valueIterator.remove();

           // Have Telecom pretend its not a conference.
           setConferenceState(false);

           //Remove manage conference capability.
           mCouldManageConference = can(Connection.CAPABILITY_MANAGE_CONFERENCE);
           int currentCapabilities = getConnectionCapabilities();
           currentCapabilities &= ~Connection.CAPABILITY_MANAGE_CONFERENCE;
           setConnectionCapabilities(currentCapabilities);
      }
 

ImsConference.java中会议成员更新处理详解的更多相关文章

  1. Java 中的异常和处理详解

    Java 中的异常和处理详解 原文出处: 代码钢琴家 简介 程序运行时,发生的不被期望的事件,它阻止了程序按照程序员的预期正常执行,这就是异常.异常发生时,是任程序自生自灭,立刻退出终止,还是输出错误 ...

  2. Java中的IO流系统详解(转载)

    摘要: Java 流在处理上分为字符流和字节流.字符流处理的单元为 2 个字节的 Unicode 字符,分别操作字符.字符数组或字符串,而字节流处理单元为 1 个字节,操作字节和字节数组. Java ...

  3. Java中的IO流系统详解

    Java 流在处理上分为字符流和字节流.字符流处理的单元为 2 个字节的 Unicode 字符,分别操作字符.字符数组或字符串,而字节流处理单元为 1 个字节,操作字节和字节数组. Java 内用 U ...

  4. java中内存结构及堆栈详解

    一. java内存结构 1. Heap(堆):实例分配的地方,通过-Xms与-Xmx来设置 2. MethodArea(方法区域):类的信息及静态变量. 对应是Permanet Generation, ...

  5. java中的final和volatile详解

    相比synchronized,final和volatile也是经常使用的关键字,下面聊一聊这两个关键字的使用和实现 1.使用 final使用: 修饰类表示该类为终态类,无法被继承 修饰方法表示该方法无 ...

  6. Java中23种经典设计模式详解

    Java中23种设计模式目录1. 设计模式 31.1 创建型模式 41.1.1 工厂方法 41.1.2 抽象工厂 61.1.3 建造者模式 101.1.4 单态模式 131.1.5 原型模式 151. ...

  7. JAVA中堆栈和内存分配详解(摘抄)

    在Java中,有六个不同的地方可以存储数据: 1.寄存器:最快的存储区, 由编译器根据需求进行分配,我们在程序中无法控制. 2. 栈:存放基本类型的变量数据和对象的引用,但对象本身不存放在栈中,而是存 ...

  8. 2018.8.1 Java中的反射和同步详解

    为何要使用同步? java允许多线程并发控制,当多个线程同时操作一个可共享的资源变量时(如数据的增删改查), 将会导致数据不准确,相互之间产生冲突,因此加入同步锁以避免在该线程没有完成操作之前,被其他 ...

  9. Java中hashCode与equal方法详解

    转载自http://blog.csdn.net/jiangwei0910410003/article/details/22739953 Java中的equals方法和hashCode方法是Object ...

随机推荐

  1. 抓包工具tcpdump用法说明--1

    本文目录: 1.1 tcpdump选项 1.2 tcpdump表达式 1.3 tcpdump示例 tcpdump采用命令行方式对接口的数据包进行筛选抓取,其丰富特性表现在灵活的表达式上. 不带任何选项 ...

  2. Windows环境下Oracle数据库的自动备份脚本自动删除30天前的备份

    @echo off echo ================================================ echo Windows环境下Oracle数据库的自动备份脚本 echo ...

  3. 【转】JMX之ObjectName

    原文链接:https://blog.csdn.net/yunlong34574/article/details/46563187 ObjectName 就是存储了一个domain(域)下的一些属性,属 ...

  4. Python List列表的操作说明

    Python中List的N种操作,其简单程度令人叹为观止... C:\Users\rhys>python Python 2.7.14 (v2.7.14:84471935ed, Sep 16 20 ...

  5. IOU计算python实现

    def compute_iou(rec1, rec2): """ computing IoU :param rec1: (y0, x0, y1, x1), which r ...

  6. 深入JAVA虚拟机笔记-垃圾收集器与内存分配策略

    第三章:垃圾收集器与内存分配 问题:1.哪些内存需要回收 2.什么时候回收 3.怎么回收 回收方法区:

  7. 38-python基础-python3-检查字典中是否存在键或值

    in 和 not in 操作符   请注意, 在前面的例子中,‘name’ in spam 本质上是一个简写版本.相当于'name' in spam.keys()

  8. Python之字符串正则匹配

    需求: 正则表达式匹配某个文本模式,但是它找到的是模式的最长可能匹配(因为是贪婪匹配 ). 而你想修改它变成查找最短的可能匹配. import re text2 = 'Computer says &q ...

  9. Vue.js文档学习

    Vue细碎小点 生命周期钩子:created().mounted().updated().destroyed() 不要在选项属性或回调上使用箭头函数,比如 created: () => cons ...

  10. node层设置proxy不生效的原因

    43服务器上pm2部署的项目,原本是想请求代理到69服务器,但是仍然代理到75服务器了,检查node层proxy代码没问题,原因是端口号被占用了,项目的5000端口被其他项目占用,5000端口实际用的 ...