CN117478645A

CN117478645A - Call negotiation method, device, communication equipment and readable storage medium

Info

Publication number: CN117478645A
Application number: CN202210869240.XA
Authority: CN
Inventors: 程思涵; 吴晓波; 崇卫微
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2022-07-22
Filing date: 2022-07-22
Publication date: 2024-01-30
Also published as: WO2024017238A1

Abstract

The application discloses a method, a device, a communication device and a readable storage medium for call negotiation, wherein the method comprises the following steps: the method comprises the steps that a terminal receives a first message, wherein the first message is used for establishing a first bearing; acquiring parameters of the first bearer according to the first message; and under the condition that the parameters of the first bearer are not matched with the IMS session parameters of the terminal, the terminal sends a second message, wherein the second message is used for requesting IMS session renegotiation so that the IMS session parameters are matched with the parameters of the first bearer.

Description

Call negotiation method, device, communication equipment and readable storage medium

Technical Field

The application belongs to the technical field of communication, and particularly relates to a method and device for call negotiation, communication equipment and a readable storage medium.

Background

The different operators support different cases for voice, for example, the guaranteed Bit Rate (Guaranteed Bit Rate, GBR) or the Maximum Bit Rate (Maximum Bit Rate, MBR) of voice supported by the operator A, B, C is 64kbps,156kbps,512kbps:

the value of GBR used by the mobile network operator (mobile network operator, MNO) a is equal to 64kbps;

The value of GBR used by MNO B is equal to 156kbps;

the value of GBR used by MNO C is equal to 512kbps.

For example, when a terminal of MNO C (e.g., user Equipment (UE)) roams to MNO a, the terminal initiates an IP multimedia system (IP Multimedia Subsystem, IMS) session request according to the stored MNO C configuration, and establishes a voice bearer or a video call bearer with GBR of 512kbps. Specifically, session description information (Session Description Protocol, SDP) information is carried in a session initiation protocol (Session Initiation Protocol, SIP) invite (invite) message, and the SDP information includes information using 512kbps GBR parameters.

When the MNO establishes a voice bearer or a video call bearer according to the negotiation result of the IMS layer, the MNO only supports the establishment of the voice bearer of 64kbps, which results in that the network side refuses the voice bearer establishment request or the video call bearer, thereby resulting in failure of the establishment of the voice bearer or the video call bearer, and resulting in that the user cannot use the voice service or the video call service in roaming.

Disclosure of Invention

The embodiment of the application provides a method, a device, communication equipment and a readable storage medium for call negotiation, which solve the problem of how to successfully establish a bearing for both communication parties.

In a first aspect, a method for call negotiation is provided, including:

the method comprises the steps that a terminal receives a first message, wherein the first message is used for establishing a first bearing;

acquiring parameters of the first bearer according to the first message;

and under the condition that the parameters of the first bearer are not matched with the parameters of the IMS session of the IP multimedia system of the terminal, the terminal sends a second message, and the second message is used for requesting IMS session renegotiation so that the parameters of the IMS session are matched with the parameters of the first bearer.

In a second aspect, an apparatus for call negotiation is provided, which is applied to a terminal, and includes:

the first receiving module is used for receiving a first message, and the first message is used for establishing a first bearing;

the acquisition module is used for acquiring the parameters of the first bearer according to the first message;

and the first sending module is used for sending a second message when the parameter of the first bearer is not matched with the MS session parameter of the terminal, wherein the second message is used for requesting IMS session renegotiation so that the IMS session parameter is matched with the parameter of the first bearer.

In a third aspect, there is provided a communication device comprising: a processor, a memory and a program or instruction stored on the memory and executable on the processor, which when executed by the processor, implements the steps of the method as described in the first aspect.

In a fourth aspect, there is provided a readable storage medium having stored thereon a program or instructions which when executed by a processor perform the steps of the method according to the first aspect.

In a fifth aspect, there is provided a chip comprising a processor and a communication interface coupled to the processor for running a program or instructions implementing the steps of the method according to the first aspect.

In a sixth aspect, a computer program/program product is provided, the computer program/program product being stored in a non-transitory storage medium, the program/program product being executed by at least one processor to implement the steps of the method according to the first aspect.

In a seventh aspect, a communication system is provided, the communication system comprising a terminal and a network-side device, the terminal being configured to perform the steps of the method according to the first aspect.

In the embodiment of the application, under the condition that the parameter of the first bearer is not matched with the IMS session parameter of the terminal, the terminal can initiate an IMS session renegotiation request to the opposite communication terminal, so that the parameter of the first bearer is matched with the IMS session parameter, the first bearer is successfully established, the communication parties can successfully establish the communication of the first bearer (such as an audio bearer or a video bearer), and the user experience is improved.

Drawings

FIG. 1 is a flow chart of a UE-1 and UE-2 setup of a voice bearer;

fig. 2 is a schematic diagram of a wireless communication system according to an embodiment of the present invention;

fig. 3 is one of the flowcharts of a method for call negotiation provided in an embodiment of the present application;

FIG. 4 is a second flowchart of a method for call negotiation according to an embodiment of the present application;

FIG. 5 is one of the flowcharts for establishing a voice bearer between UE-1 and UE-2 provided in the embodiments of the present application;

FIG. 6 is a schematic diagram of the internal processing of UE-1 in the embodiment shown in FIG. 5;

FIG. 7 is a second flowchart of establishing a voice bearer between UE-1 and UE-2 according to an embodiment of the present application;

FIG. 8 is a schematic diagram of the internal processing of UE-1 in the embodiment shown in FIG. 7;

