WO2018152988A1 - 一种呼叫建立的方法及装置 - Google Patents

一种呼叫建立的方法及装置 Download PDF

Info

Publication number
WO2018152988A1
WO2018152988A1 PCT/CN2017/088520 CN2017088520W WO2018152988A1 WO 2018152988 A1 WO2018152988 A1 WO 2018152988A1 CN 2017088520 W CN2017088520 W CN 2017088520W WO 2018152988 A1 WO2018152988 A1 WO 2018152988A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
terminal
call
network device
calling
Prior art date
Application number
PCT/CN2017/088520
Other languages
English (en)
French (fr)
Inventor
袁锴
窦凤辉
丁明
金辉
Original Assignee
华为技术有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to US16/487,253 priority Critical patent/US10959278B2/en
Priority to JP2019565600A priority patent/JP6803482B2/ja
Priority to CN201780086680.5A priority patent/CN110301124B/zh
Priority to EP17898066.0A priority patent/EP3576364B1/en
Publication of WO2018152988A1 publication Critical patent/WO2018152988A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1069—Session establishment or de-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/25—Maintenance of established connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2201/00—Electronic components, circuits, software, systems or apparatus used in telephone systems
    • H04M2201/18—Comparators

Definitions

  • the embodiments of the present invention relate to the field of communications technologies, and in particular, to a method and an apparatus for establishing a call.
  • the call can realize real-time communication and communication between people, and its importance is self-evident.
  • the terminal initiates a calling telephone call, and another called called telephone is received before the calling telephone is not connected, the calling party and the called party cannot be connected at this time, which is the calling party often encountered now.
  • the called conflict problem if the terminal initiates a calling telephone call, and another called called telephone is received before the calling telephone is not connected, the calling party and the called party cannot be connected at this time, which is the calling party often encountered now.
  • the method for resolving the conflict between the calling party and the called party is as follows: a method for resolving the conflict between the calling party and the called party, including: receiving the called party signaling sent by the network device after the terminal initiates the calling party request; Determining the state conflict between the calling call request and the called signaling, discarding the called signaling, maintaining the calling call connection, and sending a status conflict message to the network device. After receiving the status conflict message sent by the terminal, the network device keeps the called link, rejects the calling call request of the terminal, and sends a reject message to the terminal. At this time, the network device does not release the called connection.
  • the terminal After receiving the reject message sent by the network device, the terminal releases the calling call; the terminal initiates a call replay of the calling call. Since the network device does not release the called connection, the network device does not match the terminal status. Therefore, the network device defaults to the state at this time as a conflict state, so that the network device rejects the request of the terminal to initiate a replay of the calling call.
  • the network device rejects the request initiated by the terminal to replay the calling call, causing the terminal to fail to match the status of the network device, thereby causing neither the calling party nor the called party to be connected, thereby affecting the user experience.
  • Another method for resolving the conflict between the calling party and the called party includes: after the terminal initiates the calling call request, the terminal receives the called signaling sent by the network device, and the terminal determines the state conflict between the calling call request and the called signaling, and Sending a conflict message to the network device, informing the network device to release the called connection, where the conflict message carrying the cause value is busy by the user. After receiving the conflict message sent by the terminal, the network device rejects the calling call request of the terminal and releases the call between the calling party and the called party.
  • this method sends a conflict message to the network device due to the conflict between the calling party and the called party.
  • the network device releases the called party according to the conflict message and rejects the calling party, which also causes the calling party and the called party to fail. Connected, affecting the user experience.
  • the embodiment of the invention provides a method and a device for establishing a call, which solves the problem that neither the calling party nor the called party is connected in the case of a conflict between the calling party and the called party.
  • an embodiment of the present application provides a method for call setup.
  • the method specifically includes: The network device sends a first message, where the first message is used by the terminal to request to establish a calling call, and the terminal enters a call initiation state; the terminal receives a second message sent by the network device, and the second message is used by the terminal to establish a called call; the terminal sends the called call to the network device.
  • Sending a third message, the third message is used to indicate that the second message is incompatible with the protocol status of the terminal; the terminal sends a fourth message to the network device, where the fourth message is used by the terminal to confirm the called call.
  • the terminal determines that the calling call request message and the called call indication message are conflict messages during the period when the calling call is not connected; the terminal buffers the called call indication message, and according to the The indication message received by the network device releases the calling call and establishes a called call connection. It ensures that the user can preferentially perceive the called call request so that the call is not missed. It solves the problem that both the calling party and the called party are not connected in the case of a conflict between the calling party and the called party. Therefore, this solution ensures that the user does not miss the call and improves the user experience.
  • the method for the “terminal receiving the second message sent by the network device” may include: the terminal determining that the second message is incompatible with the call initiation state.
  • the initial state of the called call control state is a null state.
  • the method may include: the terminal buffering the second message.
  • the method for sending the third message to the network device by the terminal may include: receiving, by the terminal, a fifth message sent by the network device, where the fifth message is used to refuse to establish a calling call; The fifth message releases the calling call.
  • the foregoing method for the “terminal sending a third message to the network device” may include: the terminal converting the call control state from the call initiation state to the mobile network call control establishment adaptive MNCC-Setup_IND state.
  • an embodiment of the present application provides a method for establishing a call.
  • the method specifically includes: the network device receiving the first message sent by the terminal, the first message is used to request to establish a calling call; the network device sends a second message to the terminal, the second message is used by the terminal to establish a called call; and the network device receives the terminal.
  • the third message is sent, the network device determines, according to the third message, that the second message is incompatible with the protocol status of the terminal; the network device receives the fourth message sent by the terminal, and the network device establishes a called call connection for the terminal.
  • the network device releases the calling call control state according to the indication message received from the terminal, enters the called call control state, and establishes the called call connection. . It ensures that the user can preferentially perceive the called call request so that the call is not missed. It solves the problem that both the calling party and the called party are not connected in the case of a conflict between the calling party and the called party. Therefore, this solution ensures that the user does not miss the call and improves the user experience.
  • the method for the “network device receiving the third message sent by the terminal” may further include: the network device maintaining the called call.
  • the method for the “network device receiving the third message sent by the terminal” may further include: the network device releasing the calling call.
  • the method for the network device to receive the third message sent by the terminal may further include: the network device sending a fifth message to the terminal, where the fifth message is used to reject the first message.
  • an embodiment of the present application provides a terminal.
  • the terminal includes: a transmitter, configured to send a first message to the network device, where the first message is used by the terminal to request to establish a calling call; the processor is configured to control the terminal to enter a call initiation state; and the receiver is configured to receive, send, by the network device Second message, the second message is used to establish a called party
  • the transmitter is further configured to send a third message to the network device, where the third message is used to indicate that the second message is incompatible with the protocol status of the terminal, and the transmitter is further configured to send the fourth message to the network device, the fourth message. Used by the terminal to confirm the called call.
  • the processor is further configured to determine that the second message is incompatible with the call origination status.
  • the processor is further configured to cache the second message.
  • the receiver is further configured to receive a fifth message sent by the network device, where the fifth message is used to refuse to establish a calling call; and the processor is further configured to: release the main message according to the fifth message. Call the call.
  • the processor is further configured to convert the call control state from a call origination state to a MNCC-Setup_IND state.
  • an embodiment of the present application provides a network device.
  • the device includes: a transmitter, a first message for sending, a first message for requesting to establish a calling call, a transmitter for transmitting a second message to the terminal, and a second message for the terminal to establish a called call.
  • the receiver is configured to receive the third message sent by the terminal, and the network device determines, according to the third message, that the second message is incompatible with the protocol status of the terminal, and the receiver is further configured to: receive the fourth message sent by the terminal.
  • a processor configured to establish a called call connection for the terminal.
  • the processor is further configured to hold the called call.
  • the processor is further configured to release the calling call.
  • the transmitter is further configured to send a fifth message to the terminal, where the fifth message is used to reject the first message.
  • an embodiment of the present application provides a method for establishing a call.
  • the method specifically includes: the terminal sends a first message to the network device, where the first message is used by the terminal to request to establish a calling call; the terminal receives the second message sent by the network device, and the second message is used by the terminal to establish a called call; The second message is sent by the terminal, and the fifth message is used to reject the establishment of the calling call or to accept the establishment of the calling call; when the fifth message is used to refuse to establish the calling call, the terminal according to the fifth message The calling call is released; when the fifth message is used to accept the establishment of the calling call, the terminal continues to establish the calling call according to the fifth message.
  • the terminal determines that the calling call request message and the called call indication message are conflict messages during the period when the calling call is not connected; the terminal does not process the protocol abnormality, and the terminal caches the called party.
  • the call indication message is released, and the calling call is released according to the indication message received from the network device, the called call connection is established, or the calling call connection is established according to the indication message received from the network device.
  • the terminal after the terminal caches the second message, the terminal starts a timer. When the timer expires, the terminal discards the second message. When the timer does not expire, the terminal waits for the indication message sent by the network device.
  • the terminal when the terminal caches the second message, the terminal starts a timer. When the timer expires, the terminal discards the second message. When the timer does not expire, the terminal waits for the indication message sent by the network device. .
  • the terminal after the terminal releases the calling call according to the fifth message, the terminal sends a fourth message to the network device, where the fourth message is used by the terminal to confirm the called call.
  • the terminal before the terminal sends the fourth message to the network device, the terminal reads the cached second message, and only after the terminal reads the second message, the terminal processes the second message.
  • Network equipment Send a fourth message confirming the called call.
  • the terminal after the terminal receives the second message sent by the network device, the terminal does not process the protocol exception (incompatible), caches the second message, waits for the receiving network device to release the calling call, or rejects the primary message. The message called the call.
  • the protocol exception incompatible
  • the terminal when the fifth message is used to accept the establishment of the calling call, the terminal discards the cached second message.
  • an embodiment of the present application provides a terminal.
  • the terminal includes: a transmitter, configured to send a first message to the network device, where the first message is used by the terminal to request to establish a calling call; the processor is configured to control the terminal to enter a call initiation state; and the receiver is configured to receive, send, by the network device The second message is used by the terminal to establish a called call; the processor is further configured to: cache the second message; the receiver is further configured to receive a fifth message sent by the network device, where the fifth message is used to refuse to establish the primary message Calling or for accepting the establishment of the calling call; the processor is further configured to: when the fifth message is used to refuse to establish the calling call, release the calling call according to the fifth message; when the fifth message is used to accept the establishment of the calling call When the call is continued according to the fifth message.
  • the processor is further configured to start a timer, and when the timer expires, the processor discards the second message.
  • the transmitter is further configured to send a fourth message to the network device, where the fourth message is used by the terminal to confirm the called call.
  • the processor is further configured to read the cached second message.
  • the processor is further configured to determine that the second message is incompatible with the call origination status.
  • the processor when the fifth message is used to accept the establishment of the calling call, the processor is further configured to discard the cached second message.
  • an embodiment of the present application provides a computer readable storage medium, where the computer readable storage medium stores instructions that, when run on a computer, cause the computer to perform the methods described in the above aspects.
  • an embodiment of the present application provides a computer program product comprising instructions, when executed on a computer, causing a computer to perform the method described in the above aspects.
  • FIG. 1 is a schematic diagram of a system for establishing a call according to an embodiment of the present invention
  • 2A is a schematic diagram of interaction of a method for establishing a call according to an embodiment of the present invention
  • 2B is a schematic diagram of interaction of another method for establishing a call according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram of interaction of another method for establishing a call according to an embodiment of the present invention.
  • FIG. 4 is a schematic structural diagram of a terminal according to an embodiment of the present invention.
  • FIG. 5 is a schematic structural diagram of a network device according to an embodiment of the present invention.
  • the terminal determines that the calling call request message and the called call indication message are conflict messages during the period when the calling call is not connected; the terminal buffers the called call indication message, and according to the The indication message received by the network device releases the calling call and establishes a called call connection. It ensures that the user can preferentially perceive the called call request so that the call is not missed. It solves the problem that both the calling party and the called party are not connected in the case of a conflict between the calling party and the called party. Therefore, this solution ensures that the user does not miss the call and improves the user experience.
  • FIG. 1 is a schematic diagram of a system for establishing a call according to an embodiment of the present invention.
  • FIG. 1 is a schematic diagram showing a partial structure of a system architecture related to an embodiment of the present invention.
  • the system architecture may include: a network device 20 and a terminal 10.
  • the network device may be a mobile switching center (MSC), and the network device may also include an access network device and a core network device.
  • the terminal 10 may include multiple.
  • the terminal 10 may include Terminal 102, terminal 103, terminal 104, and the like.
  • the plurality of terminals 10 can access the core network device through the access network device to perform communication, and further can enter the backbone network through the core network to communicate through the backbone network.
  • the core network device may be a device that provides a user connection, manages the user, and completes the bearer for the service, and serves as an interface for the bearer network to provide an interface to the external network.
  • the basic services that the core network can provide include mobile office, e-commerce, communication, entertainment services, travel and location-based services, telemetry simple messaging services (monitoring control), and so on.
  • the core network device may be a mobility management entity (MME), a serving gateway (SGW), and a packet data network gateway (packet data network gateway, P-GW) and so on.
  • MME mobility management entity
  • SGW serving gateway
  • P-GW packet data network gateway
  • the access network device can be a device deployed in the wireless access network to provide wireless communication functionality to terminal 10.
  • the apparatus may include various forms of macro base stations, micro base stations, relay stations, access points, and the like.
  • the name of a device having a base station function may be different.
  • an evolved Node B evolved Node B: eNB or eNodeB
  • Node B In the 3G network, it is called Node B and so on.
  • the foregoing access network device and the core network device provide a device for providing wireless communication functions to the terminal, and provide terminal connection, management of the terminal, and completion of the service, and the interface provided to the external network as the bearer network.
  • the devices are collectively referred to as network devices as an example.
  • the network device can be used to receive a call request and establish a call connection.
  • the above-mentioned core network device and access network device are collectively referred to as a network device as an example for description.
  • the network device can be used to receive a call request and establish a call connection.
  • the terminal 10 may include various handheld devices having wireless communication functions, in-vehicle devices, wearable devices, computing devices, or other processing devices connected to a wireless modem, and various forms of user equipment (UE), mobile stations. (mobile station, MS), terminal, terminal equipment, and the like.
  • UE user equipment
  • MS mobile station
  • terminal equipment terminal equipment
  • the interaction process between the terminal 10 and the network device 20 is further described in the specific implementation process of the embodiment of the present application.
  • the network device 20 is described in detail by taking the mobile switching center as an example.
  • FIG. 2A is a schematic diagram of interaction of a method for establishing a call according to an embodiment of the present invention. As shown in FIG. 2A, the method specifically includes:
  • the network device receives the first message sent by the terminal 102.
  • the first message is used by the terminal 102 to request to establish a calling call, and the terminal 102 enters a call initiation state.
  • the calling call means that the terminal 102 requests to establish a call connection with another terminal such as the terminal 103;
  • the call control state of 102 enters the call origination state, and the start state of the call control state may be a Null value (null value) state, or may be other states.
  • the terminal 102 when the terminal 102 needs to establish a communication connection with the terminal 103, the terminal 102 generally sends a calling call request message to the network device, and the calling object of the calling call request message is the terminal 103, and the calling call request message may also be called In the first message, the terminal 102 enters a calling call origination state.
  • the first message sent by the terminal 102 to the network device may be a CM service request message (connect management connection management layer; CM service request connection management service request message).
  • CM service request message connect management connection management layer
  • the request message carries the identifier of the terminal 103, and the request message is used to request the network device to initiate a call to the terminal 103, wherein the NAS is represented as a non-access stratum (Non-Acess Stratum), and the SERV_REQUEST represents a call request.
  • CM service request message connect management connection management layer
  • CM service request connection management service request message For example, "ID_NAS_CM_SERV_REQUEST”, the request message carries the identifier of the terminal 103, and the request message is used to request the network device to initiate a call to the terminal 103, wherein the NAS is represented as a non-access stratum (Non-Acess Stratum), and the SERV_REQUEST represents a call request.
  • NAS non-access stratum
  • the network device receives a call request message that the terminal 103 calls the terminal 102.
  • the call request of the terminal 103 to the terminal 102 may be referred to as the called call request of the terminal 102.
  • the network device receives the call request message of the calling terminal 102 transmitted by the terminal 103.
  • the terminal 102 and the user of the terminal 103 have an appointment to contact the phone at a certain time.
  • the terminal 102 and the terminal 103 may send the calling party to the network device at a time when the difference is not significant.
  • the call request message, or the call between the terminal 102 and the terminal 103 is abnormal, the connection is disconnected, but when the call needs to be continued, the terminal 102 and the terminal 103 may send a call request message of the calling party to the network device at a time when the difference is not significant. .
  • the network device sends a second message to the terminal 102.
  • the second message is used by the terminal 102 to establish a called call, and the establishment of the called call refers to establishing a connection for the called call request.
  • the network device transmits a second message to the terminal 102 according to the call request message that the terminal 103 calls the terminal 102.
  • the second message can be a Setup message (establishment message).
  • the above steps may be represented as ID_NAS_CC_SETUP, where SETUP may indicate that the terminal 103 calls the call indication message of the terminal 102, wherein the CC may be represented as Call Control.
  • the terminal 102 determines, according to the received second message, that the second message is incompatible with the call initiation status of the terminal 102, and stores the second message.
  • the terminal 102 is in the calling call state, and when the called call is received, it is determined that the calling call is incompatible with the called call, and then the second message is stored.
  • the incompatible state can be in a variety of situations, and can include: the message is incompatible and/or conflicting with the protocol state, the message type is incompatible with the protocol state and/or conflicts, and the second message is incompatible and/or conflicting with the first message, This includes but is not limited to these three situations. Specifically, it can be understood that the message type of the second message is incompatible with the call origination state or is a conflict.
  • the specific implementation scheme can be understood as that after the terminal receives the call setup message, the terminal determines that the second message is incompatible or conflicts with the current state of the terminal according to the current state, that is, after the terminal receives the second message in the call initiation state.
  • the second message is considered to be a conflict message.
  • the terminal may also wait for a mobility management (MM) connection to be established, and when in the MM Connection pending (U0.1) state, receive a second message to determine that the calling call conflicts with the called call.
  • MM mobility management
  • the process may be represented as a UE NAS_CC, and the terminal 102 is in a calling call state.
  • the called call message is received, it is determined that the calling call message and the called call message are conflict messages, and the SETUP is cached. interest.
  • the terminal 102 sends a third message to the network device.
  • the terminal 102 sends a third message to the network device, where the third message is used to indicate that the second message is incompatible with the protocol status of the terminal.
  • the third message may be a Status message (status message), and the third message may carry a cause value.
  • the terminal 102 sends a CC_STATUS message to the network device to notify the network device that the second message is incompatible with the protocol status of the terminal.
  • the Status message may be represented as a third message, such as ID_NAS_CC_STATUS, which may carry a #98 cause value of Message type not compatible with protocol state, and may also carry a #101 cause value of Message not compatible with protocol state, and the cause value is used for The type indicating the second message or the message itself is incompatible with the protocol status of the terminal.
  • the network device determines, according to the third message, that the second message is incompatible with the protocol status of the terminal 102, and the terminal 103 is called to call the terminal 102.
  • the network device maintains the called call state according to determining that the second message is incompatible with the protocol status of the terminal 102 according to the third message.
  • the network device sends a fifth message to the terminal 102.
  • the fifth message is used to refuse to establish a calling call, and the fifth message can be expressed as a CM service reject (connect management connection management layer; CM service reject connection management service rejection message).
  • the above steps may be represented as ID_NAS_CM_SERV_REJECT, indicating that the network device sends a Service Reject message to the terminal 102.
  • the terminal 102 rejects the first message according to the fifth message sent by the receiving network device, and releases the calling call.
  • the terminal 102 releases the calling call essentially releasing the MM connection (Mobile Management) that the calling call has established. Specifically, the terminal 102 releases the call control state of the terminal 103 to the terminal 103 according to the fifth message sent by the network device, and enters the call control state of the terminal 103 to the terminal 103. At this time, the terminal 102 converts the call control state from the call initiation state to the call initiation state. MNCC-Setup IND state, where the MNCC-Setup IND state is Mobile Network Call Control Set Up Indication.
  • the terminal is a UE, and the UE releases the calling call control state according to the received fifth message sent by the network device, turns off the terminal calling call control state machine, and the UE starts a new called call control state machine, and the new is The call control state machine starts from the null state and terminates in the MNCC-Setup IND state.
  • the terminal 102 converts the call control state from the call origination state to the MNCC-Setup IND state, which can be directly converted, or can pass other intermediates.
  • the state implements the conversion.
  • the specific implementation solution includes the following methods: Method 1: The primary and the called one CC entity, after releasing the calling party, the calling CC state machine is switched from call initated to Null.
  • Method 2 The calling party multiplexes a CC entity, and the caller's call initated state is converted into the called MNCC-Setup_IND state. Specifically, it can be call initiated->null->MNCC-Setup_IND or direct conversion. Including but not limited to the above two methods.
  • the terminal 102 sends a fourth message to the network device.
  • the terminal 102 sends a fourth message to the network device, the fourth message being used by the terminal 102 to confirm the called call.
  • the fourth message may be a Call confirmed message.
  • the above may indicate that, for example, ID_NAS_CC_CALL_CONFIRM, the terminal 102 is to the network device.
  • the call_confirm message is sent, and the call_confirm message can be expressed as the information of the call confirmation.
  • the network device establishes, according to the fourth message, the call connection of the terminal 103 to the terminal 102, that is, establishes a called call connection.
  • FIG. 2B is a schematic diagram of interaction of another method for establishing a call according to an embodiment of the present invention.
  • the call setup method shown in FIG. 2B is substantially the same as S210-S240 of the call setup method shown in FIG. 2A, and will not be described in detail herein.
  • the terminal 102 in S240, does not process the protocol exception (incompatible) after receiving the second message, but caches the second message. After buffering the second message, the terminal 102 does not send a third message to the network device, but performs step S241. The terminal 102 starts a timer.
  • the terminal may also wait for the establishment of the mobility management connection, and when the MM Connection pending (U0.1) state is received, the second message is received. At this time, the terminal does not process the protocol exception, and the terminal caches the second message. A message waiting to be accepted by the network to accept a calling call or reject a calling call.
  • the timer that is started by the terminal 102 may be a cache timer.
  • the cache timer is used to cache the second message within a certain period of time. When the cache timer expires, the terminal discards the cached second message.
  • the terminal starts the timer after buffering the second message.
  • the terminal may start the timer while buffering the second message.
  • the time interval between the second message and the start timer and the sequence of the two are not limited to the embodiment of the present invention.
  • the terminal waits for the fifth message sent by the network device, and performs the following different operations according to the fifth message sent by the network device.
  • the fifth message sent by the network device is used to refuse to establish the calling call
  • the fifth message can be expressed as CM service reject (connect management connection management layer; CM service reject connection management service rejection message).
  • CM service reject connect management connection management layer
  • the above steps may be represented as ID_NAS_CM_SERV_REJECT, indicating that the network device sends a Service Reject message to the terminal 102.
  • the terminal 102 rejects the first message according to the fifth message sent by the receiving network device, and releases the calling call.
  • step S290 as shown in FIG. 2A can also be performed, that is, after the terminal releases the calling call, the fourth message can be sent to the network device, and the fourth message is used by the terminal to confirm the called call.
  • the network device After receiving the fourth message, the network device establishes a call connection of the terminal 103 to the terminal 102.
  • the terminal before the terminal sends the fourth message to the network device, it is determined whether there is a call indication message indicating the calling terminal 102, that is, the terminal first reads the cached second message.
  • the terminal After processing the second message, the terminal sends a fourth message to the network device, where the fourth message is used by the terminal 102 to confirm the called call.
  • the fourth message may be a Call confirmed message.
  • the terminal does not successfully read the second message, for example, when the buffer has expired and the terminal has discarded the cached second message, the terminal does not send the fourth message to the network device.
  • the fifth message sent by the network device is used to accept the establishment of the calling call, and the fifth message can be expressed as CM service accept (connect management connection management; CM service accept connection management service acceptance message).
  • CM service accept connect management connection management
  • the above steps may be represented as ID_NAS_CM_SERV_ACCEPT, indicating that the network device sends a Service Accept message to the terminal 102.
  • the terminal 102 discards the cached second message according to the fifth message sent by the network device, and continues to establish the calling call.
  • step S281 the step of establishing a calling call connection is performed.
  • FIG. 3 is a schematic diagram of interaction of another method for establishing a call according to an embodiment of the present invention. It should be noted, The method is applicable to the terminal 102 initiating a calling call to the terminal 103. In the case that the terminal 103 is not connected, the terminal 104 initiates a calling call to the terminal 102, wherein the call between the terminal 102 and the terminal 103 can be referred to as the terminal 102. The calling call, the call between the terminal 104 and the terminal 102 may be referred to as the called call of the terminal 102. Specifically, as shown in FIG. 3, the method specifically includes:
  • the network device receives the first message sent by the terminal 102.
  • the first message is used by the terminal 102 to request to establish a calling call, and the terminal 102 enters a call initiation state.
  • the calling call refers to the terminal 102 requesting to establish a call connection with other terminals; the call control state of the terminal 102 enters a call initiation state, and the initial state of the call control state may be a null value (null value) state, or may be Other status.
  • the terminal 102 when the terminal 102 needs to establish a communication connection with the terminal 103, the terminal 102 generally sends a calling call request message to the network device, and the calling object of the calling call request message is the terminal 103, and the calling call request message may also be called In the first message, the terminal 102 enters a calling call origination state.
  • the first message sent by the terminal 102 to the network device may be a CM service request message (connect management connection management layer; CM service request connection management service request message).
  • CM service request message connect management connection management layer
  • the request message carries the identifier of the terminal 103, and the request message is used to request the network device to initiate a call to the terminal 103, wherein the NAS is represented as a non-access stratum (Non-Acess Stratum), and the SERV_REQUEST represents a call request.
  • CM service request message connect management connection management layer
  • CM service request connection management service request message For example, "ID_NAS_CM_SERV_REQUEST”, the request message carries the identifier of the terminal 103, and the request message is used to request the network device to initiate a call to the terminal 103, wherein the NAS is represented as a non-access stratum (Non-Acess Stratum), and the SERV_REQUEST represents a call request.
  • NAS non-access stratum
  • the network device receives a call request message that the terminal 104 calls the terminal 102.
  • the call request of the terminal 104 to the terminal 102 may be referred to as the called call request of the terminal 102.
  • the network device When the terminal 102 calls the terminal 103 and the terminal 103 is not turned on, the network device receives the call request message of the calling terminal 102 transmitted by the terminal 104.
  • the network device sends a second message to the terminal 102.
  • the second message is used by the terminal 102 to establish a called call, and the establishment of the called call refers to establishing a connection for the called call request.
  • the network device transmits a second message to the terminal 102 in accordance with the call request message of the calling terminal 102.
  • the second message can be a Set up message (establishment message).
  • the above steps may be represented as ID_NAS_CC_SETUP, where SETUP may represent a call indication message of the calling terminal 102, wherein the CC may be represented as Call Control.
  • the terminal 102 determines, according to the received second message, that the second message is incompatible with the call initiation state of the terminal 102, and stores the second message.
  • the terminal 102 is in the calling call state, and when the called call is received, it is determined that the calling call is incompatible with the called call, and then the second message is stored.
  • the incompatible state can be in a variety of situations, and can include: the message is incompatible and/or conflicting with the protocol state, the message type is incompatible with the protocol state and/or conflicts, and the second message is incompatible and/or conflicting with the first message, This includes but is not limited to these three situations. Specifically, it can be understood that the message type of the second message is incompatible with the call origination state or is a conflict.
  • the specific implementation scheme can be understood as that after the terminal receives the call setup message, the terminal determines that the second message is incompatible or conflicts with the current state of the terminal according to the current state, that is, after the terminal receives the second message in the call initiation state.
  • the second message is considered to be a conflict message.
  • the process may be represented as a UE NAS_CC, and the terminal 102 is in a calling call state.
  • the called call message is received, it is determined that the calling call message and the called call message are conflict messages, and the SETUP is cached. interest.
  • the terminal 102 sends a third message to the network device.
  • the terminal 102 sends a third message to the network device, where the third message is used to indicate that the second message is incompatible with the protocol status of the terminal.
  • the third message may be a Status message (status message), and the third message may carry a cause value.
  • the terminal 102 sends a CC_STATUS message to the network device to notify the network device that the second message is incompatible with the protocol status of the terminal.
  • the SETUS message may be represented as a third message, such as ID_NAS_CC_STATUS, which may carry a #98 cause value of Message type not compatible with protocol state, and may also carry a #101 cause value of Message not compatible with protocol state, and the cause value is used for The message type indicating the second message or the message itself is not compatible with the protocol status of the terminal.
  • the network device determines, according to the third message, that the second message is incompatible with the protocol status of the terminal 102, and the terminal 104 is called to call the terminal 102.
  • the network device maintains the called call state according to determining that the second message is incompatible with the protocol status of the terminal 102 according to the third message.
  • the network device sends a fifth message to the terminal 102.
  • the fifth message is used to refuse to establish a calling call, and the fifth message can be expressed as a CM service reject (connect management connection management layer; CM service reject connection management service rejection message).
  • the above steps may be represented as ID_NAS_CM_SERV_REJECT, indicating that the network device sends a Service Reject message to the terminal 102.
  • the terminal 102 rejects the first message according to the fifth message sent by the receiving network device, and releases the calling call.
  • the terminal 102 releases the calling call essentially releasing the MM connection (Mobile Management) that the calling call has established. Specifically, the terminal 102 releases the call control state of the terminal 103 to the terminal 103 according to the fifth message sent by the network device, and enters the call control state of the terminal 104 to the terminal 104. At this time, the terminal 102 converts the call control state from the call initiation state to the call initiation state. MNCC-Setup IND state, where the MNCC-Setup IND state is Mobile Network Call Control Set Up Indication.
  • the terminal is a UE, and the UE releases the calling call control state according to the received fifth message sent by the network device, turns off the terminal calling call control state machine, and the UE starts a new called call control state machine, and the new is The call control state machine starts from the null state and terminates in the MNCC-Setup IND state.
  • the terminal 102 converts the call control state from the call origination state to the MNCC-Setup IND state, which can be directly converted, or can pass other intermediates.
  • the state implements the conversion.
  • the specific implementation solution includes the following methods: Method 1: The primary and the called one CC entity, after releasing the calling party, the calling CC state machine is switched from call initated to Null.
  • Method 2 The calling party and the called party multiplex a CC entity, and the caller's call initated state is converted into the called MNCC-Setup_IND state. Specifically, it can be call initiated->null->MNCC-Setup_IND or direct conversion. Including but not limited to the above two methods.
  • the terminal 102 sends a fourth message to the network device.
  • the terminal 102 sends a fourth message to the network device, the fourth message being used by the terminal 102 to confirm the called call.
  • the fourth message may be a Call confirmed message.
  • the above may indicate that, for example, ID_NAS_CC_CALL_CONFIRM, the terminal 102 is to the network device.
  • the call_confirm message is sent, and the call_confirm message can be expressed as the information of the call confirmation.
  • the network device establishes, according to the fourth message, the call connection of the terminal 104 to the terminal 102, that is, establishes a called call connection.
  • the call setup method shown in FIG. 3 may not perform step S350 after step S340, that is, the terminal 102 also does not send the third message to the network device.
  • the second message is cached, waiting to accept the fifth message sent by the network device.
  • the operation after the second message is cached is the same as the call setup method shown in FIG. 2B. Reference may be made to the previous description, and details are not described herein again.
  • FIG. 4 is a schematic structural diagram of a terminal according to an embodiment of the present invention.
  • the terminal includes a transmitter 401, a processor 402, and a receiver 403.
  • the transceiver can include a receiver 403 and a transmitter 401, which can be integrated.
  • the transmitter conditions (eg, analog conversion, filtering, amplification, upconversion, etc.) the output samples and generates an uplink signal that is transmitted to the network device via the antenna.
  • the antenna receives the downlink signal transmitted by the network device in the above embodiment.
  • the receiver conditions (eg, filters, amplifies, downconverts, digitizes, etc.) the signals received from the antenna and provides input samples.
  • the terminal may further include a modem processor, in the modem processor, receiving service data and signaling messages to be transmitted on the uplink, and processing the service data and the signaling message (eg, formatting, Coding and interleaving).
  • the encoded service data and signaling messages are further processed (e.g., symbol mapped and modulated) and provided with output samples.
  • the input samples are processed (e.g., demodulated) and provided with symbol estimates.
  • the symbol is processed (e.g., deinterleaved and decoded) and the decoded data and signaling messages sent to the UE are provided.
  • These units are processed according to the radio access technology employed by the radio access network (e.g., access technologies of LTE and other evolved systems).
  • the processor controls and manages the actions of the terminal for performing the processing performed by the terminal in the above embodiment. For example, other processes for controlling terminal call setup and/or the techniques described herein. As an example:
  • the sender 401 is configured to send a first message to the network device, where the first message is used by the terminal to request to establish a calling call.
  • the processor 402 is configured to control an incoming call origination state.
  • the receiver 403 is configured to receive a second message sent by the network device, where the second message is used by the terminal to establish a called call.
  • the transmitter 401 is further configured to send a third message to the network device, where the third message is used to indicate that the second message is incompatible with the protocol status of the terminal.
  • the transmitter 403 is further configured to send a fourth message to the network device, where the fourth message is used by the terminal to confirm the called call.
  • the processor 402 is further configured to determine that the second message is incompatible with the call origination status.
  • the processor 402 is further configured to cache the second message.
  • the receiver 403 is further configured to receive a fifth message sent by the network device, where the fifth message is used to refuse to establish a calling call or accept to establish a calling call.
  • the processor 402 is further configured to release the calling call according to the fifth message.
  • the processor 402 is further configured to convert the call control state from a call origination state to a MNCC-Setup_IND state.
  • the processor 402 is further configured to: initiate a cache timer, and release the calling call or continue the calling call according to the fifth message.
  • the processor 402 is further configured to read the cached second message.
  • the processor 402 when the fifth message is used to accept the establishment of the calling call, the processor 402 is further configured to discard the cached second message.
  • the terminal may also include the memory for storing program codes and data for the terminal.
  • FIG. 5 is a schematic structural diagram of a network device according to an embodiment of the present invention.
  • the network device 500 includes a transmitter 501, a processor 502, and a receiver 503.
  • the processor is configured to control and manage the actions of the network device, and perform various functions to support the communication service of the terminal.
  • the sender 501 is configured to send a first message to the network device, where the first message is used to request to establish a calling call, and the sender 501 is further configured to send a second message to the terminal, where the second message is used to establish the terminal Call the call.
  • the receiver 503 is configured to receive the third message sent by the terminal, and the network device determines, according to the third message, that the second message is incompatible with the protocol status of the terminal, and the receiver is further configured to receive the fourth message sent by the terminal.
  • the processor 502 is configured to establish the called call connection for the terminal.
  • the processor is configured to support a network device to perform the process 402 of FIG. 4, and/or other processes for the techniques described herein.
  • the network device also includes a memory for storing program code and data for the network device.
  • Transceiver 503 is used to support communication with other network entities.
  • the transceiver can include a receiver and a transmitter, which can be integrated.
  • the processor for performing the foregoing functions of the terminal or the network device in the embodiment of the present invention may be a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), and an application specific integrated circuit. (Application-Specific Integrated Circuit, ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the transceiver may be a communication interface, a transceiver circuit, etc., wherein the transceiver is a collective name and may include one or more interfaces.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present invention are generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a server that includes one or more available media integrations. Data storage devices such as data centers.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)).

