Communication method and related apparatus
UEs accessed via NB-IoT use the default bearer to transmit IMS data, which solves the problem that NB-IoT UEs cannot establish a dedicated bearer, and realizes support for IMS services and improves data transmission efficiency.
Patent Information
- Application Number
- PCT/CN2026/092142
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-08
- Filing Date
- 2026-04-22
- Publication Date
- 2026-11-12
AI Technical Summary
UEs connected via NB-IoT have weak terminal capabilities and do not support the establishment of dedicated bearers, which prevents them from making IMS calls.
After receiving the message indicating the establishment of a dedicated bearer through the first network element, it flexibly replies with the second message and uses the default bearer of the terminal device to transmit IMS data, thus avoiding the dedicated bearer establishment process.
Ensuring that UEs connected to NB-IoT can support IMS services avoids the waste of resources in establishing dedicated bearers and improves the reliability and efficiency of data transmission.
Smart Images

Figure CN2026092142_12112026_PF_FP_ABST
Abstract
Description
A communication method and related apparatus
[0001] This application claims priority to Chinese Patent Application No. 202510597093.9, filed on May 8, 2025, with the China National Intellectual Property Administration, entitled “A Communication Method and Related Device”, the entire contents of which are incorporated herein by reference. Technical Field
[0002] This application relates to the field of wireless communication technology, and in particular to a communication method and related apparatus. Background Technology
[0003] The Internet Protocol Multimedia Subsystem (IMS) is a network architecture that provides voice and multimedia services over an IP network. It can meet the needs of end customers for newer and more diverse multimedia services. For example, user equipment (UE) can be used to make or receive calls. The specific process may include the IMS registration process and the IMS call setup process.
[0004] Because the IMS data (e.g., voice data) transmitted during an IMS call needs to meet certain quality of service (QoS) requirements, a dedicated bearer needs to be established in the existing IMS call setup process, whether it is the UE that initiates the IMS call (i.e., the calling UE) or the UE that receives the IMS call (i.e., the called UE). However, for UEs accessing the network through Narrowband Internet of Things (NB-IoT), the terminal capabilities are weak and do not support the establishment of a dedicated bearer, which makes it impossible for them to make IMS calls based on the existing IMS process.
[0005] Therefore, ensuring that UEs accessed via NB-IoT support IMS services is a technical problem that urgently needs to be solved by those in the field. Summary of the Invention
[0006] This application provides a communication method and related apparatus that can ensure that a UE accessed via NB-IoT supports IMS services.
[0007] The present application is described below from different aspects. It should be understood that the different implementation methods and beneficial effects described below can be referenced from each other.
[0008] In a first aspect, embodiments of this application provide a communication method, the method comprising: a first network element receiving a first message from a second network element, the first message being used to indicate the establishment of a dedicated bearer for a terminal device, the terminal device supporting Internet Protocol Multimedia Subsystem (IMS) service and not supporting the transmission of IMS data using a dedicated bearer; the first network element sending a second message to the second network element, the second message being a reply message to the first message, or the second message being used to indicate a default bearer for the terminal device, the default bearer being used to transmit IMS data, or the second message being used to indicate a refusal to establish a dedicated bearer, or the second message being used to indicate an update to the default bearer for the terminal device, the updated default bearer being used to transmit IMS data.
[0009] Here, the first network element can be understood as the network element that decides to refuse to continue the dedicated bearer establishment process when it receives a dedicated bearer establishment instruction for IMS services. It can be a core network element or a terminal device; this will not be limited here. For example, if the first network element is a core network element, it could be a policy management network element, a gateway (e.g., a service network element / public data network gateway), or a mobility management network element. If the first network element is a terminal device, it can be understood as a terminal, or a component within the terminal (e.g., a module, communication module, circuit or chip responsible for communication functions (such as a modem chip, also known as a baseband chip, or a system-on-a-chip (SoC) chip or system-in-package (SIP) chip containing a modem core), a chip system, or a processor), or it could be a logical node, logical module, or software that implements all or part of the communication device functions.
[0010] The first message is used to instruct the establishment of a dedicated bearer for the terminal device. It can also be understood that the first message can be used to instruct the network element to authorize resources, or to instruct the authorization of quality of service resources, or to instruct the authorization of resources for the session, or to instruct the resources necessary for the authorization of the session. There will be no limitation on it here.
[0011] In this application, after receiving the first message, the first network element does not continue the dedicated bearer establishment process. Instead, it flexibly replies with a second message based on the actual situation of the terminal device's default bearer. The content of the second message relates to whether the terminal device's default bearer supports IMS data transmission. For example, if the terminal device's default bearer does not support IMS data transmission, the second message can update the terminal device's default bearer to enable IMS data transmission. If the terminal device supports IMS data transmission, the second message can instruct that the terminal device's default bearer be used directly for subsequent IMS data transmission. In other words, after receiving the dedicated bearer establishment instruction, the first network element does not need to establish a dedicated bearer for the terminal device. Instead, it uses the terminal device's default bearer to transmit IMS data. Therefore, for the terminal device, whether it is a terminal device whose terminal capability does not support establishing a dedicated bearer (e.g., a UE accessed via NB-IoT) or a terminal device whose dedicated bearer is occupied, the effect of transmitting IMS data through the default bearer without establishing a dedicated bearer can be achieved, thereby effectively ensuring its support for IMS services.
[0012] In conjunction with the first aspect, in one possible implementation, before the first network element sends the second message to the second network element, the method further includes the first network element determining that the terminal device supports Internet Protocol Multimedia Subsystem (IMS) services and determining that the terminal device does not support the use of dedicated bearers to transmit IMS data.
[0013] In conjunction with the first aspect, in one possible implementation, the first network element determines that the terminal device does not support the transmission of IMS data using a dedicated bearer, including: the first network element determines that the dedicated bearer of the terminal device is occupied; or, the first network element determines that the terminal device does not support the establishment of a dedicated bearer; or, the first network element determines that the terminal device supports the transmission of IMS data via a default bearer or supports the transmission of IMS data without a dedicated bearer. The methods for determining the first network element are quite diverse and have strong applicability.
[0014] Among them, the dedicated bearer of the terminal equipment is occupied: its alternative description can also be: the dedicated bearer of the terminal equipment can support the transmission of data corresponding to other services besides IMS services.
[0015] Among them, the first network element determines that the terminal device does not support the establishment of a dedicated bearer, including: the first network element determines that the access method of the terminal device belongs to narrowband IoT access.
[0016] For example, the first network element may receive first indication information from the third network element, the first indication information being used to indicate any one or more of the following: the dedicated bearer of the terminal device is occupied, or the terminal device does not support the establishment of a dedicated bearer; then, the first network element determines that the terminal device does not support the use of a dedicated bearer to transmit IMS data, including: determining, based on the first indication information, that the terminal device does not support the use of a dedicated bearer to transmit IMS data.
[0017] In the above implementation, the basis for the first network element to determine that the terminal device does not support the use of dedicated bearers to transmit IMS data is the first indication information sent by the third network element. The entire process does not require the first network element to determine itself, thereby effectively saving the first network element's resource computing power.
[0018] For example, the first network element can receive second indication information from the third network element, the second indication information being used to indicate that the terminal device supports or authorizes IMS services; determining that the terminal device supports Internet Protocol Multimedia Subsystem (IMS) services includes: determining that the terminal device supports IMS services based on the second indication information.
[0019] In the above implementation, the basis for the first network element to determine whether the terminal device supports Internet Protocol Multimedia Subsystem (IMS) service is the second indication information sent by the third network element. The entire process does not require the first network element to determine itself, thereby effectively saving the first network element's resource computing power.
[0020] It is understood that the first and second indication information here can be in the same message or in different messages, and this will not be limited here. For example, the first indication information can be carried in a connection request (e.g., attach / PDN connection request) or a session creation request (e.g., create session request), and the second indication information can be carried in a session creation request (e.g., create session request) or a session creation response (e.g., IP-CAN session establish response).
[0021] In conjunction with the first aspect, in one possible implementation, the second message is used to indicate the default bearer of the terminal device. The default bearer is used to transmit IMS data, and includes: the default bearer of the terminal device does not include or has not been assigned a service flow template, or the service flow template assigned to the default bearer includes: a wildcard, or an address / domain name used for transmitting IMS data. In the above implementation, by limiting the setting of the service flow template of the terminal device's default bearer, it is ensured that data packets will not be dropped due to filtering when using the default bearer to transmit IMS data subsequently. Furthermore, the configuration method of the terminal device's default bearer is quite diverse, possibly any of the above methods, making it highly applicable.
[0022] In conjunction with the first aspect, in one possible implementation, the second message is used to indicate the default bearer of the terminal device; the second message includes a bearer identifier of the default bearer of the terminal device or third indication information, the third indication information being used to indicate the use of the default bearer of the terminal device. In the above implementation, the second message carries a variety of information, has strong applicability, and by indicating the default bearer of the terminal device through the bearer identifier of the default bearer or the third indication information, it can also effectively improve the reliability of data transmission.
[0023] For example, the bearer identifier is also used to set the transmission parameters of IMS data, such as setting the encoding and decoding algorithm corresponding to the IMS data to a low rate.
[0024] In conjunction with the first aspect, in one possible implementation, the second message is used to indicate a refusal to establish a dedicated bearer; the second message includes third indication information, which indicates that the dedicated bearer of the terminal device is occupied, or that the third indication information indicates that the terminal device does not support the establishment of a dedicated bearer. In the above implementation, the information carried by the third message is quite diverse and has strong applicability.
[0025] In conjunction with the first aspect, in one possible implementation, the first message includes an address / domain name for transmitting IMS data, and the second message indicates an update to the default bearer of the terminal device. The second message includes a first service flow template, which in turn includes an address / domain name. In this implementation, the first message received by the first network element includes an address / domain name for transmitting IMS data, and the first service flow template in the second message sent by the first network element includes an address / domain name. This can be understood as the first network element having updated the service flow template of the terminal device's default bearer based on the address / domain name, thereby improving the efficiency of subsequent default bearer updates.
[0026] In conjunction with the first aspect, in one possible implementation, after the first network element receives the first message from the second network element, the method further includes: the first network element does not send a bearer establishment request to the third network element, whereby the bearer establishment request is used to instruct the establishment of a dedicated bearer for the terminal equipment. In the above implementation, the first network element no longer needs to interact with the third network element, thereby reducing data transmission overhead.
[0027] The statement that the first network element does not send a bearer establishment request to the third network element can be understood as: the first network element does not send Quality of Service (QoS) parameters to the third network element, or the first network element does not send Policy and Charging Control (PCC) rules to the third network element. PCC rules can be understood as information used to indicate policies, specifically including QoS parameters and identification information of the services using those QoS parameters (e.g., IP 5-tuples, 3-tuples, etc.).
[0028] In conjunction with the first aspect, in one possible implementation, if the default bearer of the terminal device does not support the transmission of IMS data, after the first network element receives the first message from the second network element, the method further includes: the first network element sending a third message to the third network element, the third message indicating the use or updating of the default bearer of the terminal device; the first network element receiving a fourth message from the third network element, the fourth message indicating that the default bearer of the terminal device has been updated, or indicating a refusal to establish a dedicated bearer, or indicating an update to the default bearer of the terminal device. In this implementation, the first network element updates the default bearer of the terminal device through interaction with the third network element, enabling the updated default bearer to transmit IMS data, thereby ensuring that the terminal device (e.g., a UE accessed via NB-IoT) supports IMS services.
[0029] For example, the third message is used to indicate the use of the default bearer of the terminal device; the third message may or may not include the quality of service (QoS) parameters of the default bearer. In this implementation, the third message sent by the first network element to the third network element does not include the QoS parameters of the dedicated bearer, so that the third network element will no longer trigger the dedicated bearer creation process.
[0030] For example, the third message is used to instruct the terminal device to update the default bearer; the third message includes an address / domain name for transmitting IMS data, and the address / domain name is used to update the service flow template of the terminal device's default bearer.
[0031] For example, the default bearer of the terminal device does not support the transmission of IMS data. The first message includes an address / domain name for transmitting IMS data. The third message is used to indicate the update of the default bearer of the terminal device, including: the third message includes an identifier of the default bearer of the terminal device and a first service flow template, the first service flow template is used to update the default bearer of the terminal device, and the first service flow template includes an address / domain name.
[0032] For example, the fourth message is used to indicate that the default bearer of the terminal device has been updated, including: the fourth message includes the bearer identifier of the default bearer of the terminal device or the fourth indication information, which is used to indicate the use of the default bearer of the terminal device.
[0033] For example, the fourth message is used to indicate that the establishment of a dedicated bearer is refused, including: the fourth message includes fourth indication information, which indicates that the dedicated bearer of the terminal device is occupied, or the fourth indication information indicates that the terminal device does not support the establishment of a dedicated bearer.
[0034] For example, the fourth message is used to instruct the default bearer of the terminal device to be updated. The fourth message includes a first service flow template, which includes an address / domain name for transmitting IMS data.
[0035] In the above implementation methods, the third and fourth messages carry a wide variety of content and have strong applicability.
[0036] In conjunction with the first aspect, in one possible implementation, the method further includes: the first network element sending bearer configuration information to the third network element, wherein the bearer configuration information is used to indicate that the default bearer does not include or has not been allocated a service flow template, or the bearer configuration information is used to indicate that the service flow template allocated for the default bearer includes: a wildcard, or an address / domain name used for transmitting IMS data.
[0037] In conjunction with the first aspect, in one possible implementation, the method further includes: the first network element receiving bearer configuration information from the second network element, the bearer configuration information being used to indicate that the default bearer does not include or has not been assigned a service flow template, or the bearer configuration information being used to indicate that the service flow template assigned to the default bearer includes: a wildcard, or an address / domain name for transmitting IMS data.
[0038] In conjunction with the first aspect, in one possible implementation, the method further includes: the first network element sending bearer configuration information to the terminal device, the bearer configuration information being used to indicate that the default bearer does not include or has not been allocated a service flow template, or the bearer configuration information being used to indicate that the service flow template allocated for the default bearer includes: a wildcard, or an address / domain name used for transmitting IMS data.
[0039] The above implementation methods carry a variety of configuration information, and the default bearer of the terminal device can be configured to any of the above situations, making it highly applicable.
[0040] In conjunction with the first aspect, in one possible implementation, if the first network element is a terminal device, the method further includes: the terminal device does not establish a dedicated bearer for the terminal device.
[0041] In conjunction with the first aspect, in one possible implementation, the default bearer of the terminal device does not support the transmission of IMS data. The first message includes a first service flow template, which includes an address / domain name for transmitting IMS data. The method further includes: the terminal device updating the service flow template of its default bearer to the first service flow template. This implementation ensures that the terminal device supports IMS services.
[0042] In conjunction with the first aspect, in one possible implementation, the method further includes: the terminal device sending a session invitation message to the fifth network element; the terminal device receiving a response message from the fifth network element, the response message being a reply to the session invitation message. For example, the response message can be used to instruct the terminal device not to update or establish a bearer, or it can instruct the terminal device to reply with a feedback message in response to the response message, or it can instruct the terminal device to reply with a feedback message in the absence of a dedicated bearer; the terminal device then sends a feedback message in response to the response message to the fifth network element. According to this implementation, upon receiving the response message, the terminal device does not need to wait but immediately replies with a feedback message, thereby improving the timeliness of the terminal device's response.
[0043] The session invitation message can be used to request a terminal device to make an IMS call with another terminal device, or it can be used to instruct a terminal device to initiate an IMS call, or it can be used to instruct the calling UE to initiate an IMS call.
[0044] Secondly, embodiments of this application provide a communication method, the method comprising: a second network element sending a first message to a first network element, the first message being used to indicate the establishment of a dedicated bearer for a terminal device, the terminal device supporting IMS service and not supporting the transmission of IMS data using a dedicated bearer; the second network element receiving a second message from the first network element, the second message being a reply message to the first message, or the second message being used to indicate a default bearer for the terminal device, the default bearer being used to transmit IMS data, or the second message being used to indicate a refusal to establish a dedicated bearer, or the second message being used to indicate an update to the default bearer for the terminal device, the updated default bearer being used to transmit IMS data.
[0045] In this application, after the second network element sends a dedicated bearer establishment instruction to the first network element, the second network element can receive a second message from the first network element. According to the second message, the terminal device does not use the dedicated bearer to transmit IMS data, but instead uses the default bearer. Therefore, for the terminal device, whether it is a terminal device whose terminal capability does not support the establishment of a dedicated bearer (e.g., a UE accessing via NB-IoT) or a terminal device whose dedicated bearer is occupied, the effect of transmitting IMS data through the default bearer without establishing a dedicated bearer can be achieved, thereby effectively ensuring its support for IMS services.
[0046] In conjunction with the second aspect, in one possible implementation, the default bearer is used to transmit IMS data, including: the default bearer of the terminal device does not include or has not been assigned a service flow template, or the service flow template assigned to the default bearer includes: wildcards, or addresses / domain names used to transmit IMS data.
[0047] In conjunction with the second aspect, in one possible implementation, the second message is used to indicate the default bearer of the terminal device; the second message includes a bearer identifier of the default bearer of the terminal device or third indication information, the third indication information being used to indicate the use of the default bearer of the terminal device.
[0048] For example, the bearer identifier is also used to set the transmission parameters of IMS data.
[0049] In conjunction with the second aspect, in one possible implementation, the second message is used to indicate that the establishment of a dedicated bearer is refused; the second message includes third indication information, which indicates that the dedicated bearer of the terminal device is occupied, or that the third indication information indicates that the terminal device does not support the establishment of a dedicated bearer.
[0050] In conjunction with the second aspect, in one possible implementation, the first message includes an address / domain name for transmitting IMS data, and the second message updates the default bearer of the terminal device. The second message includes a first service flow template, which also includes the address / domain name. After the second network element receives the second message from the first network element, the method further includes: the second network element sending a response message to the terminal device containing a session invitation message, which includes the first service flow template. In this implementation, the second network element sends the first service flow template to the terminal device via a response message, rather than through sequential interaction between core network elements. This effectively reduces signaling interaction between network elements, saving resources consumed during signaling transmission and improving the efficiency of the IMS call setup process.
[0051] In conjunction with the second aspect, in one possible implementation, the method further includes: the second network element sending a response message to the terminal device for the session invitation message, wherein the response message is used to instruct the terminal device not to update or establish a bearer, or the response message is used to instruct the terminal device to reply with a feedback message in response to the response message, or the response message is used to instruct the terminal device to reply with a feedback message in response to the response message without establishing a dedicated bearer.
[0052] In conjunction with the second aspect, in one possible implementation, before the second network element sends the first message to the first network element, the method further includes: the second network element receiving a fifth message from the fourth network element, the fifth message indicating the establishment of a dedicated bearer for the terminal device. After receiving the second message from the first network element, the second network element sends a sixth message to the fourth network element, the sixth message being a reply to the fifth message; or, the sixth message indicating the default bearer for the terminal device, the default bearer being used to transmit IMS data; or, the sixth message indicating a refusal to establish a dedicated bearer; or, the sixth message indicating an update to the default bearer for the terminal device, the updated default bearer being used to transmit IMS data.
[0053] In conjunction with the second aspect, in one possible implementation, the method further includes: the second network element sending bearer configuration information to the first network element, wherein the bearer configuration information is used to indicate that the default bearer does not include or has not been allocated a service flow template, or the bearer configuration information is used to indicate that the service flow template allocated for the default bearer includes: a wildcard, or an address / domain name used for transmitting IMS data.
[0054] In conjunction with the second aspect, in one possible implementation, before the second network element sends the first message to the first network element, the method further includes: the second network element receiving a third message from the third network element, the third message indicating the establishment of a dedicated bearer for the terminal device. After receiving the second message from the first network element, the second network element sends a fourth message to the third network element, the fourth message indicating that the default bearer of the terminal device has been updated, the default bearer being used to transmit IMS data, or the fourth message indicating rejection of establishing a dedicated bearer.
[0055] For example, the fourth message is used to indicate that the default bearer of the terminal device has been updated; the fourth message includes the bearer identifier of the default bearer of the terminal device or the fourth indication information, which is used to indicate the use of the default bearer of the terminal device.
[0056] The bearer identifier can also be used to set the transmission parameters of IMS data.
[0057] For example, the fourth message is used to indicate that the establishment of a dedicated bearer is refused; the fourth message includes fourth indication information, which indicates that the dedicated bearer of the terminal device is occupied, or the fourth indication information indicates that the terminal device does not support the establishment of a dedicated bearer.
[0058] In conjunction with the second aspect, in one possible implementation, the method further includes: the second network element receiving first indication information from the first network element, the first indication information indicating any one or more of the following: the dedicated bearer of the terminal device is occupied, or the terminal device does not support the establishment of a dedicated bearer.
[0059] In conjunction with the second aspect, in one possible implementation, the method further includes: the second network element receiving second indication information from the first network element, the second indication information being used to indicate to the terminal device that it supports or authorizes IMS services.
[0060] In conjunction with the second aspect, in one possible implementation, the method further includes: the second network element receiving bearer configuration information from the third network element.
[0061] In conjunction with the second aspect, in one possible implementation, the method further includes: the second network element sending a first indication message (create session request) to the third network element, the first indication message indicating any one or more of the following: the dedicated bearer of the terminal device is occupied, or the terminal device does not support the establishment of a dedicated bearer.
[0062] In conjunction with the second aspect, in one possible implementation, the method further includes: the second network element sending second indication information to the third network element, the second indication information also being used to instruct the terminal device to support or authorize IMS services.
[0063] In conjunction with the second aspect, in one possible implementation, if the first network element is a terminal device, the first message sent by the second network element may include a first service flow template. The first service flow template includes an address / domain name for transmitting IMS data, and the address / domain name is used to update the default service flow template carried by the terminal device.
[0064] It is understandable that the first business flow template can be carried in the first message (e.g., activate bearer context request).
[0065] Thirdly, embodiments of this application provide a communication method, the method comprising: a third network element receiving a third message sent by a first network element, the third message indicating the use or updating of the default bearer of a terminal device, the terminal device supporting IMS service and not supporting the use of a dedicated bearer to transmit IMS data; the third network element sending a fourth message to the first network element, the fourth message indicating that the default bearer of the terminal device has been updated, or the fourth message indicating a refusal to establish a dedicated bearer, the default bearer of the terminal device being used to transmit IMS data, or the fourth message indicating an update of the default bearer of the terminal device, the updated default bearer being used to transmit IMS data.
[0066] In this application, the third network element, through interaction with the first network element, learns that the bearer used by the terminal device to transmit IMS data is not a dedicated bearer for the terminal device, but rather the default bearer. Therefore, for the terminal device, whether it is a terminal device whose terminal capabilities do not support establishing a dedicated bearer (e.g., a UE accessing via NB-IoT) or a terminal device whose dedicated bearer is occupied, it can achieve the effect of transmitting IMS data through the default bearer without establishing a dedicated bearer, thereby effectively ensuring its support for IMS services.
[0067] In conjunction with the third aspect, in one possible implementation, the third message is used to indicate the use of the default bearer of the terminal device; the third message includes the quality of service parameters of the default bearer, and / or does not include the quality of service parameters.
[0068] In conjunction with the third aspect, in one possible implementation, the third message is used to instruct the terminal device to update its default bearer; the third message also includes an address / domain name for transmitting IMS data, which is used to update the service flow template of the terminal device's default bearer.
[0069] In conjunction with the third aspect, in one possible implementation, the third message is used to instruct the updating of the default bearer of the terminal device, including: the third message includes an identifier of the default bearer of the terminal device and a first service flow template, the first service flow template being used to update the default bearer of the terminal device, the first service flow template including an address / domain name.
[0070] In conjunction with the third aspect, in one possible implementation, the third message is used to instruct the updating of the default bearer of the terminal device, including: the third message includes an identifier of the default bearer of the terminal device and a first service flow template, the first service flow template being used to update the default bearer of the terminal device, the first service flow template including an address / domain name.
[0071] In conjunction with the third aspect, in one possible implementation, the fourth message is used to indicate that the default bearer of the terminal device has been updated; the fourth message includes the bearer identifier of the default bearer of the terminal device or the fourth indication information, which is used to indicate the use of the default bearer of the terminal device.
[0072] In conjunction with the third aspect, in one possible implementation, the fourth message is used to indicate a refusal to establish a dedicated bearer, including: the fourth message includes fourth indication information, which indicates that the dedicated bearer of the terminal device is occupied, or the fourth indication information indicates that the terminal device does not support the establishment of a dedicated bearer.
[0073] In conjunction with the third aspect, in one possible implementation, the third message also includes an address / domain name for transmitting IMS data, and the fourth message is used to indicate the default bearer for the updated terminal device, including: the fourth message includes a first service flow template, the first service flow template including an address / domain name.
[0074] In conjunction with the third aspect, in one possible implementation, the method further includes: the third network element sending bearer configuration information to the fourth network element, wherein the bearer configuration information is used to indicate that the default bearer does not include or has not been allocated a service flow template, or the bearer configuration information is used to indicate that the service flow template allocated for the default bearer includes: a wildcard, or an address / domain name used for transmitting IMS data.
[0075] In conjunction with the third aspect, in one possible implementation, after the third network element receives the third message sent by the first network element, the method further includes: the third network element determining that the terminal device supports IMS services, and the third network element determining that the terminal device does not support the use of dedicated bearers to transmit IMS data.
[0076] In conjunction with the third aspect, in one possible implementation, the method further includes: a third network element receiving first indication information from a fourth network element, the first indication information indicating one or more of the following: the dedicated bearer of the terminal device is occupied, or the terminal device does not support establishing a dedicated bearer; the third network element forwarding the first indication information to the first network element. Then, the third network element determining that the terminal device does not support transmitting IMS data using a dedicated bearer includes: the third network element determining, based on the first indication information, that the terminal device does not support transmitting IMS data using a dedicated bearer.
[0077] In conjunction with the third aspect, in one possible implementation, the method further includes: the third network element receiving second indication information from the fourth network element, the second indication information also being used to indicate that the terminal device supports or authorizes IMS services; the third network element determining that the terminal device supports IMS services includes: determining that the terminal device supports IMS services based on the second indication information.
[0078] In conjunction with the third aspect, in one possible implementation, the third message is used to indicate the update of the default bearer of the terminal device. After the third network element receives the third message sent by the first network element, the method further includes: the third network element sending a bearer update request to the fourth network element. The bearer update request includes a first service flow template, which is used to update the default bearer of the terminal device. The first service flow template includes an address / domain name used for transmitting IMS data. The third network element receives a bearer update response sent from the fourth network element, which indicates that the default bearer of the terminal device has been updated.
[0079] In conjunction with the third aspect, in one possible implementation, the bearer update response includes the first business flow template.
[0080] In conjunction with the third aspect, in one possible implementation, the method further includes: the third network element receiving bearer configuration information from the first network element (PGW), the bearer configuration information being used to indicate that the default bearer does not include or has not been allocated a service flow template, or the bearer configuration information being used to indicate that the service flow template allocated for the default bearer includes: a wildcard, or an address / domain name used for transmitting IMS data; the third network element forwarding the bearer configuration information to the terminal device.
[0081] In conjunction with the third aspect, in one possible implementation, the method further includes: the third network element sending a first indication message to the first network element, the first indication message indicating any one or more of the following: the dedicated bearer of the terminal device is occupied, or the terminal device does not support the establishment of a dedicated bearer.
[0082] In conjunction with the third aspect, in one possible implementation, the method further includes: the third network element sending second indication information to the first network element, the second indication information being used to indicate to the terminal device that it supports or authorizes IMS services.
[0083] In conjunction with the third aspect, in one possible implementation, after the third network element receives the third message sent by the first network element, the method further includes: the third network element sending a bearer update request to the terminal device, the bearer update request including a first service flow template, the first service flow template being used to update the default bearer of the terminal device, the first service flow template including an address / domain name; the third network element receiving a bearer update response sent from the terminal device, the bearer update response being used to indicate that the default bearer of the terminal device has been updated.
[0084] Fourthly, embodiments of this application provide a communication method, the method comprising: a third network element sending a third message to a second network element, the third message being used to indicate the establishment of a dedicated bearer for a terminal device; the third network element receiving a fourth message from the second network element, the fourth message being used to indicate that the default bearer of the terminal device has been updated and the default bearer is used to transmit IMS data, or the fourth message being used to indicate that the establishment of a dedicated bearer is refused.
[0085] In this application, after the third network element sends a dedicated bearer establishment instruction to the second network element, it can receive a fourth message from the second network element. According to the fourth message, the bearer used by the terminal device to transmit IMS data is not the terminal device's dedicated bearer, but rather the terminal device's default bearer. Therefore, for the terminal device, whether it is a terminal device whose terminal capabilities do not support establishing a dedicated bearer (e.g., a UE accessing via NB-IoT) or a terminal device whose dedicated bearer is occupied, the effect of transmitting IMS data through the default bearer without establishing a dedicated bearer can be achieved, thereby effectively ensuring its support for IMS services.
[0086] In conjunction with the fourth aspect, in one possible implementation, the fourth message is used to indicate that the default bearer of the terminal device has been updated; the fourth message includes the bearer identifier of the default bearer of the terminal device or the fourth indication information, which is used to indicate that the use of the default bearer of the terminal device is supported.
[0087] For example, the bearer identifier is also used to set the transmission parameters of IMS data.
[0088] In conjunction with the fourth aspect, in one possible implementation, the fourth message is used to indicate that the establishment of a dedicated bearer is refused; the fourth message includes fourth indication information, which indicates that the dedicated bearer of the terminal device is occupied, or that the fourth indication information indicates that the terminal device does not support the establishment of a dedicated bearer.
[0089] In conjunction with the fourth aspect, in one possible implementation, the method further includes: the third network element receiving first indication information from the second network element, the first indication information indicating any one or more of the following: the dedicated bearer of the terminal device is occupied, or the terminal device does not support the establishment of a dedicated bearer.
[0090] In conjunction with the fourth aspect, in one possible implementation, the method further includes: the third network element receiving second indication information from the second network element, the second indication information also being used to instruct the terminal device to support or authorize IMS services.
[0091] Fifthly, embodiments of this application provide a communication method, the method comprising: a third network element receiving a fifth message from a fourth network element; the third network element sending a third message to a second network element, both the third and fifth messages being used to request the establishment of a dedicated bearer for a terminal device; the third network element receiving a fourth message from the second network element, the fourth message being used to indicate that the default bearer of the terminal device has been updated and is used to transmit IMS data, or the fourth message being used to indicate that the establishment of a dedicated bearer is refused; and the third network element sending a sixth message to the fourth network element, the sixth message being used to indicate the default bearer of the terminal device and the default bearer of the terminal device being used to transmit IMS data.
[0092] In this application, after receiving the dedicated bearer establishment instruction sent by the fourth network element, the third network element can forward it to the second network element, and then reply to the fourth network element after receiving the fourth message from the second network element. According to the fourth message from the second network element, the bearer used by the terminal device to transmit IMS data is not the terminal device's dedicated bearer, but rather the terminal device's default bearer. Therefore, for the terminal device, whether it is a terminal device whose terminal capabilities do not support establishing a dedicated bearer (e.g., a UE accessing via NB-IoT) or a terminal device whose dedicated bearer is occupied, the effect of transmitting IMS data through the default bearer without establishing a dedicated bearer can be achieved, thereby effectively ensuring its support for IMS services.
[0093] In conjunction with the fifth aspect, in one possible implementation, the method further includes: the third network element sending bearer configuration information to the second network element, wherein the bearer configuration information is used to indicate that the default bearer does not include or has not been assigned a service flow template, or the bearer configuration information is used to indicate that the service flow template assigned to the default bearer includes: a wildcard, or an address / domain name used for transmitting IMS data.
[0094] In conjunction with the fifth aspect, in one possible implementation, the third message includes an address / domain name for transmitting IMS data, the fourth message includes fourth indication information, and the method further includes updating the downlink service flow template based on the fourth indication information and the address / domain name.
[0095] In conjunction with the fifth aspect, in one possible implementation, the fourth message is used to indicate that the default bearer of the terminal device has been updated; the fourth message includes the bearer identifier of the default bearer of the terminal device, or fourth indication information, which is used to indicate that the use of the default bearer of the terminal device is supported.
[0096] For example, the bearer identifier is also used to set the transmission parameters of IMS data.
[0097] In conjunction with the fifth aspect, in one possible implementation, the fourth message is used to indicate that the establishment of a dedicated bearer is refused; the fourth message includes fourth indication information, which indicates that the dedicated bearer of the terminal device is occupied, or that the fourth indication information indicates that the terminal device does not support the establishment of a dedicated bearer.
[0098] Sixthly, embodiments of this application provide a communication method, the method comprising: a fourth network element receiving a bearer update request from a third network element, the bearer update request including a first service flow template, the first service flow template being used to update the default bearer of a terminal device, the first service flow template including an address / domain name for transmitting IMS data, the default bearer of the terminal device not supporting the transmission of IMS data; the fourth network element forwarding the bearer update request to the terminal device; the fourth network element receiving a bearer update response sent from the terminal device, the bearer update response being used to indicate that the default bearer of the terminal device has been updated, the updated default bearer of the terminal device being used for transmitting IMS data; and the fourth network element forwarding the bearer update response to the third network element.
[0099] In this application, the fourth network element, through interaction with the third network element, can update the default bearer of the terminal device. This allows the updated default bearer to be used for IMS data transmission. This means that the bearer subsequently used by the terminal device for IMS data transmission is not its dedicated bearer, but rather the updated default bearer. Therefore, for the terminal device, whether it is a device whose terminal capabilities do not support establishing a dedicated bearer (e.g., a UE accessing via NB-IoT) or a device whose dedicated bearer is occupied, the goal is to transmit IMS data using the default bearer without establishing a dedicated bearer, thus effectively ensuring its support for IMS services.
[0100] In conjunction with the sixth aspect, in one possible implementation, the method further includes: the fourth network element sending a first indication message to the third network element, the first indication message indicating any one or more of the following: the dedicated bearer of the terminal device is occupied, or the terminal device does not support the establishment of a dedicated bearer.
[0101] In conjunction with the sixth aspect, in one possible implementation, the bearer update response includes a first business flow template.
[0102] In conjunction with the sixth aspect, in one possible implementation, the method further includes: the fourth network element receiving bearer configuration information sent from the third network element, the bearer configuration information being used to indicate that the default bearer does not include or has not been allocated a service flow template, or the bearer configuration information being used to indicate that the service flow template allocated for the default bearer includes: a wildcard, or an address / domain name used for transmitting IMS data; the fourth network element forwarding the bearer configuration information to the terminal device.
[0103] In a seventh aspect, embodiments of this application provide a communication method, the method comprising: a fourth network element sending a fifth message to a second network element, the fifth message being used to indicate the establishment of a dedicated bearer for a terminal device; the fourth network element receiving a sixth message from the second network element, the sixth message being a reply message to the fifth message, or the sixth message being used to indicate a default bearer for the terminal device, the default bearer being used to transmit IMS data, or the sixth message being used to indicate a refusal to establish a dedicated bearer, or the sixth message being used to indicate an update to the default bearer for the terminal device, the updated default bearer being used to transmit IMS data.
[0104] In this application, after the fourth network element sends a dedicated bearer establishment instruction to the second network element, it can receive a sixth message from the second network element. According to the sixth message, the bearer used by the terminal device to transmit IMS data is not the terminal device's dedicated bearer, but rather the terminal device's default bearer. Therefore, for the terminal device, whether it is a terminal device whose terminal capabilities do not support establishing a dedicated bearer (e.g., a UE accessing via NB-IoT) or a terminal device whose dedicated bearer is occupied, it can achieve the effect of transmitting IMS data through the default bearer without establishing a dedicated bearer, thereby effectively ensuring its support for IMS services.
[0105] Eighthly, embodiments of this application provide a communication method, the method comprising: a terminal device sending a session invitation message to a policy management network element; the terminal device receiving a first service flow template sent from a mobility management network element or a policy management network element; the first service flow template including an address / domain name for transmitting IMS data; the default bearer of the terminal device not supporting the transmission of IMS data; the first service flow template being used to indicate an update to the default bearer of the terminal device; the updated default bearer of the terminal device being used for transmitting IMS data.
[0106] In this application, the terminal device can update its default bearer through interaction with a mobility management network element or a policy management network element. This updated default bearer can then be used to transmit IMS data. In other words, the bearer used by the terminal device to transmit IMS data is not a dedicated bearer, but rather the updated default bearer. Therefore, for the terminal device, whether it is a terminal device whose terminal capabilities do not support establishing a dedicated bearer (e.g., a UE accessing via NB-IoT) or a terminal device whose dedicated bearer is occupied, the effect of transmitting IMS data through the default bearer without establishing a dedicated bearer can be achieved, thereby effectively ensuring its support for IMS services.
[0107] For example, the first service flow template here can also be carried in the bearer update request sent by the mobility management network element, or in the response message to the session invitation message sent by the policy management network element.
[0108] In conjunction with the eighth aspect, in one possible implementation, the method includes: receiving bearer configuration information from a mobility management network element, wherein the bearer configuration information is used to indicate that the default bearer does not include or has not been assigned a service flow template, or the bearer configuration information is used to indicate that the service flow template assigned to the default bearer includes: a wildcard, or an address / domain name for transmitting IMS data.
[0109] Ninthly, embodiments of this application provide a communication device, which may be any one of a first network element, a second network element, a third network element, a fourth network element, a terminal device, or a chip thereof. The communication device includes units and / or modules for performing the methods provided by any one of the first to eighth aspects, or any possible implementation thereof, such as transceiver units and / or processing units. The transceiver units are used to transmit and receive various information or signaling, thus achieving the beneficial effects (or advantages) of the methods provided by any one of the above aspects.
[0110] In a tenth aspect, embodiments of this application provide a communication method, the method comprising: a first network element receiving a first response message, the first response message being a reply message to a session invitation message; the first network element determining that the default bearer of the terminal device is used to transmit IMS data; and the first network element not sending a bearer creation message to a second network element.
[0111] For example, the first network element here can be a network element in the IMS network (i.e., call session control function), and the second network element can be a policy management network element in the core network.
[0112] In this application, when the first network element determines that the default bearer of the terminal device is used to transmit IMS data, it changes the strategy of the existing IMS call establishment process without interacting with the network elements of the core network, that is, it does not trigger the creation process of the dedicated bearer. Therefore, for the terminal device, whether it is a terminal device whose terminal capability does not support the establishment of a dedicated bearer (e.g., a UE accessed through NB-IoT) or a terminal device whose dedicated bearer is occupied, it can achieve the effect of transmitting IMS data through the default bearer without establishing a dedicated bearer, thereby effectively ensuring its support for IMS services.
[0113] In conjunction with the tenth aspect, in one possible implementation, after the first network element determines that the default bearer of the terminal device is used to transmit IMS data, the method further includes: the first network element sending a second response message to the terminal device, the second response message being used to instruct the terminal device not to update or establish a bearer, or the second response message being used to instruct the terminal device to reply with a feedback message in response to the second response message, or the second response message being used to instruct the terminal device to reply with a feedback message in response to the second response message if a dedicated bearer has not been established.
[0114] In conjunction with aspect ten, in one possible implementation, the session invitation message is used to indicate that the dedicated bearer of the terminal device is occupied, or the session invitation message is used to indicate that the terminal device does not support establishing a dedicated bearer, or the session invitation message is used to indicate that the terminal device uses the default bearer to transmit IMS data.
[0115] In conjunction with the tenth aspect, in one possible implementation, the method further includes: a first network element receiving an IMS registration message from a terminal device, the IMS registration message being used to indicate that the terminal device does not support the establishment of a dedicated bearer.
[0116] In conjunction with aspect ten, in one possible implementation, the method further includes: receiving subscription information from a third network element, the subscription information being used to indicate that the terminal device does not support the establishment of a dedicated bearer.
[0117] In conjunction with aspect ten, in one possible implementation, the first network element determines that the default bearer of the terminal device is used for transmitting IMS data, including: determining that the default bearer of the terminal device is used for transmitting IMS data based on a session invitation message, an IMS registration message, or subscription information.
[0118] In conjunction with aspect 10, in one possible implementation, the default bearer is used to transmit IMS data, including: the default bearer of the terminal device does not include or has not been assigned a service flow template, or the service flow template assigned to the default bearer includes: a wildcard, or an address / domain name used to transmit IMS data.
[0119] Eleventhly, embodiments of this application provide a communication method, the method comprising: a terminal device sending a session invitation message to a first network element, wherein the default bearer of the terminal device is used to transmit IMS data; the terminal device receiving a second response message from the first network element, wherein the second response message is used to instruct the terminal device not to update or establish a bearer, or, the second response message is used to instruct the terminal device to reply with a feedback message in response to the second response message, or, the second response message is used to instruct the terminal device to reply with a feedback message in response to the second response message without establishing a dedicated bearer.
[0120] In this application, after the terminal device sends a session invitation message to the first network element, it can receive a second response message in response. The terminal device does not receive an instruction to establish a dedicated bearer. In other words, the embodiments of this application change the strategy of the existing IMS call establishment process. That is, the terminal device does not establish a dedicated bearer, but uses the default bearer to transmit IMS data. Therefore, for the terminal device, whether it is a terminal device whose terminal capability does not support the establishment of a dedicated bearer (e.g., a UE accessed through NB-IoT) or a terminal device whose dedicated bearer is occupied, it can achieve the effect of transmitting IMS data through the default bearer without establishing a dedicated bearer, thereby effectively ensuring its support for IMS services.
[0121] In conjunction with the eleventh aspect, in one possible implementation, the session invitation message is used to indicate that the dedicated bearer of the terminal device is occupied, or the session invitation message is used to indicate that the terminal device does not support the establishment of a dedicated bearer, or the session invitation message is used to indicate that the terminal device uses the default bearer to transmit IMS data.
[0122] In conjunction with the eleventh aspect, in one possible implementation, the method further includes: the terminal device sending an IMS registration message to the first network element, the IMS registration message being used to indicate that the terminal device's access method belongs to narrowband IoT access.
[0123] In conjunction with the eleventh aspect, in one possible implementation, the default bearer is used to transmit IMS data, including: the default bearer of the terminal device does not include or has not been assigned a service flow template, or the service flow template assigned to the default bearer includes: a wildcard, or an address / domain name used to transmit IMS data.
[0124] In conjunction with the eleventh aspect, in one possible implementation, the method further includes: the terminal device receiving bearer configuration information from the mobility management network element, wherein the bearer configuration information is used to indicate that the default bearer does not include or has not been assigned a service flow template, or the bearer configuration information is used to indicate that the service flow template assigned to the default bearer includes: a wildcard, or an address / domain name used for transmitting IMS data.
[0125] In a twelfth aspect, embodiments of this application provide a communication device, which may be any of a first network element or a terminal device, or a chip therein. The communication device includes units and / or modules for performing the methods provided by any of the tenth to eleventh aspects, or any possible implementation thereof, such as transceiver units and / or processing units. The transceiver units are used to transmit and receive various information or signaling, thus also achieving the beneficial effects (or advantages) of the methods provided by any of the above aspects.
[0126] In a thirteenth aspect, this application provides a communication device that may include a processor and a transceiver. The transceiver is used to send and receive various information or signaling. The computer program includes program instructions that, when executed by the processor, cause the communication device to perform the communication method described in any one of the first to eighth aspects, or any one of the tenth to eleventh aspects, or any possible implementation thereof. The transceiver may be a radio frequency module in the communication device, or a combination of a radio frequency module and an antenna, or an input / output interface of a chip or circuit. Optionally, the communication device further includes a memory for storing the computer program.
[0127] In a fourteenth aspect, embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed, causes a communication device to perform the communication method described in any one of the first to eighth aspects, or any one of the tenth to eleventh aspects, or any possible implementation thereof.
[0128] In a fifteenth aspect, embodiments of this application provide a computer program product including instructions that, when executed on a computer, cause the communication method described in any possible implementation of any of the first to eighth aspects to be executed.
[0129] In a sixteenth aspect, embodiments of this application provide a computer program product including instructions that, when executed on a computer, cause the communication method described in any possible implementation of any of the tenth to eleventh aspects to be executed.
[0130] In a seventeenth aspect, this application provides a communication device, which can be implemented as a chip or as a device, including a processor. The processor is used to read and execute a program stored in a memory to execute one or more of the first to eighth aspects described above, or one or more of the tenth to eleventh aspects described above, or one or more of any possible implementations of any of these aspects, providing a communication method. Optionally, the device further includes a memory connected to the processor via a circuit. Further optionally, the device includes a communication interface to which the processor is connected. The communication interface is used to receive information and / or signaling to be processed, the processor obtains the information and / or signaling from the communication interface, processes the information and / or signaling, and outputs the processing result through the communication interface. The communication interface can be an input / output interface.
[0131] Optionally, the processor and memory mentioned above can be physically independent units, or the memory can be integrated with the processor.
[0132] In an eighteenth aspect, embodiments of this application provide a communication system, which includes at least a first network element and a second network element. The first network element is used to implement the method as described in the first aspect or any one of the implementations of the first aspect, and the second network element is used to implement the method as described in the second aspect or any one of the implementations of the second aspect.
[0133] In conjunction with aspect eighteen, in one possible implementation, the communication system may further include a third network element for implementing the method provided by any one of aspects three through five above, or any possible implementation of any one of these aspects.
[0134] In conjunction with aspect eighteen, in one possible implementation, the communication system may further include a fourth network element for implementing the method provided by any of aspects six to seven above, or any possible implementation of any of these aspects.
[0135] In conjunction with aspect eighteen, in one possible implementation, the communication system may further include a terminal device for implementing the method provided by aspect eight or any of the possible implementations of aspect eight above.
[0136] In a nineteenth aspect, embodiments of this application provide a communication system, which includes at least a first network element and a terminal device. The first network element is used to implement the method as described in the tenth aspect or any one of the tenth aspects, and the terminal device is used to implement the method as described in the eleventh aspect or any one of the eleventh aspects.
[0137] The technical effects achieved in the above aspects can be referred to each other or to the beneficial effects in the method embodiments shown below, which will not be repeated here. Attached Figure Description
[0138] Figure 1 is a simplified schematic diagram of a communication system provided in an embodiment of this application;
[0139] Figure 2 is a schematic diagram of an IMS call setup process provided by the prior art;
[0140] Figure 3 is a flowchart of a communication method provided in an embodiment of this application;
[0141] Figure 4 is a schematic diagram of a core network registration process provided in an embodiment of this application;
[0142] Figure 5 is an interactive schematic diagram of an IMS service scenario provided in an embodiment of this application.
[0143] Figure 6 is a second interactive diagram of an IMS service scenario provided in an embodiment of this application.
[0144] Figure 7 is a schematic diagram of an interaction corresponding to an IMS service scenario provided in an embodiment of this application;
[0145] Figure 8 is a schematic diagram of an interaction corresponding to an IMS service scenario provided in an embodiment of this application;
[0146] Figure 9 is a schematic diagram of an interaction corresponding to an IMS service scenario provided in an embodiment of this application.
[0147] Figure 10 is a schematic diagram of an interaction corresponding to an IMS service scenario provided in an embodiment of this application;
[0148] Figure 11 is a schematic diagram of an interaction corresponding to an IMS service scenario provided in an embodiment of this application;
[0149] Figure 12 is an interactive schematic diagram of an IMS service scenario provided in an embodiment of this application.
[0150] Figure 13 is a flowchart of another communication method provided in an embodiment of this application;
[0151] Figure 14 is an interactive schematic diagram (nine) corresponding to an IMS service scenario provided in an embodiment of this application.
[0152] Figure 15 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;
[0153] Figure 16 is a schematic diagram of another communication device provided in an embodiment of this application;
[0154] Figure 17 is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation
[0155] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.
[0156] In the description of this application, terms such as "first" and "second" are used only to distinguish different objects, not to describe a specific order. Furthermore, unless otherwise stated, " / " means "or," for example, A / B can mean A or B. "And / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone. Additionally, "at least one" refers to one or more, and "multiple" refers to two or more. "One or more of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can represent: a, b, c; a and b; a and c; b and c; or a and b and c. Where a, b, and c can be single or multiple.
[0157] The terms “comprising” and “having”, and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the steps or units listed, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to such process, method, product, or apparatus.
[0158] In this application, the words "exemplary" or "for example" are used to indicate that something is an example, illustration, or illustration. Any embodiment or design described as "exemplary," "for example," or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Rather, the use of the words "exemplary," "for example," or "for example" is intended to present the relevant concepts in a specific manner.
[0159] It is understood that in this application, "when," "if," and "if" all refer to the device performing a corresponding action under certain objective circumstances, and are not time-limited, nor do they require the device to perform a judgment action when it is implemented, nor do they imply any other limitations. The device performing a corresponding action under certain objective circumstances includes: satisfying the objective circumstances, i.e., being able to perform the corresponding action; or satisfying both the objective circumstances and other circumstances, in order to perform the corresponding action.
[0160] In this application, "simultaneous" can be understood as "parallel", or at the same point in time, or within a period of time, or within the same cycle. The specific meaning can be understood in conjunction with the context.
[0161] In this application, the use of singular designations for elements is intended to represent "one or more" rather than "one and only one," unless otherwise specified.
[0162] It is understood that in the various embodiments of this application, phrases such as "B corresponding to A," "A corresponds to B," or similar expressions indicate that B is associated with A, and B can be determined based on A. This includes determining information B solely based on A, as well as determining B based on A and other information. Furthermore, the use of A to determine information B can also include indirect determination, such as B being determined based on C, and C being determined based on A.
[0163] In this application, "send" and "receive" indicate the direction of signal transmission. For example, "send information to XX" can be understood as the destination of the information being XX, which can include direct transmission via the air interface or indirect transmission by other units or modules via the air interface. "Receive information from YY" can be understood as the source of the information being YY, which can include direct reception from YY via the air interface or indirect reception from YY by other units or modules via the air interface. "Send" can also be understood as the "output" of a chip interface, and "receive" can also be understood as the "input" of a chip interface. In other words, sending and receiving can occur between devices, for example, through buses, traces, or interfaces between components, modules, chips, software modules, or hardware modules within a device.
[0164] In this application, "instruction" can include direct instruction, indirect instruction, explicit instruction, and implicit instruction. When describing certain instruction information to indicate A, it can be understood that the information carries A, directly indicates A, or indirectly indicates A. Direct instruction A can be understood as including the information A; implicit instruction A can be understood as indicating A through the correspondence between A and B and the direct instruction B.
[0165] To facilitate understanding of the technical solutions provided in the embodiments of this application, the relevant terminology of the communication system involved in the embodiments of this application will first be introduced, for details of which can be found in 3GPP protocol TS23.401:
[0166] 1. NB-IoT devices
[0167] NB-IoT devices are UEs that access the network via NB-IoT. NB-IoT is an emerging access technology and an important branch of the Internet of Things. It supports the connection of low-power devices in wide area networks and has advantages such as wide coverage, large capacity, low power consumption, low cost, and superior architecture. It can be widely used in various vertical industries, such as remote meter reading and smart street lights.
[0168] NB-IoT access can be divided into terrestrial access and satellite access. It can be understood that non-terrestrial network (NTN) communication scenarios include various types of satellites, such as geostationary Earth orbit (GEO) satellites and low-earth orbit (LEO) satellites. LEO satellites are satellites with relatively low orbital altitudes, generally referring to satellites orbiting at altitudes of several hundred to over a thousand kilometers above the Earth's surface, and they move relatively quickly relative to the Earth's surface. GEO satellites, on the other hand, are geostationary satellites with fixed orbital altitudes, operating in equatorial orbits, and are relatively stationary relative to the Earth (i.e., they always cover the same geographical area of the Earth), providing stable communication services.
[0169] In this application, narrowband IoT access via GEO satellite can be abbreviated as NB-IoT GEO access or NB-IoT (GEO).
[0170] 2. Default bearer
[0171] Default bearer: A user bearer that satisfies default QoS for data and signaling, which can be understood as a bearer that provides a best-effort IP connection. The default bearer includes the first data plane bearer (DRB) established by the UE, established with the establishment of the packet data network (PDN) connection and released with the release of the PDN connection, providing IP transport services to the user. For example, when the UE performs IMS services, it can be used to transmit IMS signaling and other data.
[0172] 3. Dedicated bearer
[0173] Dedicated bearer: A dedicated bearer is established on top of a PDN connection (i.e., on top of the default bearer) and requires a dedicated bearer activation process. A dedicated bearer can provide certain QoS guarantees for services (e.g., guaranteeing minimum bit rate, maximum latency, etc.). Generally, the QoS requirements of a dedicated bearer are higher than those of the default bearer.
[0174] It is understood that a UE may include at least one PDN connection, and a PDN connection may include at least one bearer. Therefore, for ease of explanation, in the embodiments of this application, the default bearer of the PDN connection of the terminal device can be abbreviated as the default bearer of the terminal device, and the dedicated bearer of the PDN connection of the terminal device can be abbreviated as the dedicated bearer of the terminal device.
[0175] 4. Traffic Filter Template (TFT)
[0176] A packet filter is a set of data packet filters associated with a bearer, typically divided into uplink filtering templates (UpLink TFT, UL TFT) and downlink filtering templates (DownLink TFT, DL TFT). Packet filters are used to allow or block data packets during transmission. To perform packet filtering, rules must be set to specify which types of packets are allowed and which are blocked. In other words, a TFT indicates which data packets are allowed or blocked by the associated bearer, usually represented by IP 5-tuples, IP triples, etc.
[0177] The technical solutions of this application embodiment can be applied to various communication systems, such as Global System for Mobile Communications (GSMA), Long Term Evolution (LTE) systems, Universal Mobile Telecommunications System (UMTS), 4th Generation (4G) mobile communication systems, 4.5th Generation (4.5G) mobile communication systems, and 5th Generation (5G) mobile communication systems, including new radio access technology (NR), multi-system converged networks, Internet of Things (IoT) systems, vehicle-to-everything (V2X) systems, and open-radio access networks (O-RAN). As communication technologies continue to develop, the technical solutions of this application embodiment can also be used in subsequent evolved communication systems. The technical solutions of this application embodiment can also be applied to Universal Mobile Telecommunications System (UMTS), Code Division Multiple Access (CDMA) systems, and Wireless Local Area Networks (WLANs). The methods provided in this application embodiment can also be applied to NTN communication systems or scenarios where NTN and terrestrial networks (TN) are converged. The NTN system can be an NTN system integrated with 4G, 5G, and any future generation of communication systems, such as NR NTN, IoT NTN, etc. The NTN communication system can be, for example, a satellite communication system, or it can include drones, high altitude platform stations (HAPS), and other air access network equipment; this application does not limit this.
[0178] In one possible implementation, the communication system includes communication devices that can wirelessly communicate with each other using air interface resources. These communication devices may include access network devices (also known as network devices or AP devices) and terminal devices. Air interface resources may include at least one of time-domain resources, frequency-domain resources, code resources, and spatial resources.
[0179] Terminal equipment, also known as user equipment, mobile station (MS), mobile terminal (MT), or terminal, refers to devices that provide voice and / or data connectivity to users. Examples include handheld devices and in-vehicle devices with wireless connectivity. Currently, some examples of terminal equipment include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, self-driving, remote medical surgery, smart grids, transportation safety, smart cities, and smart homes. Terminal equipment can also be a communication module, satellite phone, or its components with satellite communication capabilities, or a satellite communication terminal, such as a very small aperture terminal (VSAT) (commonly referred to as a VSAT terminal), portable station, fixed station, vehicle-mounted or airborne satellite communication terminal, etc. It should be understood that a satellite communication terminal can serve as a micro base station to further provide data interfaces to accessed user equipment.
[0180] In this application's embodiments, the device used to implement the terminal's functions can be a terminal itself; it can also be a device capable of supporting the terminal in implementing those functions, such as a chip system, a communication module, or a modem, etc., which can be installed in the terminal. In this application's embodiments, the chip system can be composed of chips, or it can include chips and other discrete devices. The embodiments of this application do not limit the specific technology or device form used in the terminal device.
[0181] In this application embodiment, the chip that can support the terminal to achieve the above functions can be referred to as a terminal communication chip. The terminal communication chip may include personal chips, vehicle chips, shipborne chips, airborne chips, etc.
[0182] Access network equipment refers to radio access network (RAN) nodes (or devices) that connect terminal devices to a wireless network; it can also be called a base station. Examples of RAN nodes include: evolved Node B (eNB), next-generation Node B (gNB), transmission reception point (TRP), radio network controller (RNC), Node B (NB), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home evolved Node B, or home Node B (HNB)), base band unit (BBU), and wireless fidelity (Wi-Fi) access point (AP). Access network equipment can also be satellites (or satellite base stations) or HAPS (Hybrid Access Point System), or base station equipment mounted on satellites / HAPS. The satellite may include at least one of the following: a geostationary orbit satellite (or geosynchronous orbit satellite) or a non-geostationary earth orbit (NGEO) satellite. A non-geostationary earth orbit satellite may include at least one of the following: a medium Earth orbit satellite or a low Earth orbit satellite. There are no limitations here. The access network equipment may also be a gateway station (or ground station, earth station, signaling station, gateway, or gateway station), etc. Additionally, in one network architecture, the access network equipment may include centralized unit (CU) nodes, distributed unit (DU) nodes, or RAN equipment including CU nodes and DU nodes.
[0183] In this application embodiment, the device used to implement the function of the access network device can be the access network device itself; it can also be a device capable of supporting the access network device in implementing this function, such as a chip system, a communication module, or a modem, etc., and this device can be installed in the access network device. The access network device can support networks with the same or different access technologies. The embodiments of this application do not limit the specific technology or specific device form used in the access network device.
[0184] It should be understood that the communication system in the embodiments of this application may include a core network and an IMS network.
[0185] In one possible implementation, if the communication system is a 4G mobile communication system, the core network elements of the communication system mainly involve: mobility management entity (MME), serving gateway (SGW), public data network gateway (PDN Gateway, PGW), and policy and charging rules function (PCRF); the network elements in the IMS network mainly involve: access gateway (AGW), call session control function (CSCF), and data management network elements.
[0186] The following section introduces the various core network elements involved in the 4G core network. For details, please refer to the technical specifications (e.g., 3GPP TS23.401, TS23.228):
[0187] MME: It is a key control node in the LTE access network. It is responsible for paging user equipment in idle mode and marking processes, including retransmissions.
[0188] SGW: A mobile core network element with functions such as local mobility anchor point for inter-eNB handover, mobility anchoring for inter-3GPP mobility, packet routing and forwarding, transport level packet marking, and inter-carrier billing considerations.
[0189] PGW: As a connection point, it provides the UE with transmission between the UE and the Public Data Network (PDN). A UE can access multiple PGWs simultaneously. The PGW implements control policies, user-specific packet filtering, billing, and packet screening. The PGW and SGW can be deployed on the same physical node or on separate physical nodes; this is not a limitation.
[0190] PCRF (Programmatical Control RF) is the decision point for policy and charging control of service data flows and IP bearer resources. It maintains the association between gateway control sessions and Internet Protocol Core Access Network (IP-CAN) sessions. In essence, PCRF can perform dynamic QoS policy control and dynamic flow-based charging control, while also providing authorization control based on user subscription information.
[0191] The following section introduces the various IMS network elements involved in the IMS network. For details, please refer to the technical specifications (e.g., 3GPP TS23.228):
[0192] AGW: Primarily used to enable interconnection between different networks, it can convert multimedia data such as voice, video, and SMS from mobile networks into IP data and transmit it to its destination via a fixed network, or it can convert IP data from a fixed network into data from a mobile network.
[0193] CSCF: Primarily responsible for the control and management of call sessions, including signaling transmission, signaling processing, and session management. CSCF can be further subdivided into proxy call session control function (P-CSCF), interrogating-call session control function (I-CSCF), and service call session control function (S-CSCF), each undertaking different roles and functions.
[0194] The P-CSCF is the first point of contact for users accessing the IMS network during service applications. It is responsible for proxying all Session Initiation Protocol (SIP) signaling and completing call routing control; providing QoS resource reservation; supporting SIP signaling compression to improve the bandwidth utilization efficiency of the air interface; providing NAT control to support Network Address Translator (NAT) traversal for enterprise networks; and maintaining a security association with the UE to protect the privacy and integrity of signaling between the UE and the UE.
[0195] The I-CSCF selects the appropriate S-CSCF for incoming calls to the P-CSCF in the home network, providing access to the external IMS network of the visited network.
[0196] The S-CSCF is responsible for functions such as UE registration and authentication, session control, user service information management, and triggering specified services to the application server (AS).
[0197] It should be understood that in the IMS service scenario, the process may include a core network registration process (i.e., the process of the UE registering to the core network), an IMS network registration process (i.e., the process of the UE registering to the IMS network), and an IMS call setup process. The core network registration process can be referred to as the attach process. All three processes involve interaction of call session control functions. For ease of explanation, the call session control function in this embodiment can be exemplified by the P-CSCF. Some or all of the actions of the P-CSCF can also be executed by the I-CSCF or S-CSCF. When some actions are executed on different network elements, interaction between one or more network elements from the P-CSCF, I-CSCF, or S-CSCF is required.
[0198] Data management network element: This can be used to store user data, such as subscription information (specifically, it can include the subscription information of the calling UE and the called UE). This data management network element can be a home subscriber server (HSS) or a home location register (HLR), which will not be limited here.
[0199] The HSS (Hospital Service Provider) is the core database in the home network of IMS users, storing user information. It is used to preserve IMS user subscription information within the home network and provides a management interface for operators and end users to customize and modify the subscription data. The main information stored in the HSS includes: IMS user identifier, IMS user security context, IMS user routing information, and service subscription information. The HSS can be understood as either an IMS network element or a core network element; this will not be considered a single definition here.
[0200] HLR is a key component of the Global System for Mobile Communications (GSM). It is a static database used to record user data in mobile communication networks, storing user account opening information (telecommunication service subscription data and user status), mobile station location information, and identifiers used to identify mobile users.
[0201] In one possible implementation, if the communication system is a 5G mobile communication system, the network elements in the core network mainly involve: access and mobility management function (AMF), session management function (SMF), user plane function (UPF), policy control function (PCF), and unified data management (UDM). The network elements in the IMS network mainly involve: call session control function (CSCF).
[0202] The following section introduces the various network elements involved in the 5G core network. For details, please refer to the technical specifications (e.g., 3GPP TS23.501):
[0203] AMF: Primarily responsible for mobility management in mobile networks, such as user location updates, user network registration, and user handover.
[0204] SMF (Service Provider Function): Primarily responsible for session management in mobile networks, such as session establishment, modification, and release. Specific functions include assigning IP addresses to users and selecting the UPF (User Provider Function) to provide packet forwarding capabilities.
[0205] UPF: Primarily responsible for processing user messages, such as forwarding and billing.
[0206] PCF: Responsible for providing policies to AMF and SMF, such as QoS policies and slice selection policies.
[0207] UDM can be used to store user data, such as contract information, authentication or authorization information.
[0208] The AMF can be set on the same node as the SMF, or on different nodes; in addition, the UPF and SMF can be set on the same node, or on different nodes, and there are no restrictions on this.
[0209] It is understood that there can be multiple terminal devices in a communication system. In this embodiment, the terminal devices in the communication system can take two terminal devices used to perform IMS services (e.g., IMS calls) as an example, specifically including terminal device A (i.e., UE-A) and terminal device B (i.e., UE-B). In this embodiment, terminal device A can be the calling UE, and terminal device B can be the called UE. For example, both terminal device A and terminal device B are devices used for user communication with the 3rd Generation Partnership Project (3GPP) and network.
[0210] It should be understood that UE-A and UE-B can connect to the radio access network using the same access network equipment or different access network equipment; this is not limited here. Furthermore, the core network serving UE-A and the core network serving UE-B can be the same (i.e., UE-A and UE-B can share the same core network) or different; in the IMS network, the IMS network elements serving UE-A and the IMS network elements serving UE-B can be the same or different; this is not limited here either.
[0211] The system architecture used in the embodiments of this application is described below. It should be noted that the system architecture and application scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, as the system architecture or application scenarios evolve, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.
[0212] For example, please refer to Figure 1, which is a simplified schematic diagram of a communication system provided in an embodiment of this application. As shown in Figure 1, the communication system 100 (e.g., a 4G mobile communication system) may include a core network (e.g., core network 120a and core network 120b) and an IMS network 130.
[0213] It is understood that UE-A and UE-B in communication system 100 can use different access network devices to connect to the radio access network. For example, UE-A can use access network device A (i.e., RAN-A) to connect to the radio access network, and UE-B can use access network device B (i.e., RAN-B) to connect to the radio access network.
[0214] The core network serving UE-A differs from the core network serving UE-B. For example, core network 120a can serve UE-A, and its network elements can be represented by "-A", specifically including MME-A, SGW-A, PGW-A, and PCRF-A. Similarly, core network 120b can serve UE-B, and its network elements can be represented by "-B", specifically including MME-B, SGW-B, PGW-B, and PCRF-B.
[0215] In the IMS network 130, it may include shared network elements (e.g., HLR or HSS) for UE-A and UE-B, and may also include IMS network elements serving UE-A and IMS network elements serving UE-B. For example, the IMS network elements serving UE-A may specifically include AGW-A, P-CSCF-A, S-CSCF-A, and I-CSCF-A, and the IMS network elements serving UE-B may specifically include AGW-B, P-CSCF-B, S-CSCF-B, and I-CSCF-B.
[0216] Some or all of the access network equipment and core network elements serving UE-A and UE-B may be the same. For example, RAN-A and RAN-B may be the same RAN, or RAN-A and RAN-B may be different, but PCRF-A and PCRF-B may be the same PCRF.
[0217] It should be understood that in this application, the UE and / or the aforementioned network elements may perform some or all of the steps in each embodiment. These steps or operations are merely examples, and other operations or variations thereof may also be performed in the embodiments of this application. Furthermore, the steps may be performed in different orders as presented in the embodiments, and it is not necessary to perform all the operations in the embodiments of this application.
[0218] To facilitate understanding of the technical methods provided in the embodiments of this application, the relevant technologies of the embodiments of this application will be briefly introduced as follows:
[0219] Before the existing IMS call setup process occurs, both the calling UE (e.g., UE-A) and the called UE (e.g., UE-B) need to register with the core network and the IMS network. After the above two registration processes are completed, the calling UE and the called UE each establish a default bearer that can transmit data with the IMS network. This bearer can be used to transmit IMS signaling, but cannot transmit IMS data such as ringtones and voice messages.
[0220] For ease of understanding, please refer to Figure 2, which is a schematic diagram of an IMS call establishment process provided by the prior art, detailed in 3GPP protocol TS23.228. As shown in Figure 2, according to the interaction flow of steps S201-S206, UE-A can send a session invitation message (e.g., INVITE message, or SDP offer) to P-CSCF-B based on the core network element and IMS network element serving UE-A. The session invitation message is used to initiate an IMS call to UE-B.
[0221] As can be seen from steps S207-S209, after receiving the session invitation message, P-CSCF-B can send an Authentication Authorization Request (AAR) message to PCRF-B to instruct it to establish a dedicated bearer (e.g., an AAR message). After receiving the response from PCRF-B, P-CSCF-B sends a session invitation message to UE-B so that UE-B replies with a response message to the session invitation message (e.g., a 183 message, or an SDP answer).
[0222] Specifically, when the 183 message is transmitted to P-CSCF-B, P-CSCF-B can execute step S212a to trigger the dedicated bearer establishment procedure for UE-B, and simultaneously forward the 183 message to P-CSCF-A. When the 183 message is transmitted to P-CSCF-A, P-CSCF-A can execute step S210 and step S212b simultaneously, that is, while forwarding the 183 message to UE-A, it triggers the dedicated bearer establishment procedure for UE-A. It can be understood that steps S212a and S212b can be executed synchronously, that is, the establishment of the called and calling dedicated bearers can be performed simultaneously.
[0223] Optionally, UE-B may also perform step S211 to send a ringing message (e.g., 180 message), which is used to trigger the calling network element to send a ringing sound to the calling UE.
[0224] As described in steps S213-S217, after the dedicated bearer is established, UE-A can send a Provisional Response ACK (PRACK) message as a response from the calling UE to the 183 message, indicating to the called party that the dedicated bearer of the calling UE has been established. After the dedicated bearer is established, UE-B can send a 200 message and a ringing message. The 200 message is the called UE's response to the PRACK message, indicating to the calling party that the dedicated bearer of the called UE has been established. After the called user answers the phone, UE-B can send a response message (e.g., a 200 message) to UE-A to indicate that the called user has answered the phone. Subsequently, IMS data can be transmitted through the dedicated bearers of both parties.
[0225] As can be seen from the above, in the existing IMS call setup process, both the calling UE and the called UE need to establish a dedicated bearer. However, for UEs whose dedicated bearers are occupied or do not support the establishment of dedicated bearers (e.g., access via NB-IoT), they cannot make IMS calls based on the existing IMS call setup process.
[0226] To address the aforementioned issues, this application provides two different communication methods. The technical solutions provided in this application will be described in detail below with reference to more accompanying drawings. It is understood that in the IMS call setup process, the interaction between the UE and the core network element or IMS network element needs to be achieved through the access network device. However, the access network device only provides message forwarding functionality and does not perform substantive processing of the message content itself. Therefore, for ease of explanation, the access network device is not shown in the subsequent drawings.
[0227] It is understood that the names of all network elements in the communication system in this application embodiment are not a limitation on the device. In other words, these network elements can be network elements that perform corresponding functions in traditional (e.g., 5G, 4G, 3G or 2G) mobile communication systems, or they can be network elements that perform corresponding functions in future (e.g., higher versions) communication systems. No limitation is made here.
[0228] The technical solutions provided in this application are illustrated through multiple embodiments, with specific reference to the descriptions of the various embodiments below. The same or similar parts between the various embodiments or implementations can be referred to mutually. In the various embodiments of this application, and in the various implementation methods / methods / implementations within each embodiment, unless otherwise specified or logically conflicting, the terminology and / or descriptions between different embodiments and between the various implementation methods / methods / implementations within each embodiment are consistent and can be mutually referenced. The technical features in different embodiments and the various implementation methods / methods / implementations within each embodiment can be combined according to their inherent logical relationships to form new embodiments, implementation methods, methods, or implementation approaches. The following embodiments of this application do not constitute a limitation on the scope of protection of this application.
[0229] Example 1:
[0230] This application's first embodiment mainly describes that when a terminal device supports IMS services but does not support the use of dedicated bearers to transmit IMS data, the first network element, upon receiving a dedicated bearer establishment instruction for IMS services, will not continue to execute the dedicated bearer establishment process, but will instead reply that the terminal device's default bearer can be used to transmit IMS data later.
[0231] For example, the first network element here can be a policy management network element (e.g., PCRF), a gateway (e.g., PGW / SGW), a mobility management network element (e.g., MME), or a UE, and the second network element can be a network element used to send a dedicated bearer establishment indication. For instance, if the first network element is a PCRF, then the second network element can be a network element in the IMS network (e.g., P-CSCF); if the first network element is a gateway, then the second network element can be a PCRF; if the first network element is an MME, then the second network element can be a gateway; if the first network element is a UE, then the second network element can be an MME.
[0232] Here, the terminal device can be either the calling UE or the called UE. In other words, the method described in Embodiment 1 applies not only to the calling UE but also to the called UE. For ease of explanation, the terminal device in this application embodiment mainly describes the implementation method related to the calling UE, while the specific implementation method of the called UE can be found in the specific implementation method of the calling UE, which will not be elaborated here.
[0233] For ease of understanding, please further refer to Figure 3, which is a flowchart illustrating a communication method provided in an embodiment of this application. As shown in Figure 3, this method can be executed jointly by a first network element and a second network element. The method may include at least steps S301-S302:
[0234] In step S301, the second network element sends a first message to the first network element. The first message is used to indicate the establishment of a dedicated bearer for the terminal device. The terminal device supports IMS services but does not support the use of a dedicated bearer to transmit IMS data.
[0235] In one possible implementation, the terminal device supports IMS services but does not support transmitting IMS data using a dedicated bearer. This includes: the terminal device supporting access to IMS services via NB-IoT; or, the terminal device supporting access to IMS services via NB-IoT access; or, the terminal device supporting making IMS calls via NB-IoT access; or, the terminal device supporting access to IMS services via NB-IoT (GEO) access; or, the terminal device supporting access to IMS services via NB-IoT satellite access; or, the terminal device supporting IMS calls based on NB-IoT access; or, the terminal device supporting IMS calls based on NB-IoT (GEO) access. Optionally, if the terminal device accesses IMS services via NB-IoT access, it can be considered that the terminal device supports accessing IMS services via NB-IoT access, and it is not necessary to explicitly indicate the terminal's capability support; this is not limited. Alternatively, both the mobile network system and the terminal device can support the above capabilities.
[0236] In this context, "terminal device supports IMS service" can be understood as the terminal device requesting or being authorized to use the IMS service. For example, "terminal device requests to use IMS service" means that the terminal device includes the APN corresponding to the IMS service in its attach request or PDN connection establishment request. Similarly, "terminal device is authorized to use IMS service" means that during the attach or PDN connection establishment process, any one of the network elements (MME, SGW, PGW, PCRF) authorizes the terminal device to use the IMS service or authorizes the terminal device to use the APN corresponding to the IMS service; or, the terminal device's subscription information indicates that the terminal device supports the IMS service or indicates that the terminal device supports the APN corresponding to the IMS service.
[0237] In one possible implementation, the terminal device does not support the use of a dedicated bearer to transmit IMS data, including: the dedicated bearer of the terminal device is occupied, or the terminal device does not support the establishment of a dedicated bearer, or the terminal device supports the transmission of IMS data through a default bearer or supports the transmission of IMS data without a dedicated bearer.
[0238] In this scenario, dedicated bearers for the terminal device are occupied. For example, a dedicated bearer for the terminal device can support the transmission of data corresponding to services other than IMS. One possible approach is that the number of DRBs (Data Radio Bearers) that a terminal device is allowed to establish depends on the device's capabilities; the stronger the capabilities, the more DRBs can be established, and vice versa. For instance, each dedicated bearer requires one DRB. If the terminal device's capabilities determine that it can only establish a maximum of two DRBs, then if both DRBs are occupied (i.e., the terminal device has already established two dedicated bearers, for example, both used to transmit services other than IMS), or if there are not enough DRBs to establish dedicated bearers, the terminal device does not support the use of dedicated bearers to transmit IMS data.
[0239] Specifically, the terminal device's inability to establish a dedicated bearer can be understood as the terminal device's capabilities being insufficient to support this. For example, if the terminal device's access method is narrowband IoT access (e.g., the terminal device is an NB-IoT device, or the terminal device's wireless access method RAT type is NB-IoT or NB-IoT(GEO), etc.), the terminal device does not support using a dedicated bearer to transmit IMS data. As another example, if the terminal device supports 0 DRBs, then the terminal device does not support establishing a dedicated bearer, meaning it does not support using a dedicated bearer to transmit IMS data (e.g., the terminal device's access method is narrowband IoT access).
[0240] The terminal device supports transmitting IMS data via the default bearer or without a dedicated bearer. This can be understood as follows: regardless of whether the terminal device's dedicated bearer is occupied or whether the terminal device supports establishing a dedicated bearer, the terminal device always transmits IMS data via the default bearer.
[0241] Correspondingly, the first network element can receive the first message from the second network element.
[0242] When the second network element is an IMS network element (e.g., P-CSCF) and the first network element is a policy management network element (e.g., PCRF), the first message here can be an AAR message, which may include the address of the IMS data (i.e., the destination address when the UE sends IMS data) / domain name, media type, maximum and minimum bandwidth of the media, etc.
[0243] In one possible implementation, the second network element can receive a response message to the session invitation message before sending the first message.
[0244] In this context, a session invitation message (e.g., an INVITE message) is used to request a terminal device (e.g., UE-A) to make an IMS call with another terminal device (e.g., UE-B), or to instruct a terminal device to initiate an IMS call, or to instruct a calling UE to initiate an IMS call. It can be understood that the INVITE message may carry Session Description Protocol (SDP) information (or initial SDP, or SDP offer). SDP information is used by the calling UE and the called UE to negotiate the media types and codec capabilities they support. The SDP information in the INVITE message may carry the media types supported by the calling UE, the media codec capabilities, etc.
[0245] The response message (e.g., 183 message, 18x message) carries SDP information (which can be called the SDP answer), which can carry the media types and codec capabilities supported by the called UE. In other words, the essence of the response message here is to instruct the calling and called UEs to negotiate the media types and media codec capabilities they support.
[0246] In one possible implementation, before the second network element sends the first message, the terminal device has already established a default bearer. The default bearer of the terminal device does not include or has not been assigned a service flow template, or the service flow template assigned to the default bearer includes: a wildcard, or an address / domain name used for transmitting IMS data (e.g., the address of a device on the path transmitting the terminal's IMS data, such as the address of an AGW network element, or the destination address when the terminal sends IMS data). In other words, the default bearer of the terminal device may not have been assigned a service flow template, or it may have been assigned a service flow template, which can be set to: a wildcard or empty, or an address / domain name used for transmitting IMS data. It is understood that this application embodiment ensures that when IMS data is subsequently transmitted using the default bearer by limiting the setting of the service flow template of the terminal device's default bearer, data packets will not be dropped by the filter. Furthermore, the configuration method of the terminal device's default bearer is quite diverse, possibly any of the above methods, or other methods, and its applicability is strong; therefore, it is not limited here.
[0247] For example, the default bearer service flow template can be set by the gateway network element (e.g., PGW or SGW) after determining that the terminal device meets the connection conditions during the terminal device's attach process or PDN connection establishment process. The connection conditions here include that the terminal device supports IMS service and does not support the use of dedicated bearer to transmit IMS data (e.g., the terminal device's RAT type is NB-IoT or NB-IoT (GEO), and the APN requested by the terminal device is the APN of the IMS service), or that the terminal device's attach or PDN connection establishment request is authorized.
[0248] In one possible implementation, before the second network element sends the first message, one or more network elements in the core network (e.g., mobility management network element, gateway network element, policy management network element) can authorize the terminal device to use IMS services (e.g., authorize it to make IMS calls), or authorize the terminal device to use the default bearer to transmit IMS data. The authorization execution entity is relatively flexible, and you can refer to the description in the embodiment corresponding to Figure 4 below.
[0249] In one possible implementation, if the default bearer of the terminal device supports the transmission of IMS data, the first network element, after receiving the first message, can directly execute step S302 without sending a bearer establishment request to the third network element. Here, the third network element can also be a gateway network element (e.g., PGW or SGW). That is, the first network element does not need to send PCC rules to the gateway network element. The PCC rules can be understood as information used to indicate policies, specifically including QoS parameters and identification information of the services using those QoS parameters (e.g., IP 5-tuples, 3-tuples, etc.). The PCC rules can be used to trigger the establishment / activation process of a dedicated bearer.
[0250] Optionally, if the default bearer of the terminal device does not support the transmission of IMS data, the first network element needs to send a third message to the third network element after receiving the first message. The first network element can continue to execute the following steps S302 after receiving the fourth message returned by the third network element.
[0251] For example, a third message may include QoS parameters carried by default (also known as default QoS parameters) or may not include QoS parameters (also known as PCC rules without QoS parameters).
[0252] In one possible implementation, the third message (e.g., a RAR message) can be used to indicate the use of the terminal device's default bearer. In this case, the fourth message can be used to indicate a refusal to establish a dedicated bearer. This fourth message may include fourth indication information indicating that the terminal device's dedicated bearer is occupied, or that the terminal device does not support establishing a dedicated bearer (e.g., the terminal device's access method is narrowband IoT access). For example, the fourth message may be a credit control request (CCR) message, which can be used to indicate that dedicated bearer establishment failed, i.e., dedicated resource reservation failed. Optionally, the fourth message may also be used to indicate that the terminal device's default bearer has been updated. This may include the bearer identifier of the terminal device's default bearer or the fourth indication information, which indicates the use of the terminal device's default bearer.
[0253] In one possible implementation, the third message here can be used to indicate an update to the default bearer of the terminal device. For example, the third message may include an address / domain name used for transmitting IMS data, which is used to update the service flow template of the UE-A's default bearer. It is understood that, in addition to including the aforementioned address / domain name, the third message may also include QoS parameters of the default bearer; alternatively, the third message may include an address / domain name used for transmitting IMS data but not QoS parameters. In this case, the fourth message here can also be used to indicate that the default bearer of the terminal device has been updated. It is understood that the fourth message may include a bearer identifier or fourth indication information of the terminal device's default bearer, which is used to indicate the use of the terminal device's default bearer.
[0254] In one possible implementation, the third message here can be used to indicate the update of the default bearer of the terminal device. In this case, the fourth message here can also be a response message to the third message, used to indicate the update of the default bearer of the terminal device. For example, the fourth message may include a first service flow template, which includes an address / domain name for transmitting IMS data.
[0255] When the second network element is a policy management network element (e.g., PCRF) and the first network element is a gateway network element (e.g., PGW), the first message here can be a re-Authentication Request (RAR) message or an IP-CAN session establishment / modification message. The RAR message can be used to indicate session-related information, which may include PCC rules (specifically, QoS parameters of the dedicated bearer) and the address / domain name used to transmit IMS data.
[0256] In one possible implementation, before the second network element sends the first message to the first network element, the second network element may receive a fifth message (i.e., a message used to indicate the establishment of a dedicated bearer for the terminal device, such as an AAR message) from the fourth network element (e.g., P-CSCF). This message may include the address of the IMS data (i.e., the destination address when the UE sends the IMS data) / domain name, media type, maximum and minimum bandwidth of the media, etc.
[0257] In one possible implementation, if the default bearer of the terminal device does not support the transmission of IMS data, the first network element, after receiving the first message, can send a third message to the third network element (e.g., via the PGW). Here, the third network element can be a mobility management network element (e.g., MME). This third message can be used to instruct the terminal device to update its default bearer; for example, the third message can be an update bearer request, which may include the identifier of the terminal device's default bearer and a first service flow template, which includes an address / domain name for transmitting IMS data. The first network element can continue to execute step S302 until it receives the fourth message returned by the third network element.
[0258] The fourth message here can be used to indicate that the default bearer of the terminal device has been updated. For example, the fourth message includes a bearer identifier of the default bearer of the terminal device or fourth indication information, which is used to indicate that the default bearer of the terminal device is used.
[0259] When the second network element is a gateway network element (e.g., PGW) and the first network element is a mobility management network element (e.g., MME), the first message here can be a bearer creation message (e.g., create bearer request), which can carry information for establishing a dedicated bearer, specifically including the address of the IMS data (i.e., the destination address when the UE sends IMS data) / domain name.
[0260] In one possible implementation, before the second network element sends the first message to the first network element, the second network element may receive a third message (i.e., a message indicating the establishment of a dedicated bearer for the terminal device, such as a RAR message) from a third network element (i.e., a policy management network element, such as a PCRF). The RAR message may be used to indicate session-related information, which may include PCC rules (specifically, QoS parameters of the dedicated bearer) and addresses / domain names for transmitting IMS data.
[0261] When the second network element is a mobility management network element (e.g., MME) and the first network element is a terminal device, the first message here can be an activation bearer context request (e.g., activate bearer context request).
[0262] In one possible implementation, the first message can be used to update the default bearer of the terminal device. For example, the first message may include a first service flow template, which includes an address / domain name for transmitting IMS data.
[0263] In one possible implementation, before the second network element sends the first message to the first network element, the second network element can receive a third message from the third network element. Here, the third network element can be a gateway network element (e.g., PGW / SGW), and the third message can be a bearer creation message (e.g., create bearer request), which can carry information for establishing a dedicated bearer, specifically including the address of the IMS data (i.e., the destination address when the UE sends IMS data) / domain name.
[0264] In step S302, the first network element sends a second message to the second network element. The second message is a reply to the first message, or the second message is used to indicate the default bearer of the terminal device, which is used to transmit IMS data, or the second message is used to indicate that the establishment of a dedicated bearer is refused, or the second message is used to indicate that the default bearer of the terminal device is updated, and the updated default bearer is used to transmit IMS data.
[0265] In one possible implementation, the default bearer is used to transmit IMS data, including: the default bearer of the terminal device does not include or is not assigned (or does not assign) a service flow template, or the service flow template assigned to the default bearer includes: wildcards, or addresses / domain names used to transmit IMS data.
[0266] In this context, if the default bearer of the terminal device does not include or has not been assigned (or is not assigned) a service flow template, or if the service flow template assigned to the default bearer includes wildcards, it can be understood that the default bearer of the terminal device does not restrict the type of data packets to be transmitted. That is, data packets corresponding to IMS data can also be transmitted through the default bearer. In other words, the default bearer allows IMS data transmission.
[0267] Correspondingly, the second network element can receive the second message from the first network element.
[0268] When the second network element is an IMS network element (e.g., P-CSCF) and the first network element is a policy management network element (e.g., PCRF), the second message here can be a reply message to the first message, or the second message can be used to indicate the default bearer of the terminal device, which is used to transmit IMS data, or the second message can be used to indicate that the establishment of a dedicated bearer is refused. For example, the second message here can be a RAR message. A RAR message can be understood as authentication / authorization information related to the session, specifically including the session identifier, whether the bearer establishment was successful, or the bearer being released and the reason for the release. It should be understood that the RAR message can be used to indicate session-related information, or to indicate that the core network element has failed to establish a dedicated bearer.
[0269] Optionally, the second message is used to instruct the default bearer of the terminal device to be updated, and the updated default bearer is used to transmit IMS data. For example, the second message may include a first service flow template, which includes an address / domain name for transmitting IMS data.
[0270] In one possible implementation, after receiving the second message from the first network element, the second network element can send a response message to the terminal device, so that the terminal device returns a feedback message (e.g., a PRACK message) to the second network element.
[0271] Here, the response message refers to a reply message to the session invitation message (e.g., 183 message, 18x message). For example, the response message can be used to instruct the terminal device not to update or establish a bearer, or to instruct the terminal device to reply with a feedback message in response to the response message, or to instruct the terminal device to reply with a feedback message in response to the response message (e.g., a PRACK message) if a dedicated bearer has not been established.
[0272] For example, the response message can also be used to instruct the terminal device to update its default bearer. For example, the response message can include a first service flow template, which includes an address / domain name for transmitting IMS data.
[0273] When the second network element is a policy management network element (e.g., PCRF) and the first network element is a gateway network element (e.g., PGW), the second message here can be a reply message to the first message. For example, the second message here can be a CCR message or a response message to an IP-CAN session establishment / modification message.
[0274] In one possible implementation, the second message can be used to indicate the default bearer of the terminal device, which is used to transmit IMS data. For example, the second message includes a bearer identifier of the terminal device's default bearer or third indication information. The third indication information indicates the use of the terminal device's default bearer. It is understood that the second message carries diverse information and has strong applicability. Furthermore, indicating the terminal device's default bearer through the bearer identifier or third indication information can effectively improve the reliability of data transmission. The bearer identifier of the default bearer can be used to set the transmission parameters of the IMS data, for example, setting the encoding / decoding algorithm corresponding to the IMS data to a low rate.
[0275] In one possible implementation, the second message can also be used to indicate that the establishment of a dedicated bearer is refused (or described as: to indicate that the activation of a dedicated bearer is refused). For example, the second message may include third indication information, which can be used to indicate that the terminal device does not support the establishment of a dedicated bearer.
[0276] In one possible implementation, if the second network element receives a fifth message (e.g., an AAR message) from the fourth network element before sending the first message to the first network element, then the second network element can send a sixth message to the fourth network element after receiving the second message sent by the first network element. Here, the sixth message (e.g., a RAR message) can be a reply to the fifth message, or it can be used to indicate the default bearer of the terminal device, which is used to transmit IMS data, or it can be used to indicate a refusal to establish a dedicated bearer.
[0277] When the second network element is a gateway network element (e.g., PGW) and the first network element is a mobility management network element (e.g., MME), for example, the second message here can be a bearer creation response (e.g., create bearer response).
[0278] In one possible implementation, the second message can be used to indicate the default bearer of the terminal device, which is used to transmit IMS data. For example, the second message includes a bearer identifier of the default bearer of the terminal device or third indication information. The third indication information is used to indicate the use of the default bearer of the terminal device. The bearer identifier of the default bearer can be used to set the transmission parameters of the IMS data, for example, setting the encoding and decoding algorithm corresponding to the IMS data to a low rate.
[0279] In one possible implementation, the second message can also be used to indicate that the establishment of a dedicated bearer is refused (or described as: to indicate that the activation of a dedicated bearer is refused). For example, the second message may include third indication information, which can be used to indicate that the terminal device does not support the establishment of a dedicated bearer.
[0280] In one possible implementation, if the second network element receives a third message (e.g., a RAR message) from a third network element (e.g., a PCRF) before sending the first message to the first network element, then the second network element can send a fourth message (e.g., a CCR message) to the third network element after receiving the second message sent by the first message. Here, the fourth message is used to indicate a refusal to establish a dedicated bearer. For example, the fourth message includes fourth indication information, which indicates that the dedicated bearer of UE-A is occupied, or that UE-A does not support the establishment of a dedicated bearer.
[0281] When the second network element is a mobility management network element (e.g., MME) and the first network element is a terminal device, the second message here can be an activate bearer context response (e.g., activate bearer context response). The second message here can be a reply to the first message, or it can be used to indicate the terminal device's default bearer for transmitting IMS data, or it can also be used to indicate a refusal to establish a dedicated bearer (or described as: indicating a refusal to activate a dedicated bearer).
[0282] In one possible implementation, if the second network element receives a third message (bearer creation message, e.g., create bearer request) from a third network element (e.g., PGW / SGW) before sending the first message to the first network element, then the second network element can send a fourth message (bearer creation response, e.g., create bearer response) to the third network element after receiving the second message sent by the first message.
[0283] The fourth message can be used to indicate that the default bearer of the terminal device has been updated and is used to transmit IMS data, or it can be used to indicate that the establishment of a dedicated bearer is refused.
[0284] For example, if the fourth message is used to indicate that the default bearer of the terminal device has been updated, the fourth message may include the bearer identifier of the default bearer of the terminal device or the fourth indication information, which is used to indicate the use of the default bearer of UE-A.
[0285] For example, if the fourth message is used to indicate that the establishment of a dedicated bearer is refused, the fourth message may include fourth indication information, which indicates that the dedicated bearer of the terminal device is occupied, or the fourth indication information indicates that the terminal device does not support the establishment of a dedicated bearer.
[0286] In one possible implementation, the first network element can receive a response message from the fifth network element (IMS network element, e.g., P-CSCF) so that the terminal device can return a feedback message (e.g., PRACK) to the fifth network element.
[0287] Here, the response message refers to a reply message to the session invitation message (e.g., a 183 message). For example, the response message can be used to instruct the terminal device not to update or establish a bearer, or it can be used to instruct the terminal device to reply with a feedback message in response to the response message, or it can be used to instruct the terminal device to reply with a feedback message in response to the response message without establishing a dedicated bearer.
[0288] For example, the response message can also be used to instruct the terminal device to update its default bearer. For example, the response message can include a first service flow template, which includes an address / domain name for transmitting IMS data.
[0289] In this application, after receiving the first message, the first network element does not continue the dedicated bearer establishment process. Instead, it flexibly replies with a second message based on the actual situation of the terminal device's default bearer. The content of the second message relates to whether the terminal device's default bearer supports IMS data transmission. For example, if the terminal device's default bearer does not support IMS data transmission, the second message can update the terminal device's default bearer to enable IMS data transmission. If the terminal device supports IMS data transmission, the second message can instruct that the terminal device's default bearer be used directly for subsequent IMS data transmission. In other words, after receiving the dedicated bearer establishment instruction, the first network element does not need to establish a dedicated bearer for the terminal device. Instead, it uses the terminal device's default bearer to transmit IMS data. Therefore, for the terminal device, whether it is a terminal device whose terminal capability does not support establishing a dedicated bearer (e.g., a UE accessed via NB-IoT) or a terminal device whose dedicated bearer is occupied, the effect of transmitting IMS data through the default bearer without establishing a dedicated bearer can be achieved, thereby effectively ensuring its support for IMS services.
[0290] It is understandable that after receiving the first message, the first network element needs to determine whether the terminal device supports IMS service and whether the terminal device supports transmitting IMS data using a dedicated bearer. If it is determined that the terminal device supports IMS service (for example, by determining that the terminal device supports IMS service based on the APN corresponding to the IMS service included in the attach request or PDN connection establishment request), and it is determined that the terminal device does not support transmitting IMS data using a dedicated bearer (for example, by determining that the terminal device is an NB-IoT device, or by determining that the RAT type of the terminal device is NB-IoT or NB-IoT(GEO), etc.), then the first network element can send a second message to the second network element.
[0291] The methods by which the first network element determines that a terminal device supports IMS services are diverse and have strong applicability. For example, it can be determined by the first network element itself, or it can be determined by the first network element based on indication information received from other network elements. For instance, the indication information received by the first network element could be the terminal device's subscription information provided by the HSS, which could be used to indicate that the terminal device supports IMS services or to indicate that the terminal device supports the APN corresponding to the IMS service. Of course, the methods by which the first network element determines that a terminal device does not support the transmission of IMS data using a dedicated bearer are also diverse. It can be determined by the first network element itself, or it can be determined by the first network element based on indication information received from other network elements. For example, the indication information received by the first network element could be indication information sent by access network equipment or other network elements, which could be used to indicate that the terminal device's RAT type is NB-IoT or NB-IoT(GEO), etc.
[0292] In one possible implementation, during the core network registration process, the first network element can receive first and second indication information from other network elements. The first indication information can indicate one or more of the following: the dedicated bearer of the terminal device is occupied, or the terminal device does not support establishing a dedicated bearer; the second indication information can indicate that the terminal device supports or authorizes IMS services. The first and second indication information can be in the same message or in different messages; this is not limited here. Furthermore, after receiving the first message, the first network element can determine, based on the first indication information, that the terminal device does not support transmitting IMS data using a dedicated bearer, and based on the second indication information, determine that the terminal device supports IMS services. This effectively saves the computing power of the first network element.
[0293] For ease of understanding, please refer to Figure 4, which is a schematic diagram of a core network registration process (also known as an attach process) provided in an embodiment of this application, as detailed in 3GPP protocol TS23.401. As shown in Figure 4, this core network registration process may include at least steps S401-S415, wherein steps S403, S405, and S407 are optional steps. A detailed description follows:
[0294] In step S401, UE-A sends a connection request to RAN-A.
[0295] The connection request (e.g., attach / PDN connection request) may include initial indication information, which may be used to indicate that the UE-A's access point name (APN) is IMS.
[0296] In step S402, RAN-A sends a connection request to MME-A.
[0297] The connection request may include initial indication information and first indication information. The first indication information may indicate that the UE-A's access method is narrowband IoT access (e.g., NB-IoT GEO access).
[0298] Step S403: MME-A authorizes UE-A to use IMS services.
[0299] For example, when the MME-A determines that the UE-A's request information matches the subscription information, it can authorize the UE-A to make a satellite phone call.
[0300] In step S404, MME-A sends a session creation request to PCRF-A via PGW-A / SGW-A.
[0301] Here, the session creation request (e.g., create session request) is used to create the default bearer for UE-A, and the indication information it carries may include initial indication information and first indication information. After MME-A executes step S403, the session creation request may also include second indication information (e.g., for instructing UE-A to authorize IMS services).
[0302] Step S405: PCRF-A authorizes UE-A to use IMS services.
[0303] In step S406, PCRF-A sends a session creation response to PGW-A / SGW-A.
[0304] Here, the session creation response (e.g., IP-CAN session establish response) is a response message to the session creation request. After PCRF-A executes step S405, the session creation response may include second indication information.
[0305] Step S407: PGW-A / SGW-A authorizes UE-A to use IMS services.
[0306] In step S408, if it is determined that UE-A supports IMS services and that UE-A does not support transmitting IMS data using a dedicated bearer, then PGW-A / SGW-A will set the TFT of the default bearer to the address pool corresponding to the wildcard / IMS data, or will not allocate a TFT.
[0307] The address pool corresponding to IMS data refers to the address / address pool of the AGW, that is, the destination address for the UE-A to access the AGW. It can be understood that the address pool corresponding to IMS data can include addresses / domain names used for transmitting IMS data.
[0308] In step S409, PGW-A / SGW-A sends a session creation response to MME-A.
[0309] The session creation response (e.g., create session response) is a response message to the session creation request. This session creation response may carry bearer configuration information. The bearer configuration information may be used to indicate that the default bearer does not include or has not been assigned a service flow template. Alternatively, the bearer configuration information may be used to indicate that the service flow template assigned to the default bearer includes: wildcards, or addresses / domain names used to transmit IMS data.
[0310] In step S410, MME-A sends an initial context establishment request to RAN-A.
[0311] The initial context request (e.g., initial context setup request) here can carry configuration information.
[0312] Step S411, RAN-A sends a connection configuration message to UE-A.
[0313] The connection configuration message here (e.g., Radio Resource Control connection reconfiguration) can carry bearer configuration information.
[0314] In step S412, UE-A sends a configuration completion message to RAN-A.
[0315] Here, the configuration completion response (e.g., Radio Resource Control connection reconfiguration complete) is the response message for the link configuration message.
[0316] In step S413, RAN-A sends an initial context establishment response to MME-A.
[0317] Here, the initial context setup response (e.g., the initial context setup response) is the response message to the initial context setup request.
[0318] In step S414, UE-A sends a connection completion message to RAN-A.
[0319] Here, the connection completion response (e.g., direct transter) is used to indicate that the attach process is complete.
[0320] In step S415, RAN-A sends a connection completion message to MME-A.
[0321] For example, the connection completion message (e.g., attach complete) here is used to indicate that the attach process is complete.
[0322] Since the first network element here can be any one of the following: PCRF, gateway (e.g., PGW / SGW), MME, or UE, the process will be explained in detail below with reference to the accompanying diagrams for easier understanding:
[0323] If the first network element is PCRF-A, then the second network element is P-CSCF-A, the third network element is PGW-A / SGW-A, the fourth network element is MME-A, and the fifth network element is HLR / HSS. For details, please refer to the following implementation methods one, two, three, and four.
[0324] Implementation method 1:
[0325] Implementation Method 1 is mainly used to introduce that when the default bearer of UE-A supports the transmission of IMS data, after receiving the first message from P-CSCF-A, PCRF-A does not send a bearer establishment request to the third network element, but directly replies to the second message to P-CSCF-A.
[0326] For example, please refer to Figure 5, which is an interactive schematic diagram of an IMS service scenario provided in an embodiment of this application. As shown in Figure 5, the IMS service scenario may include a core network registration process, an IMS network registration process, and an IMS call establishment process. The core network registration process can be specifically described in the embodiment corresponding to Figure 4 above, and will not be limited here. The IMS call establishment process shown in Figure 5 may specifically include steps S501-S509:
[0327] Step S501, UE-A sends a session invitation message to P-CSCF-A.
[0328] For example, a session invitation message can be an INVITE message.
[0329] Step S502, P-CSCF-A receives the response message of the session invitation message.
[0330] For example, the response message could be a 183 message.
[0331] In step S503, P-CSCF-A sends the first message to PCRF-A.
[0332] The first message here can be used to instruct the establishment of a dedicated bearer for the terminal device. For example, the first message can be an AAR message, which may include the address (i.e., the destination address when the UE sends IMS data) / domain name of the IMS data, the media type, the maximum and minimum bandwidth of the media, etc.
[0333] In step S504, PCRF-A determines that UE-A supports IMS services and that UE-A does not support transmitting IMS data using a dedicated bearer.
[0334] It should be understood that after PCRF-A executes step S504, it does not send a bearer establishment request to PGW-A / SGW-A. In other words, PCRF-A does not need to send PCC rules to PGW-A / SGW-A. PCC rules can be understood as information used to indicate policies, which may specifically include QoS parameters and identification information of the services using those QoS parameters (e.g., IP 5-tuples, 3-tuples, etc.).
[0335] In step S505, PCRF-A sends a second message to P-CSCF-A.
[0336] Here, the second message can be a reply to the first message, or it can be used to indicate the default bearer of the terminal device, which is used to transmit IMS data, or it can be used to indicate that the establishment of a dedicated bearer is refused. For example, the second message here can be a RAR message.
[0337] Step S506, P-CSCF-A sends a response message to UE-A.
[0338] Here, the response message refers to the reply message to the session invitation message (e.g., a 183 message).
[0339] It is understood that existing UE-A needs to trigger the establishment process of a dedicated bearer when it receives a response message, and sends a feedback message (e.g., a PRACK message) to P-CSCF-A after the dedicated bearer is established. However, in this embodiment of the application, UE-A does not need to establish a dedicated bearer. Therefore, in order to improve the response timeliness of UE-A, in one possible implementation, the response message sent in step S506 can be used to instruct the terminal device not to update or establish a bearer, or the response message can be used to instruct the terminal device to reply with a feedback message in response to the response message, or the response message can be used to instruct the terminal device to reply with a feedback message in response to the response message without establishing a dedicated bearer.
[0340] In step S507, UE-A sends a feedback message to P-CSCF-A.
[0341] In step S508, after receiving the feedback message, UE-B can send a response message to UE-A to instruct the called user to answer the call.
[0342] For example, the response message (e.g., a 200 message) is the called UE's response to the PRACK message.
[0343] Step S509, UE-B sends a ringing message.
[0344] After the IMS call setup process is completed, IMS data can be transmitted through the default bearer of UE-A. Of course, if UE-B does not support the use of a dedicated bearer to transmit IMS data, then UE-B can refer to the specific implementation of UE-A so that IMS data can be transmitted through the default bearer of UE-B. This will not be elaborated further here.
[0345] Implementation Method Two:
[0346] The second implementation method is mainly used to introduce that when the default bearer of UE-A supports the transmission of IMS data, after receiving the first message from P-CSCF-A, PCRF-A can send a third message to PGW-A / SGW-A (to indicate the use of the default bearer of the terminal equipment), and when it receives the response, it can directly reply to P-CSCF-A with a second message.
[0347] For example, please refer to Figure 6, which is a second interactive schematic diagram corresponding to an IMS service scenario provided in an embodiment of this application. As shown in Figure 6, the IMS service scenario may include a core network registration process, an IMS network registration process, and an IMS call establishment process. The core network registration process can be specifically referred to in the description of the embodiment corresponding to Figure 4 above, and will not be limited here. The IMS call establishment process shown in Figure 6 may specifically include steps S601-S612:
[0348] Step S601, UE-A sends a session invitation message to P-CSCF-A.
[0349] Step S602, P-CSCF-A receives the response message of the session invitation message.
[0350] In step S603, P-CSCF-A sends the first message to PCRF-A.
[0351] In step S604, PCRF-A determines that UE-A supports IMS services and that UE-A does not support transmitting IMS data using a dedicated bearer.
[0352] In step S605, PCRF-A sends a third message to PGW-A / SGW-A.
[0353] For example, the third message here can be a RAR message, which may include QoS parameters of the default bearer (also known as default QoS parameters) or no QoS parameters (also known as PCC rules without QoS parameters).
[0354] It is understood that after executing step S603, the existing PCRF-A sends a bearer establishment request to the PGW-A / SGW-A. This bearer establishment request can carry PCC rules, which may include QoS parameters for the dedicated bearer. However, in this embodiment, the PCRF-A can update the QoS parameters of the dedicated bearer in the PCC rules to the QoS parameters of the default bearer, or delete the QoS parameters of the dedicated bearer in the PCC rules to obtain the third message.
[0355] Step S606: PGW-A / SGW-A determines that UE-A supports IMS services and determines that UE-A does not support the use of dedicated bearers to transmit IMS data.
[0356] In step S607, PGW-A / SGW-A sends a fourth message to PCRF-A.
[0357] The fourth message here can be used to indicate that the establishment of a dedicated bearer is refused. For example, the fourth message here can be a CCR message, which can be used to indicate that the establishment of the dedicated bearer has failed, that is, the reservation of dedicated resources has failed.
[0358] In step S608, PCRF-A sends a second message to P-CSCF-A.
[0359] Here, the second message can be a reply to the first message, or it can be used to indicate the default bearer of the terminal device, which is used to transmit IMS data, or it can be used to indicate that the establishment of a dedicated bearer is refused.
[0360] In step S609, P-CSCF-A sends a response message to UE-A.
[0361] In one possible implementation, the response message here can be used to instruct the terminal device not to update or establish a bearer, or the response message can be used to instruct the terminal device to reply with a feedback message in response to the response message, or the response message can be used to instruct the terminal device to reply with a feedback message in response to the response message if a dedicated bearer has not been established.
[0362] In step S610, UE-A sends a feedback message to P-CSCF-A.
[0363] In step S611, after receiving the feedback message, UE-B can send a response message to UE-A to instruct the called user to answer the call.
[0364] In step S612, UE-B sends a ringing message.
[0365] The specific implementation of steps S601-S604 can be found in the description of steps S501-S504 in the embodiment corresponding to Figure 5 above, and the specific implementation of steps S609-S612 can be found in the description of steps S506-S509 in the embodiment corresponding to Figure 5 above, and will not be repeated here.
[0366] Implementation method three:
[0367] The third implementation method is mainly used to introduce that when the default bearer of UE-A does not support the transmission of IMS data, after receiving the first message from P-CSCF-A, PCRF-A can send a third message to PGW-A / SGW-A to update the default bearer of the terminal device, thereby ensuring that the terminal device supports IMS services.
[0368] For example, please refer to Figure 7, which is a schematic diagram of an interaction corresponding to an IMS service scenario provided in an embodiment of this application. As shown in Figure 7, the IMS service scenario may include a core network registration process, an IMS network registration process, and an IMS call establishment process. Specifically, the IMS call establishment process shown in Figure 7 may include steps S701-S715:
[0369] Step S701, UE-A sends a session invitation message to P-CSCF-A.
[0370] Step S702, P-CSCF-A receives the response message of the session invitation message.
[0371] In step S703, P-CSCF-A sends the first message to PCRF-A.
[0372] In step S704, PCRF-A determines that UE-A supports IMS services and that UE-A does not support transmitting IMS data using a dedicated bearer.
[0373] In step S705, PCRF-A sends a third message to PGW-A / SGW-A.
[0374] Here, the third message (e.g., a RAR message) can be used to instruct the terminal device to update its default bearer. For example, the third message may include an address / domain name used to transmit IMS data, which is used to update the service flow template of the UE-A's default bearer.
[0375] Step S706: If it is determined that UE-A supports IMS services and that UE-A does not support transmitting IMS data using a dedicated bearer, then PGW-A / SGW-A adjusts the TFT of the default bearer of UE-A.
[0376] In this embodiment of the application, the adjusted TFT can be referred to as the first TFT, which is used to update the default bearer of UE-A. The first TFT includes an address / domain name for transmitting IMS data.
[0377] In step S707, PGW-A / SGW-A sends a bearer update request to MME-A.
[0378] The bearer update request may include a first TFT.
[0379] In step S708, MME-A sends a bearer update request to UE-A.
[0380] The bearer update request (e.g., bearer modification request / RRC connection reconfiguration) may also include the first TFT.
[0381] In step S709, UE-A sends a bearer update response to MME-A.
[0382] The bearer update response (e.g., bearer modify response / RRC connection reconfiguration complete / update bearer response) is a response message to the bearer update request, which is used to indicate that the default bearer of the terminal device has been updated. For example, the bearer update response may include the first TFT.
[0383] In step S710, PGW-A / SGW-A sends a fourth message to PCRF-A.
[0384] The fourth message here can be used to indicate that the default bearer of the terminal device has been updated.
[0385] In step S711, PCRF-A sends a second message to P-CSCF-A.
[0386] The second message here can be used to instruct the default bearer of the terminal device to be updated, and the updated default bearer is used to transmit IMS data.
[0387] In step S712, P-CSCF-A sends a response message to UE-A.
[0388] In one possible implementation, the response message here can be used to instruct the terminal device not to establish a bearer, or the response message can be used to instruct the terminal device to reply with a feedback message in response to the response message, or the response message can be used to instruct the terminal device to reply with a feedback message in response to the response message without establishing a dedicated bearer.
[0389] In step S713, UE-A sends a feedback message to P-CSCF-A.
[0390] In step S714, after receiving the feedback message, UE-B can send a response message to UE-A to instruct the called user to answer the call.
[0391] Step S715, UE-B sends a ringing message.
[0392] The specific implementation of steps S701-S704 can be found in the description of steps S501-S504 in the embodiment corresponding to Figure 5 above, and the specific implementation of steps S711-S715 can be found in the description of steps S505-S509 in the embodiment corresponding to Figure 5 above, and will not be repeated here.
[0393] Implementation Method 4:
[0394] Implementation method four mainly describes how, when the default bearer of UE-A does not support the transmission of IMS data, PCRF-A, after receiving the first message from P-CSCF-A, can send a third message to PGW-A / SGW-A to update the default bearer of the terminal device, thereby ensuring that the terminal device supports IMS services. The first TFT (i.e., the result of adjusting the TFT of the default bearer) can be sent to UE-A through the response message of the session invitation message.
[0395] For example, please refer to Figure 8, which is an interactive schematic diagram of an IMS service scenario provided in an embodiment of this application. As shown in Figure 8, the IMS service scenario may include a core network registration process, an IMS network registration process, and an IMS call establishment process. Specifically, the IMS call establishment process shown in Figure 8 may include steps S801-S812:
[0396] Step S801, UE-A sends a session invitation message to P-CSCF-A.
[0397] In step S802, P-CSCF-A receives a response message to the session invitation message.
[0398] In step S803, P-CSCF-A sends the first message to PCRF-A.
[0399] In step S804, PCRF-A determines that UE-A supports IMS services and that UE-A does not support transmitting IMS data using a dedicated bearer.
[0400] In step S805, PCRF-A sends a third message to PGW-A / SGW-A.
[0401] The third message here is used to instruct the terminal device to update its default bearer.
[0402] Step S806: If it is determined that UE-A supports IMS services and that UE-A does not support transmitting IMS data using a dedicated bearer, then PGW-A / SGW-A adjusts the TFT of the default bearer of UE-A.
[0403] The adjusted TFT (i.e., the first TFT) can be used to update the default bearer of UE-A. The first TFT includes the address / domain name used to transmit IMS data.
[0404] In step S807, PGW-A / SGW-A sends a fourth message to PCRF-A.
[0405] Here, the fourth message is a response message to the third message, which can be used to indicate that the default bearer of UE-A should be updated. For example, the fourth message may include the first TFT.
[0406] In step S808, PCRF-A sends a second message to P-CSCF-A.
[0407] The second message here can be used to instruct the default bearer of the terminal device to be updated, and the updated default bearer is used to transmit IMS data. For example, the second message may include a first TFT.
[0408] In step S809, P-CSCF-A sends a response message to UE-A.
[0409] For example, the response message may include a first TFT to cause the UE-A to update its default bearer.
[0410] In one possible implementation, the response message here can be used to instruct the terminal device not to establish a bearer, or the response message can be used to instruct the terminal device to reply with a feedback message in response to the response message, or the response message can be used to instruct the terminal device to reply with a feedback message in response to the response message without establishing a dedicated bearer.
[0411] In step S810, UE-A sends a feedback message to P-CSCF-A.
[0412] In step S811, after receiving the feedback message, UE-B can send a response message to UE-A to instruct the called user to answer the call.
[0413] In step S812, UE-B sends a ringing message.
[0414] The specific implementation of steps S801-S804 can be found in the description of steps S501-S504 in the embodiment corresponding to Figure 5 above. The specific implementation of steps S805-S806 can be found in the description of steps S705-S706 in the embodiment corresponding to Figure 7 above. The specific implementation of steps S810-S812 can be found in the description of steps S506-S509 in the embodiment corresponding to Figure 5 above. They will not be repeated here.
[0415] Compared to implementation method three, implementation method four sends the first TFT to the terminal device through a response message, which can effectively reduce the signaling interaction between network elements. This not only saves the resources consumed during signaling transmission, but also improves the efficiency of the IMS call setup process.
[0416] If the first network element is PGW-A / SGW-A, then the second network element can be PCRF-A, the third network element can be MME-A, the fourth network element can be P-CSCF-A, and the fifth network element can be HLR / HSS. See Implementation Methods 5 and 6 below for details.
[0417] Implementation Method 5:
[0418] Implementation method five is mainly used to introduce how, when the default bearer of UE-A supports the transmission of IMS data, PGW-A / SGW-A directly replies to PCRF-A with a second message after receiving the first message from PCRF-A.
[0419] For example, please refer to Figure 9, which is a schematic diagram of an interaction corresponding to an IMS service scenario provided in an embodiment of this application. As shown in Figure 9, the IMS service scenario may include a core network registration process, an IMS network registration process, and an IMS call establishment process. The core network registration process can be specifically referred to in the description of the embodiment corresponding to Figure 4 above, and will not be limited here. The IMS call establishment process shown in Figure 9 may specifically include steps S901-S911:
[0420] Step S901, UE-A sends a session invitation message to P-CSCF-A.
[0421] Step S902, P-CSCF-A receives the response message of the session invitation message.
[0422] In step S903, P-CSCF-A sends the fifth message to PCRF-A.
[0423] The fifth message here can be used to instruct the establishment of a dedicated bearer for the terminal device; for example, the first message can be an AAR message.
[0424] In step S904, PCRF-A sends the first message to PGW-A / SGW-A.
[0425] The first message here can be used to instruct the establishment of a dedicated bearer for the terminal device, which may include PCC rules (specifically, QoS parameters of the dedicated bearer) and an address / domain name for transmitting IMS data.
[0426] In step S905, PGW-A / SGW-A determines that UE-A supports IMS services and that UE-A does not support the use of dedicated bearers to transmit IMS data.
[0427] In step S906, PGW-A / SGW-A sends a second message to PCRF-A.
[0428] Here, the second message can be a reply to the first message, or it can be used to indicate the default bearer of UE-A, which is used to transmit IMS data, or it can be used to indicate that the establishment of a dedicated bearer is refused (or described as: used to indicate that the activation of a dedicated bearer is refused).
[0429] For example, the second message here could be a CCR message.
[0430] In step S907, PCRF-A sends a sixth message to P-CSCF-A.
[0431] Here, the sixth message (e.g., a RAR message) can be a reply to the fifth message, or the sixth message can be used to indicate the default bearer of the terminal device, which is used to transmit IMS data, or the sixth message can be used to indicate that the establishment of a dedicated bearer is refused.
[0432] In step S908, P-CSCF-A sends a response message to UE-A.
[0433] Here, the response message refers to the reply message to the session invitation message (e.g., a 183 message).
[0434] In one possible implementation, the response message can be used to instruct the terminal device not to update or establish a bearer, or the response message can be used to instruct the terminal device to reply with a feedback message in response to the response message, or the response message can be used to instruct the terminal device to reply with a feedback message in response to the response message if a dedicated bearer has not been established.
[0435] In step S909, UE-A sends a feedback message to P-CSCF-A.
[0436] In step S910, after receiving the feedback message, UE-B can send a response message to UE-A to instruct the called user to answer the call.
[0437] For example, the response message is the called UE's response to the PRACK message.
[0438] Step S911, UE-B sends a ringing message.
[0439] The specific implementation of steps S901-S903 can be found in the description of steps S501-S503 in the embodiment corresponding to Figure 5 above, and the specific implementation of steps S908-S911 can be found in the description of steps S506-S509 in the embodiment corresponding to Figure 5 above, and will not be repeated here.
[0440] Implementation method six:
[0441] Implementation method six is mainly used to introduce how, when the default bearer of UE-A does not support the transmission of IMS data, PGW-A / SGW-A updates the TFT of the default bearer after receiving the first message from PCRF-A, thereby ensuring that the terminal equipment supports IMS services.
[0442] For example, please refer to Figure 10, which is a schematic diagram of an interaction corresponding to an IMS service scenario provided in an embodiment of this application. As shown in Figure 10, the IMS service scenario may include a core network registration process, an IMS network registration process, and an IMS call establishment process. Specifically, the IMS call establishment process shown in Figure 10 may include steps S1001-S1015:
[0443] Step S1001: UE-A sends a session invitation message to P-CSCF-A.
[0444] Step S1002, P-CSCF-A receives the response message of the session invitation message.
[0445] In step S1003, P-CSCF-A sends the fifth message to PCRF-A.
[0446] In step S1004, PCRF-A sends the first message to PGW-A / SGW-A.
[0447] For example, the first message here may include QoS parameters for a dedicated bearer.
[0448] Step S1005: If it is determined that UE-A supports IMS services and that UE-A does not support transmitting IMS data using a dedicated bearer, then PGW-A / SGW-A adjusts the TFT of the default bearer of UE-A.
[0449] The adjusted TFT (i.e., the first TFT) can be used to update the default bearer of UE-A. The first TFT includes the address / domain name used to transmit IMS data.
[0450] Step S1006: PGW-A / SGW-A sends a third message to MME-A.
[0451] The third message here (e.g., update bearer request) is used to indicate the update of the default bearer for UE-A.
[0452] For example, the third message may include the identifier of the default bearer of UE-A and the first TFT.
[0453] In step S1007, MME-A sends a bearer update request to UE-A.
[0454] The bearer update request here may include the first TFT.
[0455] In step S1008, UE-A sends a bearer update response to MME-A.
[0456] The bearer update response here is used to indicate that the default bearer of UE-A has been updated.
[0457] In step S1009, MME-A sends a fourth message to UE-A.
[0458] The fourth message here can be used to indicate that the default bearer of UE-A has been updated.
[0459] In step S1010, PGW-A / SGW-A sends a second message to PCRF-A.
[0460] Here, the second message can be a reply to the first message, or it can be used to instruct the default bearer of the terminal device to be updated, and the updated default bearer is used to transmit IMS data.
[0461] For example, the second message here could be a CCR message.
[0462] In step S1011, PCRF-A sends a sixth message to P-CSCF-A.
[0463] Here, the sixth message (e.g., a RAR message) can be a reply to the fifth message, or the sixth message can be used to indicate that the default bearer of the terminal device should be updated, and the updated default bearer should be used to transmit IMS data.
[0464] In step S1012, P-CSCF-A sends a response message to UE-A.
[0465] Here, the response message refers to the reply message to the session invitation message (e.g., a 183 message).
[0466] In one possible implementation, the response message can be used to instruct the terminal device not to update or establish a bearer, or the response message can be used to instruct the terminal device to reply with a feedback message in response to the response message, or the response message can be used to instruct the terminal device to reply with a feedback message in response to the response message if a dedicated bearer has not been established.
[0467] In step S1013, UE-A sends a feedback message to P-CSCF-A.
[0468] In step S1014, after receiving the feedback message, UE-B can send a response message to UE-A to instruct the called user to answer the call.
[0469] For example, the response message is the called UE's response to the PRACK message.
[0470] Step S1015, UE-B sends a ringing message.
[0471] The specific implementation of steps S1001-S1005 can be found in the description of steps S901-S905 in the embodiment corresponding to Figure 9 above, and the specific implementation of steps S1012-S1015 can be found in the description of steps S506-S509 in the embodiment corresponding to Figure 5 above, and will not be repeated here.
[0472] If the first network element is MME-A, then the second network element can be PGW-A / SGW-A, the third network element can be PCRF-A, the fourth network element is P-CSCF-A, and the fifth network element is HLR / HSS. For details, please refer to the following implementation method seven:
[0473] Implementation method seven is mainly used to introduce how, when the default bearer of UE-A supports the transmission of IMS data, MME-A directly replies to PGW-A / SGW-A with a second message after receiving the first message from PGW-A / SGW-A.
[0474] For example, please refer to Figure 11, which is a schematic diagram of an interaction corresponding to an IMS service scenario provided in an embodiment of this application. As shown in Figure 11, the IMS service scenario may include a core network registration process, an IMS network registration process, and an IMS call establishment process. The core network registration process can be specifically referred to in the description of the embodiment corresponding to Figure 4 above, and will not be limited here. The IMS call establishment process shown in Figure 11 may specifically include steps S1101-S1113:
[0475] Step S1101: UE-A sends a session invitation message to P-CSCF-A.
[0476] Step S1102, P-CSCF-A receives the response message of the session invitation message.
[0477] In step S1103, P-CSCF-A sends the fifth message to PCRF-A.
[0478] The fifth message here can be used to instruct the establishment of a dedicated bearer for the terminal device; for example, the first message can be an AAR message.
[0479] In step S1104, PCRF-A sends a third message to PGW-A / SGW-A.
[0480] The third message here can be used to instruct the establishment of a dedicated bearer for the terminal device, which may include PCC rules (specifically, QoS parameters of the dedicated bearer) and an address / domain name for transmitting IMS data.
[0481] Step S1105: PGW-A / SGW-A sends the first message to MME-A.
[0482] The first message here can be used to instruct the establishment of a dedicated bearer for terminal equipment.
[0483] Step S1106: MME-A determines that UE-A supports IMS services and determines that UE-A does not support the use of dedicated bearers to transmit IMS data.
[0484] In step S1107, MME-A sends a second message to PGW-A / SGW-A.
[0485] Here, the second message can be a reply to the first message, or it can be used to indicate the default bearer of the terminal device, which is used to transmit IMS data, or it can be used to indicate that the establishment of a dedicated bearer is refused.
[0486] In step S1108, PGW-A / SGW-A sends a fourth message to PCRF-A.
[0487] The fourth message is used to indicate that the establishment of a dedicated bearer is refused.
[0488] In step S1109, PCRF-A sends a sixth message to P-CSCF-A.
[0489] Here, the sixth message (e.g., a RAR message) can be a reply to the fifth message, or the sixth message can be used to indicate the default bearer of the terminal device, which is used to transmit IMS data, or the sixth message can be used to indicate that the establishment of a dedicated bearer is refused.
[0490] In step S1110, P-CSCF-A sends a response message to UE-A.
[0491] Here, the response message refers to the reply message to the session invitation message (e.g., a 183 message).
[0492] In one possible implementation, the response message can be used to instruct the terminal device not to update or establish a bearer, or the response message can be used to instruct the terminal device to reply with a feedback message in response to the response message, or the response message can be used to instruct the terminal device to reply with a feedback message in response to the response message if a dedicated bearer has not been established.
[0493] In step S1111, UE-A sends a feedback message to P-CSCF-A.
[0494] In step S1112, after receiving the feedback message, UE-B can send a response message to UE-A to instruct the called user to answer the call.
[0495] For example, the response message is the called UE's response to the PRACK message.
[0496] Step S1113, UE-B sends a ringing message.
[0497] The specific implementation of steps S1101-S1103 can be found in the description of steps S501-S503 in the embodiment corresponding to Figure 5 above, and the specific implementation of steps S1111-S1113 can be found in the description of steps S506-S509 in the embodiment corresponding to Figure 5 above, which will not be repeated here.
[0498] If the first network element is UE-A, then the second network element is MME-A, the third network element is PGW-A / SGW-A, the fourth network element can be PCRF-A, and the fifth network element is P-CSCF-A. For details, please refer to the following implementation method eight:
[0499] Implementation method eight is mainly used to introduce how UE-A directly replies to MME-A with a second message after receiving the first message from MME-A.
[0500] For example, please refer to Figure 12, which is an interactive schematic diagram of an IMS service scenario provided in an embodiment of this application. As shown in Figure 12, the IMS service scenario may include a core network registration process, an IMS network registration process, and an IMS call establishment process. The core network registration process can be specifically referred to in the description of the embodiment corresponding to Figure 4 above, and will not be limited here. The IMS call establishment process shown in Figure 12 may specifically include steps S1201-S1217:
[0501] Step S1201: UE-A sends a session invitation message to P-CSCF-A.
[0502] Step S1202: P-CSCF-A receives the response message of the session invitation message.
[0503] In step S1203, P-CSCF-A sends an AAR message to PCRF-A.
[0504] Here, the AAR message can be used to instruct the establishment of a dedicated bearer for the terminal device. For example, the first message may include the address (i.e., the destination address when the UE sends IMS data) / domain name, media type, maximum and minimum bandwidth of the media, etc.
[0505] In step S1204, PCRF-A sends the fifth message to PGW-A / SGW-A.
[0506] The fifth message here can be used to instruct the establishment of a dedicated bearer for the terminal device, which may include PCC rules (specifically, QoS parameters of the dedicated bearer) and an address / domain name for transmitting IMS data.
[0507] In step S1205, PGW-A / SGW-A sends a third message to MME-A.
[0508] The third message here can be used to instruct the establishment of a dedicated bearer for the terminal device.
[0509] Step S1206: MME-A sends the first message to UE-A.
[0510] The first message here (e.g., activate bearer context request) is used to instruct the establishment of a dedicated bearer for the terminal device.
[0511] In step S1207, if it is determined that UE-A supports IMS services and that UE-A does not support the use of a dedicated bearer to transmit IMS data, then UE-A may refuse to establish a dedicated bearer or update the default bearer.
[0512] The refusal to establish a dedicated bearer can also be described as: not establishing a dedicated bearer or not activating a dedicated bearer.
[0513] When the default bearer of UE-A does not support the transmission of IMS data, UE-A can update the default bearer locally, or when the first message includes the first TFT, the default bearer of UE-A can be updated according to the first TFT. This will not be limited here.
[0514] In step S1208, UE-A sends a second message to PGW-A / SGW-A.
[0515] For example, the second message here could be an activate bearer context response. For example, the second message could include third indication information, which could be used to indicate the use of the terminal device's default bearer.
[0516] In step S1209, MME-A determines the context content as the default bearer based on the third instruction information.
[0517] In step S1210, MME-A sends a fourth message to PGW-A / SGW-A.
[0518] The fourth message can be used to indicate that the default bearer of UE-A has been updated, and the default bearer is used to transmit IMS data, or the fourth message can be used to indicate that the establishment of a dedicated bearer is refused. For example, the fourth message may include fourth indication information, which can be used to indicate the use of the default bearer of the terminal device.
[0519] In step S1211, PGW-A / SGW-A updates the downlink TFT based on the fourth instruction information and address / domain name.
[0520] In step S1212, PGW-A / SGW-A sends the sixth message to PCRF-A.
[0521] Here, the sixth message (e.g., the CCR message) can be a reply to the fifth message, or the sixth message can be used to indicate the default bearer of the terminal device, which is used to transmit IMS data, or the sixth message can be used to indicate that the establishment of a dedicated bearer is refused.
[0522] In step S1213, PCRF-A sends a RAR message to P-CSCF-A.
[0523] Here, the RAR message can be a reply message to the AAR message.
[0524] In step S1214, P-CSCF-A sends a response message to UE-A.
[0525] Here, the response message refers to the reply message to the session invitation message (e.g., a 183 message).
[0526] In one possible implementation, the response message can be used to instruct the terminal device not to update or establish a bearer, or the response message can be used to instruct the terminal device to reply with a feedback message in response to the response message, or the response message can be used to instruct the terminal device to reply with a feedback message in response to the response message if a dedicated bearer has not been established.
[0527] In step S1215, UE-A sends a feedback message to P-CSCF-A.
[0528] In step S1216, after receiving the feedback message, UE-B can send a response message to UE-A to instruct the called user to answer the call.
[0529] For example, the response message is the called UE's response to the PRACK message.
[0530] Step S1217, UE-B sends a ringing message.
[0531] The specific implementation of steps S1201-S1205 can be found in the description of steps S1101-S1105 in the embodiment corresponding to Figure 11 above, and the specific implementation of steps S1214-S1217 can be found in the description of steps S506-S509 in the embodiment corresponding to Figure 5 above, and will not be repeated here.
[0532] Example 2:
[0533] This application's second embodiment mainly introduces that when the terminal device supports IMS services but does not support the use of dedicated bearers to transmit IMS data, the first network element does not trigger the dedicated bearer creation process when it determines that the default bearer of the terminal device is used to transmit IMS data.
[0534] For example, the first network element here can be a network element in the IMS network (i.e., call session control function, such as P-CSCF), and the second network element can be a policy management network element in the core network (such as PCRF).
[0535] Here, the terminal device can be the calling UE (e.g., UE-A) or the called UE (e.g., UE-B). In other words, the method described in Embodiment 1 applies not only to the calling UE but also to the called UE. For ease of explanation, the terminal device in this application embodiment mainly describes the implementation method related to the calling UE, while the specific implementation method of the called UE can be found in the specific implementation method of the calling UE, which will not be elaborated here.
[0536] For example, please refer to Figure 13, which is a flowchart illustrating another communication method provided in this application embodiment. As shown in Figure 13, this method can be executed by a first network element (e.g., P-CSCF-A, i.e., the P-CSCF serving UE-A), and the method can at least include steps S1301-S1303:
[0537] Step S1301: Receive the first response message, which is a reply message to the session invitation message.
[0538] Here, the session invitation message (e.g., INVITE message) is used to request a terminal device (e.g., UE-A) to make an IMS call with another terminal device (e.g., UE-B), or the session invitation message is used to instruct a terminal device to initiate an IMS call, or the session invitation message is used to instruct the calling UE to initiate an IMS call.
[0539] For example, the first network element can receive a first response message (e.g., 183 message) from the P-CSCF-B. The first response message can be used to indicate that the UE-B has received the session invitation message. In other words, the first response message is the UE-B's reply message to the session invitation message.
[0540] Step S1302: Determine the default bearer of the terminal device for transmitting IMS data.
[0541] It can be understood that the first network element determines that the default bearer of the terminal device is used to transmit IMS data. Alternatively, it can be described as: the first network element determines that the terminal device does not support the use of a dedicated bearer to transmit IMS data; this will not be restricted here. In other words, the terminal device supports IMS services but does not support the use of a dedicated bearer to transmit IMS data.
[0542] In one possible implementation, the terminal device supports IMS services but does not support transmitting IMS data using a dedicated bearer. This includes: the terminal device supporting access to IMS services via NB-IoT; or, the terminal device supporting access to IMS services via NB-IoT access; or, the terminal device supporting making IMS calls via NB-IoT access; or, the terminal device supporting access to IMS services via NB-IoT (GEO) access; or, the terminal device supporting access to IMS services via NB-IoT satellite access; or, the terminal device supporting IMS calls based on NB-IoT access; or, the terminal device supporting IMS calls based on NB-IoT (GEO) access. Optionally, if the terminal device accesses IMS services via NB-IoT access, it can be considered that the terminal device supports accessing IMS services via NB-IoT access, and it is not necessary to explicitly indicate the terminal's capability support; this is not limited. Alternatively, both the mobile network system and the terminal device can support the above capabilities.
[0543] The default bearer is used to transmit IMS data, which can also be referred to as transmitting IMS data through the default bearer. Specifically, it may include: the default bearer of the terminal device does not include or has not been assigned a service flow template, or the service flow template assigned to the default bearer includes: wildcards, or addresses / domain names used to transmit IMS data.
[0544] For example, the first network element can determine the default bearer of the terminal device for transmitting IMS data based on the session invitation message, IMS registration message, or subscription information. It is understood that any of the session invitation message, IMS registration message, or subscription information can be explicit indication information (e.g., carrying specific indication information) or implicit information indicated by message format, etc., which will not be limited here.
[0545] In one possible implementation, the session invitation message can be used to indicate that the terminal device's dedicated bearer is occupied, or it can be used to indicate that the terminal device does not support establishing a dedicated bearer (e.g., the terminal device's access method is NB-IoT access), or it can be used to indicate that the terminal device uses the default bearer to transmit IMS data. Therefore, when the first network element receives any of the above session invitation messages, it can determine, based on the session invitation message, that the terminal device's default bearer is used to transmit IMS data.
[0546] In one possible implementation, when the first network element receives the aforementioned session invitation message, it can be understood that the IMS data transmitted by the default bearer of the terminal device is not all IMS data, but only the IMS data generated in this session. If the terminal device subsequently makes another IMS call with other terminal devices, the first network element needs to re-determine whether the default bearer of the terminal device supports the transmission of IMS data.
[0547] The aforementioned IMS registration message (e.g., REGISTER message) can be a message sent by the terminal device to the first network element during the IMS network registration process.
[0548] In one possible implementation, the IMS registration message can be used to indicate that the terminal device does not support the establishment of a dedicated bearer (for example, the terminal device's access method is NB-IoT access). In this case, when the first network element receives this IMS registration message, it can also determine the default bearer of the terminal device for transmitting IMS data based on the IMS registration message.
[0549] The aforementioned contract information may be information provided by a third network element (e.g., HSS / HLR) to the first network element during the IMS network registration process (e.g., authorized services that the UE can use).
[0550] In one possible implementation, the subscription information can be used to indicate that the terminal device does not support establishing a dedicated bearer. For example, this subscription information can be used to indicate that the terminal device is authorized to make IMS calls via NB-IoT access. Then, upon receiving this subscription information, the first network element can also determine, based on this subscription information, that the terminal device's default bearer is used for transmitting IMS data.
[0551] In one possible implementation, the IMS registration message or subscription information can be used to instruct the terminal device to always transmit IMS data through the default bearer. For example, at any time after receiving the IMS registration message or subscription information from the terminal device, the IMS network element always assumes that the terminal device is transmitting IMS data through the default bearer. For instance, if the terminal device initiates an IMS session at any time after IMS registration, step S1303 can be executed.
[0552] In one possible implementation, the first network element determines that the terminal device does not support the use of a dedicated bearer to transmit IMS data, including: the first network element determines that the dedicated bearer of the terminal device is occupied; or, the first network element determines that the terminal device does not support the establishment of a dedicated bearer; or, the first network element determines that the terminal device supports transmitting IMS data via a default bearer or supports transmitting IMS data without using a dedicated bearer. The methods for determining the first network element are quite diverse and have strong applicability.
[0553] Among them, the dedicated bearer of the terminal device is occupied. For example, the dedicated bearer of the terminal device can support the transmission of data corresponding to other services besides IMS services.
[0554] In this context, "terminal devices do not support establishing dedicated bearers" can be understood as meaning that the terminal device's capabilities are insufficient to support establishing dedicated bearers. For example, if the terminal device's access method is narrowband IoT access (e.g., the terminal device is an NB-IoT device), the terminal device does not support using dedicated bearers to transmit IMS data.
[0555] The terminal device supports transmitting IMS data via the default bearer or without a dedicated bearer. This can be understood as follows: regardless of whether the terminal device's dedicated bearer is occupied or whether the terminal device supports establishing a dedicated bearer, the terminal device always transmits IMS data via the default bearer.
[0556] In one possible implementation, after determining that the default bearer of the terminal device is used to transmit IMS data, the first network element can also send a second response message to the terminal device. This allows the terminal device to return a feedback message (e.g., a PRACK message) to the first network element without waiting, thereby improving the response timeliness of the terminal device. Here, the second response message can be used to instruct the terminal device not to update or establish a bearer, or it can be used to instruct the terminal device to reply with a feedback message in response to the second response message, or it can be used to instruct the terminal device to reply with a feedback message in the absence of a dedicated bearer.
[0557] In step S1303, no bearer creation message is sent to the second network element.
[0558] The bearer creation message here can be used to instruct the terminal device to create a bearer (e.g., a dedicated bearer).
[0559] For example, the second network element here can be a PCRF (e.g., PCRF-A) of the core network serving the terminal equipment.
[0560] In this application, when the first network element determines that the default bearer of the terminal device is used to transmit IMS data, it changes the strategy of the existing IMS call establishment process and does not interact with the network elements of the core network, that is, it does not trigger the creation process of the dedicated bearer. Therefore, for the terminal device, whether it is a terminal device whose terminal capability does not support the establishment of a dedicated bearer (e.g., a UE accessed through NB-IoT) or a terminal device whose dedicated bearer is occupied, it can achieve the effect of transmitting IMS data through the default bearer without establishing a dedicated bearer, thereby effectively ensuring its support for IMS services.
[0561] To facilitate understanding of the above process, please refer to Figure 14. Figure 14 is an interactive schematic diagram nine corresponding to an IMS service scenario provided in an embodiment of this application. As shown in Figure 14, the IMS service scenario may include a core network registration process, an IMS network registration process, and an IMS call establishment process. The core network registration process can be specifically referred to in the description of the embodiment corresponding to Figure 4 above, and will not be limited here.
[0562] The IMS network registration process shown in Figure 14 mainly involves steps S1401 and S1402. The remaining processes can be found in the existing registration process and will not be described in detail here.
[0563] Step S1401, UE-A sends an IMS registration message to P-CSCF-A.
[0564] Accordingly, P-CSCF-A receives an IMS registration message from UE-A. For example, the IMS registration message here can be used to indicate that the UE's access method is NB-IoT access.
[0565] In step S1402, HLR / HSS provides contract information to P-CSCF-A.
[0566] Accordingly, P-CSCF-A receives subscription information from HLR / HSS, which, for example, can be used to instruct: authorized terminal devices to make IMS calls via narrowband IoT access.
[0567] The IMS call setup process shown in Figure 14 may specifically include steps S1403-S1409:
[0568] In step S1403, UE-A sends a session invitation message to P-CSCF-A.
[0569] The session invitation message here can be used to indicate that UE-A's access method belongs to NB-IoT access.
[0570] In step S1404, P-CSCF-A receives the first response message of the session invitation message.
[0571] In step S1405, P-CSCF-A determines the default bearer of UE-A for transmitting IMS data based on the session invitation message, IMS registration message, or subscription information.
[0572] It is understandable that after P-CSCF-A completes step S1405, it does not send a bearer creation message to PCRF-A, but instead continues to execute step S1406:
[0573] In step S1406, P-CSCF-A sends a second response message to UE-A.
[0574] Here, the second response message refers to the reply message to the session invitation message (e.g., the 183 message).
[0575] In one possible implementation, the second response message can be used to instruct the terminal device not to update or establish a bearer, or the second response message can be used to instruct the terminal device to reply with a feedback message (e.g., a PRACK message) in response to the second response message, or the second response message can be used to instruct the terminal device to reply with a feedback message in response to the second response message if a dedicated bearer has not been established.
[0576] In step S1407, UE-A sends a feedback message to P-CSCF-A.
[0577] In step S1408, after receiving the feedback message, UE-B sends a response message to UE-A to instruct the called user to answer the call.
[0578] In step S1409, UE-B sends a ringing message to UE-A.
[0579] The specific implementation of steps S1403-S1404 can be found in the description of steps S501-S502 in the embodiment corresponding to Figure 5 above, and the specific implementation of steps S1406-S1409 can be found in the description of steps S506-S509 in the embodiment corresponding to Figure 5 above, and will not be repeated here.
[0580] After the IMS call setup process is completed, IMS data can be transmitted through the default bearer of UE-A. Of course, if UE-B does not support the use of a dedicated bearer to transmit IMS data, then UE-B can refer to the specific implementation of UE-A so that IMS data can be transmitted through the default bearer of UE-B. This will not be elaborated further here.
[0581] It is understood that in step S212b of the existing IMS call setup process shown in Figure 2 above, after receiving the 183 message, P-CSCF-A needs to trigger the establishment of a dedicated bearer, that is, it needs to send a bearer creation message (e.g., an AAR message) to the second network element to instruct the core network element to establish a dedicated bearer for the terminal device. However, the embodiment of this application determines that the default bearer of the terminal device is used to transmit IMS data, and does not send a bearer creation message to the second network element, that is, it does not trigger the dedicated bearer creation process. In other words, it skips the dedicated bearer creation process when executing IMS services, reduces the interaction between the core network element and the IMS network element, and can directly use the default bearer of the terminal device to transmit IMS data. Thus, terminal devices that do not support the use of dedicated bearers to transmit IMS data can support IMS services.
[0582] The foregoing details the method provided in this application. To facilitate the implementation of the above-described solutions in the embodiments of this application, corresponding apparatus or devices are also provided in the embodiments of this application.
[0583] This application divides the communication device into functional modules according to the above-described method embodiments. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated modules can be implemented in hardware or as software functional modules. It should be noted that the module division in this application is illustrative and represents only one logical functional division; in actual implementation, there may be other division methods. The communication device of this application embodiment will be described in detail below with reference to Figures 15 and 16.
[0584] Referring to Figure 15, which is a schematic diagram of a communication device provided in an embodiment of this application, the communication device 1 includes at least one of a transceiver module 151 and a processing module 152. These modules can perform the corresponding functions of the communication device in the above method embodiment. The transceiver module 151 can implement the corresponding communication function, and the processing module 152 is used to implement the corresponding processing function. For example, the transceiver module 151 can also be referred to as an interface, a communication interface, or a communication module, etc.
[0585] In some embodiments of this application, the communication device 1 may be the first network element shown above, that is, the communication device 1 shown in FIG. 15 may be used to perform the steps or functions performed by the first network element in the above method embodiments. Exemplarily, the communication device 1 may be the first network element or a chip or functional module configured in the first network element, etc., and this application embodiment does not limit this. The transceiver module 151 is used to perform the transceiver-related operations of the first network element in the above method embodiments, and the processing module 152 is used to perform the processing-related operations of the first network element in the above method embodiments.
[0586] For example, the transceiver module 151 is configured to receive a first message from the second network element, the first message being used to instruct the establishment of a dedicated bearer for the terminal device, the terminal device supporting Internet Protocol Multimedia Subsystem (IMS) service, and not supporting the transmission of IMS data using a dedicated bearer; the transceiver module 151 is also configured to send a second message to the second network element, the second message being a reply message to the first message, or the second message being used to instruct the terminal device to use a default bearer for transmitting IMS data, or the second message being used to instruct the refusal to establish a dedicated bearer, or the second message being used to instruct the updating of the terminal device's default bearer, the updated default bearer being used for transmitting IMS data.
[0587] For example, the processing module 152 is used to determine that the terminal device supports Internet Protocol Multimedia Subsystem (IMS) service and to determine that the terminal device does not support the use of dedicated bearers to transmit IMS data.
[0588] For example, the processing module 152 is specifically used to determine that the dedicated bearer of the terminal device is occupied, or specifically used to determine that the terminal device does not support the establishment of a dedicated bearer, or specifically used to determine that the terminal device supports the transmission of IMS data through the default bearer or supports the transmission of IMS data without the dedicated bearer.
[0589] For example, processing module 152 is specifically used to determine that the access method of the terminal device belongs to narrowband Internet of Things access.
[0590] For example, the transceiver module 151 is further configured to receive first indication information from a third network element, the first indication information being used to indicate any one or more of the following: the dedicated bearer of the terminal device is occupied, or the terminal device does not support the establishment of a dedicated bearer; the processing module 152 is specifically configured to determine, based on the first indication information, that the terminal device does not support the use of a dedicated bearer to transmit IMS data.
[0591] For example, the transceiver module 151 is further configured to receive second indication information from a third network element, the second indication information being used to indicate that the terminal device supports or is authorized to provide IMS services; the processing module 152 is specifically configured to determine, based on the second indication information, that the terminal device supports Internet Protocol Multimedia Subsystem (IMS) services.
[0592] For example, the second message is used to indicate the default bearer of the terminal device, which is used to transmit IMS data, including: the default bearer of the terminal device does not include or has not been assigned a service flow template, or the service flow template assigned to the default bearer includes: a wildcard, or an address / domain name used to transmit IMS data.
[0593] For example, the second message is used to indicate the default bearer of the terminal device; the second message includes a bearer identifier of the default bearer of the terminal device or third indication information, the third indication information being used to indicate the use of the default bearer of the terminal device.
[0594] For example, the bearer identifier is also used to set the transmission parameters of IMS data.
[0595] For example, the second message is used to indicate that the establishment of a dedicated bearer is refused; the second message includes third indication information, which indicates that the dedicated bearer of the terminal device is occupied, or that the third indication information indicates that the terminal device does not support the establishment of a dedicated bearer.
[0596] For example, the first message includes an address / domain name for transmitting IMS data, and the second message is used to indicate that the default bearer of the terminal device should be updated. The second message includes a first service flow template, which includes an address / domain name.
[0597] For example, the processing module 152 is further configured to determine not to send a bearer establishment request to the third network element, the bearer establishment request being used to instruct the establishment of a dedicated bearer for the terminal device.
[0598] For example, the transceiver module 151 is further configured to send a third message to a third network element, the third message being used to indicate the use or update of the default bearer of the terminal device; the transceiver module 151 is further configured to receive a fourth message from the third network element, the fourth message being used to indicate that the default bearer of the terminal device has been updated, or the fourth message being used to indicate that the establishment of a dedicated bearer is refused, or the fourth message being used to indicate that the default bearer of the terminal device is updated.
[0599] For example, the third message is used to indicate the use of the default bearer of the terminal device; the third message may include the quality of service parameters of the default bearer, or may not include the quality of service parameters.
[0600] For example, the third message is used to instruct the terminal device to update the default bearer; the third message includes an address / domain name for transmitting IMS data, and the address / domain name is used to update the service flow template of the terminal device's default bearer.
[0601] For example, the default bearer of the terminal device does not support the transmission of IMS data. The first message includes an address / domain name for transmitting IMS data. The third message is used to indicate the update of the default bearer of the terminal device, including: the third message includes an identifier of the default bearer of the terminal device and a first service flow template, the first service flow template is used to update the default bearer of the terminal device, and the first service flow template includes an address / domain name.
[0602] For example, the fourth message is used to indicate that the default bearer of the terminal device has been updated, including: the fourth message includes the bearer identifier of the default bearer of the terminal device or the fourth indication information, which is used to indicate the use of the default bearer of the terminal device.
[0603] For example, the fourth message is used to indicate that the establishment of a dedicated bearer is refused, including: the fourth message includes fourth indication information, which indicates that the dedicated bearer of the terminal device is occupied, or the fourth indication information indicates that the terminal device does not support the establishment of a dedicated bearer.
[0604] For example, the fourth message is used to instruct the default bearer of the terminal device to be updated. The fourth message includes a first service flow template, which includes an address / domain name for transmitting IMS data.
[0605] For example, the transceiver module 151 is also used to send bearer configuration information to the third network element. The bearer configuration information is used to indicate that the default bearer does not include or has not been assigned a service flow template, or the bearer configuration information is used to indicate that the service flow template assigned to the default bearer includes: a wildcard, or an address / domain name used to transmit IMS data.
[0606] For example, the transceiver module 151 is further configured to receive bearer configuration information from the second network element. The bearer configuration information is used to indicate that the default bearer does not include or has not been assigned a service flow template, or the bearer configuration information is used to indicate that the service flow template assigned to the default bearer includes: a wildcard, or an address / domain name used to transmit IMS data.
[0607] For example, the transceiver module 151 is also used to send bearer configuration information to the terminal device.
[0608] For example, if the first network element is a terminal device, the processing module 152 is also used to determine that a dedicated bearer for the terminal device should not be established.
[0609] For example, the default bearer of the terminal device does not support the transmission of IMS data. The first message includes a first service flow template, which includes an address / domain name for transmitting IMS data. The processing module 152 is specifically used to update the service flow template of the default bearer of the terminal device to the first service flow template.
[0610] For example, transceiver module 151 is used to send a session invitation message to the fifth network element; transceiver module 151 is also used to receive a response message from the fifth network element, the response message being a reply message to the session invitation message. For example, the response message here can be used to instruct the terminal device not to update or establish a bearer, or the response message can be used to instruct the terminal device to reply with a feedback message in response to the response message, or the response message can be used to instruct the terminal device to reply with a feedback message in response to the response message without establishing a dedicated bearer; transceiver module 151 is also used to send a feedback message in response to the response message to the fifth network element.
[0611] It is understood that the specific descriptions of the transceiver module and the processing module shown in the embodiments of this application are merely examples. For the specific functions or execution steps of the transceiver module and the processing module, please refer to the above method embodiment one, which will not be described in detail here.
[0612] Reusing Figure 15, in some other embodiments of this application, the communication device 1 may be the second network element shown above. That is, the communication device 1 shown in Figure 15 may be used to perform the steps or functions performed by the second network element in the above method embodiments. For example, the communication device 1 may be the second network element or a chip or functional module configured in the second network element, etc., and this application embodiment does not limit this. The transceiver module 151 is used to perform the transceiver-related operations of the second network element in the above method embodiments, and the processing module 152 is used to perform the processing-related operations of the second network element in the above method embodiments.
[0613] For example, the transceiver module 151 is configured to send a first message to the first network element, the first message being used to instruct the establishment of a dedicated bearer for the terminal device, the terminal device supporting IMS service but not supporting the transmission of IMS data using a dedicated bearer; the transceiver module 151 is also configured to receive a second message from the first network element, the second message being a reply message to the first message, or the second message being used to instruct the terminal device to use a default bearer for transmitting IMS data, or the second message being used to instruct the refusal to establish a dedicated bearer, or the second message being used to instruct the updating of the terminal device's default bearer, the updated default bearer being used for transmitting IMS data.
[0614] For example, processing module 152 is used to generate a second message.
[0615] For example, the default bearer used to transmit IMS data includes: the default bearer of the terminal device does not include or has not been assigned a service flow template, or the service flow template assigned to the default bearer includes: wildcards, or addresses / domain names used to transmit IMS data.
[0616] For example, the second message is used to indicate the default bearer of the terminal device; the second message includes a bearer identifier of the default bearer of the terminal device or third indication information, the third indication information being used to indicate the use of the default bearer of the terminal device.
[0617] For example, the bearer identifier is also used to set the transmission parameters of IMS data.
[0618] For example, the second message is used to indicate that the establishment of a dedicated bearer is refused; the second message includes third indication information, which indicates that the dedicated bearer of the terminal device is occupied, or that the third indication information indicates that the terminal device does not support the establishment of a dedicated bearer.
[0619] For example, the first message includes an address / domain name for transmitting IMS data, and the second message updates the default bearer of the terminal device. The second message includes a first service flow template, which includes the address / domain name. The transceiver module 151 is also configured to send a response message to the terminal device for the session invitation message, the response message including the first service flow template.
[0620] For example, the transceiver module 151 is further configured to send a response message to the session invitation message to the terminal device. The response message is used to instruct the terminal device not to update or establish a bearer, or to instruct the terminal device to reply with a feedback message in response to the response message, or to instruct the terminal device to reply with a feedback message in response to the response message if a dedicated bearer is not established.
[0621] For example, the transceiver module 151 is further configured to receive a fifth message from the fourth network element, the fifth message being used to indicate the establishment of a dedicated bearer for the terminal device. The transceiver module 151 is also configured to send a sixth message to the fourth network element, the sixth message being a reply to the fifth message, or the sixth message being used to indicate the default bearer of the terminal device, the default bearer being used to transmit IMS data, or the sixth message being used to indicate rejection of establishing a dedicated bearer, or the sixth message being used to indicate updating the default bearer of the terminal device, the updated default bearer being used to transmit IMS data.
[0622] For example, the transceiver module 151 is used to send bearer configuration information to the first network element. The bearer configuration information is used to indicate that the default bearer does not include or has not been assigned a service flow template, or the bearer configuration information is used to indicate that the service flow template assigned to the default bearer includes: a wildcard, or an address / domain name used to transmit IMS data.
[0623] For example, the transceiver module 151 is further configured to receive a third message from a third network element, the third message being used to indicate the establishment of a dedicated bearer for the terminal device. The transceiver module 151 is further configured to send a fourth message to the third network element, the fourth message being used to indicate that the default bearer of the terminal device has been updated and the default bearer is used to transmit IMS data, or the fourth message being used to indicate that the establishment of a dedicated bearer is refused.
[0624] For example, the fourth message is used to indicate that the default bearer of the terminal device has been updated; the fourth message includes the bearer identifier of the default bearer of the terminal device or the fourth indication information, which is used to indicate the use of the default bearer of the terminal device.
[0625] The bearer identifier can also be used to set the transmission parameters of IMS data.
[0626] For example, the fourth message is used to indicate that the establishment of a dedicated bearer is refused; the fourth message includes fourth indication information, which indicates that the dedicated bearer of the terminal device is occupied, or the fourth indication information indicates that the terminal device does not support the establishment of a dedicated bearer.
[0627] The transceiver module 151 is also used to receive first indication information from the first network element, the first indication information being used to indicate any one or more of the following: the dedicated bearer of the terminal device is occupied, or the terminal device does not support the establishment of a dedicated bearer.
[0628] The transceiver module 151 is also used to receive second indication information from the first network element, the second indication information being used to indicate that the terminal device supports or authorizes IMS services.
[0629] The transceiver module 151 is also used to receive bearer configuration information from a third network element.
[0630] The transceiver module 151 is also used to send a first indication information to a third network element. The first indication information is used to indicate any one or more of the following: the dedicated bearer of the terminal device is occupied, or the terminal device does not support the establishment of a dedicated bearer.
[0631] The transceiver module 151 is also used to send second indication information to the third network element. The second indication information is also used to instruct the terminal device to support or authorize IMS services.
[0632] For example, if the first network element is a terminal device, the first message sent by the second network element may include a first service flow template. The first service flow template includes an address / domain name for transmitting IMS data. The address / domain name is used to update the default service flow template carried by the terminal device.
[0633] It is understood that the specific descriptions of the transceiver module and the processing module shown in the embodiments of this application are merely examples. For the specific functions or execution steps of the transceiver module and the processing module, please refer to the above method embodiment one, which will not be described in detail here.
[0634] Reusing Figure 15, in some other embodiments of this application, the communication device 1 may be the third network element shown above. That is, the communication device 1 shown in Figure 15 may be used to perform the steps or functions performed by the third network element in the above method embodiments. For example, the communication device 1 may be the third network element or a chip or functional module configured in the third network element, etc., and this application embodiment does not limit this. The transceiver module 151 is used to perform the transceiver-related operations of the third network element in the above method embodiments, and the processing module 152 is used to perform the processing-related operations of the third network element in the above method embodiments.
[0635] In one possible implementation, the third network element can be a gateway network element (e.g., PGW-A / SGW-A) shown in Figures 5, 6, 7, or 8, or a mobility management network element (e.g., MME-A) shown in Figure 9 or 10, as described below:
[0636] For example, the transceiver module 151 is configured to receive a third message sent by the first network element, the third message being used to indicate the use or update of the default bearer of the terminal device, the terminal device supporting IMS service and not supporting the use of a dedicated bearer to transmit IMS data; the transceiver module 151 is also configured to send a fourth message to the first network element, the fourth message being used to indicate that the default bearer of the terminal device has been updated, or the fourth message being used to indicate that the establishment of a dedicated bearer is refused, the default bearer of the terminal device being used to transmit IMS data, or the fourth message being used to indicate the update of the default bearer of the terminal device.
[0637] For example, the third message is used to indicate the use of the default bearer of the terminal device; the third message includes the quality of service parameters of the default bearer, and / or does not include the quality of service parameters.
[0638] For example, the third message is used to instruct the terminal device to update the default bearer; the third message also includes an address / domain name for transmitting IMS data, the address / domain name being used to update the service flow template of the terminal device's default bearer.
[0639] For example, the third message is used to instruct the terminal device to update the default bearer, including: the third message includes an identifier of the terminal device's default bearer and a first service flow template, the first service flow template is used to update the terminal device's default bearer, and the first service flow template includes an address / domain name.
[0640] For example, the third message is used to instruct the terminal device to update the default bearer, including: the third message includes an identifier of the terminal device's default bearer and a first service flow template, the first service flow template is used to update the terminal device's default bearer, and the first service flow template includes an address / domain name.
[0641] For example, the fourth message is used to indicate that the default bearer of the terminal device has been updated; the fourth message includes the bearer identifier of the default bearer of the terminal device or the fourth indication information, which is used to indicate the use of the default bearer of the terminal device.
[0642] For example, the fourth message is used to indicate that the establishment of a dedicated bearer is refused, including: the fourth message includes fourth indication information, which indicates that the dedicated bearer of the terminal device is occupied, or the fourth indication information indicates that the terminal device does not support the establishment of a dedicated bearer.
[0643] For example, the third message also includes an address / domain name for transmitting IMS data, and the fourth message is used to indicate the default bearer for the updated terminal device, including: the fourth message includes a first service flow template, the first service flow template including an address / domain name.
[0644] For example, the transceiver module 151 is also used to send bearer configuration information to the fourth network element. The bearer configuration information is used to indicate that the default bearer does not include or has not been assigned a service flow template, or the bearer configuration information is used to indicate that the service flow template assigned to the default bearer includes: a wildcard, or an address / domain name used to transmit IMS data.
[0645] The processing module 152 is used to determine that the terminal device supports IMS services and that the terminal device does not support the use of a dedicated bearer to transmit IMS data.
[0646] For example, the transceiver module 151 is further configured to receive first indication information from a fourth network element, the first indication information indicating one or more of the following: the dedicated bearer of the terminal device is occupied, or the terminal device does not support the establishment of a dedicated bearer; the third network element forwards the first indication information to the first network element. The processing module 152 is specifically configured to determine, based on the first indication information, that the terminal device does not support the use of a dedicated bearer to transmit IMS data.
[0647] For example, the transceiver module 151 is further configured to receive second indication information from the fourth network element, the second indication information being further configured to indicate that the terminal device supports or authorizes IMS services; the processing module 152 is specifically configured to determine, based on the second indication information, that the terminal device supports IMS services.
[0648] For example, the third message is used to instruct the terminal device to update its default bearer. The transceiver module 151 is also used to send a bearer update request to the fourth network element. The bearer update request includes a first service flow template, which is used to update the default bearer of the terminal device. The first service flow template includes an address / domain name for transmitting IMS data. The transceiver module 151 is also used to receive a bearer update response sent from the fourth network element. The bearer update response is used to indicate that the default bearer of the terminal device has been updated.
[0649] For example, the bearer update response includes a first business flow template.
[0650] For example, the transceiver module 151 is further configured to receive bearer configuration information from the first network element, wherein the bearer configuration information is used to indicate that the default bearer does not include or has not been allocated a service flow template, or the bearer configuration information is used to indicate that the service flow template allocated for the default bearer includes: a wildcard, or an address / domain name used for transmitting IMS data; the transceiver module 151 is further configured to forward the bearer configuration information to the terminal device.
[0651] For example, the transceiver module 151 is further configured to send a first indication information to the first network element, the first indication information being used to indicate any one or more of the following: the dedicated bearer of the terminal device is occupied, or the terminal device does not support the establishment of a dedicated bearer.
[0652] For example, the transceiver module 151 is further configured to send a second indication information to the first network element, the second indication information being used to indicate that the terminal device supports or authorizes IMS services.
[0653] For example, the transceiver module 151 is further configured to send a bearer update request to the terminal device. The bearer update request includes a first service flow template, which is used to update the default bearer of the terminal device. The first service flow template includes an address / domain name. The transceiver module 151 is further configured to receive a bearer update response sent from the terminal device, which is used to indicate that the default bearer of the terminal device has been updated.
[0654] In another possible implementation, the third network element can also be the policy management network element shown in Figure 11 above (e.g., PCRF-A), as described below:
[0655] For example, the transceiver module 151 is used to send a third message to the second network element, the third message being used to indicate the establishment of a dedicated bearer for the terminal device; the transceiver module 151 is also used to receive a fourth message from the second network element, the fourth message being used to indicate that the default bearer of the terminal device has been updated and the default bearer is used to transmit IMS data, or the fourth message being used to indicate that the establishment of a dedicated bearer is refused.
[0656] For example, the fourth message is used to indicate that the default bearer of the terminal device has been updated; the fourth message includes the bearer identifier of the default bearer of the terminal device or the fourth indication information, which is used to indicate that the use of the default bearer of the terminal device is supported.
[0657] For example, the bearer identifier is also used to set the transmission parameters of IMS data.
[0658] For example, the fourth message is used to indicate that the establishment of a dedicated bearer is refused; the fourth message includes fourth indication information, which indicates that the dedicated bearer of the terminal device is occupied, or the fourth indication information indicates that the terminal device does not support the establishment of a dedicated bearer.
[0659] For example, the transceiver module 151 is further configured to receive first indication information from the second network element, the first indication information being used to indicate any one or more of the following: the dedicated bearer of the terminal device is occupied, or the terminal device does not support the establishment of a dedicated bearer.
[0660] For example, the transceiver module 151 is further configured to receive second indication information from the second network element, and the second indication information is further configured to indicate to the terminal device that it supports or authorizes IMS services.
[0661] For example, processing module 152 is used to generate a third message.
[0662] In another possible implementation, the third network element can also be the gateway network element shown in Figure 12 above (e.g., PGW-A / SGW-A), as described below:
[0663] For example, transceiver module 151 is configured to receive a fifth message from a fourth network element; transceiver module 151 is also configured to send a third message to a second network element, both the third and fifth messages being used to request the establishment of a dedicated bearer for the terminal device; transceiver module 151 is also configured to receive a fourth message from the second network element, the fourth message being used to indicate that the default bearer of the terminal device has been updated and is used to transmit IMS data, or the fourth message being used to indicate that the establishment of a dedicated bearer is refused; transceiver module 151 is also configured to send a sixth message to the fourth network element, the sixth message being used to indicate the default bearer of the terminal device and the default bearer of the terminal device being used to transmit IMS data.
[0664] For example, the transceiver module 151 is further configured to send bearer configuration information to the second network element. The bearer configuration information is used to indicate that the default bearer does not include or has not been assigned a service flow template, or the bearer configuration information is used to indicate that the service flow template assigned to the default bearer includes: a wildcard, or an address / domain name used to transmit IMS data.
[0665] For example, the third message includes an address / domain name for transmitting IMS data, the fourth message includes fourth indication information, and the method further includes: updating the downlink service flow template based on the fourth indication information and the address / domain name.
[0666] For example, the fourth message is used to indicate that the default bearer of the terminal device has been updated; the fourth message includes the bearer identifier of the default bearer of the terminal device, or the fourth indication information, which is used to indicate that the use of the default bearer of the terminal device is supported.
[0667] For example, the bearer identifier is also used to set the transmission parameters of IMS data.
[0668] For example, the fourth message is used to indicate that the establishment of a dedicated bearer is refused; the fourth message includes fourth indication information, which indicates that the dedicated bearer of the terminal device is occupied, or the fourth indication information indicates that the terminal device does not support the establishment of a dedicated bearer.
[0669] For example, processing module 152 is used to generate a third message.
[0670] It is understood that the specific descriptions of the transceiver module and the processing module shown in the embodiments of this application are merely examples. For the specific functions or execution steps of the transceiver module and the processing module, please refer to the above method embodiment one, which will not be described in detail here.
[0671] Reusing Figure 15, in some further embodiments of this application, the communication device 1 may be the fourth network element shown above. That is, the communication device 1 shown in Figure 15 may be used to perform the steps or functions performed by the fourth network element in the above method embodiments. For example, the communication device 1 may be the fourth network element or a chip or functional module configured in the fourth network element, etc., and this application embodiment does not limit this. The transceiver module 151 is used to perform the transceiver-related operations of the fourth network element in the above method embodiments, and the processing module 152 is used to perform the processing-related operations of the fourth network element in the above method embodiments.
[0672] In one possible implementation, the fourth network element can be the mobility management network element shown in Figure 7 above (e.g., MME-A), as described below:
[0673] For example, transceiver module 151 is configured to receive a bearer update request from a third network element. The bearer update request includes a first service flow template, which is used to update the default bearer of the terminal device. The first service flow template includes an address / domain name for transmitting IMS data. The default bearer of the terminal device does not support the transmission of IMS data. Transceiver module 151 is also configured to forward the bearer update request to the terminal device. Transceiver module 151 is also configured to receive a bearer update response sent by the terminal device. The bearer update response is used to indicate that the default bearer of the terminal device has been updated. The updated default bearer of the terminal device is used for transmitting IMS data. Transceiver module 151 is also configured to forward the bearer update response to the third network element.
[0674] For example, the bearer update response includes a first business flow template.
[0675] For example, the transceiver module 151 is used to send a first indication information to a third network element. The first indication information is used to indicate any one or more of the following: the dedicated bearer of the terminal device is occupied, or the terminal device does not support the establishment of a dedicated bearer.
[0676] For example, processing module 152 is used to determine first indication information.
[0677] For example, the transceiver module 151 is used to receive bearer configuration information sent from a third network element. The bearer configuration information is used to indicate that the default bearer does not include or has not been assigned a service flow template, or the bearer configuration information is used to indicate that the service flow template assigned to the default bearer includes: a wildcard, or an address / domain name used to transmit IMS data; the fourth network element forwards the bearer configuration information to the terminal device.
[0678] In another possible implementation, the fourth network element can also be the IMS network element shown in Figure 9 above (e.g., P-CSCF-A), as described below:
[0679] For example, transceiver module 151 is used to send a fifth message to the second network element, the fifth message being used to indicate the establishment of a dedicated bearer for the terminal device; transceiver module 151 is also used to receive a sixth message from the second network element, the sixth message being a reply message to the fifth message, or the sixth message being used to indicate the default bearer of the terminal device, the default bearer being used to transmit IMS data, or the sixth message being used to indicate the refusal to establish a dedicated bearer, or the sixth message being used to indicate the update of the default bearer of the terminal device, the updated default bearer being used to transmit IMS data.
[0680] Processing module 152 is used to generate the fifth message.
[0681] It is understood that the specific descriptions of the transceiver module and the processing module shown in the embodiments of this application are merely examples. For the specific functions or execution steps of the transceiver module and the processing module, please refer to the above method embodiment one, which will not be described in detail here.
[0682] Reusing Figure 15, in some further embodiments of this application, the communication device 1 may be the terminal device shown above. That is, the communication device 1 shown in Figure 15 may be used to perform the steps or functions performed by the terminal device in the above method embodiments. For example, the communication device 1 may be a terminal device or a chip or functional module configured in a terminal device, etc., and this application embodiment does not limit this. The transceiver module 151 is used to perform the transceiver-related operations of the terminal device in the above method embodiments, and the processing module 152 is used to perform the processing-related operations of the terminal device in the above method embodiments.
[0683] For example, transceiver module 151 is used to send a session invitation message to the policy management network element. Transceiver module 151 is also used to receive a first service flow template sent from the mobility management network element or the policy management network element. The first service flow template includes an address / domain name for transmitting IMS data. The default bearer of the terminal device does not support the transmission of IMS data. The first service flow template is used to indicate that the default bearer of the terminal device should be updated. The updated default bearer of the terminal device is used to transmit IMS data.
[0684] For example, the first service flow template here can also be carried in the bearer update request sent by the mobility management network element, or in the response message to the session invitation message sent by the policy management network element.
[0685] For example, the transceiver module 151 is further configured to receive bearer configuration information from the mobility management network element. The bearer configuration information is used to indicate that the default bearer does not include or has not been assigned a service flow template, or the bearer configuration information is used to indicate that the service flow template assigned to the default bearer includes: a wildcard, or an address / domain name used to transmit IMS data.
[0686] For example, processing module 152 is used to configure the default bearer of the terminal device according to bearer configuration information.
[0687] It is understood that the specific descriptions of the transceiver module and the processing module shown in the embodiments of this application are merely examples. For the specific functions or execution steps of the transceiver module and the processing module, please refer to the above method embodiment one, which will not be described in detail here.
[0688] Reusing Figure 15, in some further embodiments of this application, the communication device 1 may be the first network element shown above, that is, the communication device 1 shown in Figure 15 may be used to perform the steps or functions performed by the first network element in the above method embodiments. Exemplarily, the communication device 1 may be the first network element or a chip or functional module configured in the first network element, etc., and this application embodiment does not limit this. The transceiver module 151 is used to perform transceiver-related operations of the first network element in the above method embodiments, and the processing module 152 is used to perform processing-related operations of the first network element in the above method embodiments.
[0689] For example, the transceiver module 151 is used to receive a first response message, which is a reply message to the session invitation message; the processing module 152 is used to determine that the default bearer of the terminal device is used to transmit IMS data; the processing module 152 is also used to determine not to send a bearer creation message to the second network element.
[0690] For example, the transceiver module 151 is further configured to send a second response message to the terminal device from the first network element. The second response message is used to instruct the terminal device not to update or establish a bearer, or to instruct the terminal device to reply with a feedback message in response to the second response message, or to instruct the terminal device to reply with a feedback message in response to the second response message if a dedicated bearer has not been established.
[0691] For example, a session invitation message may be used to indicate that a dedicated bearer for the terminal device is occupied, or a session invitation message may be used to indicate that the terminal device does not support establishing a dedicated bearer, or a session invitation message may be used to indicate that the terminal device uses the default bearer to transmit IMS data.
[0692] For example, the transceiver module 151 is also used for the first network element to receive the IMS registration message of the terminal device, the IMS registration message being used to indicate that the terminal device does not support the establishment of a dedicated bearer.
[0693] For example, the transceiver module 151 is also configured to receive subscription information from a third network element, the subscription information being used to indicate that the terminal device does not support the establishment of a dedicated bearer.
[0694] For example, the processing module 152 is specifically used to determine the default bearer of the terminal device for transmitting IMS data based on the session invitation message, IMS registration message, or subscription information.
[0695] For example, the default bearer used to transmit IMS data includes: the default bearer of the terminal device does not include or has not been assigned a service flow template, or the service flow template assigned to the default bearer includes: wildcards, or addresses / domain names used to transmit IMS data.
[0696] It is understood that the specific descriptions of the transceiver module and the processing module shown in the embodiments of this application are merely examples. For the specific functions or execution steps of the transceiver module and the processing module, please refer to the above-described method embodiment two, which will not be described in detail here.
[0697] Reusing Figure 15, in some further embodiments of this application, the communication device 1 may be the terminal device shown above. That is, the communication device 1 shown in Figure 15 may be used to perform the steps or functions performed by the terminal device in the above method embodiments. For example, the communication device 1 may be a terminal device or a chip or functional module configured in a terminal device, etc., and this application embodiment does not limit this. The transceiver module 151 is used to perform the transceiver-related operations of the terminal device in the above method embodiments, and the processing module 152 is used to perform the processing-related operations of the terminal device in the above method embodiments.
[0698] For example, the transceiver module 151 is used to send a session invitation message to the first network element, and the default bearer of the terminal device is used to transmit IMS data; the transceiver module 151 is also used to receive a second response message from the first network element, the second response message being used to instruct the terminal device not to update or establish a bearer, or the second response message being used to instruct the terminal device to reply with a feedback message in response to the second response message, or the second response message being used to instruct the terminal device to reply with a feedback message in response to the second response message without establishing a dedicated bearer.
[0699] For example, a session invitation message may be used to indicate that a dedicated bearer for a terminal device is occupied, or a session invitation message may be used to indicate that a terminal device does not support establishing a dedicated bearer, or a session invitation message may be used to indicate that a terminal device uses a default bearer to transmit IMS data.
[0700] For example, the transceiver module 151 is also used to send an IMS registration message to the first network element. The IMS registration message is used to indicate that the access method of the terminal device belongs to narrowband Internet of Things access.
[0701] For example, the default bearer used to transmit IMS data includes: the default bearer of the terminal device does not include or has not been assigned a service flow template, or the service flow template assigned to the default bearer includes: wildcards, or addresses / domain names used to transmit IMS data.
[0702] For example, the transceiver module 151 is further configured to receive bearer configuration information from the mobility management network element. The bearer configuration information is used to indicate that the default bearer does not include or has not been assigned a service flow template, or the bearer configuration information is used to indicate that the service flow template assigned to the default bearer includes: a wildcard, or an address / domain name used to transmit IMS data.
[0703] For example, processing module 152 is used to configure the default bearer of the terminal device according to bearer configuration information.
[0704] It is understood that the specific descriptions of the transceiver module and the processing module shown in the embodiments of this application are merely examples. For the specific functions or execution steps of the transceiver module and the processing module, please refer to the above-described method embodiment two, which will not be described in detail here.
[0705] The communication device according to embodiments of this application has been described above. The following describes possible product forms of the communication device. It should be understood that any product possessing the functions of the communication device described in FIG. 15 above falls within the protection scope of the embodiments of this application. It should also be understood that the following description is merely illustrative and does not limit the product form of the communication device according to the embodiments of this application to this extent.
[0706] In one possible implementation, in the communication device shown in FIG15, the processing module 152 may be one or more processors, and the transceiver module 151 may be a transceiver, or the transceiver module 151 may also be a transmitting module and a receiving module. The transmitting module may be a transmitter, and the receiving module may be a receiver. The transmitting module and the receiving module are integrated into a single device, such as a transceiver. In the embodiments of this application, the processor and the transceiver may be coupled, etc., and the connection method between the processor and the transceiver is not limited in the embodiments of this application. In the process of executing the above method, the process of sending information in the above method can be understood as the process of the processor outputting the above information. When outputting the above information, the processor outputs the above information to the transceiver so that the transceiver can transmit it. After the above information is output by the processor, it may need to undergo other processing before reaching the transceiver. Similarly, the process of receiving information in the above method can be understood as the process of the processor receiving the input above information. When the processor receives the input information, the transceiver receives the above information and inputs it into the processor. Furthermore, after the transceiver receives the aforementioned information, the information may need to undergo further processing before being input into the processor.
[0707] Referring to Figure 16, which is a schematic diagram of another communication device provided in an embodiment of this application, the communication device 2 can be used to implement the operations performed by the first network element, second network element, third network element, fourth network element, or terminal device in the above embodiments. Alternatively, the communication device 2 can be the first network element, second network element, third network element, fourth network element, or terminal device mentioned above. The communication device 2 includes a processor 161, a memory 162, and a bus system 163.
[0708] Memory 162 includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM). Memory 162 is used to store related instructions and data. Memory 162 stores executable modules or data structures, or subsets thereof, or extended sets thereof:
[0709] Operation instructions: This includes various operation instructions used to perform various operations.
[0710] Operating system: includes various system programs used to implement various basic business functions and handle hardware-based tasks.
[0711] Figure 16 shows only one memory, but of course, multiple memories can be set as needed.
[0712] The communication device 2 may further include a transceiver 164. The transceiver 164 may be a communication module or a transceiver circuit. In the embodiments of this application, the transceiver 164 is used to perform the transmission and reception operations involved in the above embodiments.
[0713] Processor 161 may be a controller, central processor (CPU), general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or other programmable logic device, transistor logic device, hardware component, or any combination thereof. Processor 161 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.
[0714] In specific applications, the various components of communication device 2 are coupled together through bus system 163. Bus system 163 includes not only a data bus but may also include a power bus, control bus, and status signal bus. However, for clarity, all buses are labeled as bus system 163 in Figure 16. For ease of illustration, Figure 16 is only schematically shown.
[0715] In specific implementation, the communication device 2 can execute the steps of the method performed by the first network element, the second network element, the third network element, the fourth network element, or the terminal device in the above embodiments. Specifically, when the communication device 2 is used to implement the various steps performed by the first network element, the second network element, the third network element, the fourth network element, or the terminal device in the communication method provided in the embodiments, the processor 161 can implement the function of the processing module 152, and the transceiver 164 can implement the function of the transceiver module 151.
[0716] It should be noted that in practical applications, the processor in the embodiments of this application can be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiments can be completed by the integrated logic circuitry in the processor's hardware or by instructions in software form. The processor can be a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied as being executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads the information in the memory and, in conjunction with its hardware, completes the steps of the above methods.
[0717] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Non-volatile memory can be ROM, programmable read-only memory (PROM), EPROM, electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be RAM, which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory described in the embodiments of this application is intended to include, but is not limited to, these and any other suitable types of memory.
[0718] In another possible implementation, in the communication device shown in FIG15, the processing module 152 can be one or more logic circuits, and the transceiver module 151 can be an input / output interface, or a communication interface, or an interface circuit, or an interface, etc. Alternatively, the transceiver module 151 can also be a sending module and a receiving module. The sending module can be an output interface, and the receiving module can be an input interface. The sending module and the receiving module are integrated into one unit, such as an input / output interface. Referring to FIG17, FIG17 is a schematic diagram of the structure of another communication device provided in an embodiment of this application. As shown in FIG17, the communication device shown in FIG17 includes a logic circuit 171 and an interface 172. That is, the above-mentioned processing module 152 can be implemented by the logic circuit 171, and the transceiver module 151 can be implemented by the interface 172. Among them, the logic circuit 171 can be a chip, a processing circuit, an integrated circuit, or a system on chip (SoC) chip, etc., and the interface 172 can be a communication interface, an input / output interface, a pin, etc. For example, FIG17 shows the above-mentioned communication device as a chip, which includes a logic circuit 171 and an interface 172.
[0719] In this embodiment, the logic circuit and the interface can also be coupled to each other. The specific connection method between the logic circuit and the interface is not limited in this embodiment.
[0720] For example, the communication device shown in FIG17 can be used to implement the method described in the above method embodiments, as can be seen from the description in the above method embodiments. The communication device can be any one of the aforementioned first network element, second network element, third network element, fourth network element, or terminal device.
[0721] It is understood that the communication device shown in the embodiments of this application can implement the method provided in the embodiments of this application in hardware form or in software form, etc., and the embodiments of this application do not limit it in this way.
[0722] For specific implementations of the various embodiments shown in Figure 17, please refer to the above embodiments, which will not be described in detail here.
[0723] This application also provides a communication system, which includes at least a first network element, a second network element, a third network element, and a fourth network element. The first network element, the second network element, the third network element, and the fourth network element can all be used to implement the method in the aforementioned method embodiment one.
[0724] This application also provides another communication system, which includes at least a first network element and a terminal device, both of which can be used to implement the method in the aforementioned method embodiment two.
[0725] This application also provides a chip system including a processor for supporting the apparatus on which the chip system is installed to implement the method steps performed by the first network element, second network element, third network element, fourth network element, or terminal device in the above embodiments, such as generating or processing data and / or information involved in the above methods. In one possible design, the chip system further includes a memory for storing program instructions and data necessary for the data transmission device. The chip system may be composed of chips or may include chips and other discrete devices.
[0726] This application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a computer, implements the method steps performed by the first network element, the second network element, the third network element, the fourth network element, or the terminal device in the above embodiments.
[0727] This application also provides a computer program product that, when executed by a computer, implements the method steps performed by the first network element, the second network element, the third network element, the fourth network element, or the terminal device in the above embodiments.
[0728] In the above method embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions according to the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. Computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. A computer-readable storage medium can be any available medium that a computer can access, or a data storage device such as a server or data center that integrates one or more available media. Available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).
[0729] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers described above does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.
[0730] The above are merely preferred embodiments of the technical solutions of this application and are not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.
Claims
1. A communication method, characterized in that, Applied to the first network element, the method includes: The system receives a first message from a second network element. The first message is used to instruct the establishment of a dedicated bearer for a terminal device. The terminal device supports Internet Protocol Multimedia Subsystem (IMS) services but does not support the transmission of IMS data using a dedicated bearer. A second message is sent to the second network element. The second message is a reply to the first message. Alternatively, the second message can be used to indicate the default bearer of the terminal device, which is used to transmit IMS data. Or, the second message can be used to indicate that the establishment of the dedicated bearer is refused. Or, the second message can be used to indicate that the default bearer of the terminal device is updated, and the updated default bearer is used to transmit IMS data.
2. The method according to claim 1, characterized in that, The method further includes: It is determined that the terminal device supports Internet Protocol Multimedia Subsystem (IMS) service, and that the terminal device does not support the use of dedicated bearers to transmit IMS data.
3. The method according to claim 2, characterized in that, The determination that the terminal device does not support the use of a dedicated bearer to transmit IMS data includes: It is determined that the dedicated bearer of the terminal device is occupied, or that the terminal device does not support the establishment of a dedicated bearer.
4. The method according to claim 3, characterized in that, The determination that the terminal device does not support establishing a dedicated bearer includes: It has been determined that the access method of the terminal device belongs to narrowband Internet of Things access.
5. The method according to any one of claims 1-4, characterized in that, The second message is used to indicate the default bearer of the terminal device, the default bearer being used to transmit IMS data, including: The default bearer of the terminal device does not include or has not been assigned a service flow template, or the service flow template assigned to the default bearer includes: wildcards, or addresses / domain names used to transmit IMS data.
6. The method according to claim 2, characterized in that, The method further includes: Receive a first indication message from a third network element, wherein the first indication message is used to indicate any one or more of the following: The dedicated bearer of the terminal device is occupied, or the terminal device does not support the establishment of a dedicated bearer; The determination that the terminal device does not support the use of a dedicated bearer to transmit IMS data includes: Based on the first indication information, it is determined that the terminal device does not support the use of a dedicated bearer to transmit IMS data.
7. The method according to claim 2, characterized in that, The method further includes: Receive a second indication information from a third network element, the second indication information being used to indicate that the terminal device supports or authorizes IMS services; The step of determining that the terminal device supports Internet Protocol Multimedia Subsystem (IMS) service includes: Based on the second indication information, it is determined that the terminal device supports Internet Protocol Multimedia Subsystem (IMS) service.
8. The method according to any one of claims 1-7, characterized in that, The second message is used to indicate the default bearer of the terminal device; The second message includes a bearer identifier of the default bearer of the terminal device or a third indication information, wherein the third indication information is used to indicate the use of the default bearer of the terminal device.
9. The method according to any one of claims 1-7, characterized in that, The second message is used to indicate that the establishment of the dedicated bearer is refused; The second message includes a third indication, which indicates that the dedicated bearer of the terminal device is occupied, or that the terminal device does not support the establishment of a dedicated bearer.
10. The method according to any one of claims 1-9, characterized in that, The method further includes: No bearer establishment request is sent to the third network element, the bearer establishment request being used to instruct the establishment of a dedicated bearer for the terminal device.
11. The method according to any one of claims 1-9, characterized in that, The method further includes: Send a third message to a third network element, the third message being used to indicate the use or update of the default bearer of the terminal device; The terminal device receives a fourth message from the third network element, the fourth message indicating that the default bearer of the terminal device has been updated, or the fourth message indicating that the establishment of a dedicated bearer is refused.
12. The method according to claim 11, characterized in that, The fourth message is used to indicate that the default bearer of the terminal device has been updated, including: The fourth message includes a bearer identifier or a fourth indication information of the default bearer of the terminal device, the fourth indication information being used to indicate the use of the default bearer of the terminal device.
13. The method according to claim 11 or 12, characterized in that, The fourth message is used to indicate that the establishment of a dedicated bearer is refused, including: The fourth message includes a fourth indication message, which indicates that the dedicated bearer of the terminal device is occupied, or that the terminal device does not support the establishment of a dedicated bearer.
14. The method according to any one of claims 11-13, characterized in that, The third message is used to indicate the use of the default bearer of the terminal device; The third message may include the quality of service parameters of the default bearer, or it may not include the quality of service parameters.
15. The method according to any one of claims 11-13, characterized in that, The third message is used to instruct the terminal device to update its default bearer. The third message includes an address / domain name for transmitting IMS data, which is used to update the default service flow template carried by the terminal device.
16. The method according to any one of claims 11-13, characterized in that, The default bearer of the terminal device does not support the transmission of IMS data, and the first message includes an address / domain name for transmitting IMS data. The third message is used to instruct the terminal device to update its default bearer, including: The third message includes the identifier of the default bearer of the terminal device and a first service flow template. The first service flow template is used to update the default bearer of the terminal device and includes the address / domain name.
17. The method according to any one of claims 11-13, 16, characterized in that, The method further includes: Send bearer configuration information to the third network element. The bearer configuration information is used to indicate that the default bearer does not include or has not been assigned a service flow template. Alternatively, the bearer configuration information is used to indicate that the service flow template assigned to the default bearer includes: a wildcard, or an address / domain name used to transmit IMS data.
18. The method according to any one of claims 1-4 and 7-9, characterized in that, The first network element is a terminal device. The default bearer of the terminal device does not support the transmission of IMS data. The first message includes a first service flow template, which includes an address / domain name for transmitting IMS data. The method further includes: Update the default service flow template of the terminal device to the first service flow template.
19. A communication method, characterized in that, Applied to a second network element, the method includes: Send a first message to the first network element. The first message is used to instruct the establishment of a dedicated bearer for the terminal device. The terminal device supports IMS services but does not support the transmission of IMS data using a dedicated bearer. The system receives a second message from the first network element. The second message is a reply to the first message. Alternatively, the second message may indicate the default bearer of the terminal device, which is used to transmit IMS data. Or, the second message may indicate that the establishment of the dedicated bearer is refused. Or, the second message may indicate that the default bearer of the terminal device is updated, and the updated default bearer is used to transmit IMS data.
20. The method according to claim 19, characterized in that, The method further includes: A response message to the terminal device for sending a session invitation message, wherein the response message is used to instruct the terminal device not to update or establish a bearer, or, the response message is used to instruct the terminal device to reply with a feedback message in response to the response message, or, the response message is used to instruct the terminal device to reply with a feedback message in response to the response message without establishing a dedicated bearer.
21. A communication method, characterized in that, Applied to the fourth network element, the method includes: The device receives a bearer update request from a third network element. The bearer update request includes a first service flow template, which is used to update the default bearer of the terminal device. The first service flow template includes an address / domain name for transmitting IMS data. The default bearer of the terminal device does not support the transmission of IMS data. The bearer update request is forwarded to the terminal device; Receive a bearer update response from the terminal device, the bearer update response being used to indicate that the default bearer of the terminal device has been updated, and the updated default bearer of the terminal device is used to transmit IMS data; The bearer update response is forwarded to the third network element.
22. A communication method, characterized in that, Applied to the first network element, the method includes: Receive a first response message, which is a reply message to the session invitation message; The default bearer of the terminal device is determined to be used for transmitting IMS data; Do not send a bearer creation message to the second network element.
23. The method according to claim 22, characterized in that, The method further includes: A second response message is sent to the terminal device, the second response message being used to instruct the terminal device not to update or establish a bearer, or the second response message being used to instruct the terminal device to reply with a feedback message in response to the second response message, or the second response message being used to instruct the terminal device to reply with a feedback message in response to the second response message without establishing a dedicated bearer.
24. The method according to claim 22 or 23, characterized in that, The session invitation message is used to indicate that the dedicated bearer of the terminal device is occupied, or the session invitation message is used to indicate that the terminal device does not support the establishment of a dedicated bearer, or the session invitation message is used to indicate that the terminal device uses the default bearer to transmit IMS data.
25. The method according to claim 24, characterized in that, The step of determining the default bearer of the terminal device for transmitting IMS data includes: Based on the session invitation message, the default bearer of the terminal device is determined to be used for transmitting IMS data.
26. The method according to any one of claims 22-25, characterized in that, The default bearer is used to transmit IMS data, including: The default bearer of the terminal device does not include or has not been assigned a service flow template, or the service flow template assigned to the default bearer includes: wildcards, or addresses / domain names used to transmit IMS data.
27. A network element, characterized in that, It includes modules for implementing the method as described in any one of claims 1 to 18, or modules for implementing the method as described in any one of claims 19 to 20, or modules for implementing the method as described in claim 21, or modules for implementing the method as described in any one of claims 22 to 26.
28. A communication device, characterized in that, The device includes a processor and an interface circuit, the interface circuit being used to receive signals from other communication devices and transmit them to the processor or to send signals from the processor to other communication devices, the processor being used to enable the communication devices to implement the method as described in any one of claims 1 to 26.
29. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store a computer program that, when executed by a processor, causes a communication device including the processor to implement the method as described in any one of claims 1 to 26.
30. A computer program product, characterized in that, The computer program product includes instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1 to 26.