fig. 9 is one of schematic diagrams of an apparatus for call negotiation according to an embodiment of the present application;

FIG. 10 is a second schematic diagram of a device for call negotiation according to the embodiment of the present application;

fig. 11 is a schematic diagram of a terminal provided in an embodiment of the present application;

fig. 12 is a schematic diagram of a core network device according to an embodiment of the present application;

fig. 13 is a schematic diagram of a communication device according to an embodiment of the present application.

Detailed Description

Technical solutions in the embodiments of the present application will be clearly described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application are within the scope of the protection of the present application.

The terms first, second and the like in the description and in the claims, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments of the application are capable of operation in sequences other than those illustrated or otherwise described herein, and that the terms "first" and "second" are generally intended to be used in a generic sense and not to limit the number of objects, for example, the first object may be one or more. Furthermore, in the description and claims, "and/or" means at least one of the connected objects, and the character "/" generally means a relationship in which the associated object is an "or" before and after.

It is noted that the techniques described in embodiments of the present application are not limited to long term evolution (Long Term Evolution, LTE)/LTE evolution (LTE-Advanced, LTE-a) systems, but may also be used in other wireless communication systems, such as code division multiple access (Code Division Multiple Access, CDMA), time division multiple access (Time Division Multiple Access, TDMA), frequency division multiple access (Frequency Division Multiple Access, FDMA), orthogonal frequency division multiple access (Orthogonal Frequency Division Multiple Access, OFDMA), single carrier frequency division multiple access (Single-carrier Frequency Division Multiple Access, SC-FDMA), and other systems. The terms "system" and "network" in embodiments of the present application are often used interchangeably, and the techniques described may be used for both the above-mentioned systems and radio technologies, as well as other systems and radio technologies. The following description describes a New air interface (NR) system for purposes of example and uses NR terminology in much of the description that follows, but these techniques are also applicable to applications other than NR system applications, such as generation 6 (6) ^th Generation, 6G) communication system.

Referring to fig. 1, a flow of establishing a voice bearer between UE-1 and UE-2 is illustrated, and specific steps are as follows:

step 1: UE-1 establishes a protocol data unit (Protocol Data Unit, PDU) session at a roaming network (e.g., MNO a) using a roaming session management function (Visiting Session Management Function, V-SMF).

Step 2: UE-1 initiates an IMS setup request, which is initiated by an Invite message, carrying the information of the voice media to be set up in the requested SDP, requesting to set up a voice bearer with GBR of 512kbps by b=as: 512.

Step 3: the Proxy call session control function (Proxy-Call Session Control Function, P-CSCF) sends the invite message to UE-2 through (Serving Call Session Control Function, S-CSCF).

It should be noted that, in the figure, both the P-CSCF and the S-CSCF are IMS network elements that provide services for UE-1, and the IMS network elements that provide services for UE-2 are not embodied.

Step 4: UE-2 replies to the SIP 183 message via the S-CSCF, which contains the SDP answer (answer).

Step 5: the P-CSCF sends a hypertext transfer protocol (HyperText Transfer Protocol, HTTP) notify request (request) message to a policy control function (Policy Control Function, PCF) serving the UE-1, which carries media description information (media info) negotiated through SDP, derived from an SDP answer message, containing information that requires the use of 512 kbps.

Step 6: the PCF sends a request to the Home SMF (Home-Session Management Function, H-SMF) of UE-1 requesting to establish a voice bearer, and the request carries the quality of service (Quality of Service, qoS) parameters of the voice bearer to be established, including information that GBR is 512 kbps.

Step 7: the H-SMF sends a PDU session Update Request message (e.g., nsmf_pduse_update Request message) to the V-SMF, which may include QoS parameters.

Step 8: the V-SMF determines that the GBR bearer of 512kbps cannot be supported according to the requested QoS parameters and the QoS parameters that can be supported by the V-SMF, and then the V-SMF sends a PDU session update Reject message (e.g., nsmf_pduse_reject message) to the H-SMF.

Step 9: the H-SMF sends a rejection message to the PCF, i.e., an SM policy association rejection initiated by the H-SMF (H-SMF initiated SM policy association reject).

Step 10: the PCF sends a reject message to the P-CSCF.

Step 11: the P-CSCF sends an end (Bye) message to UE-1 for rejecting the call.

Step 12: the P-CSCF sends a Bye message to UE-2 for terminating the call.

That is, when the UE-1 is in the roaming state, the UE-1 cannot dial or answer the voice due to the inconsistent home location parameter and roaming location parameter, which affects the user experience

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 device 22.

The terminal 21 may be a mobile phone, a tablet (Tablet Personal Computer), a Laptop (Laptop Computer) or a terminal-side Device called a notebook, a personal digital assistant (Personal Digital Assistant, PDA), a palm top, a netbook, an ultra-mobile personal Computer (ultra-mobile personal Computer, UMPC), a mobile internet appliance (Mobile Internet Device, MID), an augmented reality (augmented reality, AR)/Virtual Reality (VR) Device, a robot, a Wearable Device (weather Device), a vehicle-mounted Device (VUE), a pedestrian terminal (PUE), a smart home (home Device with a wireless communication function, such as a refrigerator, a television, a washing machine, or a furniture), a game machine, a personal Computer (personal Computer, PC), a teller machine, or a self-service machine, and the Wearable Device includes: intelligent wrist-watch, intelligent bracelet, intelligent earphone, intelligent glasses, intelligent ornament (intelligent bracelet, intelligent ring, intelligent necklace, intelligent anklet, intelligent foot chain etc.), intelligent wrist strap, intelligent clothing etc.. In addition to the above terminal device, the terminal related to the present application may also be a Chip in the terminal, such as a Modem (Modem) Chip, a System on Chip (SoC). Note that, the specific type of the terminal 21 is not limited in the embodiment of the present application.