Abstract

本发明实施例涉及了一种呼叫建立的方法和装置，涉及通信技术领域，具体方法包括：终端向网络设备发送第一消息，第一消息用于终端请求建立主叫呼叫；终端接收网络设备发送的第二消息；终端向网络设备发送第三消息；终端向网络设备发送第四消息，第四消息用于终端确认被叫呼叫。本方案中，若主叫和被叫冲突，在主叫呼叫没有接通的时段，终端确定主叫呼叫请求消息与被叫呼叫指示消息为冲突消息；终端缓存被叫呼叫指示消息，并根据从网络设备接收的指示消息释放主叫通话，建立被叫通话连接。保证了用户能够优先感知被叫呼叫请求，从而不会漏接电话。解决了在主叫和被叫冲突的情况下，主叫和被叫均未接通的问题。

Description

一种呼叫建立的方法及装置
本申请要求2017年2月22日提交中国专利局、申请号为201710096800.1、发明名称为“一种呼叫发起方法和设备”的中国专利申请的优先权，本申请要求2017年5月5日提交中国专利局、申请号为PCT/CN2017/083291、发明名称为“一种呼叫建立的方法”的PCT专利申请的优先权，上述两个专利的全部内容通过引用结合在本申请文件中。
技术领域
本发明实施例涉及通信技术领域，尤其涉及一种呼叫建立的方法及装置。
背景技术
通话作为终端最重要的功能之一，它可以实现人与人之间的实时沟通与交流，其重要性是不言而喻的。然而，若终端发起一路主叫电话呼叫后，在主叫电话未接通之前又接收到另外一路被叫电话，此时主叫和被叫均无法接通，是现在经常遇到的主叫与被叫冲突问题。
通常，解决主叫与被叫冲突的方法有如下几种：一种解决主叫与被叫冲突的方法，包括：终端发起主叫呼叫请求后收到网络设备下发的被叫信令；终端确定主叫呼叫请求与被叫信令的状态冲突，则丢弃被叫信令，保持主叫呼叫连接，并向网络设备发送状态冲突消息。网络设备接收到终端发送的状态冲突消息后，保持被叫链路，拒绝终端的主叫呼叫请求，并向终端发送拒绝消息，此时，网络设备没有释放被叫连接。终端接收到网络设备发送的拒绝消息后，释放主叫通话；终端发起主叫呼叫重播。由于网络设备没有释放被叫连接，导致网络设备与终端状态不匹配。所以，网络设备默认为此时的状态为冲突状态，以至于网络设备拒绝终端发起主叫呼叫重播的请求。
然而，此方法由于终端丢弃被叫信令，网络设备拒绝终端发起的主叫呼叫重播的请求，导致终端与网络设备状态不匹配，从而导致主叫与被叫均未接通，影响用户体验。
另一种解决主叫与被叫冲突的方法，包括：终端发起主叫呼叫请求后收到网络设备下发的被叫信令，终端确定主叫呼叫请求与被叫信令的状态冲突，并向网络设备发送冲突消息，通知网络设备释放被叫连接，其中，上述冲突消息携带原因值为用户忙。网络设备接收到终端发送的冲突消息后，拒绝掉终端的主叫呼叫请求并释放主叫和被叫的通话。
然而，此方法由于处在主叫和被叫冲突的场景下，终端向网络设备发送冲突消息，网络设备根据冲突消息释放了被叫并拒绝了主叫，同样导致了主叫和被叫均未接通，影响用户体验。
发明内容
本发明实施例提供了一种呼叫建立的方法及装置，解决了在主叫和被叫冲突的情况下，主叫和被叫均未接通的问题。
第一方面，本申请实施例提供了一种呼叫建立的方法。该方法具体包括：终端向 网络设备发送第一消息，第一消息用于终端请求建立主叫呼叫，终端进入呼叫发起状态；终端接收网络设备发送的第二消息，第二消息用于终端建立被叫呼叫；终端向网络设备发送第三消息，第三消息用于指示第二消息与终端的协议状态不兼容；终端向网络设备发送第四消息，第四消息用于终端确认被叫呼叫。
本方案中，若主叫和被叫冲突，在主叫呼叫没有接通的时段，终端确定主叫呼叫请求消息与被叫呼叫指示消息为冲突消息；终端缓存被叫呼叫指示消息，并根据从网络设备接收的指示消息释放主叫通话，建立被叫通话连接。保证了用户能够优先感知被叫呼叫请求，从而不会漏接电话。解决了在主叫和被叫冲突的情况下，主叫和被叫均未接通的问题。所以本方案保证了用户不会漏接电话，提高了用户体验。
在一个可选的实现方式中，上述“终端接收网络设备发送的第二消息”的方法之后可以包括：所述终端确定所述第二消息与所述呼叫发起状态不兼容。
在另一个可选的实现方式中，被叫呼叫控制状态的起始状态为空值状态。
在又一个可选的实现方式中，上述在“终端接收网络设备发送的第二消息”的方法之后可以包括：终端缓存第二消息。
在再一个可选的实现方式中，上述“终端向网络设备发送第三消息”的方法之后可以包括：终端接收网络设备发送的第五消息，第五消息用于拒绝建立主叫呼叫；终端根据第五消息释放主叫呼叫。
在再一个可选的实现方式中，上述“终端向网络设备发送第三消息”的方法之后可以包括：终端将呼叫控制状态从呼叫发起状态转换为移动网络呼叫控制建立适应性MNCC-Setup_IND状态。
第二方面，本申请实施例提供了一种呼叫建立的方法。该方法具体包括：网络设备接收终端发送的第一消息，第一消息用于请求建立主叫呼叫；网络设备向终端发送第二消息，第二消息用于终端建立被叫呼叫；网络设备接收终端发送的第三消息，网络设备根据第三消息确定第二消息与终端的协议状态不兼容；网络设备接收终端发送的第四消息，网络设备为终端建立被叫呼叫连接。
本方案中，若主叫和被叫冲突，在主叫呼叫没有接通的时段，网络设备根据从终端接收的指示消息释放主叫呼叫控制状态，进入被叫呼叫控制状态，建立被叫通话连接。保证了用户能够优先感知被叫呼叫请求，从而不会漏接电话。解决了在主叫和被叫冲突的情况下，主叫和被叫均未接通的问题。所以本方案保证了用户不会漏接电话，提高了用户体验。
在一个可选的实现方式中，上述“网络设备接收所述终端发送的第三消息”的方法之后还可以包括：网络设备保持被叫呼叫。
在另一个可选的实现方式中，上述“网络设备接收所述终端发送的第三消息”的方法之后还可以包括：网络设备释放所述主叫呼叫。
在又一个可选的实现方式中，上述“网络设备接收所述终端发送的第三消息”的方法之后还可以包括：网络设备向终端发送第五消息，第五消息用于拒绝第一消息。
第三方面，本申请实施例提供了一种终端。该终端包括：发送器，用于向网络设备发送第一消息，第一消息用于终端请求建立主叫呼叫；处理器，用于控制终端进入呼叫发起状态；接收器，用于接收网络设备发送的第二消息，第二消息用于终端建立被叫 呼叫；发送器还用于，向网络设备发送第三消息，第三消息用于指示第二消息与终端的协议状态不兼容；发送器还用于，向网络设备发送第四消息，第四消息用于终端确认被叫呼叫。
在一个可选的实现方式中，上述处理器还用于，确定第二消息与呼叫发起状态不兼容。
在另一个可选的实现方式中，上述处理器还用于，缓存所述第二消息。
在又一个可选的实现方式中，上述接收器还用于，接收网络设备发送的第五消息，第五消息用于拒绝建立主叫呼叫；上述处理器还用于，根据第五消息释放主叫呼叫。
在再一个可选的实现方式中，上述处理器还用于，将呼叫控制状态从呼叫发起状态转换为MNCC-Setup_IND状态。
第四方面，本申请实施例提供了一种网络设备。该设备包括：发送器，用于发送的第一消息，第一消息用于请求建立主叫呼叫；发送器还用于，向终端发送第二消息，第二消息用于终端建立被叫呼叫。
接收器，用于接收终端发送的第三消息，网络设备根据第三消息确定第二消息与终端的协议状态不兼容；接收器还用于，接收终端发送的第四消息。
处理器，用于为终端建立被叫呼叫连接。
在一个可选的实现方式中，上述处理器还用于，保持被叫呼叫。
在另一个可选的实现方式中，上述处理器还用于，释放主叫呼叫。
在又一个可选的实现方式中，上述发送器还用于，向终端发送第五消息，第五消息用于拒绝第一消息。
第五方面，本申请实施例提供了一种呼叫建立的方法。该方法具体包括：终端向网络设备发送第一消息，第一消息用于终端请求建立主叫呼叫；终端接收网络设备发送的第二消息，第二消息用于终端建立被叫呼叫；终端缓存第二消息；终端接收网络设备发送的第五消息，第五消息用于拒绝建立主叫呼叫或用于接受建立主叫呼叫；当第五消息用于拒绝建立主叫呼叫时，终端根据第五消息释放主叫呼叫；当第五消息用于接受建立主叫呼叫时，终端根据第五消息继续建立主叫呼叫。
本方案中，若主叫和被叫冲突，在主叫呼叫没有接通的时段，终端确定主叫呼叫请求消息与被叫呼叫指示消息为冲突消息；终端不处理为协议异常，终端缓存被叫呼叫指示消息，并根据从网络设备接收的指示消息释放主叫通话，建立被叫通话连接，或者根据从网络设备接收的指示消息建立主叫通话连接。解决了在主叫和被叫冲突的情况下，主叫和被叫均未接通的问题。
在一个可选的实现方式中，终端缓存第二消息后，终端启动定时器，当定时器超时时，终端丢弃第二消息；当定时器未超时时，终端等待网络设备下发的指示消息。
在一个可选的实现方式中，终端缓存第二消息的同时，终端启动定时器，当定时器超时时，终端丢弃第二消息；当定时器未超时时，终端等待网络设备下发的指示消息。
在一个可选的实现方式中，终端根据第五消息释放主叫呼叫之后，终端向网络设备发送第四消息，第四消息用于终端确认被叫呼叫。
在另一个可选的实现方式中，终端向网络设备发送第四消息之前，终端读取缓存的第二消息，仅当终端读取到第二消息，对第二消息进行处理后，终端才向网络设备发 送确认被叫呼叫的第四消息。
在另一个可选的实现方式中，终端接收网络设备发送的第二消息之后，终端不处理为协议异常(不兼容)，缓存第二消息，等待接收网络设备发送的释放主叫呼叫或者拒绝主叫呼叫的消息。
在再一个可选的实现方式中，当第五消息用于接受建立所述主叫呼叫时，终端丢弃缓存的第二消息。
第六方面，本申请实施例提供了一种终端。该终端包括：发送器，用于向网络设备发送第一消息，第一消息用于终端请求建立主叫呼叫；处理器，用于控制终端进入呼叫发起状态；接收器，用于接收网络设备发送的第二消息，第二消息用于终端建立被叫呼叫；处理器还用于，缓存第二消息；接收器还用于，接收网络设备发送的第五消息，第五消息用于拒绝建立主叫呼叫或用于接受建立主叫呼叫；处理器还用于，当第五消息用于拒绝建立主叫呼叫时，根据第五消息释放主叫呼叫；当第五消息用于接受建立主叫呼叫时，根据第五消息继续主叫呼叫。
在一个可选的实现方式中，上述处理器还用于启动定时器，当所述定时器超时时，处理器丢弃第二消息。
在一个可选的实现方式中，上述发送器还用于向网络设备发送第四消息，第四消息用于终端确认被叫呼叫。
在一个可选的实现方式中，上述处理器还用于，读取缓存的第二消息。
在一个可选的实现方式中，上述处理器还用于，确定第二消息与呼叫发起状态不兼容。
在一个可选的实现方式中，当第五消息用于接受建立主叫呼叫时，上述处理器还用于，丢弃缓存的第二消息。
第七方面，本申请实施例提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
第八方面，本申请实施例提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
附图说明
图1为本发明实施例提供的一种呼叫建立的系统示意图；
图2A为本发明实施例提供的一种呼叫建立的方法的交互示意图；
图2B为本发明实施例提供的另一种呼叫建立的方法的交互示意图；
图3为本发明实施例提供的再一种呼叫建立的方法的交互示意图；
图4为本发明实施例中所涉及的一种终端的结构示意图；
图5为本发明实施例中所涉及的一种网络设备的结构示意图。
具体实施方式
为便于对本发明实施例的理解，下面将结合附图对具体实施例做进一步的解释说明，实施例并不构成对本发明实施例的限定。
本方案中，若主叫和被叫冲突，在主叫呼叫没有接通的时段，终端确定主叫呼叫请求消息与被叫呼叫指示消息为冲突消息；终端缓存被叫呼叫指示消息，并根据从网络设备接收的指示消息释放主叫通话，建立被叫通话连接。保证了用户能够优先感知被叫呼叫请求，从而不会漏接电话。解决了在主叫和被叫冲突的情况下，主叫和被叫均未接通的问题。所以本方案保证了用户不会漏接电话，提高了用户体验。
图1为本发明实施例提供的一种呼叫建立的系统示意图。图1示出的是与本发明实施例相关的系统架构的部分结构的示意图，如图1所示，该系统架构具体可以包括：网络设备20，终端10。其中，网络设备可以为移动交换中心(mobile switching center，MSC)，网络设备也可以包括接入网设备以及核心网设备；终端10可以包括多个，例如，如图1所示，终端10可以包括终端102、终端103以及终端104等等。多个终端10可以通过接入网设备接入核心网设备，进行通信，进一步地，还可以再通过核心网进入骨干网，通过骨干网进行通信。
核心网设备可以为提供用户连接、对用户进行管理以及对业务完成承载，作为承载网络提供到外部网络的接口的设备。核心网可以提供的基本业务包括移动办公、电子商务、通信、娱乐性业务、旅行和基于位置的服务、遥感业务(Telemetry)简单消息传递业务(监视控制)等等。以长期演进(Long Term Evolution,LTE)通信系统为例，核心网设备可以是移动管理实体(mobility management entity，MME)，服务网关(serving gateway，SGW)，分组数据网网关(packet data network gateway，P-GW)等等。
接入网设备可以为一种部署在无线接入网中用以为终端10提供无线通信功能的装置。该装置可以包括各种形式的宏基站，微基站，中继站，接入点等等。在采用不同的无线接入技术的系统中，具备基站功能的设备的名称可能会有所不同，例如在LTE网络中，称为演进的节点B(evolved NodeB简称：eNB或者eNodeB),在第三代3G网络中，称为节点B(Node B)等等。为了方便描述，本申请中，上述的接入网设备和核心网设备为终端提供无线通信功能的装置以及提供终端连接、对终端的管理以及对业务完成承载、作为承载网络提供到外部网络的接口的设备统称为网络设备为例进行描述。该网络设备可以用于接收呼叫请求并建立通话连接。
为了方便描述，本申请中，以上述的核心网设备和接入网设备统称为网络设备为例进行描述。该网络设备可以用于接收呼叫请求并建立通话连接。
该终端10可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备,以及各种形式的用户设备(user equipment,UE),移动台(mobile station,MS)，终端(terminal)，终端设备(terminal equipment)等。
下面结合附图对在本申请实施例的具体实施过程中，终端10与网络设备20的交互过程进行进一步地介绍，其中，网络设备20以移动交换中心为例详细说明。
图2A为本发明实施例提供的一种呼叫建立的方法的交互示意图。如图2A所示，该方法具体包括：
S210，网络设备接收终端102发送的第一消息。
其中，该第一消息用于终端102请求建立主叫呼叫，该终端102进入呼叫发起状态。该主叫呼叫是指终端102请求建立一个与其他终端例如终端103的通话连接；终端 102的呼叫控制状态进入到呼叫发起状态，呼叫控制状态的起始状态可以为Null值(空值)状态，也可以为其他状态。
具体地，终端102在需要与终端103建立通信连接时，一般会向网络设备发送主叫呼叫请求消息，该主叫呼叫请求消息的呼叫对象为终端103，该主叫呼叫请求消息也可称为第一消息，该终端102进入主叫呼叫发起状态。
具体地，终端102向网络设备发送的第一消息可以为CM service request消息(connect management连接管理层；CM service request连接管理层服务请求消息)。例如，“ID_NAS_CM_SERV_REQUEST”，该请求消息携带终端103的标识，该请求消息用于请求网络设备发起对终端103的呼叫，其中，NAS表示为非接入层(Non-Acess Stratum)，SERV_REQUEST表示呼叫请求消息。
S220，网络设备接收终端103呼叫终端102的呼叫请求消息。
其中，该终端103呼叫终端102的呼叫请求可以称为终端102的被叫呼叫请求。
在终端102呼叫终端103时，终端103没有接通的情况下，网络设备接收到终端103发送的呼叫终端102的呼叫请求消息。出现上述情况的原因可能有多种，例如，终端102与终端103的用户约好在某一时间电话联系，此时，终端102与终端103可能在相差不大的时刻，向网络设备发送呼叫对方的呼叫请求消息，或者，终端102与终端103的通话出现异常，连接断开，但是需要继续通话时，终端102与终端103可能在相差不大的时刻，向网络设备发送呼叫对方的呼叫请求消息。
S230，网络设备向终端102发送第二消息。
其中，第二消息用于终端102建立被叫呼叫，该建立被叫呼叫是指为被叫呼叫请求建立一个连接。
例如，网络设备根据终端103呼叫终端102的呼叫请求消息向终端102发送第二消息。该第二消息可以为Setup消息(建立消息)。上述步骤可以表示为ID_NAS_CC_SETUP，其中，SETUP可以表示终端103呼叫终端102的呼叫指示消息，其中，CC可以表示为呼叫控制(Call Control)。
S240，终端102根据接收到的第二消息确定第二消息与终端102呼叫发起状态不兼容，并存储第二消息。
其中，此时终端102处于主叫呼叫状态，接收到被叫呼叫时，确定主叫呼叫与被叫呼叫不兼容，然后存储第二消息。该不兼容状态可以为多种情况，可以包括：消息与协议状态不兼容和/或冲突、消息类型与协议状态不兼容和/或冲突以及第二消息与第一消息不兼容和/或冲突，包括但不限于这三种情况。具体可以理解为第二消息的消息类型与呼叫发起状态不兼容，或者是冲突。具体实现方案可以理解为终端收到建立被叫呼叫消息后根据当前状态是呼叫发起状态确定第二消息与终端当前状态不兼容或者冲突，也就是在呼叫发起状态下，终端收到第二消息后认为第二消息是冲突消息。
可选地，终端也可以在等待建立移动性管理(mobility management，MM)连接，处于MM Connection pending(U0.1)状态时，接收到第二消息，确定主叫呼叫与被叫呼叫冲突。
例如，终端为UE，该过程可以表示为UE NAS_CC，终端102处于主叫呼叫状态，收到被叫呼叫消息时，确定主叫呼叫消息与被叫呼叫消息为冲突消息，缓存SETUP消 息。
S250，终端102向网络设备发送第三消息。
其中，终端102向网络设备发送第三消息，该第三消息用于指示第二消息与终端的协议状态不兼容。第三消息可以为Status消息(状态消息)，第三消息中可以携带原因值。
例如，终端102向网络设备发送CC_STATUS消息，通知网络设备，第二消息与终端的协议状态不兼容。其中，Status消息可以表示为第三消息，如ID_NAS_CC_STATUS，该STATUS消息中可携带#98原因值Message type not compatible with protocol state，也可以携带#101原因值Message notcompatible with protocol state,该原因值用于指示上述第二消息的类型或者消息本身与终端的协议状态不兼容。
S260.网络设备根据第三消息确定第二消息与终端102的协议状态不兼容，保持终端103呼叫终端102的呼叫。
具体地，网络设备根据根据第三消息确定第二消息与终端102的协议状态不兼容，保持被叫呼叫状态。
S270.网络设备向终端102发送第五消息。
具体地，该第五消息用于拒绝建立主叫呼叫，第五消息可以表示为CM service reject(connect management连接管理层；CM service reject连接管理层服务拒绝消息)。
例如，上述步骤可以表示为ID_NAS_CM_SERV_REJECT，表示网络设备向终端102发送Service Reject消息。
S280.终端102根据接收网络设备发送的第五消息拒绝第一消息，释放主叫呼叫。
其中，终端102释放主叫呼叫的本质上释放的是主叫呼叫已经建立的MM连接(移动性管理，Mobile Management)。具体地，终端102根据网络设备发送的第五消息，释放终端102呼叫终端103的呼叫控制状态，进入终端103呼叫终端102的呼叫控制状态，此时终端102将呼叫控制状态从呼叫发起状态转换为MNCC-Setup IND状态，其中MNCC-Setup IND状态为移动网络呼叫控制建立适应性(Mobile Network Call Control Set Up Indication)。
例如，终端为UE，UE根据收到的网络设备发送的第五消息，释放主叫呼叫控制状态，关闭终端主叫呼叫控制状态机，UE开启新的被叫呼叫控制状态机，该新的被叫呼叫控制状态机起始于空值状态，终止于MNCC-Setup IND状态，具体地，终端102将呼叫控制状态从呼叫发起状态转换为MNCC-Setup IND状态可以直接转换，或者可以通过其他一些中间状态实现转换。具体实现方案包括以下方法：方法一：主被叫各一个CC实体，释放主叫后，主叫CC状态机由call initated转换到Null。同时开启被叫状态机，由Null转换为MNCC-Setup_IND状态。方法二：主被叫复用一个CC实体，由主叫的call initated(电话开始)状态转化为被叫MNCC-Setup_IND状态。具体可以为call initiated->null->MNCC-Setup_IND或者直接转换。包括但不限于上述两种方法。
S290.终端102向网络设备发送第四消息。
具体地，终端102向网络设备发送第四消息，该第四消息用于终端102确认被叫呼叫。其中，该第四消息可以为Call confirmed(通话确认)消息。
例如，上述可以表示，如ID_NAS_CC_CALL_CONFIRM，终端102向网络设备 发送call_confirm消息，call_confirm消息可以表示为通话确认的信息。
最后，网络设备根据该第四消息，建立终端103呼叫终端102的通话连接，即建立被叫呼叫连接。
图2B为本发明实施例提供的另一种呼叫建立的方法的交互示意图。图2B中所示的呼叫建立方法与图2A中所示的呼叫建立方法的S210-S240基本相同，在此不再详述。
图2B中所示的呼叫建立方法，在S240中，终端102接收到第二消息后不处理为协议异常(不兼容)，而是缓存第二消息。在缓存第二消息之后，终端102没有向网络设备发送第三消息，而是执行步骤S241.终端102启动定时器。
可选地，终端也可以在等待建立移动性管理连接，处于MM Connection pending(U0.1)状态时，接收到第二消息，此时，终端并不处理为协议异常，终端缓存第二消息，等待网络发送的接受主叫呼叫或者拒绝主叫呼叫的消息。
终端102启动的定时器可以为缓存定时器，该缓存定时器用于在一定时间内缓存第二消息，当缓存定时器超时时，终端丢弃缓存的第二消息。
虽然在图2B中示出，终端缓存第二消息之后启动定时器，可选的，终端也可以在缓存第二消息的同时启动定时器。缓存第二消息和启动定时器二者之间的时间间隔和二者的先后顺序，不构成对本发明实施例的限制。
终端102开启定时器后，在定时器未超时的情况下，等待网络设备发送的第五消息，根据网络设备发送的第五消息分别执行以下不同操作。
在第一种情况中，网络设备发送的第五消息用于拒绝建立主叫呼叫，第五消息可以表示为CM service reject(connect management连接管理层；CM service reject连接管理层服务拒绝消息)。例如，上述步骤可以表示为ID_NAS_CM_SERV_REJECT，表示网络设备向终端102发送Service Reject消息。相应的，在步骤S281中，终端102根据接收网络设备发送的第五消息拒绝第一消息，释放主叫呼叫。
在步骤S281之后，同样可以执行如图2A中所示的步骤S290，即终端释放主叫呼叫后，可以向网络设备发送第四消息，第四消息用于终端确认被叫呼叫。网络设备接收到第四消息后，建立终端103呼叫终端102的通话连接。
可选的，终端向网络设备发送第四消息之前，先判断是否存在表示呼叫终端102的呼叫指示消息，即终端首先读取缓存的第二消息。当终端成功读取第二消息时，对第二消息进行处理后，终端向网络设备发送第四消息，该第四消息用于终端102确认被叫呼叫。其中，该第四消息可以为Call confirmed(通话确认)消息。当终端未成功读取第二消息时，例如，由于缓存定时器超时，终端已丢弃缓存的第二消息时，终端不向网络设备发送第四消息。
在第二种情况中，网络设备发送的第五消息用于接受建立主叫呼叫，第五消息可以表示为CM service accept(connect management连接管理层；CM service accept连接管理层服务接受消息)。例如，上述步骤可以表示为ID_NAS_CM_SERV_ACCEPT，表示网络设备向终端102发送Service Accept消息。相应的，在步骤S281中，终端102根据网络设备发送的第五消息丢弃缓存的第二消息，继续建立主叫呼叫。在步骤S281之后，执行建立主叫呼叫连接的步骤。
图3为本发明实施例提供的另一种呼叫建立的方法的交互示意图。需要说明的是， 此方法适用于终端102向终端103发起主叫呼叫，在终端103没有接通的情况下，终端104向终端102发起主叫呼叫，其中，终端102与终端103之间的呼叫可以称为终端102的主叫呼叫，终端104与终端102之间的呼叫可以称为终端102的被叫呼叫。具体如图3所示，该方法具体包括：
S310，网络设备接收终端102发送的第一消息。
其中，该第一消息用于终端102请求建立主叫呼叫，该终端102进入呼叫发起状态。该主叫呼叫是指终端102请求建立一个与其他终端的通话连接；终端102的呼叫控制状态进入到呼叫发起状态，呼叫控制状态的起始状态可以为Null值(空值)状态，也可以为其他状态。
具体地，终端102在需要与终端103建立通信连接时，一般会向网络设备发送主叫呼叫请求消息，该主叫呼叫请求消息的呼叫对象为终端103，该主叫呼叫请求消息也可称为第一消息，该终端102进入主叫呼叫发起状态。
具体地，终端102向网络设备发送的第一消息可以为CM service request消息(connect management连接管理层；CM service request连接管理层服务请求消息)。例如，“ID_NAS_CM_SERV_REQUEST”，该请求消息携带终端103的标识，该请求消息用于请求网络设备发起对终端103的呼叫，其中，NAS表示为非接入层(Non-Acess Stratum)，SERV_REQUEST表示呼叫请求消息。
S320，网络设备接收终端104呼叫终端102的呼叫请求消息。
其中，该终端104呼叫终端102的呼叫请求可以称为终端102的被叫呼叫请求。
在终端102呼叫终端103时，终端103没有接通的情况下，网络设备接收到终端104发送的呼叫终端102的呼叫请求消息。
S330，网络设备向终端102发送第二消息。
其中，第二消息用于终端102建立被叫呼叫，该建立被叫呼叫是指为被叫呼叫请求建立一个连接。
例如，网络设备根据呼叫终端102的呼叫请求消息向终端102发送第二消息。该第二消息可以为Set up消息(建立消息)。上述步骤可以表示为ID_NAS_CC_SETUP，其中，SETUP可以表示呼叫终端102的呼叫指示消息，其中，CC可以表示为呼叫控制(Call Control)。
S340，终端102根据接收到的第二消息确定第二消息与终端102呼叫发起状态不兼容，并存储第二消息。
其中，此时终端102处于主叫呼叫状态，接收到被叫呼叫时，确定主叫呼叫与被叫呼叫不兼容，然后存储第二消息。该不兼容状态可以为多种情况，可以包括：消息与协议状态不兼容和/或冲突、消息类型与协议状态不兼容和/或冲突以及第二消息与第一消息不兼容和/或冲突，包括但不限于这三种情况。具体可以理解为第二消息的消息类型与呼叫发起状态不兼容，或者是冲突。具体实现方案可以理解为终端收到建立被叫呼叫消息后根据当前状态是呼叫发起状态确定第二消息与终端当前状态不兼容或者冲突，也就是在呼叫发起状态下，终端收到第二消息后认为第二消息是冲突消息。
例如，终端为UE，该过程可以表示为UE NAS_CC，终端102处于主叫呼叫状态，收到被叫呼叫消息时，确定主叫呼叫消息与被叫呼叫消息为冲突消息，缓存SETUP消 息。
S350，终端102向网络设备发送第三消息。
其中，终端102向网络设备发送第三消息，该第三消息用于指示第二消息与终端的协议状态不兼容。第三消息可以为Status消息(状态消息)，第三消息中可以携带原因值。
例如，终端102向网络设备发送CC_STATUS消息，通知网络设备，第二消息与终端的协议状态不兼容。其中，SETUS消息可以表示为第三消息，如ID_NAS_CC_STATUS，该STATUS消息中可携带#98原因值Message type not compatible with protocol state，也可以携带#101原因值Message notcompatible with protocol state,该原因值用于指示上述第二消息的消息类型或者消息本身与终端的协议状态不兼容。
S360.网络设备根据第三消息确定第二消息与终端102的协议状态不兼容，保持终端104呼叫终端102的呼叫。
具体地，网络设备根据根据第三消息确定第二消息与终端102的协议状态不兼容，保持被叫呼叫状态。
S370.网络设备向终端102发送第五消息。
具体地，该第五消息用于拒绝建立主叫呼叫，第五消息可以表示为CM service reject(connect management连接管理层；CM service reject连接管理层服务拒绝消息)。
例如，上述步骤可以表示为ID_NAS_CM_SERV_REJECT，表示网络设备向终端102发送Service Reject消息。
S380.终端102根据接收网络设备发送的第五消息拒绝第一消息，释放主叫呼叫。
其中，终端102释放主叫呼叫的本质上释放的是主叫呼叫已经建立的MM连接(移动性管理，Mobile Management)。具体地，终端102根据网络设备发送的第五消息，释放终端102呼叫终端103的呼叫控制状态，进入终端104呼叫终端102的呼叫控制状态，此时终端102将呼叫控制状态从呼叫发起状态转换为MNCC-Setup IND状态，其中MNCC-Setup IND状态为移动网络呼叫控制建立适应性(Mobile Network Call Control Set Up Indication)。
例如，终端为UE，UE根据收到的网络设备发送的第五消息，释放主叫呼叫控制状态，关闭终端主叫呼叫控制状态机，UE开启新的被叫呼叫控制状态机，该新的被叫呼叫控制状态机起始于空值状态，终止于MNCC-Setup IND状态，具体地，终端102将呼叫控制状态从呼叫发起状态转换为MNCC-Setup IND状态可以直接转换，或者可以通过其他一些中间状态实现转换。具体实现方案包括以下方法：方法一：主被叫各一个CC实体，释放主叫后，主叫CC状态机由call initated转换到Null。同时开启被叫状态机，由Null转换为MNCC-Setup_IND状态。方法二：主被叫复用一个CC实体，由主叫的call initated状态转化为被叫MNCC-Setup_IND状态。具体可以为call initiated->null->MNCC-Setup_IND或者直接转换。包括但不限于上述两种方法。
S390.终端102向网络设备发送第四消息。
具体地，终端102向网络设备发送第四消息，该第四消息用于终端102确认被叫呼叫。其中，该第四消息可以为Call confirmed(通话确认)消息。
例如，上述可以表示，如ID_NAS_CC_CALL_CONFIRM，终端102向网络设备 发送call_confirm消息，call_confirm消息可以表示为通话确认的信息。
最后，网络设备根据该第四消息，建立终端104呼叫终端102的通话连接，即建立被叫呼叫连接。
可选的，与如图2B所示的呼叫建立方法相对应，图3所示的呼叫建立方法在步骤S340之后，可以不执行步骤S350，即终端102同样没有向网络设备发送第三消息，而是缓存第二消息，等待接受网络设备发送的第五消息。缓存第二消息之后的操作，与图2B所示的呼叫建立方法相同，可以参照之前的描述，在此不再赘述。
图4为本发明实施例所涉及的一种终端的结构示意图。该终端包括发送器401，处理器402，接收器403。
收发器可以包括接收器403和发送器401，该接收器和发送器可以集成在一起。发送器调节(例如，模拟转换、滤波、放大和上变频等)该输出采样并生成上行链路信号，该上行链路信号经由天线发射给网络设备。在下行链路上，天线接收上述实施例中网络设备发射的下行链路信号。接收器调节(例如，滤波、放大、下变频以及数字化等)从天线接收的信号并提供输入采样。终端还可以包括调制解调处理器，在调制解调处理器中，接收要在上行链路上发送的业务数据和信令消息，并对业务数据和信令消息进行处理(例如，格式化、编码和交织)。进一步处理(例如，符号映射和调制)编码后的业务数据和信令消息并提供输出采样。处理(例如，解调)该输入采样并提供符号估计。处理(例如，解交织和解码)该符号估计并提供发送给UE的已解码的数据和信令消息。这些单元根据无线接入网采用的无线接入技术(例如，LTE及其他演进系统的接入技术)来进行处理。
处理器对终端的动作进行控制管理，用于执行上述实施例中由终端进行的处理。例如用于控制终端呼叫建立和/或本发明所描述的技术的其他过程。作为示例：
发送器401，用于向网络设备发送第一消息，第一消息用于终端请求建立主叫呼叫。
处理器402，用于控制进入呼叫发起状态。
接收器403，用于接收网络设备发送的第二消息，第二消息用于终端建立被叫呼叫。
发送器401还用于，向网络设备发送第三消息，第三消息用于指示第二消息与终端的协议状态不兼容。
在一个可选的实现方式中，发送器403还用于，向网络设备发送第四消息，第四消息用于终端确认所述被叫呼叫。
在一个可选的实现方式中，处理器402还用于，确定第二消息与呼叫发起状态不兼容。
在一个可选的实现方式中，处理器402还用于，缓存第二消息。
接收器403还用于，接收网络设备发送的第五消息，第五消息用于拒绝建立主叫呼叫或接受建立主叫呼叫。
在一个可选的实现方式中，处理器402还用于，根据第五消息释放主叫呼叫。
在一个可选的实现方式中，处理器402还用于，将呼叫控制状态从呼叫发起状态转换为MNCC-Setup_IND状态。
在一个可选的实现方式中，处理器402还用于，启动缓存定时器，并根据第五消息释放主叫呼叫或继续主叫呼叫。
在一个可选的实现方式中，处理器402还用于，读取缓存的第二消息。
在一个可选的实现方式中，当第五消息用于接受建立主叫呼叫时，处理器402还用于，丢弃缓存的第二消息。
此外，该终端还也可以包括该存储器，用于存储用于终端的程序代码和数据。
图5为本发明实施例中所涉及的一种网络设备的结构示意图。该网络设备500包括：发送器501、处理器502和接收器503。其中，处理器用于对网络设备的动作进行控制管理，执行各种功能来支持终端的通信服务。
具体地，发送器501，用于向网络设备发送第一消息，第一消息用于请求建立主叫呼叫；发送器501还用于，向终端发送第二消息，第二消息用于终端建立被叫呼叫。
接收器503，用于接收终端发送的第三消息，网络设备根据第三消息确定第二消息与终端的协议状态不兼容；接收器还用于，接收终端发送的第四消息。
处理器502，用于为终端建立所述被叫呼叫连接。
例如，处理器用于支持网络设备执行图4中的过程402，和/或用于本文所描述的技术的其他过程。该网络设备还包括存储器，用于存储用于网络设备的程序代码和数据。收发器503用于支持与其他网络实体的通信。收发器可以包括接收器和发送器，该接收器和发送器可以集成在一起。
用于执行本发明实施例上述终端或网络设备功能的处理器可以是可以是中央处理器(Central Processing Unit，CPU)，通用处理器，数字信号处理器(Digital Signal Processor，DSP)，专用集成电路(Application-Specific Integrated Circuit，ASIC)，现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。收发器可以是通信接口、收发电路等，其中，收发器是统称，可以包括一个或多个接口。
专业人员应该还可以进一步意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、计算机软件或者二者的结合来实现，为了清楚地说明硬件和软件的可互换性，在上述说明中已经按照功能一般性地描述了各示例的组成及步骤。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、 数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。
以上所述，仅为本发明较佳的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到的变化或替换，都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应该以权利要求的保护范围为准。

