WO2024017238A1 - 呼叫协商的方法、装置、通信设备及可读存储介质 - Google Patents

呼叫协商的方法、装置、通信设备及可读存储介质 Download PDF

Info

Publication number
WO2024017238A1
WO2024017238A1 PCT/CN2023/107882 CN2023107882W WO2024017238A1 WO 2024017238 A1 WO2024017238 A1 WO 2024017238A1 CN 2023107882 W CN2023107882 W CN 2023107882W WO 2024017238 A1 WO2024017238 A1 WO 2024017238A1
Authority
WO
WIPO (PCT)
Prior art keywords
bearer
parameters
message
access layer
terminal
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.)
Ceased
Application number
PCT/CN2023/107882
Other languages
English (en)
French (fr)
Inventor
程思涵
吴晓波
崇卫微
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Vivo Mobile Communication Co Ltd
Original Assignee
Vivo Mobile Communication Co Ltd
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 Vivo Mobile Communication Co Ltd filed Critical Vivo Mobile Communication Co Ltd
Publication of WO2024017238A1 publication Critical patent/WO2024017238A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

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/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • 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

Definitions

  • the present application belongs to the field of communication technology, and specifically relates to a call negotiation method, device, communication equipment and readable storage medium.
  • GBR Guarantee Bit Rate
  • MBR Maximum Bit Rate
  • MNO mobile network operator
  • the GBR value used by MNO B is equal to 156kbps
  • the terminal of MNO C for example, User Equipment (UE)
  • MNO A the terminal will initiate the Internet Protocol Multimedia Subsystem (IMS) based on the stored configuration of MNO C.
  • Session request and establishment of a voice bearer or video call bearer with a GBR of 512kbps.
  • Session Initiation Protocol Session Initiation Protocol, SIP
  • invite invitation
  • SDP Session Description Protocol
  • MNO A When MNO A establishes a voice bearer or video call bearer based on the negotiation result of the IMS layer, since MNO A only supports the establishment of a 64kbps voice bearer, the network side will reject the voice bearer establishment request or video call bearer, resulting in a voice bearer or video call bearer. The bearer establishment failed, causing users to be unable to use voice services or video call services in roaming areas.
  • Embodiments of the present application provide a call negotiation method, device, communication equipment, and readable storage medium to solve the problem of how to successfully establish a bearer for communicating parties.
  • the first aspect is to provide a call negotiation method, including:
  • the terminal receives a first message, the first message being used to establish a first bearer
  • the terminal sends a second message, and the second message is used to request IMS session renegotiation, so that the The IMS session parameters match the parameters of the first bearer.
  • a call negotiation device applied to terminals, including:
  • a first receiving module configured to receive a first message, where the first message is used to establish a first bearer
  • An acquisition module configured to acquire parameters of the first bearer according to the first message
  • a first sending module configured to send a second message when the parameters of the first bearer do not match the MS session parameters of the terminal, where the second message is used to request IMS session renegotiation, so that The IMS session parameters match the parameters of the first bearer.
  • a communication device including: a processor, a memory, and a program or instruction stored on the memory and executable on the processor.
  • a program or instruction stored on the memory and executable on the processor.
  • a readable storage medium is provided. Programs or instructions are stored on the readable storage medium. When the programs or instructions are executed by a processor, the steps of the method described in the first aspect are implemented.
  • a chip in a fifth aspect, includes a processor and a communication interface.
  • the communication interface is coupled to the processor.
  • the processor is used to run programs or instructions to implement the method described in the first aspect. A step of.
  • a sixth aspect provides a computer program/program product, the computer program/program product is stored in a non-transitory storage medium, and the program/program product is executed by at least one processor to implement the first aspect steps of the method.
  • a seventh aspect provides a communication system.
  • the communication system includes a terminal and a network side device.
  • the terminal is configured to perform the steps of the method described in the first aspect.
  • the terminal when the parameters of the first bearer do not match the IMS session parameters of the terminal, the terminal can initiate an IMS session renegotiation request to the communication peer, so that the parameters of the first bearer are consistent with the IMS session parameters. Matching enables the first bearer to be successfully established, allowing the communicating parties to successfully establish the first bearer (such as audio bearer or video bearer) communication, thereby improving user experience.
  • the first bearer such as audio bearer or video bearer
  • Figure 1 is a flow chart for establishing a voice bearer between UE-1 and UE-2;
  • Figure 2 is a schematic architectural diagram of a wireless communication system according to an embodiment of the present application.
  • Figure 3 is one of the flow charts of a call negotiation method provided by an embodiment of the present application.
  • Figure 4 is the second flow chart of a call negotiation method provided by an embodiment of the present application.
  • Figure 5 is one of the flow charts for establishing a voice bearer between UE-1 and UE-2 provided by the embodiment of the present application;
  • Figure 6 is a schematic diagram of the internal processing of UE-1 in the embodiment shown in Figure 5;
  • Figure 7 is the second flow chart of establishing a voice bearer between UE-1 and UE-2 provided by the embodiment of the present application;
  • Figure 8 is a schematic diagram of the internal processing of UE-1 in the embodiment shown in Figure 7;
  • Figure 9 is one of the schematic diagrams of a call negotiation device provided by an embodiment of the present application.
  • Figure 10 is a second schematic diagram of a call negotiation device provided by an embodiment of the present application.
  • Figure 11 is a schematic diagram of a terminal provided by an embodiment of the present application.
  • Figure 12 is a schematic diagram of a core network device provided by an embodiment of the present application.
  • Figure 13 is a schematic diagram of a communication device provided by an embodiment of the present application.
  • first, second, etc. in the description and claims of this application are used to distinguish similar objects and are not used to describe a specific order or sequence. It is to be understood that the terms so used are interchangeable under appropriate circumstances so that the embodiments of the present application can be practiced in sequences other than those illustrated or described herein, and that "first" and “second” are distinguished objects It is usually one type, and the number of objects is not limited.
  • the first object can be one or multiple.
  • “and/or” in the description and claims indicates at least one of the connected objects, and the character “/" generally indicates that the related objects are in an "or” relationship.
  • LTE Long Term Evolution
  • LTE-Advanced, LTE-A Long Term Evolution
  • LTE-A Long Term Evolution
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-carrier Frequency Division Multiple Access
  • NR New Radio
  • FIG. 1 the figure illustrates the process of establishing a voice bearer between UE-1 and UE-2.
  • the specific steps are as follows:
  • Step 1 UE-1 establishes a Protocol Data Unit (PDU) session in the roaming network (for example, MNO A) and uses the roaming session management function (Visiting Session Management Function, V-SMF).
  • PDU Protocol Data Unit
  • MNO A Mobility Management Function
  • V-SMF Visit Management Function
  • Invite invitation
  • Step 3 The Proxy-Call Session Control Function (P-CSCF) sends the invite message to UE-2 through (Serving Call Session Control Function, S-CSCF).
  • P-CSCF Proxy-Call Session Control Function
  • P-CSCF and S-CSCF in the figure are both IMS network elements that provide services for UE-1, but the IMS network element that provides services for UE-2 is not reflected.
  • Step 4 UE-2 replies to the SIP 183 message through S-CSCF, which contains the SDP answer (answer).
  • Step 5 P-CSCF sends a HyperText Transfer Protocol (HTTP) notification (POST) request message to the Policy Control Function (PCF) that provides services for UE-1.
  • HTTP HyperText Transfer Protocol
  • PCF Policy Control Function
  • the message carries SDP negotiated media description information (media info).
  • the media description information is obtained based on the SDP response message and contains information that requires the use of 512kbps.
  • Step 6 PCF sends a request to the home SMF (Home-Session Management Function, H-SMF) of UE-1. Please establish a voice bearer.
  • the request carries the Quality of Service (QoS) of the voice bearer to be established.
  • QoS Quality of Service
  • Step 7 H-SMF sends a PDU session update request message (for example, Nsmf_PDUSession_Update Request message) to V-SMF, which may contain QoS parameters.
  • a PDU session update request message for example, Nsmf_PDUSession_Update Request message
  • Step 8 Based on the requested QoS parameters and the QoS parameters it can support, V-SMF determines that it cannot support the 512kbps GBR bearer, and V-SMF sends a PDU session update rejection message (for example, Nsmf_PDUSession_Reject message) to H-SMF.
  • a PDU session update rejection message for example, Nsmf_PDUSession_Reject message
  • Step 9 H-SMF sends a rejection message to PCF, that is, H-SMF initiated SM policy association reject (H-SMF initiated SM policy association reject).
  • Step 10 PCF sends a reject message to P-CSCF.
  • Step 11 P-CSCF sends a Bye message to UE-1 to reject this call.
  • Step 12 P-CSCF sends a Bye message to UE-2 to terminate this call.
  • FIG. 2 shows a block diagram of a wireless communication system to which embodiments of the present application are applicable.
  • the wireless communication system includes a terminal 21 and a network side device 22.
  • the terminal 21 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a palmtop computer, a netbook, or a super mobile personal computer.
  • Tablet Personal Computer Tablet Personal Computer
  • laptop computer laptop computer
  • PDA Personal Digital Assistant
  • palmtop computer a netbook
  • super mobile personal computer a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a palmtop computer, a netbook, or a super mobile personal computer.
  • PDA Personal Digital Assistant
  • the terminal involved in this application may also be a chip within the terminal, such as a modem chip or a system on chip (SoC).
  • SoC system on chip
  • the network side equipment 22 may include access network equipment or core network equipment, where the access network equipment may also be called wireless access network equipment, radio access network (Radio Access Network, RAN), radio access network function or wireless access network unit.
  • Access network equipment can include base stations, Wireless Local Area Network (WLAN) access points or Wireless Fidelity (WiFi) nodes, etc.
  • the base station can be called Node B, Evolved Node B (Evolved Node B).
  • the base station is not limited to specific technical terms. It needs to be explained that , in the embodiment of this application, only the base station in the NR system is taken as an example for introduction, and the specific type of the base station is not limited.
  • Core network equipment may include but is not limited to at least one of the following: core network nodes, core network functions, mobility management entities (Mobility Management Entity, MME), access mobility management functions (Access and Mobility Management Function, AMF), session management functions (Session Management Function, SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Services Discovery function (Edge Application Server Discovery Function, EASDF), unified data management (Unified Data Management, UDM), unified data warehousing (Unified Data Repository, UDR), home subscriber server (Home Subscriber Server, HSS), centralized network configuration ( Centralized network configuration, CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (Local NEF, or L-NEF), Binding Support Function (Binding Support Function, BSF), application function (Application Function, AF), etc.
  • MME mobility management entities
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • an embodiment of the present application provides a call negotiation method, which is applied to a terminal. Specific steps include: step 301, step 302 and step 303.
  • Step 301 The terminal receives the first message, which is used to establish the first bearer;
  • the first bearer includes at least one of an audio bearer and a video bearer, where the audio bearer can also be described as a voice bearer, and the first message can also be described as a voice establishment request message.
  • the terminal receives the first message sent by the first core network device.
  • the first core network device may be a 4G core network device or a 5G core network device, such as MME or V-SMF. Of course, it is not Not limited to this.
  • the first bearer is an Evolved Packet System (EPS) bearer
  • the first message may be a session management request (Session Management Request) message
  • the first bearer may be a Quality of Service (QoS) flow
  • the first message may be a PDU session modification command (PDU session modification). command).
  • QoS Quality of Service
  • the first message carries parameters of the first bearer modified by the first core network device.
  • the first core network device may modify the first bearer according to the parameters of the bearer supported by the first core network device. The parameters carried are modified.
  • the terminal receives a first message sent from an access network device (such as a base station).
  • the first message may be a Radio Resource Configuration Connection Reconfiguration (Radio Resource Configuration Connection Reconfiguration) message or a Radio Resource Configuration Reconfiguration message.
  • Configuration Radio Resource Configuration Reconfiguration
  • Step 302 Obtain parameters of the first bearer according to the first message
  • the parameters of the first bearer may include: at least one of a guaranteed bit rate (Guaranteed Bit Rate, GBR) and a maximum bit rate (Maximum Bit Rate, MBR).
  • GBR refers to the minimum bit rate that needs to be guaranteed in order to support the service.
  • MBR refers to the maximum bit rate that can be guaranteed to support the service.
  • the parameters of the first bearer may also be described as QoS parameters of the first bearer.
  • Step 303 When the parameters of the first bearer do not match the IMS session parameters of the terminal, the terminal sends a second message, where the second message is used to request IMS session renegotiation, so that the The IMS session parameters match the parameters of the first bearer.
  • the second message may also be described as an IMS session renegotiation request message or an IMS session modification request message.
  • the IMS session renegotiation request may be a re-invite message
  • the IMS session modification request may be an update message.
  • Both the re-Invite message and the Update message are Session Initialization Protocol (Session initialization Protocol, SIP) messages.
  • the terminal when the parameters of the first bearer do not match the IMS session parameters of the terminal, the terminal (for example, UE-1) can initiate an IMS session resumption to the communication counterpart (for example, UE-2).
  • the communication counterpart for example, UE-2
  • the terminal can initiate an IMS session resumption to the communication counterpart (for example, UE-2).
  • the terminal when the parameters of the first bearer do not match the IMS session parameters of the terminal, the terminal sends a second message, including:
  • the IMS layer of the terminal determines whether the parameters of the first bearer match the IMS session parameters of the terminal;
  • the terminal sends a second message according to the parameters of the first bearer.
  • the second message carries IMS session parameters corresponding to the parameters of the first bearer.
  • the IMS layer involved in this application can also be understood as the IMS protocol layer.
  • the terminal receiving the first message includes: the non-access stratum (Non-Access-Stratum, NAS) of the terminal receiving the first message;
  • NAS non-access-Stratum
  • obtaining the parameters of the first bearer according to the first message includes:
  • the non-access layer of the terminal obtains the parameters of the first bearer according to the first message; the non-access layer of the terminal The layer delivers the parameters of the first bearer to the IMS layer.
  • the terminal receiving the first message includes: the access layer (Access Stratum, AS) of the terminal receiving the first message;
  • obtaining the parameters of the first bearer according to the first message includes:
  • the access layer of the terminal obtains the access layer parameters corresponding to the first bearer according to the first message; the access layer of the terminal delivers the access layer parameters corresponding to the first bearer to the IMS layer; The IMS layer of the terminal obtains the parameters of the first bearer according to the access layer parameters corresponding to the first bearer.
  • the terminal receiving the first message includes: the access layer of the terminal receiving the first message;
  • obtaining the parameters of the first bearer according to the first message includes:
  • the access layer of the terminal obtains the access layer parameters corresponding to the first bearer according to the first message; the access layer of the terminal delivers the access layer parameters corresponding to the first bearer to the non-access layer; the non-access layer of the terminal determines the non-access layer parameters corresponding to the first bearer according to the access layer parameters corresponding to the first bearer; the non-access layer of the terminal determines the non-access layer parameters of the first bearer
  • the corresponding non-access layer parameters are delivered to the IMS layer; the IMS layer of the terminal obtains the parameters of the first bearer according to the non-access layer parameters corresponding to the first bearer.
  • the IMS layer of the terminal determines whether the parameters of the first bearer match the IMS session parameters of the terminal, including:
  • the IMS layer of the terminal determines whether the absolute value of the difference between the parameter of the first bearer and the IMS session parameter of the terminal is greater than a preset value
  • the terminal when the parameters of the first bearer do not match the IMS session parameters of the terminal, the terminal can initiate an IMS session renegotiation request to the communication peer, so that the parameters of the first bearer are consistent with the IMS session parameters. Matching enables the first bearer to be successfully established, allowing the communicating parties to successfully establish the first bearer communication and improving user experience.
  • an embodiment of the present application provides a call negotiation method, which is applied to a first core network device.
  • the first core network device may be a 4G core network device or a 5G core network device, such as MME or V-SMF. Specific steps include: step 401, step 402, step 403 and step 404.
  • Step 401 The first core network device receives a third message, where the third message is used to request the establishment of a first bearer for the terminal;
  • the first core network device receives the third message from the second core network device.
  • the second core network device may include an H-SMF or a Packet Data Network Gateway (Packet Data Network Gateway, PGW). Of course, it is not limited to this.
  • the third message may be called a PDU session update request message, and the message may carry the parameters of the first bearer. number.
  • Step 402 The first core network device determines whether the parameters of the first bearer included in the third message match the bearer parameters supported by the first core network device;
  • the first core network determines whether the absolute value of the difference between the first bearer parameter and the bearer parameter supported by the first core network device is greater than a preset value
  • Step 403 In the case of mismatch, the first core network device modifies the parameters of the first bearer according to the parameters of the bearer supported by the first core network device;
  • the first core network device compares the parameters of the first bearer according to the parameters of the bearer supported by the first core network device, so that the modified parameters of the first bearer are consistent with the parameters supported by the first core network device.
  • the bearer parameters match, for example, the absolute value of the difference between the modified first bearer parameters and the bearer parameters supported by the first core network device is less than a preset value.
  • Step 404 The first core network device sends a first message, the first message is used to establish the first bearer, and the first message carries modified parameters of the first bearer.
  • the first core network device sends a first message to the terminal, so that the terminal determines whether the parameters of the first bearer match the IMS session parameters of the terminal, and whether the parameters of the first bearer match the IMS session parameters of the terminal.
  • the terminal may send a second message to the communication counterpart, where the second message is used to request IMS session renegotiation so that the IMS session parameters match the parameters of the first bearer.
  • the first bearer may include at least one of an audio bearer and a video bearer.
  • the parameters of the first bearer may include: at least one of a guaranteed bit rate and a maximum bit rate.
  • the first core network device may modify the parameters of the first bearer based on the parameters of the bearer it supports. Modify and establish the first bearer according to the modified parameters of the first bearer, which can prevent the first core network device from directly rejecting the first bearer establishment request due to a mismatch between the parameters of the first bearer and the bearer parameters supported by the first core network device.
  • the problem can allow the communicating parties to successfully establish the first bearer communication and improve the user experience.
  • Step 1 UE-1 establishes a PDU session in the roaming network and uses the roaming session management function (Visiting-Session Management Function, V-SMF).
  • V-SMF Visit-Session Management Function
  • Step 2 UE-1 initiates an IMS establishment request through an invitation (Invite) message.
  • the requested session description protocol Session Description Protocol, SDP
  • SDP Session Description Protocol
  • Step 3 P-CSCF sends the invitation message to UE-2 through S-CSCF.
  • P-CSCF and S-CSCF in the figure are both IMS network elements that provide services for UE-1, but the IMS network element that provides services for UE-2 is not reflected.
  • Step 4 UE-2 replies to the Session Initialization Protocol (SIP) 183 message through S-CSCF, which contains the SDP response.
  • SIP Session Initialization Protocol
  • Step 5 P-CSCF sends an HTTP POST request message to the PCF that provides services for UE-1.
  • the message carries the media description information negotiated through SDP.
  • the media description information is obtained based on the SDP response message, which includes the need to use 512kbps. Information.
  • Step 6 The PCF sends a request to the H-SMF of UE-1 to establish a voice bearer.
  • the request carries the QoS parameters of the first bearer to be established, which includes information that the GBR is 512kbps.
  • Step 7 H-SMF sends a PDU session update request message to V-SMF.
  • the message can contain QoS parameters.
  • Step 8 When V-SMF determines that the request is used to establish the first bearer, and the GBR or MBR parameters of the first bearer requested to be established do not match the GBR or MBR parameters it supports, V-SMF modifies the first message sent to the UE.
  • the GBR or MBR parameters in the PDU session modification command are the parameters of the bearer it supports.
  • V-SMF sends the modified GBR or MBR parameters of the first bearer to AMF through the Namf_Communication_N1N2MessageTransfer message. Modify The GBR or MBR parameters of the subsequent first bearer are the parameters of the bearer supported by V-SMF.
  • the above-mentioned first message may also be a non-access stratum (Non Access Stratum, NAS) message, or it may also be an access stratum (Access Stratum, AS) message.
  • Non Access Stratum NAS
  • Access Stratum AS
  • Step 9 AMF sends the modified GBR or MBR parameters to the base station (the next Generation Node B, gNB), and the message also contains the first message sent to UE-1.
  • the base station the next Generation Node B, gNB
  • Step 10 gNB forwards the first message sent to UE-1 to UE-1, and UE-1 replies with a confirmation message.
  • step 10 the NAS layer of UE-1 receives the first message, or the AS layer of UE-1 receives the first message.
  • the AS layer is used to configure the Data Radio Bearer (DRB) between the UE and gNB, and is used to transmit the data of UE-1 between UE-1 and gNB.
  • DRB Data Radio Bearer
  • Step 11 gNB sends a confirmation message to AMF.
  • Step 12 AMF sends confirmation message to V-SMF
  • Step 13 V-SMF sends a confirmation message to H-SMF, such as the Nsmf_PDUSession_UpdateSM Context message, which carries the modified GBR or MBR parameters of the first bearer.
  • Step 14 H-SMF sends a confirmation message to PCF, that is, H-SMF initiates SM policy association modification.
  • Step 15 PCF sends a confirmation message to P-CSCF, for example, 201 Created message.
  • Step 16 P-CSCF sends a 183 message to the UE.
  • the 183 message contains an SDP response message.
  • the reply message contains the IMS session parameters confirmed by the peer, such as bandwidth parameters.
  • Steps 17-18 The communication peer (UE-2) answers the call and sends a 200OK message to UE-1.
  • Step 19 The NAS layer of UE-1 receives the first message, for example, the PDU session modification command message.
  • the NAS layer of UE-1 sends the parameters of the first bearer to the IMS layer, such as GBR or MBR parameters.
  • the IMS of UE-1 The layer determines whether the parameters of the first bearer match the IMS session parameters. If they do not match, UE-1 initiates an IMS session renegotiation request (that is, UE-1 sends a second message), and the IMS session renegotiation request includes the first
  • the IMS session parameters corresponding to the bearer parameters are shown in Figure 6.
  • the parameters negotiated by the IMS layer are 512kbps, and the parameters obtained by the NAS layer are 64kbps.
  • the IMS layer uses 64kbps to renegotiate with UE-2, so that the communicating parties use 64kbps for communication.
  • the second message may be a SIP re-invite message or a SIP update message.
  • Step 19 can be sent before or after step 18. If it is sent before step 18, UE-1 will renegotiate through the SIP update message. If it is sent after step 18, it will be sent through the SIP re-Invite message.
  • the GBR or MBR parameter in the first bearer parameter may be inconsistent with "b: AS parameter" of the IMS layer.
  • "b: AS parameter” is used to describe the rate used by the Real-time Transport Protocol (RTP) of voice media.
  • the GBR or MBR parameters can be the RTP and Real-time Transmission Control Protocol (Real-time Transmission Control Protocol) that describe the voice media.
  • the sum of the rates used by time Transport Control Protocol (RTCP), where the rate used by RTCP can be a fixed value.
  • the IMS layer of UE-1 determines whether the parameters of the first bearer match the IMS session parameters, including:
  • the IMS layer determines that the absolute value of the difference between the parameters of the first bearer and the IMS session parameters is greater than the preset value, it determines that there is a mismatch; the IMS layer determines that the absolute value of the difference between the parameters of the first bearer and the IMS session parameters is less than the preset value. When, it is judged to be a match.
  • Step 20 UE-1 sends a second message, which contains the IMS parameters corresponding to the parameters of the first bearer.
  • Step 21 Send the second message to UE-2.
  • Step 22-23 UE-2 replies with a 200OK message, carrying the result of IMS session renegotiation.
  • the UE-1 may initiate an IMS session re-negotiation request to UE-2, thereby changing the parameters of the first bearer. Matching the IMS session parameters allows the first bearer to be successfully established, allowing UE-1 and UE-2 to successfully establish audio or video communication, thereby improving user experience.
  • Steps 1-7 Please refer to the description of steps 1-7 in Figure 5.
  • Step 8 When the V-SMF determines that the request is used to establish the first bearer, and the GBR or MBR parameters of the first bearer requested to be established do not match the GBR or MBR parameters of the bearer it supports, the V-SMF modifies the first bearer sent to the gNB.
  • the GBR or MBR parameters of a bearer are the parameters of the bearer it supports.
  • the V-SMF sends the first message, and the first message carries GBR or MBR parameters with modified first bearer.
  • V-SMF does not send the modified parameters of the first bearer to the NAS layer of UE-1.
  • Step 9 The AMF sends the modified parameters of the first bearer to the gNB, and the message also contains the first message sent to the UE.
  • Step 10 gNB forwards the first message sent to UE-1 to UE-1, and UE-1 replies with a confirmation message.
  • Steps 11-18 Please refer to the description of steps 11-18 in Figure 5.
  • Step 19 The AS layer of UE-1 receives the first message to establish the first bearer, for example, the RRC reconfiguration message.
  • the first message contains the AS layer parameters corresponding to the first bearer, for example, the prioritized bit rate (prioritisedBitRate). ;
  • the AS layer of UE-1 sends AS layer parameters to the IMS layer, and the IMS layer determines whether the parameters of the first bearer match the IMS session parameters based on the AS layer parameters; or,
  • the AS layer of UE-1 sends the AS layer parameters to the NAS layer.
  • the NAS obtains the GBR or MBR parameters based on the AS layer parameters.
  • the NAS layer sends the NAS layer parameters to the IMS layer.
  • the IMS layer determines the parameters of the first bearer and the IMS based on the NAS layer parameters. Whether the session parameters match.
  • the IMS layer determines that the parameters of the first bearer do not match the IMS session parameters, UE-1 initiates an IMS session re-negotiation request, and the session re-negotiation request includes the IMS session parameters corresponding to the parameters of the voice bearer.
  • Step 20 UE-1 sends a second message, which contains the IMS session parameters corresponding to the parameters of the first bearer.
  • Step 21 Send the second message to UE-2.
  • Step 22-23 UE-2 replies 200 OK, carrying the result of IMS session renegotiation.
  • the UE-1 may initiate an IMS session re-negotiation request to UE-2, thereby changing the parameters of the first bearer. Matching the IMS session parameters allows the first bearer to be successfully established, allowing UE-1 and UE-2 to successfully establish audio or video communication, thereby improving user experience.
  • an embodiment of the present application provides a call negotiation device, which is applied to a terminal.
  • the device 900 includes:
  • the first receiving module 901 is configured to receive a first message, where the first message is used to establish a first bearer;
  • Obtaining module 902 configured to obtain parameters of the first bearer according to the first message
  • the first sending module 903 is configured to send a second message when the parameters of the first bearer do not match the IMS session parameters of the terminal.
  • the second message is used to request IMS session renegotiation.
  • the IMS session parameters are matched with the parameters of the first bearer.
  • the first sending module 903 is further configured to: determine whether the parameters of the first bearer match the IMS session parameters of the terminal through the IMS layer; in the case of mismatch, send Send the second message using the parameters of the first bearer.
  • the first receiving module 901 is further configured to: receive the first message through the non-access layer;
  • the obtaining module 902 is further configured to: obtain the parameters of the first bearer according to the first message through the non-access layer; and deliver the parameters of the first bearer to the IMS layer through the non-access layer.
  • the first receiving module 901 is further configured to: receive the first message through the access layer;
  • the acquisition module 902 is further configured to: obtain the access layer parameters corresponding to the first bearer through the access layer according to the first message; and deliver the access layer parameters corresponding to the first bearer to the IMS layer through the access layer. ; Obtain the parameters of the first bearer through the IMS layer according to the access layer parameters corresponding to the first bearer.
  • the first receiving module 901 is further configured to: receive the first message through the access layer;
  • the acquisition module 902 is further configured to: obtain the access layer parameters corresponding to the first bearer through the access layer according to the first message; and deliver the access layer parameters corresponding to the first bearer to the non-connected access layer through the access layer. Enter the layer; determine the non-access layer parameters corresponding to the first bearer according to the access layer parameters corresponding to the first bearer through the non-access layer; use the non-access layer to determine the non-access layer parameters corresponding to the first bearer.
  • the layer parameters are delivered to the IMS layer; the parameters of the first bearer are obtained through the IMS layer according to the non-access layer parameters corresponding to the first bearer.
  • the first sending module 903 is further configured to: determine through the IMS layer whether the absolute value of the difference between the parameters of the first bearer and the IMS session parameters of the terminal is greater than a preset value; When the absolute value of the difference between the parameters of the first bearer and the IMS session parameter is greater than or equal to the preset value, it is determined that there is no match; or, when the parameter of the first bearer and the IMS session parameter When the absolute value of the difference is less than the preset value, a match is determined.
  • the first receiving module 901 is further configured to: receive a first message sent by the first core network device, where the first message is a session management request message or a protocol data unit session modification command.
  • the first receiving module 901 is further configured to: receive a first message sent by the access network device, where the first message is a wireless resource configuration connection reconfiguration or a wireless resource configuration reconfiguration message. .
  • the first bearer includes at least one of an audio bearer and a video bearer.
  • the second message carries IMS session parameters corresponding to parameters of the first bearer.
  • the parameters of the first bearer include: at least one of a guaranteed bit rate and a maximum bit rate.
  • the device provided by the embodiment of the present application can implement each process implemented by the method embodiment in Figure 3 and achieve the same technical effect. To avoid duplication, the details will not be described here.
  • an embodiment of the present application provides a call negotiation device, which is applied to the first core network equipment.
  • the device 1000 includes:
  • the second receiving module 1001 is used to receive a third message, where the third message is used to request the establishment of a first bearer for the terminal;
  • Determination module 1002 used to determine whether the parameters of the first bearer included in the third message are consistent with the first core Whether the bearer parameters supported by the heart network equipment match;
  • Modification module 1003 configured to modify the parameters of the first bearer according to the parameters of the bearer supported by the first core network device in the case of mismatch;
  • the second sending module 1004 is configured to send a first message to the terminal, where the first message carries modified parameters of the first bearer.
  • the parameters of the first bearer include: at least one of a guaranteed bit rate and a maximum bit rate.
  • the first core network device includes: a mobility management entity or a roaming session management function.
  • the device provided by the embodiment of the present application can implement each process implemented by the method embodiment in Figure 4 and achieve the same technical effect. To avoid duplication, the details will not be described here.
  • FIG 11 is a schematic diagram of the hardware structure of a terminal that implements an embodiment of the present application.
  • the terminal 1100 includes but is not limited to: a radio frequency unit 1101, a network module 1102, an audio output unit 1103, an input unit 1104, a sensor 1105, a display unit 1106, a user input unit 1107, an interface unit 1108, a memory 1109, a processor 1110, etc. At least some parts.
  • the terminal 1100 may also include a power supply (such as a battery) that supplies power to various components.
  • the power supply may be logically connected to the processor 1110 through a power management system, thereby managing charging, discharging, and power consumption through the power management system. Management and other functions.
  • the terminal structure shown in FIG. 11 does not constitute a limitation on the terminal.
  • the terminal may include more or fewer components than shown in the figure, or some components may be combined or arranged differently, which will not be described again here.
  • the input unit 1104 may include a graphics processing unit (Graphics Processing Unit, GPU) 11041 and a microphone 11042.
  • the graphics processor 11041 is responsible for the image capture device (GPU) in the video capture mode or the image capture mode. Process the image data of still pictures or videos obtained by cameras (such as cameras).
  • the display unit 1106 may include a display panel 11061, which may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like.
  • the user input unit 1107 includes at least one of a touch panel 11071 and other input devices 11072 .
  • Touch panel 11071 also called touch screen.
  • the touch panel 11071 may include two parts: a touch detection device and a touch controller.
  • Other input devices 11072 may include but are not limited to physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, and joysticks, which will not be described again here.
  • the radio frequency unit 1101 after receiving downlink data from the network side device, the radio frequency unit 1101 can transmit it to the processor 1110 for processing; in addition, the radio frequency unit 1101 can send uplink data to the network side device.
  • the radio frequency unit 1101 includes, but is not limited to, an antenna, amplifier, transceiver, coupler, low noise amplifier, duplexer, etc.
  • Memory 1109 may be used to store software programs or instructions as well as various data.
  • the memory 1109 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instructions required for at least one function (such as a sound playback function, Image playback function, etc.) etc.
  • memory 1109 may include volatile memory or nonvolatile memory, or memory 1109 may include volatile Both volatile and non-volatile memory.
  • the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electrically removable memory. Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • Volatile memory can be random access memory (Random Access Memory, RAM), static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDRSDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (Synch link DRAM) , SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DRRAM).
  • RAM Random Access Memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM Double Data Rate SDRAM
  • DDRSDRAM double data rate synchronous dynamic random access memory
  • Enhanced SDRAM, ESDRAM enhanced synchronous dynamic random access memory
  • Synch link DRAM synchronous link dynamic random access memory
  • SLDRAM direct memory bus
  • the processor 1110 may include one or more processing units; optionally, the processor 1110 integrates an application processor and a modem processor, where the application processor mainly handles operations related to the operating system, user interface, application programs, etc., Modem processors mainly process wireless communication signals, such as baseband processors. It can be understood that the above modem processor may not be integrated into the processor 1110.
  • the terminal provided by the embodiment of this application can implement each process implemented by the method embodiment in Figure 3 and achieve the same technical effect. To avoid duplication, details will not be described here.
  • Figure 12 is a structural diagram of a communication device applied in an embodiment of the present application.
  • the communication device 1200 includes: a processor 1201, a transceiver 1202, a memory 1203 and a bus interface.
  • the processor 1201 May be responsible for managing the bus architecture and general processing.
  • Memory 1203 may store data used by processor 1201 in performing operations.
  • the communication device 1200 further includes: a program stored in the memory 1203 and executable on the processor 1201. When the program is executed by the processor 1201, the steps in the method shown in FIG. 3 are implemented.
  • the bus architecture may include any number of interconnected buses and bridges, specifically linked together by various circuits of one or more processors represented by processor 1201 and memory represented by memory 1203.
  • the bus architecture can also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are all well known in the art and therefore will not be described further herein.
  • the bus interface provides the interface.
  • Transceiver 1202 may be a plurality of elements, including a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium.
  • this embodiment of the present application also provides a communication device 1300, which includes a processor 1301 and a memory 1302.
  • the memory 1302 stores programs or instructions that can be run on the processor 1301, such as , when the communication device 1300 is a terminal, when the program or instruction is executed by the processor 1301, each step of the method embodiment in Figure 3 is implemented.
  • the communication device 1300 is a core network device, when the program or instruction is executed by the processor 1301
  • Each step of the above-mentioned method embodiment in Figure 4 can be implemented and the same technical effect can be achieved. To avoid repetition, details will not be described here.
  • Embodiments of the present application also provide a readable storage medium, with programs or instructions stored on the readable storage medium.
  • the program or instructions are executed by a processor, the method in Figure 3 or Figure 4 and each process of the above embodiments are implemented. , and can reach The same technical effects are not repeated here to avoid repetition.
  • the processor is the processor in the terminal described in the above embodiment.
  • the readable storage medium includes computer readable storage media, such as computer read-only memory ROM, random access memory RAM, magnetic disk or optical disk, etc.
  • An embodiment of the present application further provides a chip.
  • the chip includes a processor and a communication interface.
  • the communication interface is coupled to the processor.
  • the processor is used to run programs or instructions to implement what is shown in Figure 3 or Figure 4 and each process of the above method embodiments, and can achieve the same technical effect. To avoid repetition, they will not be described again here.
  • chips mentioned in the embodiments of this application may also be called system-on-chip, system-on-a-chip, system-on-chip or system-on-chip, etc.
  • the embodiment of the present application further provides a computer program/program product, the computer program/program product is stored in a storage medium, and the computer program/program product is executed by at least one processor to implement what is shown in Figure 3 or Figure 4
  • the computer program/program product is executed by at least one processor to implement what is shown in Figure 3 or Figure 4
  • Each process of each of the above method embodiments is shown and can achieve the same technical effect. To avoid repetition, it will not be described again here.
  • An embodiment of the present application further provides a communication system.
  • the communication system includes a terminal and a network side device.
  • the terminal is used to perform various processes in Figure 3 and the above method embodiments.
  • the network side device is used to perform the following: The processes in Figure 4 and the above-mentioned method embodiments can achieve the same technical effect. To avoid repetition, they will not be described again here.
  • the methods of the above embodiments can be implemented by means of software plus the necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is better. implementation.
  • the technical solution of the present application can be embodied in the form of a computer software product that is essentially or contributes to the existing technology.
  • the computer software product is stored in a storage medium (such as ROM/RAM, disk , CD), including several instructions to cause a terminal (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in various embodiments of this application.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请公开了一种呼叫协商的方法、装置、通信设备及可读存储介质，属于通信技术领域，该方法包括：终端接收第一消息，所述第一消息用于建立第一承载；根据所述第一消息获取所述第一承载的参数；在所述第一承载的参数与所述终端的IMS会话参数不匹配的情况下，所述终端发送第二消息，所述第二消息用于请求进行IMS会话重协商，以使得所述IMS会话参数与所述第一承载的参数匹配。

Description

呼叫协商的方法、装置、通信设备及可读存储介质
相关申请的交叉引用
本申请主张在2022年07月22日在中国提交的中国专利申请No.202210869240.X的优先权，其全部内容通过引用包含于此。
技术领域
本申请属于通信技术领域，具体涉及一种呼叫协商的方法、装置、通信设备及可读存储介质。
背景技术
不同的运营商对于语音的支持情况不一样，例如，运营商A、B、C支持的语音的保证比特速率(Guaranteed Bit Rate，GBR)或最大比特速率(Maximum Bit Rate，MBR)分别为64kbps，156kbps，512kbps：
·移动网络运营商(mobile network operator，MNO)A使用的GBR的值等于64kbps；
·MNO B使用的GBR的值等于156kbps；
·MNO C使用的GBR的值等于512kbps。
例如，MNO C的终端(比如，用户设备(User Equipment，UE))漫游到MNO A时，该终端会根据存储的MNO C的配置发起互联网协议多媒体系统(Internet Protocol(IP)Multimedia Subsystem，IMS)会话请求，以及建立GBR为512kbps的语音承载或视频通话承载。具体为，在会话初始化协议(Session Initiation Protocol，SIP)邀请(invite)消息中携带会话描述信息(Session Description Protocol，SDP)信息，在SDP信息中包含使用512kbps GBR参数的信息。
当MNO A根据IMS层的协商结果建立语音承载或视频通话承载时，由于MNO A仅支持64kbps的语音承载建立，会导致网络侧拒绝语音承载建立请求或视频通话承载，从而导致语音承载或视频通话承载建立失败，造成用户在漫游地无法使用语音业务或视频通话业务。
发明内容
本申请实施例提供一种呼叫协商的方法、装置、通信设备及可读存储介质，解决如何为通信双方成功建立承载的问题。
第一方面，提供一种呼叫协商的方法，包括：
终端接收第一消息，所述第一消息用于建立第一承载；
根据所述第一消息获取所述第一承载的参数；
在所述第一承载的参数与所述终端的IP多媒体系统IMS会话参数不匹配的情况下，所述终端发送第二消息，所述第二消息用于请求进行IMS会话重协商，以使得所述IMS会话参数与所述第一承载的参数匹配。
第二方面，提供一种呼叫协商的装置，应用于终端，包括：
第一接收模块，用于接收第一消息，所述第一消息用于建立第一承载；
获取模块，用于根据所述第一消息获取所述第一承载的参数；
第一发送模块，用于在所述第一承载的参数与所述终端的MS会话参数不匹配的情况下，发送第二消息，所述第二消息用于请求进行IMS会话重协商，以使得所述IMS会话参数与所述第一承载的参数匹配。
第三方面，提供了一种通信设备，包括：处理器，存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第一方面所述的方法的步骤。
第四方面，提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如第一方面所述的方法的步骤。
第五方面，提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如第一方面所述的法的步骤。
第六方面，提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在非瞬态的存储介质中，所述程序/程序产品被至少一个处理器执行以实现如第一方面所述的方法的步骤。
第七方面，提供一种通信系统，所述通信系统包括终端与网络侧设备，所述终端用于执行如第一方面所述的方法的步骤。
在本申请实施例中，在第一承载的参数与终端的IMS会话参数不匹配的情况下，该终端可以向通信对端发起IMS会话重协商请求，从而使第一承载的参数与IMS会话参数匹配，使得第一承载建立成功，可以让通信双方成功建立第一承载(比如音频承载或视频承载)通信，提升用户体验。
附图说明
图1是UE-1与UE-2建立语音承载的流程图；
图2为本申请实施例的无线通信系统的架构示意图；
图3是本申请实施例提供的一种呼叫协商的方法的流程图之一；
图4是本申请实施例提供的一种呼叫协商的方法的流程图之二；
图5是本申请实施例提供的UE-1与UE-2建立语音承载的流程图之一；
图6是图5所示的实施例中UE-1的内部处理的示意图；
图7是本申请实施例提供的UE-1与UE-2建立语音承载的流程图之二；
图8是图7所示的实施例中UE-1的内部处理的示意图；
图9是本申请实施例提供的一种呼叫协商的装置的示意图之一；
图10是本申请实施例提供的一种呼叫协商的装置的示意图之二；
图11是本申请实施例提供的一种终端的示意图；
图12是本申请实施例提供的一种核心网设备的示意图；
图13是本申请实施例提供的一种通信设备的示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员所获得的所有其他实施例，都属于本申请保护的范围。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施，且“第一”、“第二”所区别的对象通常为一类，并不限定对象的个数，例如第一对象可以是一个，也可以是多个。此外，说明书以及权利要求中“和/或”表示所连接对象的至少其中之一，字符“/”一般表示前后关联对象是一种“或”的关系。
值得指出的是，本申请实施例所描述的技术不限于长期演进型(Long Term Evolution，LTE)/LTE的演进(LTE-Advanced，LTE-A)系统，还可用于其他无线通信系统，诸如码分多址(Code Division Multiple Access，CDMA)、时分多址(Time Division Multiple Access，TDMA)、频分多址(Frequency Division Multiple Access，FDMA)、正交频分多址(Orthogonal Frequency Division Multiple Access，OFDMA)、单载波频分多址(Single-carrier Frequency Division Multiple Access，SC-FDMA)和其他系统。本申请实施例中的术语“系统”和“网络”常被可互换地使用，所描述的技术既可用于以上提及的系统和无线电技术，也可用于其他系统和无线电技术。以下描述出于示例目的描述了新空口(New Radio，NR)系统，并且在以下大部分描述中使用NR术语，但是这些技术也可应用于NR系统应用以外的应用，如第6代(6th Generation，6G)通信系统。
参见图1，图中示意UE-1与UE-2建立语音承载的流程，具体步骤如下：
步骤1：UE-1在漫游地网络(比如，MNO A)建立协议数据单元(Protocol Data Unit，PDU)会话(session)，使用了漫游地会话管理功能(Visiting Session Management Function，V-SMF)。
步骤2：UE-1发起IMS建立请求，通过邀请(Invite)消息发起该请求，在请求的SDP中携带待建立的语音媒体的信息，通过b＝AS:512请求建立GBR为512kbps的语音承载。
步骤3：代理呼叫会话控制功能(Proxy-Call Session Control Function，P-CSCF)通过(Serving Call Session Control Function，S-CSCF)将该invite消息发给UE-2。
需要说明的是，图中的P-CSCF和S-CSCF都是为UE-1提供服务的IMS网元，而为UE-2提供服务的IMS网元未体现。
步骤4：UE-2通过S-CSCF回复SIP 183消息，该消息中包含SDP应答(answer)。
步骤5：P-CSCF向为UE-1提供服务的策略控制功能(Policy Control Function，PCF)发送超文本运输协议(HyperText Transfer Protocol，HTTP)通知(POST)请求(request)消息，该消息携带通过SDP协商好的媒体描述信息(media info)，该媒体描述信息是根据SDP应答消息得到的，其中包含需要使用512kbps的信息。
步骤6：PCF向UE-1的归属地SMF(Home-Session Management Function，H-SMF)发送请求，请建立语音承载，在请求中携带待建立的语音承载的服务质量(Quality of Service，QoS)参数，其中包含GBR为512kbps的信息。
步骤7：H-SMF向V-SMF发送PDU会话更新请求消息(比如，Nsmf_PDUSession_Update Request消息)，该消息中可以包含QoS参数。
步骤8：V-SMF根据请求的QoS参数和其能支持的QoS参数，判断出无法支持512kbps的GBR承载，则V-SMF向H-SMF发送PDU会话更新拒绝消息(比如，Nsmf_PDUSession_Reject消息)。
步骤9：H-SMF向PCF发送拒绝消息，即H-SMF发起的SM策略关联拒绝(H-SMF initiated SM policy association reject)。
步骤10：PCF向P-CSCF发送拒绝消息。
步骤11：P-CSCF向UE-1发送结束(Bye)消息，用于拒绝本次通话。
步骤12：P-CSCF向UE-2发送Bye消息，用于终止本次通话。
也就是，在UE-1处于漫游状态时，由于归属地的参数和漫游地的参数不一致，导致UE-1无法拨打或接听语音，影响用户体验
图2示出本申请实施例可应用的一种无线通信系统的框图。无线通信系统包括终端21和网络侧设备22。
其中，终端21可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)或称为笔记本电脑、个人数字助理(Personal Digital Assistant，PDA)、掌上电脑、上网本、超级移动个人计算机(ultra-mobile personal computer，UMPC)、移动上网装置(Mobile Internet Device，MID)、增强现实(augmented reality，AR)/虚拟现实(virtual reality，VR)设备、机器人、可穿戴式设备(Wearable Device)、车载设备(Vehicle User Equipment，VUE)、行人终端(Pedestrian User Equipment，PUE)、智能家居(具有无线通信功能的家居设备，如冰箱、电视、洗衣机或者家具等)、游戏机、个人计算机(personal computer，PC)、柜员机或者自助机等终端侧设备，可穿戴式设备包括：智能手表、智能手环、智能耳机、智能眼镜、智能首饰(智能手镯、智能手链、智能戒指、智能项链、智能脚镯、智能脚链等)、智能腕带、智能服装等。除了上述终端设备，本申请涉及的终端也可以是终端内的芯片，例如调制解调器(Modem)芯片，系统级芯片(System on Chip，SoC)。需要 说明的是，在本申请实施例并不限定终端21的具体类型。
网络侧设备22可以包括接入网设备或核心网设备，其中，接入网设备也可以称为无线接入网设备、无线接入网(Radio Access Network,RAN)、无线接入网功能或无线接入网单元。接入网设备可以包括基站、无线局域网(Wireless Local Area Network，WLAN)接入点或无线保真(Wireless Fidelity，WiFi)节点等，基站可被称为节点B、演进节点B(Evolved Node B，eNB)、接入点、基收发机站(Base Transceiver Station，BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set，BSS)、扩展服务集(Extended Service Set，ESS)、家用B节点、家用演进型B节点、发送接收点(Transmitting Receiving Point，TRP)或所述领域中其他某个合适的术语，只要达到相同的技术效果，所述基站不限于特定技术词汇，需要说明的是，在本申请实施例中仅以NR系统中的基站为例进行介绍，并不限定基站的具体类型。
核心网设备可以包含但不限于如下至少一项：核心网节点、核心网功能、移动管理实体(Mobility Management Entity，MME)、接入移动管理功能(Access and Mobility Management Function，AMF)、会话管理功能(Session Management Function，SMF)、用户平面功能(User Plane Function，UPF)、策略控制功能(Policy Control Function，PCF)、策略与计费规则功能单元(Policy and Charging Rules Function，PCRF)、边缘应用服务发现功能(Edge Application Server Discovery Function，EASDF)、统一数据管理(Unified Data Management，UDM)，统一数据仓储(Unified Data Repository，UDR)、归属用户服务器(Home Subscriber Server，HSS)、集中式网络配置(Centralized network configuration，CNC)、网络存储功能(Network Repository Function，NRF)，网络开放功能(Network Exposure Function，NEF)、本地NEF(Local NEF，或L-NEF)、绑定支持功能(Binding Support Function，BSF)、应用功能(Application Function，AF)等。需要说明的是，在本申请实施例中仅以NR系统中的核心网设备为例进行介绍，并不限定核心网设备的具体类型。
下面结合附图，通过一些实施例及其应用场景对本申请实施例提供的呼叫协商的方法、装置、通信设备及可读存储介质进行详细地说明。
参见图3，本申请的实施例提供一种呼叫协商的方法，应用于终端，具体步骤包括：步骤301、步骤302和步骤303。
步骤301：终端接收第一消息，所述第一消息用于建立第一承载；
可选地，所述第一承载包括音频承载和视频承载中的至少一项，其中，音频承载也可以描述为语音承载，该第一消息也可以描述为语音建立请求消息。
作为一种可能的实现，终端接收第一核心网设备发送的第一消息，可选地，第一核心网设备可以是4G核心网设备或者5G核心网设备，比如MME或者V-SMF，当然并不限于此。
其中，当第一核心网设备是4G核心网设备，该第一承载为演进分组系统(Evolved Packet System，EPS)承载(bearer)，该第一消息可以为会话管理请求(Session Management  Request)消息；当第一核心网设备是5G核心网设备，该第一承载可以为服务质量(Quality of Service，QoS)流(flow)，该第一消息可以为PDU会话修改命令(PDU session modification command)。
可选地，第一消息中携带有由第一核心网设备修改后的第一承载的参数，该第一核心网设备可以根据所述第一核心网设备支持的承载的参数对所述第一承载的参数进行修改。
作为另外一种可能的实现，终端接收来自接入网设备(比如基站)发送的第一消息，该第一消息可以是无线资源配置连接重配置(Radio Resource Configuration Connection Reconfiguration)消息或无线资源配置重配置(Radio Resource Configuration Reconfiguration)消息。
步骤302：根据所述第一消息获取所述第一承载的参数；
可选地，所述第一承载的参数可以包括：保证比特速率(Guaranteed Bit Rate，GBR)、最大比特速率(Maximum Bit Rate，MBR)中的至少一项。其中，GBR是指为了支持该业务，需要保证的最小比特速率。MBR是指为了支持该业务，能保证的最大比特速率，可选地，GBR≤MBR。其中，第一承载的参数也可以描述为第一承载的QoS参数。
步骤303：在所述第一承载的参数与所述终端的IMS会话参数不匹配的情况下，所述终端发送第二消息，所述第二消息用于请求进行IMS会话重协商，以使得所述IMS会话参数与所述第一承载的参数匹配。
其中，第二消息也可以描述为IMS会话重协商请求消息或者IMS会话修改请求消息。该IMS会话重协商请求可以是重邀请(re-Invite)消息，该IMS会话修改请求可以是更新(Update)消息。re-Invite消息和Update消息均是会话初始协议(Session initialization Protocol，SIP)消息。
在本申请实施例中，在第一承载的参数与终端的IMS会话参数不匹配的情况下，该终端(比如，UE-1)可以向通信对端(比如，UE-2)发起IMS会话重协商请求，从而使第一承载的参数与IMS会话参数匹配，使得第一承载建立成功，可以让通信双方成功建立音频或视频通信，提升用户体验。
在本申请的一种实施方式中，在所述第一承载的参数与所述终端的IMS会话参数不匹配的情况下，所述终端发送第二消息，包括：
所述终端的IMS层判断所述第一承载的参数与所述终端的IMS会话参数是否匹配；
在不匹配的情况下，所述终端根据所述第一承载的参数发送第二消息，比如，所述第二消息携带与所述第一承载的参数对应的IMS会话参数。本申请涉及的IMS层也可以理解为IMS协议层。
在本申请的一种实施方式中，所述终端接收第一消息，包括：所述终端的非接入层(Non-Access-Stratum，NAS)接收第一消息；
其中，所述根据所述第一消息获取所述第一承载的参数，包括：
所述终端的非接入层根据所述第一消息获取所述第一承载的参数；所述终端的非接入 层将所述第一承载的参数递送给IMS层。
在本申请的一种实施方式中，所述终端接收第一消息，包括：所述终端的接入层(Access Stratum，AS)接收第一消息；
其中，所述根据所述第一消息获取所述第一承载的参数，包括：
所述终端的接入层根据所述第一消息获取所述第一承载对应的接入层参数；所述终端的接入层将所述第一承载对应的接入层参数递送给IMS层；所述终端的IMS层根据所述第一承载对应的接入层参数获取所述第一承载的参数。
在本申请的一种实施方式中，所述终端接收第一消息，包括：所述终端的接入层接收第一消息；
其中，所述根据所述第一消息获取所述第一承载的参数，包括：
所述终端的接入层根据所述第一消息获取所述第一承载对应的接入层参数；所述终端的接入层将所述第一承载对应的接入层参数递送给非接入层；所述终端的非接入层根据所述第一承载对应的接入层参数确定所述第一承载对应的非接入层参数；所述终端的非接入层将所述第一承载对应的非接入层参数递送给所述IMS层；所述终端的IMS层根据所述第一承载对应的非接入层参数获取所述第一承载的参数。
在本申请的一种实施方式中，所述终端的IMS层判断所述第一承载的参数与所述终端的IMS会话参数是否匹配，包括：
所述终端的IMS层判断所述第一承载的参数与所述终端的IMS会话参数的差值的绝对值是否大于预设值；
在所述第一承载的参数与所述IMS会话参数的差值的绝对值大于或等于预设值的情况下，判定不匹配；或者，
在所述第一承载的参数与所述IMS会话参数的差值的绝对值小于预设值的情况下，判定匹配。
可以理解的是，对上述预设值的值不做限定，可以根据具体情况进行调整。
在本申请实施例中，在第一承载的参数与终端的IMS会话参数不匹配的情况下，该终端可以向通信对端发起IMS会话重协商请求，从而使第一承载的参数与IMS会话参数匹配，使得第一承载建立成功，可以让通信双方成功建立第一承载通信，提升用户体验。
参见图4，本申请的实施例提供一种呼叫协商的方法，应用于第一核心网设备，该第一核心网设备可以是4G核心网设备或者5G核心网设备，比如MME或者V-SMF，具体步骤包括：步骤401、步骤402、步骤403和步骤404。
步骤401：第一核心网设备接收第三消息，所述第三消息用于请求为终端建立第一承载；
比如，第一核心网设备从第二核心网设备接收第三消息，该第二核心网设备可以包括H-SMF或分组数据网络网关(Packet Data Network Gateway，PGW)，当然并不限于此。
其中，第三消息可以称为PDU会话更新请求消息，该消息中可以携带第一承载的参 数。
步骤402：所述第一核心网设备判断所述第三消息中包含的所述第一承载的参数与所述第一核心网设备支持的承载参数是否匹配；
比如，所述第一核心网判断所述第一承载的参数与第一核心网设备支持的承载参数的差值的绝对值是否大于预设值；
在所述第一承载的参数与第一核心网设备支持的承载参数的差值的绝对值大于或等于预设值的情况下，判定不匹配；或者，
在所述第一承载的参数与第一核心网设备支持的承载参数的差值的绝对值小于预设值的情况下，判定匹配。
步骤403：在不匹配的情况下，所述第一核心网设备根据所述第一核心网设备支持的承载的参数对所述第一承载的参数进行修改；
作为一种可能的实现，第一核心网设备根据所述第一核心网设备支持的承载的参数对所述第一承载的参数，使得修改后的第一承载的参数与第一核心网设备支持的承载参数匹配，比如，修改后的第一承载的参数与第一核心网设备支持的承载参数的差值的绝对值小于预设值。
步骤404：所述第一核心网设备发送第一消息，所述第一消息用于建立所述第一承载，所述第一消息中携带修改后的所述第一承载的参数。
可选地，所述第一核心网设备向终端发送第一消息，使得终端判断第一承载的参数与所述终端的IMS会话参数是否匹配，以及在第一承载的参数与终端的IMS会话参数不匹配的情况下，终端可以向通信对端发送第二消息，所述第二消息用于请求进行IMS会话重协商，以使得所述IMS会话参数与所述第一承载的参数匹配。
在本申请的一种实施方式中，所述第一承载可以包括音频承载和视频承载中的至少一项。
在本申请的一种实施方式中，所述第一承载的参数可以包括：保证比特速率、最大比特速率中的至少一项。
在本申请实施例中，在第一承载的参数与第一核心网设备支持的承载参数不匹配的情况下，该第一核心网设备可以根据其支持的承载的参数对第一承载的参数进行修改，并按照修改后的第一承载的参数建立第一承载，可以避免第一核心网设备由于第一承载的参数与第一核心网设备支持的承载参数不匹配而直接拒绝第一承载建立请求的问题，可以让通信双方成功建立第一承载通信，提升用户体验。
下面结合实施例一和实施例二介绍本申请的实施方式。
实施例一
参见图5，具体步骤如下：
步骤1：UE-1在漫游地网络建立PDU会话，使用了漫游地的会话管理功能(Visiting-Session Management Function，V-SMF)。
步骤2：UE-1发起IMS建立请求，通过邀请(Invite)消息发起该请求，在请求的描述会话的协议(Session Description Protocol，SDP)中携带待建立的语音媒体的信息，通过“b＝AS:512”请求建立GBR为512kbps的语音承载。
步骤3：P-CSCF通过S-CSCF将邀请消息发给UE-2。
需要说明的是，图中的P-CSCF和S-CSCF都是为UE-1提供服务的IMS网元，而为UE-2提供服务的IMS网元未体现。
步骤4：UE-2通过S-CSCF回复会话初始协议(Session initialization Protocol，SIP)183消息，该消息中包含SDP应答。
步骤5：P-CSCF向为UE-1提供服务的PCF发送HTTP POST请求消息，该消息携带通过SDP协商好的媒体描述信息，该媒体描述信息是根据SDP应答消息得到的，其中包含需要使用512kbps的信息。
步骤6：PCF向UE-1的H-SMF发送请求，请建立语音承载，在请求中携带待建立的第一承载的QoS参数，其中包含GBR为512kbps的信息。
步骤7：H-SMF向V-SMF发送PDU会话更新请求消息，消息中可以包含QoS参数。
步骤8：V-SMF判断该请求用于建立第一承载，并且请求建立的第一承载的GBR或MBR参数与其支持的GBR或MBR参数不匹配时，V-SMF修改发送给UE的第一消息的PDU会话修改命令(PDU session modification command)中的GBR或MBR参数为其支持的承载的参数，同时，V-SMF通过Namf_Communication_N1N2MessageTransfer消息将修改后的第一承载的GBR或MBR参数发送给AMF，修改后的第一承载的GBR或MBR参数为V-SMF支持的承载的参数。
上述第一消息也可以是非接入层(Non Access Stratum，NAS)消息，或者也可以是接入层(Access Stratum，AS)消息。
步骤9：AMF将修改后的GBR或MBR参数发给基站(the next Generation Node B，gNB)，在该消息中同时包含发送给UE-1的第一消息。
步骤10：gNB将发送给UE-1的第一消息转给UE-1，UE-1回复确认消息。
在步骤10中UE-1的NAS层接收第一消息，或者UE-1的AS层接收第一消息。
其中，AS层用于配置UE与gNB间的数据无线承载(Data Radio Bearer，DRB)，用于在UE-1和gNB间传输UE-1的数据。
步骤11：gNB向AMF发送确认消息。
步骤12：AMF向V-SMF发送确认消息
步骤13：V-SMF向H-SMF发送确认消息，比如Nsmf_PDUSession_UpdateSM Context消息，消息中携带修改后的第一承载的GBR或MBR参数。
步骤14：H-SMF向PCF发送确认消息，即，H-SMF发起SM策略关联修改。
步骤15：PCF向P-CSCF发送确认消息，比如，201已创建(Created)消息。
步骤16：P-CSCF向UE发送183消息，在该183消息中包含SDP应答消息，SDP应 答消息中包含对端确认的IMS会话参数，例如，带宽参数。
步骤17-18：通信对端(UE-2)接听电话，向UE-1发送200OK消息。
步骤19：UE-1的NAS层收到第一消息，例如，PDU会话修改命令消息，UE-1的NAS层向IMS层发送第一承载的参数，例如GBR或MBR参数，UE-1的IMS层判断第一承载的参数与IMS会话参数是否匹配，若不匹配，则UE-1发起IMS会话重协商请求(即，UE-1发送第二消息)，在IMS会话重协商请中包含第一承载的参数对应的IMS会话参数，如图6所示。
例如，IMS层协商的参数是512kbps，NAS层得到的参数是64kbps，NAS层将64kbps发送给IMS层后，IMS层使用64kbps与UE-2进行重协商，从而通信双方使用64kbps进行通信。
其中，第二消息可以是SIP重邀请(re-Invite)消息或SIP更新(update)消息。步骤19可以在步骤18之前发送或之后发送，若在步骤18之前发送，则UE-1通过SIP update消息进行重协商，若在步骤18之后发送，则通过SIP re-Invite消息发送。
其中，第一承载的参数中的GBR或MBR参数和IMS层的“b：AS的参数”可能不一致。两者有对应关系。例如，“b：AS的参数”用于描述语音媒体的实时传输协议(Real-time Transport Protocol，RTP)使用的速率，GBR或MBR参数可以是描述语音媒体的RTP和实时传输控制协议(Real-time Transport Control Protocol，RTCP)使用的速率的总和，其中RTCP使用的速率可以是固定值。
其中，UE-1的IMS层判断第一承载的参数与IMS会话参数是否匹配，包括：
IMS层判断第一承载的参数与IMS会话参数的差值的绝对值大于预设值时，判定不匹配；IMS层判断第一承载的参数与IMS会话参数的差值的绝对值小于预设值时，判定匹配。
步骤20：UE-1发送第二消息，在第二消息中包含第一承载的参数对应的IMS参数。
步骤21：将第二消息发给UE-2。
步骤22-23：UE-2回复200OK消息，携带IMS会话重协商的结果。
在本申请实施例中，在第一承载的参数与UE-1的IMS会话参数不匹配的情况下，该UE-1可以向UE-2发起IMS会话重协商请求，从而使第一承载的参数与IMS会话参数匹配，使得第一承载建立成功，可以让UE-1和UE-2成功建立音频或视频通信，提升用户体验。
实施例二
参见图7，具体步骤如下：
步骤1-7：可以参考图5中的步骤1-7的描述。
步骤8：V-SMF判断该请求用于建立第一承载，并且请求建立的第一承载的GBR或MBR参数与其支持的承载的GBR或MBR参数不匹配时，V-SMF修改发送给gNB的第一承载的GBR或MBR参数为其支持的承载的参数，V-SMF发送第一消息，第一消息携 带修改后的第一承载的GBR或MBR参数。
与实施例1的区别，V-SMF没有将修改后的第一承载的参数发送给UE-1的NAS层。
步骤9：AMF将修改后的第一承载的参数发给gNB，在该消息中同时包含发送给UE的第一消息。
步骤10：gNB将发送给UE-1的第一消息转给UE-1，UE-1回复确认消息。
步骤11-18：可以参考图5中的步骤11-18的描述。
步骤19：UE-1的AS层收到建立第一承载的第一消息，例如，RRC reconfiguration消息，在该第一消息中包含第一承载对应的AS层参数，例如，优先比特速率(prioritisedBitRate)；
如图8，UE-1的AS层向IMS层发送AS层参数，IMS层根据AS层参数判断第一承载的参数与IMS会话参数是否匹配；或者，
UE-1的AS层将AS层参数发给NAS层，NAS根据AS层参数获得GBR或MBR参数，NAS层向IMS层发送NAS层参数，IMS层根据NAS层参数判断第一承载的参数与IMS会话参数是否匹配。
若IMS层判断第一承载的参数与IMS会话参数不匹配，则UE-1发起IMS会话重协商请求，在会话重协商请中包含语音承载的参数对应的IMS会话参数。
步骤20：UE-1发送第二消息，在第二消息中包含第一承载的参数对应的IMS会话参数。
步骤21：将该第二消息发给UE-2。
步骤22-23：UE-2回复200OK，携带IMS会话重协商的结果。
在本申请实施例中，在第一承载的参数与UE-1的IMS会话参数不匹配的情况下，该UE-1可以向UE-2发起IMS会话重协商请求，从而使第一承载的参数与IMS会话参数匹配，使得第一承载建立成功，可以让UE-1和UE-2成功建立音频或视频通信，提升用户体验。
参见图9，本申请的实施例提供一种呼叫协商的装置，应用于终端，装置900包括：
第一接收模块901，用于接收第一消息，所述第一消息用于建立第一承载；
获取模块902，用于根据所述第一消息获取所述第一承载的参数；
第一发送模块903，用于在所述第一承载的参数与所述终端的MS会话参数不匹配的情况下，发送第二消息，所述第二消息用于请求进行IMS会话重协商，以使得所述IMS会话参数与所述第一承载的参数匹配。
在本申请的一种实施方式中，第一发送模块903进一步用于：通过IMS层判断所述第一承载的参数与所述终端的IMS会话参数是否匹配；在不匹配的情况下，根据所述第一承载的参数发送第二消息。
在本申请的一种实施方式中，第一接收模块901进一步用于：通过非接入层接收第一消息；
获取模块902进一步用于：通过非接入层根据所述第一消息获取所述第一承载的参数；通过非接入层将所述第一承载的参数递送给IMS层。
在本申请的一种实施方式中，第一接收模块901进一步用于：通过接入层接收第一消息；
获取模块902进一步用于：通过接入层根据所述第一消息获取所述第一承载对应的接入层参数；通过接入层将所述第一承载对应的接入层参数递送给IMS层；通过IMS层根据所述第一承载对应的接入层参数获取所述第一承载的参数。
在本申请的一种实施方式中，第一接收模块901进一步用于：通过接入层接收第一消息；
获取模块902进一步用于：通过接入层根据所述第一消息获取所述第一承载对应的接入层参数；通过接入层将所述第一承载对应的接入层参数递送给非接入层；通过非接入层根据所述第一承载对应的接入层参数确定所述第一承载对应的非接入层参数；通过非接入层将所述第一承载对应的非接入层参数递送给所述IMS层；通过IMS层根据所述第一承载对应的非接入层参数获取所述第一承载的参数。
在本申请的一种实施方式中，第一发送模块903进一步用于：通过IMS层判断所述第一承载的参数与所述终端的IMS会话参数的差值的绝对值是否大于预设值；在所述第一承载的参数与所述IMS会话参数的差值的绝对值大于或等于预设值的情况下，判定不匹配；或者，在所述第一承载的参数与所述IMS会话参数的差值的绝对值小于预设值的情况下，判定匹配。
在本申请的一种实施方式中，第一接收模块901进一步用于：接收第一核心网设备发送的第一消息，所述第一消息为会话管理请求消息或者协议数据单元会话修改命令。
在本申请的一种实施方式中，第一接收模块901进一步用于：接收接入网设备发送的第一消息，所述第一消息为无线资源配置连接重配置或者或无线资源配置重配置消息。
在本申请的一种实施方式中，所述第一承载包括音频承载和视频承载中的至少一项。
在本申请的一种实施方式中，所述第二消息携带与所述第一承载的参数对应的IMS会话参数。
在本申请的一种实施方式中，所述第一承载的参数包括：保证比特速率、最大比特速率中的至少一项。
本申请实施例提供的装置能够实现图3的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
参见图10，本申请的实施例提供一种呼叫协商的装置，应用于第一核心网设备，该装置1000包括：
第二接收模块1001，用于接收第三消息，所述第三消息用于请求为终端建立第一承载；
判断模块1002，用于判断所述第三消息中包含的所述第一承载的参数与所述第一核 心网设备支持的承载参数是否匹配；
修改模块1003，用于在不匹配的情况下，所述第一核心网设备根据所述第一核心网设备支持的承载的参数对所述第一承载的参数进行修改；
第二发送模块1004，用于向所述终端发送第一消息，所述第一消息中携带修改后的所述第一承载的参数。
在本申请的一种实施方式中，所述第一承载的参数包括：保证比特速率、最大比特速率中的至少一项。
在本申请的一种实施方式中，所述第一核心网设备包括：移动管理实体或者漫游地会话管理功能。
本申请实施例提供的装置能够实现图4的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
图11为实现本申请实施例的一种终端的硬件结构示意图。该终端1100包括但不限于：射频单元1101、网络模块1102、音频输出单元1103、输入单元1104、传感器1105、显示单元1106、用户输入单元1107、接口单元1108、存储器1109以及处理器1110等中的至少部分部件。
本领域技术人员可以理解，终端1100还可以包括给各个部件供电的电源(比如电池)，电源可以通过电源管理系统与处理器1110逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。图11中示出的终端结构并不构成对终端的限定，终端可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置，在此不再赘述。
应理解的是，本申请实施例中，输入单元1104可以包括图形处理单元(Graphics Processing Unit，GPU)11041和麦克风11042，图形处理器11041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。显示单元1106可包括显示面板11061，可以采用液晶显示器、有机发光二极管等形式来配置显示面板11061。用户输入单元1107包括触控面板11071以及其他输入设备11072中的至少一种。触控面板11071，也称为触摸屏。触控面板11071可包括触摸检测装置和触摸控制器两个部分。其他输入设备11072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
本申请实施例中，射频单元1101接收来自网络侧设备的下行数据后，可以传输给处理器1110进行处理；另外，射频单元1101可以向网络侧设备发送上行数据。通常，射频单元1101包括但不限于天线、放大器、收发信机、耦合器、低噪声放大器、双工器等。
存储器1109可用于存储软件程序或指令以及各种数据。存储器1109可主要包括存储程序或指令的第一存储区和存储数据的第二存储区，其中，第一存储区可存储操作系统、至少一个功能所需的应用程序或指令(比如声音播放功能、图像播放功能等)等。此外，存储器1109可以包括易失性存储器或非易失性存储器，或者，存储器1109可以包括易失 性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDRSDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synch link DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DRRAM)。本申请实施例中的存储器1109包括但不限于这些和任意其它适合类型的存储器。
处理器1110可包括一个或多个处理单元；可选地，处理器1110集成应用处理器和调制解调处理器，其中，应用处理器主要处理涉及操作系统、用户界面和应用程序等的操作，调制解调处理器主要处理无线通信信号，如基带处理器。可以理解的是，上述调制解调处理器也可以不集成到处理器1110中。
本申请实施例提供的终端能够实现图3的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
请参阅图12，图12是本申请实施例应用的通信设备的结构图，如图12所示，通信设备1200包括：处理器1201、收发机1202、存储器1203和总线接口，其中，处理器1201可以负责管理总线架构和通常的处理。存储器1203可以存储处理器1201在执行操作时所使用的数据。
在本申请的一个实施例中，通信设备1200还包括：存储在存储器1203并可在处理器1201上运行的程序，程序被处理器1201执行时实现以上图3所示方法中的步骤。
在图12中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器1201代表的一个或多个处理器和存储器1203代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发机1202可以是多个元件，即包括发送机和接收机，提供用于在传输介质上与各种其他装置通信的单元。
可选地，如图13所示，本申请实施例还提供一种通信设备1300，包括处理器1301和存储器1302，存储器1302上存储有可在所述处理器1301上运行的程序或指令，例如，该通信设备1300为终端时，该程序或指令被处理器1301执行时实现上述图3方法实施例的各个步骤，该通信设备1300为核心网设备时，该程序或指令被处理器1301执行时实现上述图4方法实施例的各个步骤且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供一种可读存储介质，所述可读存储介质上存储有程序或指令，该程序或指令被处理器执行时实现图3或图4方法及上述各个实施例的各个过程，且能达到 相同的技术效果，为避免重复，这里不再赘述。
其中，所述处理器为上述实施例中所述的终端中的处理器。所述可读存储介质，包括计算机可读存储介质，如计算机只读存储器ROM、随机存取存储器RAM、磁碟或者光盘等。
本申请实施例另提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现图3或图4所示及上述各个方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
本申请实施例另提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在存储介质中，所述计算机程序/程序产品被至少一个处理器执行以实现图3或图4所示及上述各个方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例另提供一种通信系统，所述通信系统包括终端与网络侧设备，所述终端用于执行如图3及上述各个方法实施例的各个过程，所述网络侧设备用于执行如图4及上述各个方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外，需要指出的是，本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能，还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能，例如，可以按不同于所描述的次序来执行所描述的方法，并且还可以添加、省去、或组合各种步骤。另外，参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以计算机软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本申请的保护之内。