The network-side device 22 may comprise an access network device or a core network device, wherein the access network device may also be referred to as a radio access network device, a radio access network (Radio Access Network, RAN), a radio access network function or a radio access network element. Access network device 12 may include a base station, a WLAN access point, a WiFi node, or the like, which may be referred to as a node B, an evolved node B (eNB), an access point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a basic service set (Basic Service Set, BSS), an extended service set (Extended Service Set, ESS), a home node B, a home evolved node B, a transmission and reception point (Transmitting Receiving Point, TRP), or some other suitable terminology in the art, and the base station is not limited to a particular technical vocabulary so long as the same technical effect is achieved, and it should be noted that in the embodiments of the present application, only a base station in an NR system is described as an example, and the specific type of the base station is not limited.

The core network device may include, but is not limited to, at least one of: 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 functions (User Plane Function, UPF), policy control functions (Policy Control Function, PCF), policy and charging rules function units (Policy and Charging Rules Function, PCRF), edge application service discovery functions (Edge Application Server Discovery Function, EASDF), unified data management (Unified Data Management, UDM), unified data repository (Unified Data Repository, UDR), home subscriber server (Home Subscriber Server, HSS), centralized network configuration (Centralized network configuration, CNC), network storage functions (Network Repository Function, NRF), network opening functions (Network Exposure Function, NEF), local NEF (or L-NEF), binding support functions (Binding Support Function, BSF), application functions (Application Function, AF), and the like. In the embodiment of the present application, only the core network device in the NR system is described as an example, and the specific type of the core network device is not limited.

The method, apparatus, communication device and readable storage medium for call negotiation provided in the embodiments of the present application are described in detail below with reference to the accompanying drawings by some embodiments and application scenarios thereof.

Referring to fig. 3, an embodiment of the present application provides a method for call negotiation, which is applied to a terminal, and specifically includes the steps of: step 301, step 302 and step 303.

Step 301: the method comprises the steps that a terminal receives a first message, wherein the first message is used for establishing a first bearing;

optionally, the first bearer includes at least one of an audio bearer and a video bearer, where the audio bearer may also be described as a voice bearer, and the first message may also be described as a voice setup request message.

As a possible implementation, the terminal receives the first message sent by the first core network device, and optionally, the first core network device may be a 4G core network device or a 5G core network device, such as an MME or a V-SMF, but is not limited thereto.

Wherein, when the first core network device is a 4G core network device, the first bearer is an evolved packet system (Evolved Packet System, EPS) bearer (bearer), and the first message may be a session management request (Session Management Request) message; when the first core network device is a 5G core network device, the first bearer may be a quality of service (Quality of Service, qoS) flow (flow) and the first message may be a PDU session modification command (PDU session modification command).

Optionally, the first message carries a parameter of the first bearer modified by the first core network device, and the first core network device may modify the parameter of the first bearer according to the parameter of the bearer supported by the first core network device.

As another possible implementation, the terminal receives a first message sent from an access network device (such as a base station), which may be a radio resource configuration connection reconfiguration (Radio Resource Configuration Connection Reconfiguration) message or a radio resource configuration reconfiguration (Radio Resource Configuration Reconfiguration) message.

Step 302: acquiring parameters of the first bearer according to the first message;

optionally, the parameters of the first bearer may include: at least one of guaranteed Bit Rate (Guaranteed Bit Rate, GBR), maximum Bit Rate (MBR). GBR refers to the minimum bit rate that needs to be guaranteed in order to support this service. MBR refers to the maximum bit rate that can be guaranteed in order to support the service, optionally GBR+.MBR.

The parameters of the first bearer may also be described as QoS parameters of the first bearer.

Step 303: and under the condition that the parameters of the first bearer are not matched with the IMS session parameters of the terminal, the terminal sends a second message, wherein the second message is used for requesting IMS session renegotiation so that the IMS session parameters are matched with 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 and the IMS session modification request may be an Update message. Both the re-Invite message and Update message are session initiation protocol (Session initialization Protocol, SIP) messages.

In the embodiment of the application, under the condition that the parameter of the first bearer is not matched with the IMS session parameter of the terminal, the terminal (for example, UE-1) can initiate an IMS session renegotiation request to a communication opposite end (for example, UE-2), so that the parameter of the first bearer is matched with the IMS session parameter, the first bearer is successfully established, the two communication parties can successfully establish audio or video communication, and the user experience is improved.

In one embodiment of the present application, in a case where the parameter of the first bearer does not match the IMS session parameter of the terminal, the terminal sends a second message, including:

The IMS layer of the terminal judges whether the parameter of the first bearing is matched with the IMS session parameter of the terminal;

and under the condition of no matching, the terminal sends a second message according to the parameters of the first bearer, for example, the second message carries IMS session parameters corresponding to the parameters of the first bearer. The IMS layer referred to in this application may also be understood as an IMS protocol layer. In one embodiment of the present application, the terminal receives a first message, including: a Non-Access-Stratum (NAS) of the terminal receives a first message;

the obtaining the parameter of the first bearer according to the first message includes:

the non-access layer of the terminal acquires the parameters of the first bearer according to the first message; and the non-access layer of the terminal delivers the parameters of the first bearer to an IMS layer.