Claims (32)

  1. 一种呼叫建立的方法，其特征在于，包括：
    终端向网络设备发送第一消息，所述第一消息用于所述终端请求建立主叫呼叫，所述终端进入呼叫发起状态；
    所述终端接收所述网络设备发送的第二消息，所述第二消息用于所述终端建立被叫呼叫；
    所述终端向所述网络设备发送第三消息，所述第三消息用于指示所述第二消息与所述终端的协议状态不兼容；
    所述终端向所述网络设备发送第四消息，所述第四消息用于所述终端确认所述被叫呼叫。
  2. 根据权利要求1所述的方法，其特征在于，所述终端接收所述网络设备发送的第二消息之后，包括：
    所述终端确定所述第二消息与所述呼叫发起状态不兼容。
  3. 根据权利要求1或2所述的方法，其特征在于，所述终端接收所述网络设备发送的第二消息之后，还包括：
    所述终端缓存所述第二消息。
  4. 根据权利要求1所述的方法，其特征在于，所述终端向所述网络设备发送第三消息之后，包括：
    所述终端接收所述网络设备发送的第五消息，所述第五消息用于拒绝建立所述主叫呼叫；
    所述终端根据所述第五消息释放所述主叫呼叫。
  5. 根据权利要求1-4任意一项所述的方法，其特征在于，所述终端向所述网络设备发送第三消息之后，还包括：
    所述终端将呼叫控制状态从呼叫发起状态转换为移动网络呼叫控制建立适应性MNCC-Setup_IND状态。
  6. 一种呼叫建立的方法，其特征在于，包括：
    网络设备接收终端发送的第一消息，所述第一消息用于请求建立主叫呼叫；
    所述网络设备向所述终端发送第二消息，所述第二消息用于所述终端建立被叫呼叫；
    所述网络设备接收所述终端发送的第三消息，所述网络设备根据所述第三消息确定所述第二消息与所述终端的协议状态不兼容；
    所述网络设备接收所述终端发送的第四消息，所述网络设备为所述终端建立所述被叫呼叫连接。
  7. 根据权利要求1所述的方法，其特征在于，所述网络设备接收所述终端发送的第三消息之后，还包括：
    所述网络设备保持所述被叫呼叫。
  8. 根据权利要求6或7所述的方法，其特征在于，所述网络设备接收所述终端发送的第三消息之后，还包括：
    所述网络设备释放所述主叫呼叫。
  9. 根据权利要求6-8任意一项所述的方法，其特征在于，所述网络设备接收所述终 端发送的第三消息之后，还包括：
    所述网络设备向所述终端发送第五消息，所述第五消息用于拒绝所述第一消息。
  10. 一种终端，其特征在于，包括：
    发送器，用于向网络设备发送第一消息，所述第一消息用于所述终端请求建立主叫呼叫；
    处理器，用于控制所述终端进入呼叫发起状态；
    接收器，用于接收所述网络设备发送的第二消息，所述第二消息用于所述终端建立被叫呼叫；
    所述发送器还用于，向所述网络设备发送第三消息，所述第三消息用于指示所述第二消息与所述终端的协议状态不兼容；
    所述发送器还用于，向所述网络设备发送第四消息，所述第四消息用于所述终端确认所述被叫呼叫。
  11. 根据权利要求10所述的终端，其特征在于，所述处理器还用于，确定所述第二消息与所述呼叫发起状态不兼容。
  12. 根据权利要求10或11所述的终端，其特征在于，所述处理器还用于，缓存所述第二消息。
  13. 根据权利要求10所述的终端，其特征在于，所述接收器还用于，接收所述网络设备发送的第五消息，所述第五消息用于拒绝建立所述主叫呼叫；
    所述处理器还用于，根据所述第五消息释放所述主叫呼叫。
  14. 根据权利要求10或13所述的终端，其特征在于，所述处理器还用于，将呼叫控制状态从呼叫发起状态转换为MNCC-Setup_IND状态。
  15. 一种网络设备，其特征在于，包括：
    发送器，用于发送的第一消息，所述第一消息用于请求建立主叫呼叫；
    所述发送器还用于，向所述终端发送第二消息，所述第二消息用于所述终端建立被叫呼叫；
    接收器，用于接收所述终端发送的第三消息，所述网络设备根据所述第三消息确定所述第二消息与所述终端的协议状态不兼容；
    所述接收器还用于，接收所述终端发送的第四消息；
    处理器，用于为所述终端建立所述被叫呼叫连接。
  16. 根据权利要求15所述的网络设备，其特征在于，所述处理器还用于，保持所述被叫呼叫。
  17. 根据权利要求15或16所述的网络设备，其特征在于，所述处理器还用于，释放所述主叫呼叫。
  18. 根据权利要求15-17任意一项所述的网络设备，其特征在于，所述发送器还用于，向所述终端发送第五消息，所述第五消息用于拒绝所述第一消息。
  19. 一种呼叫建立的方法，其特征在于，包括：
    终端向网络设备发送第一消息，所述第一消息用于所述终端请求建立主叫呼叫；
    所述终端接收所述网络设备发送的第二消息，所述第二消息用于所述终端建立被叫呼叫；
    所述终端缓存所述第二消息；
    所述终端接收所述网络设备发送的第五消息，所述第五消息用于拒绝建立所述主叫呼叫或用于接受建立所述主叫呼叫；
    当所述第五消息用于拒绝建立所述主叫呼叫时，所述终端根据所述第五消息释放所述主叫呼叫；
    当所述第五消息用于接受建立所述主叫呼叫时，所述终端根据所述第五消息继续建立所述主叫呼叫。
  20. 根据权利要求19所述的方法，其特征在于，所述终端缓存所述第二消息，包括：
    所述终端缓存所述第二消息并启动定时器，当所述定时器超时时，所述终端丢弃所述第二消息。
  21. 根据权利要求19或20所述的方法，其特征在于，在所述终端根据所述第五消息释放所述主叫呼叫之后，包括：
    所述终端向所述网络设备发送第四消息，所述第四消息用于所述终端确认所述被叫呼叫。
  22. 根据权利要求21所述的方法，其特征在于，在所述终端向所述网络设备发送所述第四消息之前，包括：
    所述终端读取缓存的所述第二消息。
  23. 根据权利要求19-22任一所述的方法，其特征在于，所述终端缓存所述第二消息之后，包括：
    所述终端等待接收所述第五消息。
  24. 根据权利要求19-23任一所述的方法，其特征在于，当所述第五消息用于接受建立所述主叫呼叫时，所述终端丢弃缓存的所述第二消息。
  25. 一种终端，其特征在于，包括：
    发送器，用于向网络设备发送第一消息，所述第一消息用于所述终端请求建立主叫呼叫；
    处理器，用于控制所述终端进入呼叫发起状态；
    接收器，用于接收所述网络设备发送的第二消息，所述第二消息用于所述终端建立被叫呼叫；
    所述处理器还用于，缓存所述第二消息；
    所述接收器还用于，接收所述网络设备发送的第五消息，所述第五消息用于拒绝建立所述主叫呼叫或用于接受建立所述主叫呼叫；
    所述处理器还用于，当所述第五消息用于拒绝建立所述主叫呼叫时，根据所述第五消息释放所述主叫呼叫；当所述第五消息用于接受建立所述主叫呼叫时，根据所述第五消息继续所述主叫呼叫。
  26. 根据权利要求25所述的终端，其特征在于，所述处理器还用于启动定时器，当所述定时器超时时，所述处理器丢弃所述第二消息。
  27. 根据权利要求25或26所述的终端，其特征在于，
    所述发送器还用于，向所述网络设备发送第四消息，所述第四消息用于所述终端确认所述被叫呼叫。
  28. 根据权利要求25-27任一所述的终端，其特征在于，
    所述处理器还用于，读取缓存的所述第二消息。
  29. 根据权利要求25-28任一所述的终端，其特征在于，所述处理器还用于，确定所述第二消息与所述呼叫发起状态不兼容。
  30. 根据权利要求25-29任一所述的终端，其特征在于，当所述第五消息用于接受建立所述主叫呼叫时，所述处理器还用于，丢弃缓存的所述第二消息。
  31. 一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行如权利要求1-9、19-24任意一项所述的方法。
  32. 一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行如权利要求1-9、19-24任意一项所述的方法。