Claims (21)

  1. 一种呼叫协商的方法，包括：
    终端接收第一消息，所述第一消息用于建立第一承载；
    根据所述第一消息获取所述第一承载的参数；
    在所述第一承载的参数与所述终端的IP多媒体系统IMS会话参数不匹配的情况下，所述终端发送第二消息，所述第二消息用于请求进行IMS会话重协商，以使得所述IMS会话参数与所述第一承载的参数匹配。
  2. 根据权利要求1所述的方法，其中，在所述第一承载的参数与所述终端的IMS会话参数不匹配的情况下，所述终端发送第二消息，包括：
    所述终端的IMS层判断所述第一承载的参数与所述终端的IMS会话参数是否匹配；
    在不匹配的情况下，所述终端根据所述第一承载的参数发送第二消息。
  3. 根据权利要求2所述的方法，其中，所述终端接收第一消息，包括：
    所述终端的非接入层接收第一消息；
    其中，所述根据所述第一消息获取所述第一承载的参数，包括：
    所述终端的非接入层根据所述第一消息获取所述第一承载的参数；
    所述终端的非接入层将所述第一承载的参数递送给IMS层。
  4. 根据权利要求2所述的方法，其中，所述终端接收第一消息，包括：
    所述终端的接入层接收第一消息；
    其中，所述根据所述第一消息获取所述第一承载的参数，包括：
    所述终端的接入层根据所述第一消息获取所述第一承载对应的接入层参数；
    所述终端的接入层将所述第一承载对应的接入层参数递送给IMS层；
    所述终端的IMS层根据所述第一承载对应的接入层参数获取所述第一承载的参数。
  5. 根据权利要求2所述的方法，其中，所述终端接收第一消息，包括：
    所述终端的接入层接收第一消息；
    其中，所述根据所述第一消息获取所述第一承载的参数，包括：
    所述终端的接入层根据所述第一消息获取所述第一承载对应的接入层参数；
    所述终端的接入层将所述第一承载对应的接入层参数递送给非接入层；
    所述终端的非接入层根据所述第一承载对应的接入层参数确定所述第一承载对应的非接入层参数；
    所述终端的非接入层将所述第一承载对应的非接入层参数递送给所述IMS层；
    所述终端的IMS层根据所述第一承载对应的非接入层参数获取所述第一承载的参数。
  6. 根据权利要求2或3或4或5所述的方法，其中，所述终端的IMS层判断所述第一承载的参数与所述终端的IMS会话参数是否匹配，包括：
    所述终端的IMS层判断所述第一承载的参数与所述终端的IMS会话参数的差值的绝 对值是否大于预设值；
    在所述第一承载的参数与所述IMS会话参数的差值的绝对值大于或等于预设值的情况下，判定不匹配；或者，
    在所述第一承载的参数与所述IMS会话参数的差值的绝对值小于预设值的情况下，判定匹配。
  7. 根据权利要求1至5任一项所述的方法，其中，终端接收第一消息，包括：
    所述终端接收第一核心网设备发送的第一消息，所述第一消息为会话管理请求消息或者协议数据单元会话修改命令。
  8. 根据权利要求1至5任一项所述的方法，其中，终端接收第一消息，包括：
    所述终端接收接入网设备发送的第一消息，所述第一消息为无线资源配置连接重配置或者或无线资源配置重配置消息。
  9. 根据权利要求1至5任一项所述的方法，其中，所述第一承载包括音频承载和视频承载中的至少一项。
  10. 根据权利要求1至5任一项所述的方法，其中，所述第二消息携带与所述第一承载的参数对应的IMS会话参数。
  11. 根据权利要求1至5任一项所述的方法，其中，所述第一承载的参数包括：保证比特速率、最大比特速率中的至少一项。
  12. 一种呼叫协商的装置，应用于终端，包括：
    第一接收模块，用于接收第一消息，所述第一消息用于建立第一承载；
    获取模块，用于根据所述第一消息获取所述第一承载的参数；
    第一发送模块，用于在所述第一承载的参数与所述终端的MS会话参数不匹配的情况下，发送第二消息，所述第二消息用于请求进行IMS会话重协商，以使得所述IMS会话参数与所述第一承载的参数匹配。
  13. 根据权利要求12所述的装置，其中，所述第一发送模块进一步用于：通过IMS层判断所述第一承载的参数与所述终端的IMS会话参数是否匹配；在不匹配的情况下，根据所述第一承载的参数发送第二消息。
  14. 根据权利要求12所述的装置，其中，所述第一接收模块进一步用于：通过非接入层接收第一消息；
    所述获取模块进一步用于：通过非接入层根据所述第一消息获取所述第一承载的参数；通过非接入层将所述第一承载的参数递送给IMS层。
  15. 根据权利要求12所述的装置，其中，所述第一接收模块进一步用于：通过接入层接收第一消息；
    所述获取模块进一步用于：通过接入层根据所述第一消息获取所述第一承载对应的接入层参数；通过接入层将所述第一承载对应的接入层参数递送给IMS层；通过IMS层根据所述第一承载对应的接入层参数获取所述第一承载的参数。
  16. 根据权利要求12所述的装置，其中，所述第一接收模块进一步用于：通过接入层接收第一消息；
    所述获取模块进一步用于：通过接入层根据所述第一消息获取所述第一承载对应的接入层参数；通过接入层将所述第一承载对应的接入层参数递送给非接入层；通过非接入层根据所述第一承载对应的接入层参数确定所述第一承载对应的非接入层参数；通过非接入层将所述第一承载对应的非接入层参数递送给IMS层；通过IMS层根据所述第一承载对应的非接入层参数获取所述第一承载的参数。
  17. 根据权利要求12所述的装置，其中，所述第一发送模块进一步用于：通过IMS层判断所述第一承载的参数与所述终端的IMS会话参数的差值的绝对值是否大于预设值；在所述第一承载的参数与所述IMS会话参数的差值的绝对值大于或等于预设值的情况下，判定不匹配；或者，在所述第一承载的参数与所述IMS会话参数的差值的绝对值小于预设值的情况下，判定匹配。
  18. 一种通信设备，包括处理器，存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求1至11中任一项所述的方法的步骤。
  19. 一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如权利要求1至11中任一项所述的方法的步骤。
  20. 一种芯片，包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如权利要求1至11中任一项所述的方法的步骤。
  21. 一种计算机程序产品，所述程序产品被存储在非瞬态的存储介质中，所述程序产品被至少一个处理器执行以实现如权利要求1至11中任一项所述的方法的步骤。