In one embodiment of the present application, the terminal receives a first message, including: an Access Stratum (AS) of the terminal receives a first message;

the access layer of the terminal acquires 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 load to an IMS layer; and the IMS layer of the terminal acquires the parameters of the first bearer according to the access layer parameters corresponding to the first bearer.

In one embodiment of the present application, the terminal receives a first message, including: the access layer of the terminal receives a first message;

the access layer of the terminal acquires 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 bearing to a non-access layer; the non-access layer of the terminal determines 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 delivers the non-access layer parameters corresponding to the first load to the IMS layer; and the IMS layer of the terminal acquires the parameters of the first bearer according to the parameters of the non-access layer corresponding to the first bearer.

In one embodiment of the present application, the determining, by the IMS layer of the terminal, whether the parameter of the first bearer matches the IMS session parameter of the terminal includes:

the IMS layer of the terminal judges whether the absolute value of the difference value between the parameter of the first bearer and the IMS session parameter of the terminal is larger than a preset value;

Judging that the first bearer is not matched under the condition that the absolute value of the difference value between the first bearer parameter and the IMS session parameter is larger than or equal to a preset value; or,

and judging matching under the condition that the absolute value of the difference value between the parameter of the first bearer and the IMS session parameter is smaller than a preset value.

It will be appreciated that the value of the preset value is not limited and may be adjusted according to the specific situation.

In the embodiment of the application, under the condition that the parameter of the first bearer is not matched with the IMS session parameter of the terminal, the terminal can initiate an IMS session renegotiation request to the opposite communication terminal, so that the parameter of the first bearer is matched with the IMS session parameter, the first bearer is successfully established, the communication parties can successfully establish the first bearer communication, and the user experience is improved.

Referring to fig. 4, an embodiment of the present application provides a method for call negotiation, which is applied to a first core network device, where the first core network device may be a 4G core network device or a 5G core network device, such as an MME or a V-SMF, and the specific steps include: step 401, step 402, step 403, and step 404.

Step 401: the first core network equipment receives a third message, wherein the third message is used for requesting to establish a first bearing for a terminal;

For example, the first core network device receives the third message from a second core network device, which may be, but is not limited to, an H-SMF or a packet data network gateway (Packet Data Network Gateway, PGW).

The third message may be referred to as a PDU session update request message, where the message may carry parameters of the first bearer.

Step 402: the first core network device judges whether the parameters of the first bearer contained in the third message are matched with the bearer parameters supported by the first core network device;

for example, the first core network judges 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;

judging that the first load parameter and the load parameter supported by the first core network equipment are not matched under the condition that the absolute value of the difference value of the first load parameter and the load parameter supported by the first core network equipment is larger than or equal to a preset value; or,

and under the condition that the absolute value of the difference value between the first bearer parameter and the bearer parameter supported by the first core network equipment is smaller than a preset value, judging matching.

Step 403: under the condition of no matching, the first core network equipment modifies the parameters of the first bearer according to the parameters of the bearer supported by the first core network equipment;

As a possible implementation, the first core network device matches the parameter of the first bearer according to the parameter of the bearer supported by the first core network device, so that the modified parameter of the first bearer matches the parameter of the bearer supported by the first core network device, for example, an absolute value of a difference between the modified parameter of the first bearer and the parameter of the bearer supported by the first core network device is smaller than a preset value.

Step 404: the first core network device sends a first message, where the first message is used to establish the first bearer, and the first message carries the modified parameter of the first bearer.

Optionally, the first core network device sends a first message to the terminal, so that the terminal determines whether the parameter of the first bearer is matched with the IMS session parameter of the terminal, and if the parameter of the first bearer is not matched with the IMS session parameter of the terminal, the terminal may send a second message to the opposite communication terminal, where the second message is used to request IMS session renegotiation so that the IMS session parameter is matched with the parameter of the first bearer.

In one embodiment of the present application, the first bearer may include at least one of an audio bearer and a video bearer.

In one embodiment of the present application, the parameters of the first bearer may include: at least one of a guaranteed bit rate and a maximum bit rate.

In the embodiment of the present application, in the case that the parameter of the first bearer is not matched with the bearer parameter supported by the first core network device, the first core network device may modify the parameter of the first bearer according to the parameter of the bearer supported by the first core network device, and establish the first bearer according to the modified parameter of the first bearer, so that the problem that the first core network device directly refuses the first bearer establishment request due to the fact that the parameter of the first bearer is not matched with the bearer parameter supported by the first core network device can be avoided, and both communication parties can successfully establish the first bearer communication, thereby improving user experience.

Embodiments of the present application are described below in conjunction with example one and example two.

Example 1

Referring to fig. 5, the specific steps are as follows:

step 1: UE-1 establishes a PDU session at the roaming network using a roaming session management function (V-SMF) (serving-Session Management Function).

Step 2: UE-1 initiates an IMS setup request, which is initiated by an Invite message, carrying the information of the voice media to be set up in the requested protocol (Session Description Protocol, SDP) describing the session, requesting to set up a voice bearer with GBR of 512kbps by "b=as: 512".

Step 3: the P-CSCF sends the invite message to UE-2 via the S-CSCF.

Step 4: UE-2 replies to the session initiation protocol (Session initialization Protocol, SIP) 183 message via the S-CSCF, which contains the SDP answer.

Step 5: the P-CSCF sends an HTTP POST request message to the PCF that serves UE-1, carrying the media description information negotiated through SDP, derived from the SDP answer message, containing information that requires the use of 512 kbps.

