CN100401848C - A Method for Solving Caller-Call Collision in Wireless Network - Google Patents
A Method for Solving Caller-Call Collision in Wireless NetworkDownload PDFInfo
- Publication number
- CN100401848C CN100401848CCNB2005101074179ACN200510107417ACN100401848CCN 100401848 CCN100401848 CCN 100401848CCN B2005101074179 ACNB2005101074179 ACN B2005101074179ACN 200510107417 ACN200510107417 ACN 200510107417ACN 100401848 CCN100401848 CCN 100401848C
- Authority
- CN
- China
- Prior art keywords
- calling
- called
- msc
- information
- request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
- Telephonic Communication Services (AREA)
Abstract
Translated fromChinese
Description
Translated fromChinese技术领域technical field
本发明涉及无线通信技术，特别是指一种解决无线网络中主被叫碰撞的方法。The invention relates to wireless communication technology, in particular to a method for solving the collision between the calling party and the called party in the wireless network.
背景技术Background technique
无线通信系统，包括移动交换中心(MSC)、归属位置寄存器(HLR)、拜访位置寄存器(VLR)、基站控制器(BSC)、移动台(MS)等。MSC完成全部必须的信令功能以建立主被叫用户之间的连接。HLR存储有关开户MS的所有签约数据，并存储关于MS当前位置相关的信息；VLR是存储MS位置信息的动态数据库，当MS漫游进入某个MSC控制区域时，必须向与该MSC相关的VLR登记，以能够提供建立呼叫接续的必要条件。一般情况下VLR和MSC合设在同一个设备上，称为MSC/VLR。BSC管理各种接口，承担无线资源和无线参数的管理。Wireless communication system, including Mobile Switching Center (MSC), Home Location Register (HLR), Visitor Location Register (VLR), Base Station Controller (BSC), Mobile Station (MS), etc. MSC completes all necessary signaling functions to establish the connection between the calling and called users. HLR stores all the subscription data of the account-opening MS, and stores information about the current location of the MS; VLR is a dynamic database that stores the location information of the MS. When the MS roams into a certain MSC control area, it must register with the VLR related to the MSC. , to be able to provide the necessary conditions for establishing call connection. Generally, VLR and MSC are combined on the same device, which is called MSC/VLR. The BSC manages various interfaces and undertakes the management of radio resources and radio parameters.
在通信过程中，可能出现主被叫碰撞的情况，如：当用户A拨打用户B的过程中，恰好用户B拨打用户C，这时，对于用户B就是主被叫碰撞。从用户B所在MSC/VLR的角度来看，MSC/VLR正在处理被叫，正准备给BSC下发寻呼消息或者已经下发寻呼消息而还没有得到MS的寻呼响应，这时，MSC/VLR收到BSC上发的业务请求。从用户B的MS的角度来看，MS正在进行接入试探，同时空中信道正在对该MS进行寻呼。During the communication process, there may be a caller-caller collision. For example, when user A dials user B, user B happens to call user C. At this time, for user B, it is a caller-caller collision. From the perspective of the MSC/VLR where user B resides, the MSC/VLR is processing the called party and is preparing to deliver a paging message to the BSC or has already delivered a paging message but has not yet received a paging response from the MS. At this time, the MSC / The VLR receives the service request from the BSC. From the perspective of user B's MS, the MS is doing an access probe while the air channel is paging the MS.
一般情况下，MSC/VLR采用“用户状态抢占”的处理机制，即在MSC/VLR中保留一个用户状态：对于同一个用户，如果被叫请求先到MSC/VLR，则被叫将用户状态置为“保护态”，此后MSC/VLR将拒绝该用户上发的主叫业务请求；如果主叫请求先到MSC/VLR，则主叫将用户状态置为“保护态”，此后MSC/VLR将拒绝呼叫该用户的被叫请求。Generally, MSC/VLR adopts the processing mechanism of "user state preemption", that is, a user state is reserved in MSC/VLR: for the same user, if the called party requests to MSC/VLR first, the called party will set the user state to If the calling service request is sent by the user to the "protected state", the MSC/VLR will reject the calling service request sent by the user; Reject the called party's request to call the user.
下面举例说明主被叫碰撞带来的影响。当A用户呼叫B用户时，又恰好B用户呼叫C用户，此时B用户发生主被叫碰撞。假设，A用户呼叫B用户的被叫请求先到B用户所在MSC/VLR，图1所示为主被叫碰撞时B用户所在网络侧的流程图，详细描述如下。其中的呼叫流程以CDMA2000的信令流程为例，包括其它流程的说明。The following example illustrates the impact of the collision between the calling party and the called party. When user A calls user B, it happens that user B calls user C. At this time, user B collides with the calling party. Assume that the called request from user A to call user B first arrives at the MSC/VLR where user B is located. Figure 1 shows the flow chart on the network side where user B is located when the calling and called party collide. The details are as follows. The call flow takes the signaling flow of CDMA2000 as an example, including descriptions of other flows.
步骤101：MSC/VLR收到呼叫B用户的被叫请求，由于被叫请求先到MSC/VLR，因此被叫将B用户状态置为“保护态”；Step 101: MSC/VLR receives the called request of calling B user, because the called request arrives at MSC/VLR first, so the called state puts B user into "protected state";
步骤102：MSC/VLR向该B用户MS所在的BSC下发寻呼请求(PagingRequest)；Step 102: MSC/VLR sends a paging request (PagingRequest) to the BSC where the B user MS is located;
步骤103：BSC寻呼该B用户MS；Step 103: The BSC pages the B user MS;
步骤104：当B用户MS收到步骤103所述寻呼时，B用户又恰好呼叫C用户，B用户MS向BSC发起呼叫；Step 104: When the B user MS receives the paging described in step 103, the B user just calls the C user again, and the B user MS initiates a call to the BSC;
步骤105：BSC根据B用户MS的主叫请求向MSC/VLR上发业务请求(Service Request)；Step 105: BSC sends a service request (Service Request) to MSC/VLR according to the calling request of B user MS;
步骤106：MSC/VLR判断出主被叫碰撞，并根据“用户状态抢占”的处理机制，拒绝BSC上发的业务请求消息；Step 106: The MSC/VLR judges that the calling party and the called party collide, and rejects the service request message sent by the BSC according to the processing mechanism of "user status preemption";
步骤107：由于B用户MS正处于主叫接入过程无法处理步骤103的寻呼消息，所以寻呼超时，一般情况下，MSC/VLR在寻呼超时之后会下发二次寻呼，如步骤109、110；Step 107: Since the B user MS is in the calling access process and cannot process the paging message in step 103, the paging timeout, generally, the MSC/VLR will issue a second paging after the paging timeout, as in
步骤108：由于B用户发起呼叫而长时间无法接通时，也会重新发起呼叫，如步骤111、112；Step 108: When the call cannot be connected for a long time due to the call initiated by user B, the call will be re-initiated, such as
步骤109：MSC/VLR向该B用户MS所在的BSC下发寻呼请求；Step 109: MSC/VLR sends a paging request to the BSC where the B user MS is located;
步骤110：BSC寻呼该B用户MS；Step 110: BSC pages the B user MS;
步骤111：B用户重新发起呼叫，B用户MS重新向BSC发起呼叫；Step 111: User B initiates a call again, and user B MS initiates a call to BSC again;
步骤112：BSC根据B用户MS的主叫请求向MSC/VLR上发业务请求；Step 112: The BSC sends a service request to the MSC/VLR according to the calling request of the B user MS;
步骤113：如果步骤108所述的呼叫过程发生在步骤110之后MS还没来得及处理该寻呼时，又会发生主被叫碰撞，MSC/VLR再次判断出主被叫碰撞。Step 113: If the call process described in step 108 occurs before the MS has time to process the paging after step 110, there will be a caller-caller collision again, and the MSC/VLR judges a caller-caller collision again.
按照上述流程，如果没有处理主被叫碰撞的机制，则对于主被叫碰撞的用户来说，不仅主叫接续时间变长，而且无法成功呼叫到该用户。According to the above process, if there is no mechanism for dealing with the collision between the calling party and the called party, then for the user who has the collision between the calling party and the called party, not only the connection time of the calling party will become longer, but also the user cannot be successfully called.
现有技术中，按照优先处理主叫的方法来解决上述主被叫碰撞的问题，即：MSC/VLR判断出主被叫碰撞后，拒绝被叫请求和清除被叫的“保护态”，然后处理主叫请求，同时主叫将用户状态置为“保护态”。In the prior art, the above-mentioned problem of calling and called collision is solved according to the method of prioritizing calling and calling, that is, after MSC/VLR judges that calling and called collide, it rejects the called request and clears the "protected state" of the called, and then Process the caller's request, and at the same time, the caller sets the user status to "protected state".
按照上述方法，当主被叫碰撞时，主叫优先、拒绝被叫的处理方法存在缺点：越是业务繁忙的用户，碰撞的概率越高，按照上述主叫优先的方法，往往会漏掉一些电话，因此用户对上述现有的主叫优先的处理方法不能接受或感到不满。而且，发生主被叫碰撞的用户并不能知道发生了碰撞，觉得发起呼叫的接入时间变长，因此，会抱怨网络质量不好。According to the above method, when the calling party and the called party collide, there are disadvantages in the processing method of giving priority to the calling party and rejecting the called party: the more busy the user is, the higher the probability of collision is, and according to the above method of giving priority to the calling party, some calls are often missed , so the user cannot accept or feel dissatisfied with the above-mentioned existing calling priority processing method. Moreover, the user who has the collision between the calling party and the called party does not know that the collision has occurred, and feels that the access time for initiating a call becomes longer, and therefore complains that the network quality is not good.
发明内容Contents of the invention
有鉴于此，本发明的主要目的在于提供一种解决无线网络中主被叫碰撞的方法，以提供发生主被叫碰撞时的处理方法。In view of this, the main purpose of the present invention is to provide a method for solving the collision of the calling party and the called party in the wireless network, so as to provide a processing method when the collision of the calling party and the called party occurs.
为达到上述目的，本发明提供一种解决无线网络中主被叫碰撞的方法，该方法包括：In order to achieve the above object, the present invention provides a method for solving the collision between the calling party and the called party in the wireless network, the method comprising:
a.当移动交换中心MSC接收到移动台MS的主叫请求和呼叫该MS的被叫请求，并确定该MS发生主被叫碰撞后，MSC向该MS发送主被叫碰撞信息；a. When the mobile switching center MSC receives the calling request of the mobile station MS and the called request to call the MS, and determines that the MS has a calling and called collision, the MSC sends the calling and called collision information to the MS;
b.MS根据主被叫碰撞信息向MSC返回当前优先处理呼叫的信息，MSC根据所述当前优先处理呼叫的信息处理对应的请求。b. The MS returns the information of the current priority call to the MSC according to the collision information of the calling party and the called party, and the MSC processes the corresponding request according to the information of the current priority call.
其中，步骤a所述主被叫碰撞信息是MSC通过闪动请求Flash Request消息携带；或，步骤a中所述主被叫碰撞信息是MSC通过指配信道请求消息携带。Wherein, the calling and calling party collision information described in step a is carried by the MSC through a Flash Request message; or, the calling and calling party collision information described in step a is carried by the MSC through an assigned channel request message.
其中，所述主被叫碰撞信息包括：碰撞产生时呼叫该MS的对方用户终端的号码、选择主叫优先还是被叫优先的选择项、除呼叫该MS的对方用户终端的号码、选择主叫优先还是被叫优先的选择项之外的文字、图片、声音中的一种或任意组合。Wherein, the collision information of the calling party and the called party includes: the number of the other party user terminal that called the MS when the collision occurred, the option to select whether the calling party or the called party is first, the number of the other party user terminal except for calling the MS, and the option to select the calling party. The priority is one or any combination of text, picture, and sound other than the option of the called priority.
其中，步骤b所述当前优先处理呼叫的信息为MS向MSC返回挂机操作或不挂机操作信息，如果返回挂机操作信息，MSC处理被叫请求；如果返回不挂机操作信息，MSC处理主叫请求。Wherein, the information of the current priority processing call described in step b is that the MS returns the on-hook operation or no-hook operation information to the MSC. If the on-hook operation information is returned, the MSC processes the called request; if the no-on-hook operation information is returned, the MSC processes the calling request.
其中，步骤b所述当前优先处理呼叫的信息为主叫请求信息，则MSC拒绝被叫请求，然后处理该MS的主叫请求。Wherein, the information of the current preferential treatment of the call in step b is the calling request information, and the MSC rejects the called request, and then processes the calling request of the MS.
其中，步骤b所述当前优先处理呼叫的信息为主叫请求信息，如果MSC确定被叫请求已被清除，则处理该MS的主叫请求。Wherein, the information of the current priority processing call in step b is the calling request information, and if the MSC determines that the called request has been cleared, then process the calling request of the MS.
其中，步骤b所述当前优先处理呼叫的信息为被叫请求信息，则MSC处理被叫请求。Wherein, the information of the current priority processing call in step b is called request information, and the MSC processes the called request.
其中，所述步骤a之前进一步包括：在归属位置寄存器HLR中保存该MS签约主被叫碰撞通知业务的信息；Wherein, before the step a, it further includes: storing the information of the MS signing the caller and called party collision notification service in the home location register HLR;
步骤a所述MSC确定该MS主被叫碰撞后进一步包括：MSC从HLR中获取该MS的签约数据，如果确定该MS签约主被叫碰撞通知业务，则向MS发送主被叫碰撞信息；如果确定该MS没有签约该业务，则处理主叫请求，结束本流程。After the MSC in step a determines that the MS has a calling and called collision, it further includes: the MSC obtains the subscription data of the MS from the HLR, and if it is determined that the MS has subscribed to the calling and called collision notification service, then sending the calling and called collision information to the MS; if If it is determined that the MS has not subscribed to the service, the calling request is processed, and this process ends.
其中，所述在HLR中保存该MS签约主被叫碰撞通知业务的信息步骤包括：MS向MSC发送签约主被叫碰撞通知业务的请求，MSC根据该MS的请求，在HLR记录该MS签约主被叫碰撞通知业务的信息；Wherein, the step of storing the information of the MS’s contracted caller and called party collision notification service in the HLR includes: the MS sends a request for the caller and called party’s collision notification service to the MSC, and the MSC records the MS’s caller and called party collision notification service in the HLR according to the MS’s request. Information about the called collision notification service;
或，所述该MS签约主被叫碰撞通知业务的信息是预先保存在HLR中。Or, the information that the MS subscribes to the caller-caller collision notification service is pre-stored in the HLR.
其中，步骤b所述MS根据主被叫碰撞信息向MSC返回当前优先处理呼叫的信息的步骤包括：MS中配置主被叫碰撞信息所对应的内部操作，根据用户选择结果，向MSC返回相应的操作信息。Wherein, in step b, the step of the MS returning the information of the current priority call to the MSC according to the collision information of the calling party and the called party includes: configuring the internal operation corresponding to the collision information of the calling party and the called party in the MS, and returning the corresponding Action information.
根据本发明提供的解决主被叫碰撞的方法，当发生主被叫碰撞时，MSC通知发生主被叫碰撞的用户，由用户选择主叫优先还是被叫优先，MSC根据用户返回的信息处理对应的呼叫，因此用户知道发生了主被叫碰撞，且可以根据自己的需求接通被叫或继续呼叫，提高用户的满意程度。According to the method for solving calling and called collisions provided by the present invention, when a calling and called collision occurs, the MSC notifies the user that the calling and called collision occurs, and the user chooses whether the calling priority or the called priority is selected, and the MSC processes the corresponding information according to the information returned by the user. Therefore, the user knows that a collision between the calling party and the called party has occurred, and can connect to the called party or continue the call according to his own needs, thereby improving user satisfaction.
附图说明Description of drawings
图1所示为背景技术中主被叫碰撞流程图；Fig. 1 shows that in the background technology, the calling and called party collision flow chart;
图2所示为HLR中用户签约数据更改之后，主动发出请求更新MSC/VLR中用户数据的流程图；Fig. 2 shows the flow chart of requesting to update the user data in the MSC/VLR after the user subscription data in the HLR is changed;
图3所示为本发明中用户通过远程操作办理或更改业务签约数据的流程图；Fig. 3 shows the flow chart of the user handling or changing the service contract data through remote operation in the present invention;
图4所示为MSC/VLR获取HLR中用户签约数据的流程图；Fig. 4 shows the flow chart that MSC/VLR obtains subscriber subscription data in HLR;
图5所示为本发明中主被叫碰撞的用户选择主叫优先时的处理流程图；Fig. 5 shows the processing flowchart when the user of calling and called collision selects calling priority among the present invention;
图6所示为本发明中主被叫碰撞的用户选择被叫优先时的处理流程图；Fig. 6 shows the processing flowchart when the user of calling and called collides in the present invention selects the called priority;
图7所示为本发明中当被叫请求主动被结束时，主被叫碰撞的用户选择被叫优先时的处理流程图；Fig. 7 shows that in the present invention, when the called party's request is terminated actively, the user who collides with the called party selects the process flow diagram of the called party's priority;
图8所示为本发明中通过指配信道请求消息携带主被叫碰撞信息的处理流程图。Fig. 8 is a flow chart showing the process of carrying the collision information of the calling party and the called party through the assignment channel request message in the present invention.
具体实施方式Detailed ways
为使本发明的目的、技术方案和优点更加清楚明白，下面举具体实施例，对本发明作进一步详细的说明。In order to make the object, technical solution and advantages of the present invention clearer, specific examples are given below to further describe the present invention in detail.
本发明的核心思想是：当MSC/VLR判断出主被叫碰撞时，首先按照主叫优先处理，接受主叫的业务请求并发起指配信道的操作，指配成功后，向用户发送发生主被叫碰撞的信息，由用户选择接通被叫还是继续发起主叫，然后根据用户的选择，继续处理主叫或被叫即可。其中，主被叫碰撞信息中可以携带以下内容，例如，对方用户的电话号码、选择主叫优先还是被叫优先的选择项、其他文字、图片、声音等。The core idea of the present invention is: when the MSC/VLR judges that the calling party and the called party collide, it firstly treats the calling party first, accepts the service request of the calling party and initiates the operation of assigning a channel. For the information of the called collision, the user can choose to connect the called or continue to initiate the calling, and then continue to process the calling or called according to the user's choice. Wherein, the calling and called party collision information may carry the following content, for example, the phone number of the other party, an option to choose calling priority or called priority, other text, pictures, sounds, etc.
在HLR中设置用户申请主被叫碰撞通知业务的签约数据，并且可以通过两种方式实现。Set the subscription data for the user to apply for the caller and called party collision notification service in the HLR, and it can be realized in two ways.
一种是：预先直接将用户申请主被叫碰撞通知业务的签约数据保存在HLR中，HLR中签约数据变更之后，主动向MSC/VLR发出更改用户数据的请求，如图2所示，HLR向MSC/VLR发出更改用户签约数据的请求，MSC/VLR根据该请求，更新用户签约数据之后向HLR返回响应。One is: directly save the subscription data of the user applying for the caller-called collision notification service in the HLR in advance, and after the subscription data in the HLR is changed, actively send a request for changing the user data to the MSC/VLR, as shown in Figure 2, the HLR sends The MSC/VLR sends out a request for changing the subscriber subscription data, and the MSC/VLR returns a response to the HLR after updating the subscriber subscription data according to the request.
另一种是：用户终端通过远程操作实现在HLR中设置“主被叫碰撞通知”业务的用户签约信息。用户终端可以通过拨打签约主被叫碰撞通知业务的特定号码办理该业务，如图3所示，按照该方法，用户还可以远程更改业务签约数据，详细介绍如下所述：The other is: the user terminal realizes setting the user subscription information of the "collision notification of the calling party and called party" service in the HLR through remote operation. The user terminal can handle the service by dialing the specific number of the contracted caller-called collision notification service, as shown in Figure 3. According to this method, the user can also change the service subscription data remotely. The details are as follows:
步骤301：用户终端向BSC发送被叫为特定号码的呼叫请求，BSC收到该呼叫请求后，根据该特定号码向MSC/VLR发起呼叫；Step 301: the user terminal sends a call request for a specific number to the BSC, and the BSC initiates a call to the MSC/VLR according to the specific number after receiving the call request;
步骤302：MSC/VLR确定所呼叫的号码为签约“主被叫碰撞通知”业务签约数据的特定号码，向HLR发送更改HLR中签约数据的请求；Step 302: The MSC/VLR determines that the called number is a specific number that subscribes to the subscription data of the "Caller-Called Collision Notification" service, and sends a request to the HLR to change the subscription data in the HLR;
步骤303：HLR收到上述请求之后，向MSC/VLR发送更改VLR中签约数据的请求；Step 303: After the HLR receives the above request, it sends a request to the MSC/VLR to change the subscription data in the VLR;
步骤304：MSC/VLR根据步骤303中请求，先更改MSC/VLR中签约数据之后，向HLR返回更改签约数据的响应；Step 304: MSC/VLR returns the response of changing subscription data to HLR after first changing the subscription data in MSC/VLR according to the request in step 303;
步骤305：HLR收到步骤302中的请求和步骤304中MSC/VLR返回的响应之后，更改HLR中签约数据，然后向MSC/VLR返回更改签约数据的响应；Step 305: After the HLR receives the request in the step 302 and the response returned by the MSC/VLR in the step 304, it changes the subscription data in the HLR, and then returns the response of changing the subscription data to the MSC/VLR;
步骤306：MSC/VLR向BSC发送用户更改签约数据的结果，然后由BSC通知用户该结果。Step 306: The MSC/VLR sends the result of the user changing the subscription data to the BSC, and then the BSC notifies the user of the result.
当MS漫游到新的MSC/VLR或MSC/VLR数据丢失等情况下，按照如图4所示，MSC/VLR向HLR发送能够获取用户签约数据的请求，例如位置登记、资格请求或者资格指示等；HLR收到上述请求之后，向MSC/VLR返回用户签约数据的响应，MSC/VLR获取用户的签约数据。When the MS roams to a new MSC/VLR or MSC/VLR data is lost, as shown in Figure 4, the MSC/VLR sends a request to the HLR to obtain user subscription data, such as location registration, qualification request or qualification indication, etc. ; After the HLR receives the above request, it returns the response of the user's subscription data to the MSC/VLR, and the MSC/VLR obtains the user's subscription data.
综上所述，HLR中签约数据被更改或MS漫游到新的MSC/VLR等情况下，MSC/VLR都能及时获取HLR中用户签约数据，因此MSC/VLR在收到主叫请求或被叫请求之后，如果发生主被叫碰撞，则MSC从VLR可以获取用户签约数据，确定该用户是否是申请主被叫碰撞通知的用户，如果是，通知用户发生主被叫碰撞，进而户解决主被叫碰撞的问题。To sum up, when the subscription data in the HLR is changed or the MS roams to a new MSC/VLR, the MSC/VLR can obtain the user subscription data in the HLR in a timely manner. Therefore, when the MSC/VLR receives the calling request or the called After the request, if a calling and called collision occurs, the MSC can obtain user subscription data from the VLR to determine whether the user is the user who applied for calling and called collision notification. A problem called collision.
在本发明中，需要设置选择当前优先处理的呼叫对应的操作或信息。例如：对于用户挂机操作，表明选择被叫优先；不挂机操作，即无任何操作，表明选择主叫优先。根据该项业务的设置，用户收到主被叫碰撞信息之后，如果要选择主叫优先，则不挂机；如果要选择被叫优先，则挂机。为了用户使用该项业务更方便，MS中可以配置与主被叫碰撞信息对应的内部操作，或者返回对应的信息给MSC。例如，对主被叫碰撞信息中选择主叫优先还是被叫优先的选择项配置对应的内部操作，用户选择被叫优先时，MS内部处理挂机操作。In the present invention, it is necessary to set the operation or information corresponding to selecting the current priority call. For example, if the user is on-hook, it indicates that the called party is preferred; if the user does not hang up, that is, no operation, it indicates that the calling party is preferred. According to the setting of this service, after the user receives the caller-caller collision information, if he wants to choose the calling priority, he will not hang up; if he wants to choose the called priority, he will hang up. In order for the user to use this service more conveniently, the internal operation corresponding to the collision information of the calling party and the called party can be configured in the MS, or the corresponding information can be returned to the MSC. For example, in the caller-caller collision information, configure the corresponding internal operation for the selection item of calling priority or called priority. When the user selects the called priority, the MS internally processes the on-hook operation.
用户发起呼叫或被叫，MSC/VLR获取该用户签约数据，当MSC/VLR判断出该用户发生主被叫碰撞时，根据所获取的签约数据判断出该用户是“主被叫碰撞通知”业务的签约用户，则暂时优先处理主叫，即指配信道，然后向用户发出主被叫碰撞的信息，由用户选择主叫优先还是被叫优先。如果MSC/VLR在延时一段时间后仍没有检测到挂机操作或对应的信息，则认为用户选择了主叫优先，然后清除被叫请求，接续主叫；如果MSC/VLR检测到挂机操作或对应的信息，则认为用户选择了被叫优先，然后执行寻呼，接续被叫。下面结合具体实施例，详细介绍发生主被叫碰撞时解决主被叫碰撞的方法。当A用户呼叫B用户时，又恰好B用户呼叫C用户，此时B用户发生主被叫碰撞。假设，A用户呼叫B用户的被叫请求先到B用户所在MSC/VLR，下面几个实施例中均给出主被叫碰撞时B用户所在网络侧的流程图。When a user initiates a call or is called, the MSC/VLR obtains the subscription data of the user. When the MSC/VLR determines that the user has a collision between the calling party and the called party, it judges that the user is a "calling and called party collision notification" service according to the obtained subscription data. If the contracted user is a contracted user, the caller will be given priority temporarily, that is, the channel will be assigned, and then the caller and called party will be sent to the user. If the MSC/VLR still does not detect the on-hook operation or the corresponding information after a period of delay, it is considered that the user has selected the caller priority, and then clears the called request and continues the calling; if the MSC/VLR detects the on-hook operation or information, it is considered that the user has selected the called priority, and then performs paging to connect the called. The method for solving the calling and called party collision when the calling and called party collision occurs will be introduced in detail below in combination with specific embodiments. When user A calls user B, it happens that user B calls user C. At this time, user B collides with the calling party. Assuming that the called request from user A to call user B first arrives at the MSC/VLR where user B resides, the following embodiments all provide the flow charts on the network side where user B resides when the calling party and the called party collide.
图5所示为，B用户发生主被叫碰撞，且该用户选择主叫优先时的处理流程图，其中下面所述MS是属于B用户。Fig. 5 shows the processing flow chart when user B has a caller-called collision, and the user chooses calling priority, wherein the MS mentioned below belongs to user B.
步骤501：MSC/VLR收到呼叫MS的被叫请求；Step 501: MSC/VLR receives a called party request to call MS;
步骤502：MSC/VLR向该MS所在的BSC下发寻呼请求(PagingRequest)；Step 502: MSC/VLR sends a paging request (PagingRequest) to the BSC where the MS is located;
步骤503：BSC寻呼该MS；Step 503: The BSC pages the MS;
步骤504：MS收到步骤503所述寻呼时，该MS的用户恰好发起呼叫，MS向BSC发起呼叫；Step 504: When the MS receives the paging described in step 503, the user of the MS just initiates a call, and the MS initiates a call to the BSC;
步骤505：BSC根据MS的呼叫请求向MSC/VLR上发业务请求(ServiceRequest)；Step 505: BSC sends a service request (ServiceRequest) to MSC/VLR according to the call request of MS;
步骤506：MSC/VLR判断出主被叫碰撞，暂时优先处理主叫，如步骤507～510；Step 506: The MSC/VLR judges that the calling party and the called party collide, and temporarily gives priority to the calling party, such as steps 507-510;
步骤507：MSC/VLR向BSC发送指配请求(Assignment Request)；Step 507: MSC/VLR sends assignment request (Assignment Request) to BSC;
步骤508：BSC给MS指配信道；Step 508: The BSC assigns a channel to the MS;
步骤509：MS向BSC发送指配信道成功响应(Assignment Complete)；Step 509: The MS sends an assigned channel success response (Assignment Complete) to the BSC;
步骤510：BSC向MSC/VLR返回指配成功的响应；Step 510: The BSC returns a response of assignment success to the MSC/VLR;
步骤511：MSC/VLR向BSC发送闪动请求(Flash Request)消息，其中携带主被叫碰撞的信息，例如，对方用户A的电话号码、选择主叫优先还是被叫优先的选择项、其他文字、图片、声音等；Step 511: MSC/VLR sends a flash request (Flash Request) message to BSC, which carries the information of calling and called collisions, for example, the phone number of the other party user A, the option to choose calling priority or called priority, other text , picture, sound, etc.;
步骤512：BSC给MS发送上述主被叫碰撞的信息；Step 512: The BSC sends the above-mentioned calling and called party collision information to the MS;
步骤513：B用户获取上述主被叫碰撞信息之后，没有执行挂机操作，即B用户选择了主叫优先；Step 513: After obtaining the above-mentioned caller-caller collision information, user B does not perform an on-hook operation, that is, user B selects calling priority;
步骤514：MSC/VLR在步骤511之后延时一段时间后，没有检测到发生主被叫碰撞MS的挂机操作，因此判断出B用户选择了主叫优先；Step 514: After the MSC/VLR delays for a period of time after step 511, it does not detect the on-hook operation of the calling party colliding with the MS, so it is judged that the B user has selected the calling priority;
步骤515：MSC/VLR清除被叫请求，继续接续主叫。Step 515: MSC/VLR clears the called request and continues to connect the calling party.
之后，B用户作为主叫呼叫C用户成功，两者之间建立通信话路。Afterwards, user B successfully calls user C as the calling party, and a communication session is established between the two.
图6所示为，B用户发生主被叫碰撞时，该用户选择被叫优先时的处理流程图。FIG. 6 is a flow chart of processing when user B selects called priority when a caller-caller collision occurs to user B.
步骤601～步骤612：同步骤501～步骤512；Step 601 to step 612: same as step 501 to step 512;
步骤613：B用户获取主被叫碰撞的信息之后，执行挂机操作，即B用户选择了被叫优先；Step 613: User B performs an on-hook operation after obtaining the information of the collision between the calling party and the called party, that is, user B selects the called party priority;
步骤614：MS向BSC发送挂机信息；Step 614: MS sends on-hook information to BSC;
步骤615：BSC向MSC/VLR发送清除请求(Clear Request)；Step 615: BSC sends a clear request (Clear Request) to MSC/VLR;
步骤616：MSC/VLR向BSC发送清除命令(Clear Command)；Step 616: MSC/VLR sends clear command (Clear Command) to BSC;
步骤617：BSC清除业务信道之后，向MSC/VLR发送清除完成(ClearComplete)；Step 617: After the BSC clears the traffic channel, it sends ClearComplete to the MSC/VLR;
步骤618：MSC/VLR检测到清除完成之后，判断出B用户在主被叫碰撞时优先选择被叫；Step 618: After the MSC/VLR detects that the clearing is completed, it is determined that the B user preferentially selects the called party when the calling party and the called party collide;
步骤619：MSC/VLR向BSC发送寻呼请求(Paging Request)；Step 619: MSC/VLR sends a paging request (Paging Request) to BSC;
步骤620：BSC寻呼MS；Step 620: The BSC pages the MS;
步骤621：MS向BSC返回寻呼响应；Step 621: The MS returns a paging response to the BSC;
步骤622：BSC向MSC/VLR返回寻呼响应(Paging Response)。Step 622: The BSC returns a paging response (Paging Response) to the MSC/VLR.
之后，B用户作为被叫，被A用户呼叫成功，两者之间建立了通信话路。Afterwards, user B, as the called party, is successfully called by user A, and a communication session is established between the two.
在上述实施例中，如果A用户拨号后长时间没接通，则有可能会主动挂机，这时，处理流程图如图7所示。In the above embodiment, if user A does not connect for a long time after dialing, he may actively hang up. At this time, the processing flow chart is shown in FIG. 7 .
步骤701～步骤705：同步骤601～步骤605；Step 701 to step 705: same as step 601 to step 605;
步骤706：MSC/VLR判断出发生了主被叫碰撞，暂时优先处理主叫；Step 706: The MSC/VLR judges that a collision between the calling party and the called party has occurred, and temporarily gives priority to the calling party;
步骤707：A用户主动结束本次呼叫，MSC/VLR侧的被叫请求被拆除；Step 707: User A actively terminates the call, and the called request on the MSC/VLR side is removed;
步骤708～步骤713：同步骤607～步骤612；Step 708 to step 713: same as
步骤714：B用户获取主被叫碰撞信息之后，如果没有执行挂机操作，即B用户选择主叫优先时，MSC/VLR接续主叫；如果执行挂机操作，即B用户选择被叫优先时，MSC/VLR执行步骤715～724；Step 714: After user B obtains the calling and called party collision information, if the on-hook operation is not performed, that is, when user B selects calling priority, the MSC/VLR connects the calling party; if the on-hook operation is performed, that is, when user B selects calling priority, /VLR Execute steps 715-724;
步骤715～步骤718：同步骤614～步骤617；Step 715-Step 718: Same as Step 614-
步骤719：B用户等待A用户再次发起呼叫；Step 719: User B waits for user A to initiate a call again;
步骤720：A用户再次发起呼叫，MSC/VLR再次收到被叫请求；Step 720: User A initiates a call again, and the MSC/VLR receives the called request again;
步骤721～步骤724：同步骤619～步骤622；Step 721 to step 724: same as
在图7所述的流程中，如果步骤714中，B用户选择被叫优先时，可以根据步骤713中的主被叫碰撞信息中的A用户的号码回拨该A用户即可。In the process described in FIG. 7 , if in step 714, user B chooses the called priority, the user A can be dialed back according to the number of user A in the calling and called collision information in step 713.
上述几个实施例中，通过Flash Request携带主被叫碰撞信息，通知发生碰撞的用户，除此之外，还可以通过指配请求携带主被叫碰撞信息，通知发生碰撞的用户，如图8所示。In the above-mentioned several embodiments, the collision information of the calling party and the called party is carried through the Flash Request, and the user of the collision is notified. In addition, the collision information of the calling party and the called party can also be carried through the assignment request, and the user of the collision is notified, as shown in Figure 8 shown.
步骤801～步骤806：同步骤501～步骤506；Step 801 to step 806: same as step 501 to step 506;
步骤807：MSC/VLR向BSC发送指配请求，其中携带主被叫碰撞信息；Step 807: The MSC/VLR sends an assignment request to the BSC, which carries the collision information of the calling party and the called party;
步骤808：BSC给MS指配信道，并携带上述主被叫碰撞信息；Step 808: The BSC assigns a channel to the MS and carries the above-mentioned caller-caller collision information;
步骤809～步骤810：同步骤509～步骤510；Step 809 to step 810: same as step 509 to step 510;
步骤811：B用户获取上述主被叫碰撞信息之后，可以根据自己的需求选择主叫优先或被叫优先。Step 811: After obtaining the above-mentioned calling and calling collision information, user B can choose calling priority or called priority according to his needs.
B用户选择主叫优先后的处理过程如同图5所示的流程，被叫优先后的处理过程如同图6所示的流程，不再详细介绍。The processing process after user B selects calling priority is as the process shown in Figure 5, and the processing process after called priority is the same as the process shown in Figure 6, and will not be described in detail.
如果B用户作为主叫呼叫C用户的主叫业务请求先到MSC/VLR，然后MSC/VLR收到A用户呼叫B用户的被叫请求，且对于用户B恰好发生主被叫碰撞时，则MSC/VLR在主被叫碰撞后的处理流程如同上述的实施例，首先暂时按照主叫优先建立信道之后，并通知B用户，然后根据用户的选择结果处理主叫或被叫请求。If user B as the calling party calls user C, the calling service request first arrives at MSC/VLR, and then MSC/VLR receives the called request from user A to call user B, and when a collision between the calling party and the called party happens to user B, then MSC The processing flow of /VLR after the collision between the calling party and the called party is the same as the above-mentioned embodiment. First, the channel is temporarily established according to the priority of the calling party, and the user B is notified, and then the request of the calling party or the called party is processed according to the selection result of the user.
上述解决主被叫碰撞的方法虽然使用CDMA2000的信令方式描述，但其方法适用于所有无线通信网络，例如GSM、宽带码分多址(WCDMA)、CDMA2000、时分同步码分多址(TD-SCDMA)等，其中具体呼叫流程中的信令有可能不一样，但是，处理主被叫碰撞的主要思想都一样，即：当确定发生主被叫碰撞之后，首先按照主叫优先指配信道，并向用户发送发生主被叫碰撞的信息，然后根据用户的选择，继续处理主叫请求或被叫请求。Although the above-mentioned method for solving the collision between the calling party and the called party is described using the signaling mode of CDMA2000, its method is applicable to all wireless communication networks, such as GSM, Wideband Code Division Multiple Access (WCDMA), CDMA2000, Time Division Synchronous Code Division Multiple Access (TD- SCDMA), etc., wherein the signaling in the specific call flow may be different, but the main idea of dealing with the collision between the calling party and the called party is the same, that is: after it is determined that the collision between the calling party and the called party occurs, first assign the channel according to the calling party priority, And send the information of calling and called collision to the user, and then continue to process the calling request or called request according to the user's choice.
以上所述仅为本发明的较佳实施例而已，并不用以限制本发明，凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included in the scope of the present invention. within the scope of protection.
Claims (10)
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2005101074179ACN100401848C (en) | 2005-09-30 | 2005-09-30 | A Method for Solving Caller-Call Collision in Wireless Network |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2005101074179ACN100401848C (en) | 2005-09-30 | 2005-09-30 | A Method for Solving Caller-Call Collision in Wireless Network |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1882178A CN1882178A (en) | 2006-12-20 |
| CN100401848Ctrue CN100401848C (en) | 2008-07-09 |
Family
ID=37520096
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2005101074179AExpired - Fee RelatedCN100401848C (en) | 2005-09-30 | 2005-09-30 | A Method for Solving Caller-Call Collision in Wireless Network |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100401848C (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101626561B (en)* | 2009-08-05 | 2012-08-08 | 华为技术有限公司 | Call connection method and equipment |
| CN102065541A (en)* | 2010-11-17 | 2011-05-18 | 中兴通讯股份有限公司 | Method and device for processing services on single-mode chip |
| CN102573067A (en)* | 2010-12-16 | 2012-07-11 | 中兴通讯股份有限公司 | Method and system for processing paging initiation confliction |
| CN103582132B (en)* | 2012-07-24 | 2018-08-07 | 电信科学技术研究院 | A kind of distribution method and system of C-RNTI |
| CN103781173B (en)* | 2012-10-17 | 2018-11-02 | 中国移动通信集团江苏有限公司 | A kind of SOT state of termination treating method and apparatus |
| WO2016191966A1 (en)* | 2015-05-29 | 2016-12-08 | 华为技术有限公司 | Method and device for processing call |
| CN110089097B (en)* | 2016-12-23 | 2023-04-07 | 意大利电信股份公司 | Call collision resolution in a communication network |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH05292009A (en)* | 1992-04-08 | 1993-11-05 | Fujitsu Ltd | Incoming and outgoing collision call rescue method |
| CN1147326A (en)* | 1994-04-27 | 1997-04-09 | 诺基亚电信公司 | Methods for Handling Call Conflicts |
| JP2003046608A (en)* | 2001-07-30 | 2003-02-14 | Nippon Telegraph & Telephone East Corp | Telephone transmission control device, method and program |
| KR20040100059A (en)* | 2003-05-21 | 2004-12-02 | 에스케이 텔레콤주식회사 | Mobile Communication System Controllable of Priority Order of Additional Service and Method thereof |
| KR20050090603A (en)* | 2004-03-09 | 2005-09-14 | 주식회사 엘지텔레콤 | Mobile communication system and service method of simultaneity call using the same |
- 2005
- 2005-09-30CNCNB2005101074179Apatent/CN100401848C/ennot_activeExpired - Fee Related
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH05292009A (en)* | 1992-04-08 | 1993-11-05 | Fujitsu Ltd | Incoming and outgoing collision call rescue method |
| CN1147326A (en)* | 1994-04-27 | 1997-04-09 | 诺基亚电信公司 | Methods for Handling Call Conflicts |
| JP2003046608A (en)* | 2001-07-30 | 2003-02-14 | Nippon Telegraph & Telephone East Corp | Telephone transmission control device, method and program |
| KR20040100059A (en)* | 2003-05-21 | 2004-12-02 | 에스케이 텔레콤주식회사 | Mobile Communication System Controllable of Priority Order of Additional Service and Method thereof |
| KR20050090603A (en)* | 2004-03-09 | 2005-09-14 | 주식회사 엘지텔레콤 | Mobile communication system and service method of simultaneity call using the same |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1882178A (en) | 2006-12-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7580714B2 (en) | Method for attaching a mobile equipment to a wireless communication network | |
| US8185093B2 (en) | Methods for handling an apparatus terminated communication request and communication apparatuses utilizing the same | |
| JP6012772B2 (en) | Circuit-switched fallback (CSFB) during pre-paging | |
| JP2003530767A (en) | Techniques for setting up calls in the technical field of Internet Protocol mobile communication networks | |
| EP1848190A1 (en) | Method, system and device for speech codec negotiation in communication system | |
| CN101222765A (en) | Control method, system and device for circuit field fall-back | |
| KR20160014112A (en) | Telephone network system and method | |
| KR100770843B1 (en) | How to Improve Call Success Rate When Attempting Simultaneous Calls in Mobile Communication System? | |
| JP2003510988A (en) | Method and system for providing call reservation service via packet switching network | |
| JP4673375B2 (en) | SMM capability delivery method | |
| CN100484290C (en) | Method for realizing PDP address distribution in service cut-in | |
| CN100401848C (en) | A Method for Solving Caller-Call Collision in Wireless Network | |
| CN100450226C (en) | Mobile communication system and method for updating roaming location of trunking service users | |
| CN101374345B (en) | Method, apparatus and system for transferring wireless virtual private network VPN short number of calling subscriber | |
| CN101179857A (en) | A Call Establishment Method Applied in UMA Network | |
| CN100442941C (en) | A method and system for realizing roaming | |
| CN100534230C (en) | method for identifying service | |
| CN101730264A (en) | Call screening method and system | |
| WO2007033543A1 (en) | A method for solving the problem of calling mobile stations | |
| CN1947454A (en) | Method for setting up a link with prepaging while optimizing use of resources | |
| CN112118606B (en) | Method, related device and system for realizing service continuity | |
| JP2003018657A (en) | Mobile communication system, apparatus and control method | |
| KR100684941B1 (en) | System and method for providing presence service in premises wireless communication network | |
| KR101674065B1 (en) | System and method for transmittung message of mobile communication terminal based on two number service | |
| WO2007068205A1 (en) | A method, and system for realizing call waiting service for the called terminal |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| C17 | Cessation of patent right | ||
| CF01 | Termination of patent right due to non-payment of annual fee | Granted publication date:20080709 Termination date:20120930 |