PCT/CN2023/107882 2022-07-22 2023-07-18 呼叫协商的方法、装置、通信设备及可读存储介质 Ceased WO2024017238A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210869240.XA CN117478645A (zh) 2022-07-22 2022-07-22 呼叫协商的方法、装置、通信设备及可读存储介质
CN202210869240.X 2022-07-22

Publications (1)

Publication Number Publication Date
WO2024017238A1 true WO2024017238A1 (zh) 2024-01-25

Family

ID=89617163

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/107882 Ceased WO2024017238A1 (zh) 2022-07-22 2023-07-18 呼叫协商的方法、装置、通信设备及可读存储介质

Country Status (2)

Country Link
CN (1) CN117478645A (zh)
WO (1) WO2024017238A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160099934A1 (en) * 2014-10-07 2016-04-07 Google Inc. Authenticated session establishment
US20180014168A1 (en) * 2016-07-06 2018-01-11 Verizon Patent And Licensing Inc. Session establishment, maintenance, and termination by end device based on sms messaging
CN109996349A (zh) * 2019-04-02 2019-07-09 华为技术有限公司 一种会话恢复方法及其装置
CN110086746A (zh) * 2018-01-25 2019-08-02 中兴通讯股份有限公司 融合设备媒体控制方法、装置、会话控制器及通信终端
CN114731538A (zh) * 2019-11-26 2022-07-08 高通股份有限公司 车载通信中基于无线电承载质量度量的应用层中的传输控制

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160099934A1 (en) * 2014-10-07 2016-04-07 Google Inc. Authenticated session establishment
US20180014168A1 (en) * 2016-07-06 2018-01-11 Verizon Patent And Licensing Inc. Session establishment, maintenance, and termination by end device based on sms messaging
CN110086746A (zh) * 2018-01-25 2019-08-02 中兴通讯股份有限公司 融合设备媒体控制方法、装置、会话控制器及通信终端
CN109996349A (zh) * 2019-04-02 2019-07-09 华为技术有限公司 一种会话恢复方法及其装置
CN114731538A (zh) * 2019-11-26 2022-07-08 高通股份有限公司 车载通信中基于无线电承载质量度量的应用层中的传输控制