Step 6: the PCF sends a request to the H-SMF of the UE-1 requesting to establish a voice bearer, wherein the request carries QoS parameters of a first bearer to be established, and the QoS parameters comprise 512kbps GBR information.

Step 7: the H-SMF sends a PDU session update request message to the V-SMF, and the message can contain QoS parameters.

Step 8: when the V-SMF judges that the request is used for establishing the first bearer and the GBR or MBR parameters of the first bearer which are required to be established are not matched with the GBR or MBR parameters which are supported by the request, the V-SMF modifies the GBR or MBR parameters in a PDU session modification command (PDU session modification command) of the first message which is sent to the UE into the parameters of the bearers which are supported by the request, and simultaneously, the V-SMF sends the GBR or MBR parameters of the modified first bearer to the AMF through a Namf_communication_N1N2MessageTransfermessage, wherein the GBR or MBR parameters of the modified first bearer are the parameters of the bearers which are supported by the V-SMF.

The first message may be a non-Access Stratum (Non Access Stratum, NAS) message, or may be an Access Stratum (AS) message.

Step 9: the AMF sends the modified GBR or MBR parameters to the base station (the next Generation Node B, gNB), and the first message sent to the UE-1 is contained in the message.

Step 10: the gNB forwards the first message sent to UE-1, and UE-1 replies with an acknowledgement message.

In step 10 the NAS layer of the UE-1 receives the first message or the AS layer of the UE-1 receives the first message.

Wherein the AS layer is used for configuring data radio bearer (Data Radio Bearer, DRB) between the UE and the gNB, and transmitting data of the UE-1 between the UE-1 and the gNB

Step 11: the gNB sends an acknowledgement message to the AMF.

Step 12: AMF sends acknowledgement message to V-SMF

Step 13: the V-SMF sends an acknowledgement message, such as an nsmf_pduse_updatesm Context message, to the H-SMF, where the message carries the GBR or MBR parameters of the modified first bearer.

Step 14: the H-SMF sends an acknowledgement message to the PCF, i.e., the H-SMF initiates SM policy association modification.

Step 15: the PCF sends an acknowledgement message, e.g., 201 a Created message, to the P-CSCF.

Step 16: the P-CSCF sends 183 a message to the UE, which 183 contains an SDP answer message containing peer-acknowledged IMS session parameters, e.g., bandwidth parameters.

Step 17-18: the communication partner (UE-2) listens to 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 parameter of the first bearer, for example, the GBR or MBR parameter, to the IMS layer, and the IMS layer of UE-1 determines whether the parameter of the first bearer matches the IMS session parameter, if not, then UE-1 initiates an IMS session renegotiation request (i.e., UE-1 sends the second message), and the IMS session parameter corresponding to the parameter of the first bearer is included in the IMS session renegotiation request, as shown in fig. 6.

For example, the IMS layer negotiates about 512kbps, the NAS layer obtains about 64kbps, and after the NAS layer transmits 64kbps to the IMS layer, the IMS layer renegotiates with the UE-2 by using 64kbps, so that both communication parties use 64kbps for communication.

Wherein the second message may be a SIP re-Invite message or a SIP update message. Step 19 may be sent before step 18 or after step 18, if sent before step 18, the UE-1 renegotiates via a SIP update message, and if sent after step 18, via a SIP re-Invite message.

Wherein GBR or MBR parameters among the parameters of the first bearer and "b" of the IMS layer: the parameters of the AS may not be consistent. The two have a corresponding relationship. For example, "b: the parameter "a rate used to describe the Real-time transport protocol (Real-time Transport Protocol, RTP) of the voice media" of the AS, the GBR or MBR parameter may be the sum of the rates used by the RTP and the Real-time transport control protocol (Real-time Transport Control Protocol, RTCP) of the voice media, where the rate used by RTCP may be a fixed value.

The IMS layer of the UE-1 judges whether the parameter of the first bearer is matched with the IMS session parameter, and comprises the following steps:

the IMS layer judges that the absolute value of the difference value between the first bearing parameter and the IMS session parameter is larger than a preset value, and judges that the first bearing parameter and the IMS session parameter are not matched; and when the IMS layer judges that the absolute value of the difference value between the parameter of the first bearer and the IMS session parameter is smaller than a preset value, judging that the parameters are matched.

Step 20: the UE-1 sends a second message, and the second message contains IMS parameters corresponding to the parameters of the first bearing.

Step 21: the second message is sent to UE-2.

Step 22-23: the UE-2 replies a 200OK message carrying the result of the IMS session renegotiation.

In the embodiment of the application, under the condition that the parameter of the first bearer is not matched with the IMS session parameter of the UE-1, the UE-1 can initiate an IMS session renegotiation request to the UE-2, so that the parameter of the first bearer is matched with the IMS session parameter, the first bearer is successfully established, the UE-1 and the UE-2 can successfully establish audio or video communication, and the user experience is improved.

Example two

Referring to fig. 7, the specific steps are as follows:

step 1-7: reference may be made to the description of steps 1-7 in fig. 5.

Step 8: when the V-SMF judges that the request is used for establishing the first bearer and the GBR or MBR parameters of the first bearer which are required to be established are not matched with the GBR or MBR parameters of the bearer which is supported by the request, the V-SMF modifies the GBR or MBR parameters of the first bearer which are sent to the gNB into the parameters of the bearer which is supported by the request, the V-SMF sends a first message, and the first message carries the GBR or MBR parameters of the modified first bearer.