PCT/CN2017/088520 2017-02-22 2017-06-15 一种呼叫建立的方法及装置 WO2018152988A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
US16/487,253 US10959278B2 (en) 2017-02-22 2017-06-15 Call setup method and apparatus
JP2019565600A JP6803482B2 (ja) 2017-02-22 2017-06-15 呼設定方法及び装置
CN201780086680.5A CN110301124B (zh) 2017-02-22 2017-06-15 呼叫建立的方法、相关终端、网络设备和存储介质
EP17898066.0A EP3576364B1 (en) 2017-02-22 2017-06-15 Call setup method and apparatus

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201710096800.1 2017-02-22
CN201710096800 2017-02-22
CNPCT/CN2017/083291 2017-05-05
CN2017083291 2017-05-05

Publications (1)

Publication Number Publication Date
WO2018152988A1 true WO2018152988A1 (zh) 2018-08-30

Family

ID=63252328

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/088520 WO2018152988A1 (zh) 2017-02-22 2017-06-15 一种呼叫建立的方法及装置

Country Status (5)

Country Link
US (1) US10959278B2 (zh)
EP (1) EP3576364B1 (zh)
JP (1) JP6803482B2 (zh)
CN (1) CN110301124B (zh)
WO (1) WO2018152988A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101155389A (zh) * 2006-09-27 2008-04-02 大唐移动通信设备有限公司 处理呼叫冲突的方法及装置
CN102893691A (zh) * 2012-08-03 2013-01-23 华为技术有限公司 一种处理呼叫冲突的方法、系统和业务控制设备
CN105207973A (zh) * 2014-06-18 2015-12-30 北京信威通信技术股份有限公司 一种ims通信系统中用户同时呼叫对方时的互通方法
CN105338503A (zh) * 2015-12-07 2016-02-17 海能达通信股份有限公司 一种呼叫处理方法及装置