Also Published As

Publication number Publication date
CN117478645A (zh) 2024-01-30

Similar Documents

Publication Publication Date Title
US20250203677A1 (en) Communication establishment method and apparatus, terminal device, and network side device
CN117062083A (zh) 通信方法、装置、终端、网络侧设备及介质
WO2023179595A1 (zh) 非3gpp设备的会话通道建立方法、装置及设备
US20250071178A1 (en) Method and Apparatus for Processing Data Channel Application List, and Device
US20250220056A1 (en) Communication method, apparatus, ue, and readable storage medium
US20250063071A1 (en) Communication Method and Apparatus, Terminal, Network Side Device, and Medium
WO2024061085A1 (zh) 通信方法、装置及设备
WO2024017238A1 (zh) 呼叫协商的方法、装置、通信设备及可读存储介质
US11765211B2 (en) Capabilities-based network selection for cellular devices
US20250159459A1 (en) Communication processing method and apparatus, communication device, and readable storage medium
CN116828546A (zh) 非3gpp设备的会话通道建立方法、装置及设备
WO2024012238A1 (zh) 通信处理方法、装置、通信设备及可读存储介质
WO2024051663A1 (zh) 数据通道建立方法、第一终端及第二终端
WO2025067114A1 (zh) 建立数据通道的方法、第一用户设备及网络侧功能
WO2024012288A1 (zh) 数据通道的保持方法、装置、通信设备及可读存储介质
WO2024041422A1 (zh) 通信方法、装置、终端及核心网节点
CN117479341A (zh) 通信处理的方法、装置、通信设备及可读存储介质
WO2024099139A1 (zh) 呼叫方法、装置、第一核心网设备及第三核心网设备
WO2025237250A1 (zh) 通信方法、装置、设备及存储介质
WO2026056819A1 (zh) 通信方法、装置、终端、网络侧设备及介质
CN117812651A (zh) 通信处理方法、装置、第一核心网设备及第三核心网设备
WO2025026276A1 (zh) 一种数据通道建立方法、装置及通信设备
WO2023241614A1 (zh) Ims服务获取方法、终端、网络侧设备及介质
WO2025209360A1 (zh) 数字人通信方法、装置、ue、网络侧设备、介质及计算机程序产品
WO2025011503A1 (zh) 呼叫建立方法、装置及网络侧设备

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: 23842301

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 23842301

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 23842301

Country of ref document: EP

Kind code of ref document: A1