The V-SMF does not send the modified parameters of the first bearer to the NAS layer of UE-1, unlike embodiment 1.

Step 9: the AMF sends the modified parameters of the first bearer to the gNB, and the first message sent to the UE is contained in the message at the same time.

Step 10: the gNB forwards the first message sent to the UE-1, and the UE-1 replies with a confirmation message

Step 11-18: reference may be made to the description of steps 11-18 in fig. 5.

Step 19: the AS layer of the UE-1 receives a first message for establishing a first bearer, for example, a RRC reconfiguration message, wherein the first message contains AS layer parameters corresponding to the first bearer, for example, a priority bit rate (priority bit rate);

AS shown in fig. 8, the AS layer of the ue-1 sends AS layer parameters to the IMS layer, and the IMS layer determines whether the parameters of the first bearer are matched with IMS session parameters according to the AS layer parameters; or,

the AS layer of the UE-1 sends AS layer parameters to an NAS layer, the NAS obtains GBR or MBR parameters according to the AS layer parameters, the NAS layer sends the NAS layer parameters to an IMS layer, and the IMS layer judges whether the parameters of the first bearing are matched with IMS session parameters according to the NAS layer parameters.

If the IMS layer judges that the parameter of the first bearer is not matched with the IMS session parameter, the UE-1 initiates an IMS session renegotiation request, and the session renegotiation request contains the IMS session parameter corresponding to the parameter of the voice bearer.

Step 20: the UE-1 sends a second message, and the second message contains IMS session parameters corresponding to the parameters of the first bearer.

Step 21: the second message is sent to UE-2.

Step 22-23: the UE-2 replies 200OK, carrying the result of IMS session renegotiation.

Referring to fig. 9, an embodiment of the present application provides a device for call negotiation, applied to a terminal, and the device 900 includes:

a first receiving module 901, configured to receive a first message, where the first message is used to establish a first bearer;

an obtaining module 902, configured to obtain parameters of the first bearer according to the first message;

a first sending module 903, configured to send a second message when the parameter of the first bearer does not match the MS session parameter of the terminal, where the second message is used to request IMS session renegotiation so that the IMS session parameter matches the parameter of the first bearer.

In one embodiment of the present application, the first sending module 903 is further configured to: judging whether the parameter of the first load is matched with the IMS session parameter of the terminal or not through an IMS layer; and if the parameters of the first bearer are not matched, sending a second message according to the parameters of the first bearer.

In one embodiment of the present application, the first receiving module 901 is further configured to: receiving a first message through a non-access stratum;

the acquisition module 902 is further configured to: acquiring parameters of the first bearer according to the first message through a non-access layer; and delivering the parameters of the first bearer to an IMS layer through a non-access layer.

In one embodiment of the present application, the first receiving module 901 is further configured to: receiving a first message through an access layer;

the acquisition module 902 is further configured to: acquiring an access layer parameter corresponding to the first bearer according to the first message through an access layer; delivering the access layer parameters corresponding to the first load to an IMS layer through an access layer; and acquiring the parameters of the first bearer according to the access layer parameters corresponding to the first bearer through an IMS layer.

The acquisition module 902 is further configured to: acquiring an access layer parameter corresponding to the first bearer according to the first message through an access layer; delivering the access layer parameters corresponding to the first bearer to a non-access layer through an access layer; determining non-access layer parameters corresponding to the first bearer according to the access layer parameters corresponding to the first bearer through a non-access layer; delivering non-access layer parameters corresponding to the first bearer to the IMS layer through a non-access layer; and acquiring the parameters of the first bearer according to the non-access layer parameters corresponding to the first bearer through an IMS layer.

In one embodiment of the present application, the first sending module 903 is further configured to: judging whether the absolute value of the difference value between the parameter of the first bearer and the IMS session parameter of the terminal is larger than a preset value or not through an IMS layer; judging that the first bearer is not matched under the condition that the absolute value of the difference value between the first bearer parameter and the IMS session parameter is larger than or equal to a preset value; or, if the absolute value of the difference between the parameter of the first bearer and the IMS session parameter is smaller than a preset value, determining that the first bearer and the IMS session parameter are matched.

In one embodiment of the present application, the first receiving module 901 is further configured to: and receiving a first message sent by first core network equipment, wherein the first message is a session management request message or a protocol data unit session modification command.

In one embodiment of the present application, the first receiving module 901 is further configured to: and receiving a first message sent by access network equipment, wherein the first message is radio resource configuration connection reconfiguration or radio resource configuration reconfiguration message.

In one embodiment of the present application, the first bearer comprises at least one of an audio bearer and a video bearer.

In one embodiment of the present application, the second message carries IMS session parameters corresponding to the parameters of the first bearer.

In one embodiment of the present application, the parameters of the first bearer include: at least one of a guaranteed bit rate and a maximum bit rate.

The device provided in this embodiment of the present application can implement each process implemented by the method embodiment of fig. 3, and achieve the same technical effects, so that repetition is avoided, and details are not repeated here.

Referring to fig. 10, an embodiment of the present application provides an apparatus for call negotiation, applied to a first core network device, where the apparatus 1000 includes:

a second receiving module 1001, configured to receive a third message, where the third message is used to request that a first bearer be established for a terminal;

a judging module 1002, configured to judge whether a parameter of the first bearer included in the third message is matched with a bearer parameter supported by the first core network device;

A modifying module 1003, configured to modify, by the first core network device, parameters of the first bearer according to parameters of a bearer supported by the first core network device, where the parameters are not matched;