Family Cites Families (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH04154331A (ja) 1990-10-18 1992-05-27 Fujitsu Ltd Ｉｓｄｎ網発着信時の呼衝突防止方式
JPH05211553A (ja) 1992-01-31 1993-08-20 Nec Corp 再発呼ダイヤル番号記録方式
US6172977B1 (en) * 1994-05-05 2001-01-09 Sprint Communications Company, L. P. ATM direct access line system
US5655019A (en) * 1995-03-30 1997-08-05 Mckernan; Randolph W. Identity protection method for use with wireless telephone systems
US5870672A (en) * 1996-04-05 1999-02-09 Corsair Communications, Inc. Validation method and apparatus for preventing unauthorized use of cellular phones
US6870823B2 (en) * 1997-02-14 2005-03-22 Qualcomm Inc Method and apparatus for providing an alert with information signal between a mobile switching center and a base station
US6396820B1 (en) * 1997-06-24 2002-05-28 Lucent Technologies Inc. Wireless telecommunications system for improving performance and compatibility
US6826718B1 (en) * 1999-07-15 2004-11-30 Sbc Holdings Properties, L.P. Method and apparatus for tracking call processing failure data in a radiotelephone system
KR100414071B1 (ko) 2001-09-28 2004-01-07 엘지전자 주식회사 이동통신 시스템의 패킷 호 처리방법
US7248565B1 (en) * 2002-05-16 2007-07-24 Cisco Technology, Inc. Arrangement for managing multiple gateway trunk groups for voice over IP networks
US7236791B2 (en) * 2005-06-30 2007-06-26 Lucent Technologies Inc. Radio channel allocation for national security and emergency preparedness calls
US8116250B2 (en) * 2006-07-07 2012-02-14 Telefonaktiebolaget L M Ericsson (Publ) Medium access control discard notification
US7684364B2 (en) * 2006-11-14 2010-03-23 Cisco Technology, Inc. System and method for providing a virtual line channel in a packet based communication network
US8755502B1 (en) * 2007-02-07 2014-06-17 Sprint Spectrum L.P. Call contention mediation after dropped call
US8233607B1 (en) * 2007-07-30 2012-07-31 At&T Mobility Ii Llc Easy call abandon
EP2416548A4 (en) 2009-03-31 2017-06-14 Alcatel Lucent Method and corresponding device for processing calling conflict in communication network
US8537976B2 (en) * 2010-02-09 2013-09-17 International Business Machines Corporation System and method for handling telephone interruptions
US8626849B2 (en) * 2010-04-27 2014-01-07 Blackberry Limited Apparatus and method for resolving a race condition between two session initiation protocol (SIP) end points
JP5342506B2 (ja) * 2010-06-01 2013-11-13 日本電信電話株式会社 発呼衝突回避装置、発呼衝突回避方法及び発呼衝突回避プログラム
US8958543B1 (en) * 2011-06-29 2015-02-17 Cellco Partnership Use of inbound call as mechanism to trigger outbound calls to avoid collisions
US20140066118A1 (en) * 2012-08-31 2014-03-06 Motorola Solutions, Inc. Systems and methods for sending floor requests in parallel with traffic channel setup in wireless networks
US9210060B2 (en) * 2013-03-15 2015-12-08 Hewlett-Packard Development Company, L.P. Flow control transmission
CN103957330A (zh) 2014-04-03 2014-07-30 小米科技有限责任公司 处理呼叫占线的方法、装置和系统
US9544336B2 (en) * 2014-06-04 2017-01-10 Avaya Inc. Mechanisms for handling SIP glare across multiple dialogs
CN105554811A (zh) * 2015-12-04 2016-05-04 小米科技有限责任公司 通话处理方法及装置
US11108833B2 (en) * 2016-06-06 2021-08-31 Blackberry Limited Crossed-invite call handling

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101155389A (zh) * 2006-09-27 2008-04-02 大唐移动通信设备有限公司 处理呼叫冲突的方法及装置
CN102893691A (zh) * 2012-08-03 2013-01-23 华为技术有限公司 一种处理呼叫冲突的方法、系统和业务控制设备
CN105207973A (zh) * 2014-06-18 2015-12-30 北京信威通信技术股份有限公司 一种ims通信系统中用户同时呼叫对方时的互通方法
CN105338503A (zh) * 2015-12-07 2016-02-17 海能达通信股份有限公司 一种呼叫处理方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3576364A4

Also Published As

Publication number Publication date
US20190373664A1 (en) 2019-12-05
CN110301124B (zh) 2021-09-03
EP3576364A1 (en) 2019-12-04
CN110301124A (zh) 2019-10-01
US10959278B2 (en) 2021-03-23
EP3576364A4 (en) 2019-12-18
JP6803482B2 (ja) 2020-12-23
JP2020508626A (ja) 2020-03-19
EP3576364B1 (en) 2021-09-22

Similar Documents

Publication Publication Date Title
CN110582995B (zh) 用于无线通信中的会话释放的方法、电子装置及存储器
US10863390B2 (en) Method and apparatus for non-access stratum transport
RU2597209C2 (ru) Мобильное оконечное устройство связи и способ
JP4073870B2 (ja) 休止状態移動端末に対する着信データの管理方法および無線通信網内で使用するパケット制御機能装置
JP2014522165A (ja) マシンタイプ通信（ｍｔｃ）装置の低減されたモビリティを管理し、ｍｔｃ装置にダウンリンクデータを送信するための移動体通信ネットワーク、インフラ設備及び方法
JP2010536264A (ja) 無線通信システムにおけるハンドオーバー中の順序正しいデータ配信
JP2014522164A (ja) 通信端末及び方法
WO2014115711A1 (ja) ユーザ装置、ゲートウェイ装置、無線基地局、移動通信システム及び移動通信方法
WO2012025001A1 (zh) 一种优先业务的处理方法和系统
US8515485B2 (en) Provisioning of voice and other CS-domain services
WO2018141241A1 (zh) 设备切换方法及设备、承载配置方法及设备、通信系统
WO2020232576A1 (zh) 单播连接建立方法、装置及存储介质
CN104662936A (zh) 一种传输数据的方法、装置及系统
WO2018152988A1 (zh) 一种呼叫建立的方法及装置
JP6121672B2 (ja) 移動通信システムおよび移動通信方法
KR20230003141A (ko) 정보 지시 방법, 장치 및 통신 장치
EP2587883B1 (en) Method of handling service rejection for circuit switch service
EP3010261B1 (en) Method of message retransmission and user equipment using the same
WO2006079285A1 (fr) Procede et appareil destines a des utilisateurs engages dans un appel de groupe pour recevoir un message court
JP5197408B2 (ja) 通信制御方法
US8274982B2 (en) Method for packet data session release in ultra mobile broadband access network
JP4820323B2 (ja) 通信網選択システム
WO2019206248A1 (zh) 一种电路交换回退方法及装置
CN114208316A (zh) 用于下行数据的早期数据传输
KR101718104B1 (ko) 메시지 서비스 제공 방법, 메시지 서버 및 시스템

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17898066

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019565600

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2017898066

Country of ref document: EP

Effective date: 20190827