a second sending module 1004, configured to send a first message to the terminal, where the first message carries the modified parameter of the first bearer.

In one embodiment of the present application, the first core network device includes: a mobility management entity or a roaming session management function.

The device provided in this embodiment of the present application can implement each process implemented by the method embodiment of fig. 4, and achieve the same technical effects, so that repetition is avoided, and details are not repeated here.

Fig. 11 is a schematic hardware structure of a terminal implementing an embodiment of the present application. The terminal 1100 includes, but is not limited to: at least part of the components of the radio frequency unit 1101, the network module 1102, the audio output unit 1103, the input unit 1104, the sensor 1105, the display unit 1106, the user input unit 1107, the interface unit 1108, the memory 1109, and the processor 1110, etc.

Those skilled in the art will appreciate that the terminal 1100 may further include a power source (e.g., a battery) for powering the various components, and that the power source may be logically coupled to the processor 1110 by a power management system so as to perform functions such as managing charging, discharging, and power consumption by the power management system. The terminal structure shown in fig. 11 does not constitute a limitation of the terminal, and the terminal may include more or less components than shown, or may combine some components, or may be arranged in different components, which will not be described in detail herein.

It should be appreciated that in embodiments of the present application, the input unit 1104 may include a graphics processing unit (Graphics Processing Unit, GPU) 11041 and a microphone 11042, the graphics processor 11041 processing image data of still pictures or video obtained by an image capturing device (e.g., a camera) in a video capturing mode or an image capturing mode. The display unit 1106 may include a display panel 11061, and the display panel 11061 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 507 includes at least one of a touch panel 11071 and other input devices 11072. The touch panel 11071 is also referred to as a 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, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and so forth, which are not described in detail herein.

In this embodiment, after receiving downlink data from the network side device, the radio frequency unit 1101 may transmit the downlink data to the processor 1110 for processing; in addition, the radio frequency unit 1101 may send uplink data to the network side device. Typically, the radio frequency unit 1101 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.

Memory 1109 may be used to store software programs or instructions and various data. The memory 1109 may mainly include a first memory area storing programs or instructions and a second memory area storing data, wherein the first memory area may store an operating system, application programs or instructions (such as a sound playing function, an image playing function, etc.) required for at least one function, and the like. Further, the memory 1109 may include volatile memory or nonvolatile memory, or the memory 1109 may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM), static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (ddr SDRAM), enhanced SDRAM (Enhanced SDRAM), synchronous DRAM (SLDRAM), and Direct RAM (DRRAM). Memory 1109 in embodiments of the present application includes, but is not limited to, these and any other suitable types of memory.

Processor 1110 may include one or more processing units; optionally, the processor 1110 integrates an application processor that primarily processes operations involving an operating system, user interface, application programs, and the like, and a modem processor that primarily processes wireless communication signals, such as a baseband processor. It will be appreciated that the modem processor described above may not be integrated into the processor 1110.

The terminal provided in this embodiment of the present application can implement each process implemented by the method embodiment of fig. 3, and achieve the same technical effects, so that repetition is avoided, and details are not repeated here.

Referring to fig. 12, fig. 12 is a block diagram of a communication device to which an embodiment of the present invention is applied, and as shown in fig. 12, a communication device 1200 includes: processor 1201, transceiver 1202, memory 1203, and bus interface, where processor 501 may be responsible for managing the bus architecture and general processing. The memory 1203 may store data used by the processor 1201 in performing operations.

In one embodiment of the present invention, the communication device 1200 further comprises: a program stored in the memory 1203 and executable on the processor 1201, which when executed by the processor 1201, performs the steps in the method shown in fig. 3 above.

In fig. 12, a bus architecture may be comprised of any number of interconnected buses and bridges, and in particular, one or more processors represented by the processor 1201 and various circuits of memory represented by the memory 1203. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. The transceiver 1202 may be a number of elements, i.e., include a transmitter and a receiver, providing a means for communicating with various other apparatus over a transmission medium.

Optionally, as shown in fig. 13, the embodiment of the present application further provides a communication device 1300, including a processor 1301 and a memory 1302, where the memory 1302 stores a program or an instruction that can be executed on the processor 1301, for example, when the communication device 1300 is a terminal, the program or the instruction is executed by the processor 1301 to implement each step of the method embodiment of fig. 3, and when the communication device 1300 is a core network device, the program or the instruction is executed by the processor 1301 to implement each step of the method embodiment of fig. 4 and achieve the same technical effect, which is not repeated herein.

The embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored, where the program or the instruction implements the method of fig. 3 or fig. 4 and each process of each embodiment described above when executed by a processor, and the same technical effects can be achieved, so that repetition is avoided, and no further description is given here.

Wherein the processor is a processor in the terminal described in the above embodiment. The readable storage medium includes computer readable storage medium such as computer readable memory ROM, random access memory RAM, magnetic or optical disk, etc.

The embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to run a program or an instruction, implement each process of each method embodiment shown in fig. 3 or fig. 4 and described above, and achieve the same technical effect, so that repetition is avoided, and no further description is provided herein.

It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, or the like.

The embodiments of the present application further provide a computer program/program product stored in a storage medium, where the computer program/program product is executed by at least one processor to implement the respective processes of the respective method embodiments shown in fig. 3 or fig. 4 and described above, and achieve the same technical effects, and are not repeated herein.

The embodiment of the present application further provides a communication system, where the communication system includes a terminal and a network side device, the terminal is configured to execute each process of the embodiments of the method as shown in fig. 3 and described above, and the network side device is configured to execute each process of the embodiments of the method as shown in fig. 4 and described above, and the same technical effects can be achieved, so that repetition is avoided, and no further description is given here.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Furthermore, it should be noted that the scope of the methods and apparatus in the embodiments of the present application is not limited to performing the functions in the order shown or discussed, but may also include performing the functions in a substantially simultaneous manner or in an opposite order depending on the functions involved, e.g., the described methods may be performed in an order different from that described, and various steps may also be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solutions of the present application may be embodied essentially or in a part contributing to the prior art in the form of a computer software product stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk), comprising several instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method described in the embodiments of the present application.

The embodiments of the present application have been described above with reference to the accompanying drawings, but the present application is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those of ordinary skill in the art without departing from the spirit of the present application and the scope of the claims, which are also within the protection of the present application.

Claims

1. A method of call negotiation, comprising:

acquiring parameters of the first bearer according to the first message;

2. The method according to claim 1, wherein in case the parameters of the first bearer do not match the IMS session parameters of the terminal, the terminal sends a second message comprising:

and under the condition of no matching, the terminal sends a second message according to the parameters of the first bearer.

3. The method of claim 2, wherein the terminal receiving the first message comprises:

the non-access layer of the terminal receives a first message;

The non-access layer of the terminal acquires the parameters of the first bearer according to the first message;

and the non-access layer of the terminal delivers the parameters of the first bearer to an IMS layer.

4. The method of claim 2, wherein the terminal receiving the first message comprises:

the access layer of the terminal receives a first message;

the access layer of the terminal acquires 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 load to an IMS layer;

and the IMS layer of the terminal acquires the parameters of the first bearer according to the access layer parameters corresponding to the first bearer.

5. The method of claim 2, wherein the terminal receiving the first message comprises:

the access layer of the terminal receives a first message;

the access layer of the terminal delivers the access layer parameters corresponding to the first bearing to a non-access layer;

The non-access layer of the terminal determines 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 delivers the non-access layer parameters corresponding to the first load to the IMS layer;

and the IMS layer of the terminal acquires the parameters of the first bearer according to the parameters of the non-access layer corresponding to the first bearer.

6. The method according to claim 2 or 3 or 4 or 5, wherein the IMS layer of the terminal determines whether the parameter of the first bearer matches the IMS session parameter of the terminal, comprising:

7. The method according to any of claims 1 to 5, wherein the terminal receives the first message, comprising:

the terminal receives a first message sent by first core network equipment, wherein the first message is a session management request message or a protocol data unit session modification command.

8. The method according to any of claims 1 to 5, wherein the terminal receives the first message, comprising:

the terminal receives a first message sent by access network equipment, wherein the first message is radio resource configuration connection reconfiguration or radio resource configuration reconfiguration message.

9. The method of any of claims 1-5, wherein the first bearer comprises at least one of an audio bearer and a video bearer.

10. The method according to any of claims 1 to 5, wherein the second message carries IMS session parameters corresponding to parameters of the first bearer.

11. The method according to any of claims 1 to 5, wherein the parameters of the first bearer comprise: at least one of a guaranteed bit rate and a maximum bit rate.

12. A device for call negotiation, applied to a terminal, comprising:

13. The apparatus of claim 12, wherein the first transmission module is further configured to: judging whether the parameter of the first load is matched with the IMS session parameter of the terminal or not through an IMS layer; and if the parameters of the first bearer are not matched, sending a second message according to the parameters of the first bearer.

14. The apparatus of claim 12, wherein the first receiving module is further configured to: receiving a first message through a non-access stratum;

the acquisition module is further to: acquiring parameters of the first bearer according to the first message through a non-access layer; and delivering the parameters of the first bearer to an IMS layer through a non-access layer.

15. The apparatus of claim 12, wherein the first receiving module is further configured to: receiving a first message through an access layer;

the acquisition module is further to: acquiring an access layer parameter corresponding to the first bearer according to the first message through an access layer; delivering the access layer parameters corresponding to the first load to an IMS layer through an access layer; and acquiring the parameters of the first bearer according to the access layer parameters corresponding to the first bearer through an IMS layer.

16. The apparatus of claim 12, wherein the first receiving module is further configured to: receiving a first message through an access layer;

the acquisition module is further to: acquiring an access layer parameter corresponding to the first bearer according to the first message through an access layer; delivering the access layer parameters corresponding to the first bearer to a non-access layer through an access layer; determining non-access layer parameters corresponding to the first bearer according to the access layer parameters corresponding to the first bearer through a non-access layer; delivering non-access layer parameters corresponding to the first bearer to an IMS layer through a non-access layer; and acquiring the parameters of the first bearer according to the non-access layer parameters corresponding to the first bearer through an IMS layer.

17. The apparatus of claim 12, wherein the first transmission module is further configured to: judging whether the absolute value of the difference value between the parameter of the first bearer and the IMS session parameter of the terminal is larger than a preset value or not through an IMS layer; judging that the first bearer is not matched under the condition that the absolute value of the difference value between the first bearer parameter and the IMS session parameter is larger than or equal to a preset value; or, if the absolute value of the difference between the parameter of the first bearer and the IMS session parameter is smaller than a preset value, determining that the first bearer and the IMS session parameter are matched.

18. A communication device comprising a processor, a memory and a program or instruction stored on the memory and executable on the processor, which program or instruction when executed by the processor implements the steps of the method according to any of claims 1 to 11.

19. A readable storage medium, characterized in that it stores thereon a program or instructions which, when executed by a processor, implement the steps of the method according to any of claims 1 to 11.