Communication method and apparatus
Patent Information
- Application Number
- CN202510428297.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-04-03
- Publication Date
- 2026-10-16
AI Technical Summary
[0003]然而,对于物联网(internet of things,IoT)设备而言,在现有相关标准规范下,其与接入网设备之间仅支持2个DRB,不能有效支持IMS语音业务
Smart Images

Figure CN122933608A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of communications, and more particularly to communication methods and apparatus. Background Technology
[0002] Terrestrial communication networks provide voice, video, and information services to terminals via the Internet Protocol (IP) Multimedia Subsystem (IMS) network. After the terminal completes a radio resource control (RRC) connection with the access network equipment, at least one data radio bearer (DRB) for transmitting data services is established between the terminal and the access network equipment by default. To support IMS voice services, a DRB for transmitting IMS voice signaling (Session Initiation Protocol (SIP)) is first established with the access network equipment. When IMS voice services are initiated, another DRB for transmitting IMS voice services is also required. Therefore, a terminal performing IMS voice services has at least three DRBs on the air interface.
[0003] However, under existing standards and specifications, Internet of Things (IoT) devices only support two DRBs (Device Routers) with access network devices, which cannot effectively support IMS voice services. Similarly, similar issues exist for other types of service transmissions that require multiple DRBs. Therefore, how IoT devices can enable more types of service transmissions needs to be studied. Summary of the Invention
[0004] This application provides a communication method and apparatus that can enable more types of service transmission for IoT devices.
[0005] To achieve the above objectives, this application adopts the following technical solution:
[0006] In a first aspect, a communication method is provided. Taking the application of this method to a first communication device as an example, in this method: M data radio bearers (DRBs) are established with a second communication device, and N DRBs among the M DRBs are deactivated such that at most T DRBs among the M DRBs are in an active state, where M≥3 and are integers, N is a positive integer and N≤M, and T is equal to a first threshold; a first signaling is received from the second communication device, the first signaling being used to activate K DRBs, where K≤T and are positive integers; and the K DRBs are activated according to the first signaling.
[0007] In this method, when establishing M DRBs between the first and second communication devices, N DRBs are deactivated, ensuring that at most T DRBs are active. This guarantees that at most T DRBs are used for data transmission of corresponding services between the first and second communication devices. When it is necessary to use deactivated and / or inactive DRBs for data transmission of corresponding services, the first communication device receives a first signaling from the second communication device to activate K DRBs. While ensuring that the number of active DRBs does not exceed T, K DRBs are activated according to the first signaling to perform data transmission of other types of services. M ≥ 3 and is an integer, N, T, and K are positive integers, and N ≤ M, T equals a first threshold, and K ≤ T. Therefore, based on the first communication device supporting only T DRBs for corresponding service transmission, DRBs for transmitting data of more types of services can be established. Activation and deactivation operations enable the first communication device to support data transmission of more types of services, such as IMS voice services.
[0008] In one possible design, the N DRBs include at least one DRB for transmitting data services. Thus, when other types of service transmission are required, the first and second communication devices can deactivate the at least one DRB for transmitting data services and activate the DRB corresponding to the service to be transmitted, so that the number of active DRBs does not exceed T, thereby supporting the transmission of more types of services.
[0009] In one possible design, before deactivating N DRBs, the method may further include: activating Z DRBs out of M DRBs, where Z DRBs include at least one DRB used for transmitting data services, Z ≤ M, ZN ≤ T, and Z is a positive integer. Thus, by performing activation and deactivation operations on the DRBs used for transmitting data services, the first and second communication devices can subsequently deactivate the at least one DRB used for transmitting data services, while activating the DRBs corresponding to the services to be transmitted, ensuring that the number of active DRBs does not exceed T, thereby supporting the transmission of more types of services.
[0010] In one possible design, when the M DRBs include at least one DRB in an active state, the method may further include: activating L of the M DRBs in an active state according to a first signaling, such that at most T of the M DRBs are in an active state, where L is a positive integer. Therefore, before activating the K DRBs, if the M DRBs include at least one DRB in an active state (i.e., the M DRBs contain ZN≠0 active DRBs), and the number of K DRBs to be activated plus the number of these ZN≠0 DRBs is greater than T, then the first communication device further activates L of the M DRBs in an active state according to the first signaling, such that at most T of the M DRBs are in an active state, where L is a positive integer.
[0011] In one possible design, the method may further include: sending a second signaling message to a second communication device, the second signaling message being used to request the activation of K DRBs. Thus, the first communication device can trigger the sending of a first signaling message to itself, for example, when the first communication device initiates a service corresponding to a deactivated and / or inactive DRB, or when the first communication device needs to initiate a service corresponding to a deactivated and / or inactive DRB based on a paging request from the second communication device, the first communication device can send the second signaling message to the second communication device to trigger the second communication device to send the first signaling message to the first communication device according to the second signaling message.
[0012] In one possible design, when the first communication device is in a Radio Resource Control (RRC) inactive or suspended state, the second signaling can be an RRC recovery request. This allows for the reuse of predefined RRC messages to activate the DRB, reducing signaling overhead.
[0013] In one possible design, the second signaling includes information for indicating K DRBs.
[0014] In one possible design, the first signaling message can be an RRC message. For example, the first signaling message can be an RRC Reconfiguration message, an RRC Reestablishment message, an RRC Release message, an RRC Resume message, etc., wherein the first signaling message includes an activation indication.
[0015] In one possible design, the first threshold is related to the capability of the first communication device.
[0016] In one possible design, the M DRBs include at least one DRB for transmitting data services, one DRB for transmitting Internet Protocol Multimedia Subsystem (IMS) voice signaling, and one DRB for transmitting IMS voice services. Thus, the first communication device can implement IMS voice services through activation and deactivation operations.
[0017] In one possible design, the K DRBs include DRBs for transmitting IMS voice services and / or DRBs for transmitting IMS voice signaling. Thus, the first communication device can implement IMS voice services through activation and deactivation operations.
[0018] Secondly, a communication method is provided. Taking the application of this method to a second communication device as an example, in this method: M DRBs are established with the first communication device, and N DRBs among the M DRBs are deactivated such that at most T DRBs among the M DRBs are in an active state, M≥3 and are integers, N is a positive integer and N≤M, T is a positive integer and T is equal to a first threshold; a first signaling is sent to the first communication device, the first signaling is used to activate K DRBs, K≤T and are positive integers; and K DRBs are activated.
[0019] In one possible design, at least one of the N DRBs is used for transmitting data services.
[0020] In one possible design, before deactivating N DRBs, the method may further include: activating Z DRBs out of M DRBs, where Z DRBs include at least one DRB used for transmitting data services, Z≤M, ZN≤T, and Z is a positive integer.
[0021] In one possible design, when the M DRBs include at least one DRB in an active state, the method may further include: deactivating L of the M DRBs that are in an active state, such that at most T of the M DRBs are in an active state, where L is a positive integer.
[0022] In one possible design, the method may further include: receiving a second signaling from a first communication device, the second signaling being used to request the activation of K DRBs.
[0023] In one possible design, when the first communication device is in an RRC inactive state or an RRC paused state, the second signaling can be an RRC recovery request.
[0024] In one possible design, the second signaling includes information for indicating K DRBs.
[0025] In one possible design, the first signaling message can be an RRC message.
[0026] In one possible design, the first threshold is related to the capability of the first communication device.
[0027] In one possible design, the M DRBs include at least one DRB for transmitting data services, one DRB for transmitting Internet Protocol Multimedia Subsystem (IMS) voice signaling, and one DRB for transmitting IMS voice services.
[0028] In one possible design, the K DRBs include DRBs for transmitting IMS voice services and / or DRBs for transmitting IMS voice signaling.
[0029] The technical effects of the method described in the second aspect can be found in the relevant description of the technical effects of the method described in the first aspect above, and will not be repeated here.
[0030] Thirdly, a communication method is provided. Taking the application of this method to a first communication device as an example, in this method: a first message is sent to a second communication device, the first message being used to request the transmission of multiple Session Initiation Protocol (SIP) messages based on the Signaling Radio Bearer (SRB0), the first message including a first Non-Access Stratum (NAS) message, the first NAS message including a first SIP message in the first SIP process; a second message is received from the second communication device, the second message being used to confirm the transmission of multiple SIP messages based on SRB0, the second message including a second NAS message, the second NAS message including a second SIP message in the first SIP process.
[0031] In this method, the first communication device sends a first message to the second communication device, carrying a NAS message containing uplink SIP messages. The first message indicates a request for multiple SIP message transmission based on SRB0. This allows the second communication device to send a second message to the first communication device, carrying a NAS message containing downlink SIP messages, and confirms the commencement of multiple SIP message transmission based on SRB0. Thus, the first communication device, supporting only two DRBs, can complete IMS voice signaling transmission based on SRB0 by transmitting NAS messages. By transmitting IMS voice signaling through the control plane, IMS voice services can be implemented.
[0032] In one possible design, the first message is Msg3, and the first message also includes first indication information, which indicates that multiple SIP message transmissions based on SRB0 are required. Therefore, Msg3 can be reused to reduce signaling overhead.
[0033] In one possible design, the second message is Msg4, which includes second indication information used to indicate confirmation of multiple SIP message transmissions based on SRB0. This allows Msg4 to be reused, reducing signaling overhead.
[0034] In one possible design, the method may further include: not performing a Radio Resource Control (RRC) idle state or RRC connected state transition based on the second message. That is, the first communication device does not trigger an RRC state change based on the second message, and remains in the state of establishing SRB0 but not SRB1 until the SIP process ends, or an indication is given to end SIP message transmission based on SRB0.
[0035] In one possible design, the method may further include: sending a third message to the second communication device, the third message including third indication information, the third indication information being used to indicate the termination of SRP0-based SIP message transmission or to indicate the termination of the first SIP process; and receiving a fourth message from the second communication device, the fourth message including fourth indication information, the fourth indication information being used to indicate that the second communication device transitions to an RRC idle state or an RRC connected state. Thus, the first communication device can indicate the termination of SRP0-based SIP message transmission or indicate the termination of the first SIP process to trigger the second communication device to send the fourth message, completing the RRC connection establishment.
[0036] In one possible design, the third message is Msg3 and the fourth message is Msg4.
[0037] Fourthly, a communication method is provided. Taking the application of this method to a second communication device as an example, in this method: a first message is received from a first communication device, the first message being used to request the transmission of multiple Session Initiation Protocol (SIP) messages based on SRB0, the first message including a first NAS message, the first NAS message including a first SIP message in a first SIP process; a second message is sent to the first communication device, the second message being used to confirm the transmission of multiple SIP messages based on SRB0, the second message including a second NAS message, the second NAS message including a second SIP message in a first SIP process.
[0038] In one possible design, the first message is Msg3, and the first message also includes first indication information, which is used to indicate that multiple SIP message transmissions based on SRB0 are required.
[0039] In one possible design, the second message is Msg4, and the second message includes second indication information, which is used to indicate confirmation of the transmission of multiple SIP messages based on SRB0.
[0040] In one possible design, the method may further include: receiving a third message from a first communication device, the third message including third indication information, the third indication information being used to indicate the end of SRP message transmission based on SRB0 or to indicate the end of a first SRP process; and sending a fourth message to the first communication device, the fourth message including fourth indication information, the fourth indication information being used to indicate that the second communication device switches to an RRC idle state or an RRC connected state.
[0041] In one possible design, the third message is Msg3 and the fourth message is Msg4.
[0042] The technical effects of the method described in the fourth aspect can be found in the relevant description of the technical effects of the method described in the third aspect above, and will not be repeated here.
[0043] Fifthly, a communication method is provided. Taking the application of this method to a first communication device as an example, in this method: after establishing a Radio Resource Control (RRC) connection with a second communication device, a first Non-Access Stratum (NAS) message is generated. The first NAS message includes first Internet Protocol Multimedia Subsystem (IMS) data after header compression, or the first NAS message includes first IMS data, which is IMS voice signaling data or IMS voice service data; the first NAS message is then sent.
[0044] In this method, the first communication device can either compress the IMS data header and stuff it into the NAS message, or stuff it directly into the NAS message without header compression. It then sends the NAS message carrying the IMS data based on SRB1 to the third communication device, which then transmits the IMS data to the IMS network via the control plane. Thus, by supporting only two DRBs, the first communication device can transmit IMS voice signaling data or IMS voice service data based on SRB1 to transmit NAS messages, and transmit IMS voice signaling data or IMS voice service data via the control plane, thereby enabling IMS voice services.
[0045] In one possible design, if the first NAS message includes header-compressed first IMS data, the first NAS message also includes header-compressed configuration information for the third communication device to decompress and obtain the first IMS data and send the first IMS data to the IMS network.
[0046] In one possible design, where the first NAS message includes header-compressed first IMS data, the method may further include: sending a first message to a second communication device, the first message including desired header compression configuration information; and receiving a second message from the second communication device, the second message including determined header compression configuration information. Thus, the header compression configuration information can be negotiated.
[0047] In one possible design, the first message is Msg3 and the second message is Msg4.
[0048] In one possible design, the first message includes first IMS data that has not been header compressed, and the second message includes second IMS data that has not been header compressed, the second IMS data coming from the IMS network element.
[0049] In one possible design, the method may further include: receiving a second NAS message, the second NAS message including header-compressed second IMS data, the second IMS data originating from an IMS network element; and decompressing the header-compressed second IMS data according to the header compression configuration information. Thus, the first communication device can also receive header-compressed downlink IMS data from the third communication device and decompress it based on the header compression configuration information to obtain the downlink IMS data.
[0050] In one possible design, if the first NAS message includes first IMS data, the first NAS message also includes the type of the first IMS data.
[0051] Sixthly, a communication method is provided. Taking the application of this method to a third communication device as an example, in this method: receiving a first NAS message, the first NAS message including first IMS data after header compression, or the first NAS message including first IMS data, the first IMS data being IMS voice signaling data or IMS voice service data; and sending the encapsulated first IMS data to an IMS network element.
[0052] In one possible design, if the first NAS message includes header-compressed first IMS data, the first NAS message also includes header-compressed configuration information.
[0053] In one possible design, if the first NAS message includes header-compressed first IMS data, the method may further include: receiving a third message from a second communication device, the third message including header-compressed configuration information.
[0054] In one possible design, the third message also includes the first IMS data that has not undergone header compression.
[0055] In one possible design, the method may further include: receiving second IMS data from an IMS network; and sending a second NAS message, the second NAS message including the second IMS data after header compression.
[0056] In one possible design, sending the encapsulated first IMS data to the IMS network element may include: decompressing the header-compressed first IMS data according to the header compression configuration information; and sending the encapsulated first IMS data to the IMS network element.
[0057] In one possible design, if the first NAS message includes first IMS data, the first NAS message also includes the type of the first IMS data.
[0058] The technical effects of the method described in the sixth aspect can be found in the relevant description of the technical effects of the method described in the fifth aspect above, and will not be repeated here.
[0059] In a seventh aspect, a communication device is provided for implementing the various methods described above. This communication device may be the first communication device described in the first aspect, or a device comprising the first communication device, or a device included in the first communication device, such as a chip. The communication device includes corresponding modules, units, or means for implementing the methods described in the first aspect. These modules, units, or means may be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above.
[0060] In some possible designs, the communication device includes a processing module and a transceiver module. The processing module is used to establish M data radio bearers (DRBs) with the second communication device and deactivate N DRBs out of the M DRBs, such that at most T DRBs are active, where M ≥ 3 and are integers, N is a positive integer and N ≤ M, T is a positive integer, and T equals a first threshold. The transceiver module is used to receive a first signaling from the second communication device, which is used to activate K DRBs, where K ≤ T and are positive integers. The processing module is also used to activate the K DRBs according to the first signaling.
[0061] In one possible design, at least one of the N DRBs is used for transmitting data services.
[0062] In one possible design, before deactivating N DRBs, the processing module is also used to activate Z DRBs out of M DRBs. The Z DRBs include at least one DRB used for transmitting data services, Z≤M, ZN≤T, and Z is a positive integer.
[0063] In one possible design, when the M DRBs include at least one DRB in an active state, the processing module is further configured to activate L of the M DRBs in an active state according to the first signaling, such that at most T of the M DRBs are in an active state, where L is a positive integer.
[0064] In one possible design, the transceiver module is also used to send a second signaling to the second communication device, the second signaling being used to request the activation of K DRBs.
[0065] In one possible design, when the communication device is in the Radio Resource Control (RRC) inactive state or the RRC paused state, the second signaling can be an RRC recovery request.
[0066] In one possible design, the second signaling includes information for indicating K DRBs.
[0067] In one possible design, the first signaling message can be an RRC message.
[0068] In one possible design, the first threshold is related to the capability of the first communication device.
[0069] In one possible design, the M DRBs include at least one DRB for transmitting data services, one DRB for transmitting Internet Protocol Multimedia Subsystem (IMS) voice signaling, and one DRB for transmitting IMS voice services.
[0070] In one possible design, the K DRBs include DRBs for transmitting IMS voice services and / or DRBs for transmitting IMS voice signaling.
[0071] In one possible design, the transceiver module may include a receiving module and a sending module. The sending module implements the sending function of the communication device, and the receiving module implements the receiving function of the communication device.
[0072] In one possible design, the communication device may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the method described in the first aspect.
[0073] Eighthly, a communication device is provided for implementing the various methods described above. This communication device may be the second communication device described in the second aspect, or a device comprising the second communication device, or a device included in the second communication device, such as a chip. The communication device includes corresponding modules, units, or means for implementing the methods described in the second aspect. These modules, units, or means may be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above.
[0074] In some possible designs, the communication device includes a processing module and a transceiver module. The processing module is used to establish M DRBs with the first communication device and deactivate N DRBs out of the M DRBs such that at most T DRBs are active, where M ≥ 3 and is an integer, N is a positive integer and N ≤ M, T is a positive integer, and T equals a first threshold. The transceiver module is used to send a first signaling to the first communication device, the first signaling being used to activate K DRBs, K ≤ T and is a positive integer. The processing module is also used to activate the K DRBs.
[0075] In one possible design, at least one of the N DRBs is used for transmitting data services.
[0076] In one possible design, before deactivating N DRBs, the processing module is also used to activate Z DRBs out of M DRBs. The Z DRBs include at least one DRB used for transmitting data services, Z≤M, ZN≤T, and Z is a positive integer.
[0077] In one possible design, when the M DRBs include at least one DRB in an active state, the processing module is also used to deactivate L of the M DRBs that are in an active state, such that at most T of the M DRBs are in an active state, where L is a positive integer.
[0078] In one possible design, the transceiver module is also used to receive a second signaling from the first communication device, the second signaling being used to request the activation of K DRBs.
[0079] In one possible design, when the first communication device is in an RRC inactive state or an RRC paused state, the second signaling can be an RRC recovery request.
[0080] In one possible design, the second signaling includes information for indicating K DRBs.
[0081] In one possible design, the first signaling message can be an RRC message.
[0082] In one possible design, the first threshold is related to the capability of the first communication device.
[0083] In one possible design, the M DRBs include at least one DRB for transmitting data services, one DRB for transmitting Internet Protocol Multimedia Subsystem (IMS) voice signaling, and one DRB for transmitting IMS voice services.
[0084] In one possible design, the K DRBs include DRBs for transmitting IMS voice services and / or DRBs for transmitting IMS voice signaling.
[0085] In one possible design, the transceiver module may include a receiving module and a sending module. The sending module implements the sending function of the communication device, and the receiving module implements the receiving function of the communication device.
[0086] In one possible design, the communication device may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the method described in the second aspect.
[0087] Ninthly, a communication device is provided for implementing the various methods described above. This communication device may be the first communication device described in the third aspect, or a device comprising the first communication device, or a device included in the first communication device, such as a chip. The communication device includes corresponding modules, units, or means for implementing the methods described in the third aspect, which may be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above.
[0088] In some possible designs, the communication device includes a processing module and a transceiver module. The processing module generates a first message; the transceiver module sends the first message to a second communication device, the first message requesting the transmission of multiple Session Initiation Protocol (SIP) messages based on the Signaling Radio Bearer (SRB0), the first message including a first Non-Access Stratum (NAS) message, the first NAS message including a first SIP message in the first SIP process; the transceiver module also receives a second message from the second communication device, the second message confirming the transmission of multiple SIP messages based on SRB0, the second message including a second NAS message, the second NAS message including a second SIP message in the first SIP process.
[0089] In one possible design, the first message is Msg3, and the first message also includes first indication information, which is used to indicate that multiple SIP message transmissions based on SRB0 are required.
[0090] In one possible design, the second message is Msg4, and the second message includes second indication information, which is used to indicate confirmation of the transmission of multiple SIP messages based on SRB0.
[0091] In one possible design, the processing module is also configured to, based on the second message, not perform a Radio Resource Control (RRC) idle state or RRC connected state transition.
[0092] In one possible design, the transceiver module is further configured to send a third message to the second communication device, the third message including third indication information, the third indication information being used to indicate the end of SIP message transmission based on SRB0 or to indicate the end of the first SIP process, and is further configured to receive a fourth message from the second communication device, the fourth message including fourth indication information, the fourth indication information being used to indicate that the second communication device switches to RRC idle state or RRC connected state.
[0093] In one possible design, the third message is Msg3 and the fourth message is Msg4.
[0094] In one possible design, the transceiver module may include a receiving module and a sending module. The sending module implements the sending function of the communication device, and the receiving module implements the receiving function of the communication device.
[0095] In one possible design, the communication device may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the method described in the third aspect.
[0096] In a tenth aspect, a communication device is provided for implementing the various methods described above. This communication device may be the second communication device described in the fourth aspect, or a device comprising the second communication device, or a device included in the second communication device, such as a chip. The communication device includes corresponding modules, units, or means for implementing the methods described in the fourth aspect, which may be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above.
[0097] In some possible designs, the communication device includes a processing module and a transceiver module. The transceiver module is used to receive a first message from a first communication device, the first message requesting the transmission of multiple Session Initiation Protocol (SIP) messages based on SRB0, the first message including a first NAS message, the first NAS message including a first SIP message in a first SIP process; the processing module is used to generate a second message; the transceiver module is also used to send the second message to the first communication device, the second message confirming the transmission of multiple SIP messages based on SRB0, the second message including a second NAS message, the second NAS message including a second SIP message in a first SIP process.
[0098] In one possible design, the first message is Msg3, and the first message also includes first indication information, which is used to indicate that multiple SIP message transmissions based on SRB0 are required.
[0099] In one possible design, the second message is Msg4, and the second message includes second indication information, which is used to indicate confirmation of the transmission of multiple SIP messages based on SRB0.
[0100] In one possible design, the transceiver module is further configured to receive a third message from the first communication device, the third message including third indication information, the third indication information being used to indicate the end of SRP message transmission based on SRB0 or to indicate the end of the first SIP process, and is further configured to send a fourth message to the first communication device, the fourth message including fourth indication information, the fourth indication information being used to indicate that the second communication device switches to RRC idle state or RRC connected state.
[0101] In one possible design, the third message is Msg3 and the fourth message is Msg4.
[0102] In one possible design, the transceiver module may include a receiving module and a sending module. The sending module implements the sending function of the communication device, and the receiving module implements the receiving function of the communication device.
[0103] In one possible design, the communication device may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the method described in the fourth aspect.
[0104] Eleventhly, a communication device is provided for implementing the various methods described above. This communication device may be the first communication device described in the fifth aspect, or a device comprising the first communication device, or a device included in the first communication device, such as a chip. The communication device includes corresponding modules, units, or means for implementing the methods described in the fifth aspect. These modules, units, or means may be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above.
[0105] In some possible designs, the communication device includes a processing module and a transceiver module. The processing module is used to generate a first Non-Access Stratum (NAS) message after establishing a Radio Resource Control (RRC) connection with the second communication device. The first NAS message includes header-compressed first Internet Protocol Multimedia Subsystem (IMS) data, or the first NAS message includes first IMS data, which is IMS voice signaling data or IMS voice service data. The transceiver module is used to send the first NAS message.
[0106] In one possible design, if the first NAS message includes header-compressed first IMS data, the first NAS message also includes header-compressed configuration information.
[0107] In one possible design, if the first NAS message includes first IMS data after header compression, the transceiver module is further configured to send a first message to the second communication device, the first message including desired header compression configuration information, and to receive a second message from the second communication device, the second message including determined header compression configuration information.
[0108] In one possible design, the first message is Msg3 and the second message is Msg4.
[0109] In one possible design, the first message includes first IMS data that has not been header compressed, and the second message includes second IMS data that has not been header compressed, the second IMS data coming from the IMS network element.
[0110] In one possible design, the transceiver module is also used to receive a second NAS message, which includes second IMS data after header compression, and the second IMS data comes from an IMS network element; and to decompress the header-compressed second IMS data according to the header compression configuration information.
[0111] In one possible design, if the first NAS message includes first IMS data, the first NAS message also includes the type of the first IMS data.
[0112] In one possible design, the transceiver module may include a receiving module and a sending module. The sending module implements the sending function of the communication device, and the receiving module implements the receiving function of the communication device.
[0113] In one possible design, the communication device may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the method described in the fifth aspect.
[0114] In a twelfth aspect, a communication device is provided for implementing the various methods described above. This communication device may be the third communication device described in the sixth aspect, or a device comprising the third communication device, or a device included in the third communication device, such as a chip. The communication device includes corresponding modules, units, or means for implementing the methods described in the sixth aspect, which may be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above.
[0115] In some possible designs, the communication device includes a processing module and a transceiver module. The processing module performs processing functions. The transceiver module receives a first NAS message, which includes header-compressed first IMS data, or the first NAS message includes first IMS data, which is IMS voice signaling data or IMS voice service data. The transceiver module also sends encapsulated first IMS data to IMS network elements.
[0116] In one possible design, if the first NAS message includes header-compressed first IMS data, the first NAS message also includes header-compressed configuration information.
[0117] In one possible design, if the first NAS message includes header-compressed first IMS data, the transceiver module is further configured to receive a third message from the second communication device, the third message including header-compressed configuration information.
[0118] In one possible design, the third message also includes the first IMS data that has not undergone header compression.
[0119] In one possible design, the transceiver module is further configured to receive second IMS data from the IMS network and to send a second NAS message, which includes the second IMS data after header compression.
[0120] In one possible design, the transceiver module is further configured to send the encapsulated first IMS data to the IMS network element. This may include: the transceiver module being configured to decompress the header-compressed first IMS data according to the header compression configuration information, and also being configured to send the encapsulated first IMS data to the IMS network element.
[0121] In one possible design, if the first NAS message includes first IMS data, the first NAS message also includes the type of the first IMS data.
[0122] In one possible design, the transceiver module may include a receiving module and a sending module. The sending module implements the sending function of the communication device, and the receiving module implements the receiving function of the communication device.
[0123] In one possible design, the communication device may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the method described in the sixth aspect.
[0124] In a thirteenth aspect, a communication device is provided (e.g., the communication device may be a chip or a chip system). The communication device includes a processor for implementing the functions involved in any of the preceding aspects.
[0125] In one possible design, the communication device may further include a memory for storing necessary program instructions and data. A processor is coupled to the memory and is used to execute the computer program or instructions stored in the memory, causing the communication device to perform the method described in any of the possible implementations of the first to sixth aspects.
[0126] In one possible design, the communication device described in aspect thirteen may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in aspect thirteen and other communication devices.
[0127] In one possible design, the processor can be integrated with the memory.
[0128] In some possible designs, when the device is a chip system, it can be composed of chips or contain chips and other discrete components.
[0129] Fourteenth aspect, a communication device is provided, the communication device including a processor and an interface circuit, the interface circuit being configured to receive signals from other communication devices outside the communication device and transmit them to the processor or to send signals from the processor to other communication devices outside the communication device, the processor being configured to implement the method as described in any one of the possible implementations of the first to sixth aspects via logic circuits or execution code instructions.
[0130] It is understood that when the communication device provided in either the thirteenth or fourteenth aspect is a chip, the aforementioned transmitting action / function can be understood as an output, and the aforementioned receiving action / function can be understood as an input.
[0131] In a fifteenth aspect, a computer-readable storage medium is provided, which stores a computer program or instructions that, when executed on a communication device, enable the communication device to perform the method described in any one of the first to sixth aspects.
[0132] In a sixteenth aspect, a computer program product including instructions is provided, comprising computer program code, which, when executed on a communication device, enables the communication device to perform the method described in any one of the first to sixth aspects.
[0133] In a seventeenth aspect, a communication system is provided, comprising: a first communication device for implementing the method of the first aspect and a second communication device for implementing the method of the second aspect; or, comprising a first communication device for implementing the method of the third aspect and a second communication device for implementing the method of the fourth aspect; or, a first communication device for implementing the method of the fifth aspect and a third communication device for implementing the method of the sixth aspect.
[0134] Eighteenthly, a communication chip is provided, wherein instructions are stored that, when the chip is operated on a communication device, cause the method described in any one of the first to sixth aspects above to be implemented. Attached Figure Description
[0135] Figure 1 This is a schematic diagram of an IMS network architecture;
[0136] Figure 2 A schematic diagram illustrating the process of establishing DRB and QoS between a terminal and a network;
[0137] Figure 3 This application provides a schematic diagram of the architecture of a communication system.
[0138] Figure 4 This is a schematic diagram of the architecture of another communication system provided in an embodiment of this application;
[0139] Figure 5 This application provides a schematic diagram of a communication scenario applicable to the aforementioned communication system.
[0140] Figure 6 A flowchart illustrating a communication method provided in an embodiment of this application;
[0141] Figure 7 A schematic diagram illustrating three scenarios for DRB activation and deactivation provided in this application embodiment;
[0142] Figure 8 A flowchart illustrating another communication method provided in an embodiment of this application;
[0143] Figure 9 A schematic diagram illustrating a process for SIP message transmission based on Msg3 and Msg4, provided for an embodiment of this application;
[0144] Figure 10 A flowchart illustrating yet another communication method provided in an embodiment of this application;
[0145] Figure 11 A schematic diagram illustrating the process of negotiating configuration information for header compression, provided for an embodiment of this application;
[0146] Figure 12 A schematic diagram illustrating the bearer relationship between header-compressed first IMS data / first IMS data, first NAS message, and RRC message, provided for embodiments of this application;
[0147] Figure 13 A schematic diagram of a protocol stack for transmitting IMS data via NAS messages between a first communication device, a second communication device, a third communication device and an IMS network element in the control plane of this application embodiment;
[0148] Figure 14 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;
[0149] Figure 15 This is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation
[0150] To better understand the embodiments of this application, the following points are explained before introducing the embodiments of this application.
[0151] First, in the embodiments of this application, "for indicating" can include both direct and indirect indication. When describing a certain "indication information" for indicating A, it can include whether the indication information directly indicates A or indirectly indicates A, but does not necessarily mean that the indication information carries A.
[0152] The information indicated by the instruction is called the information to be instructed. In the specific implementation process, there are many ways to indicate the information to be instructed, such as, but not limited to, directly indicating the information to be instructed, such as the information to be instructed itself or its index. It can also be indirectly indicated by indicating other information, where there is a relationship between the other information and the information to be instructed. It can also indicate only a part of the information to be indicated, while the other parts are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing instruction overhead to some extent. At the same time, common parts of various pieces of information can be identified and indicated uniformly to reduce the instruction overhead caused by individually indicating the same information.
[0153] Furthermore, the specific indication method can also be any existing indication method, such as, but not limited to, the above-mentioned indication methods and their various combinations. Specific details of various indication methods can be found in existing technologies, and will not be repeated here. As described above, for example, when multiple pieces of information of the same type need to be indicated, the indication methods for different pieces of information may differ. In the specific implementation process, the required indication method can be selected according to specific needs. This application embodiment does not limit the selected indication method; therefore, the indication methods involved in this application embodiment should be understood to cover various methods that enable the party to be indicated to obtain the information to be indicated.
[0154] Secondly, in the embodiments of this application, the terms "first," "second," and various numerical designations are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. For example, "first device" and "second device" are only used to distinguish different devices and do not limit their order. Those skilled in the art will understand that the terms "first," "second," etc., do not limit the quantity or execution order, and that "first," "second," etc., are not necessarily different.
[0155] Third, in the embodiments of this application, descriptions such as "when," "under the circumstances," "if," and "if" all refer to the device making corresponding processing under certain objective circumstances. They are not time limits, nor do they require the device to make a judgment action during implementation, nor do they imply any other limitations.
[0156] Fourth, in the embodiments of this application, the words "exemplary" or "for example" are used to indicate that they are examples, illustrations, or descriptions. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design options. Specifically, the use of the words "exemplary" or "for example" is intended to present the relevant concepts in a specific manner to facilitate understanding.
[0157] Fifth, in this application, "sending information" can be understood as one device sending information to another device, or it can also be understood as one logical module within a device sending information to another logical module. For example, "terminal sending information" can be understood as a terminal sending information to another device (such as a network device), or it can be understood as logical module 1 in the terminal sending information to logical module 2 in the terminal.
[0158] In this application, "receiving information" can be understood as one device receiving information from another device, or it can also be understood as a logical module within a device receiving information from another logical module. For example, "terminal receiving information" can be understood as the terminal receiving information from another device (such as a network device), or it can be understood as logical module 1 in the terminal receiving information from logical module 2 in the terminal.
[0159] Sixth, the phrase "sending information to... (e.g., a terminal)" in this application, or the relevant illustrations in the accompanying drawings, can be understood as the destination of the information being a terminal. This can include sending information directly or indirectly to a terminal. Similarly, "receiving information from... (e.g., a terminal)," "receiving information from... (e.g., a terminal)," or "receiving information sent (e.g., by a terminal)," or the relevant illustrations in the accompanying drawings, can be understood as the source of the information being a terminal. This can include receiving information directly or indirectly from a terminal. Information may undergo necessary processing between the source and destination, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be interpreted similarly, and will not be elaborated further here.
[0160] This application will present various aspects, embodiments, or features relating to a system that may include multiple devices, components, modules, etc. It should be understood and appreciated that individual systems may include additional devices, components, modules, etc., and / or may not include all the devices, components, modules, etc. discussed in conjunction with the accompanying drawings. Furthermore, combinations of these approaches may also be used.
[0161] The technical solutions of this application can be applied to non-terrestrial network (NTN) communication systems, terrestrial network (TN) communication systems, and communication systems that integrate NTN and TN. NTN communication systems include, for example, satellite communication systems and high altitude platform station (HAPS) communication systems. TN communication systems include, for example, the Global System for Mobile Communication (GSM), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX), 4th generation (4G) mobile communication systems such as Long Term Evolution (LTE), 5th generation (4G) mobile communication systems such as New Radio (NR), and future communication systems.
[0162] For ease of understanding, the following section will first introduce the relevant terms, concepts, or technologies that may be involved in the embodiments of this application:
[0163] 1. Narrow Band Internet of Things (NB-IoT)
[0164] NB-IoT is a low-power wide-area network (LPWAN) technology designed specifically for IoT applications. Based on cellular networks, it aims to support massive device connectivity while offering advantages such as low power consumption, wide coverage, and low cost. NB-IoT is a technology standardized by the 3rd Generation Partnership Project (3GPP) and is primarily used in IoT scenarios requiring low data rates, long battery life, and wide coverage. Typical NB-IoT scenarios include: smart meter reading (remote meter reading applications for water, electricity, gas, etc.), smart cities (smart streetlights, garbage bin monitoring, environmental monitoring (such as air quality and noise)), smart agriculture (soil moisture monitoring, weather stations, irrigation control, etc.), smart homes (security monitoring, smoke detectors, smart locks, etc.), and industrial IoT (equipment condition monitoring, predictive maintenance, remote control, etc.).
[0165] NB-IoT devices are devices that support NB-IoT technology and are typically used in IoT applications. NB-IoT devices communicate with the cloud or other devices through NB-IoT networks to achieve data acquisition, transmission, and control functions. The design focus of NB-IoT devices is low power consumption, low cost, and high reliability to meet the needs of IoT applications.
[0166] In this application embodiment, NB-IoT devices may also be referred to as NB-IoT terminals, NB-IoT devices, etc., and there is no limitation thereto.
[0167] For example, an NB-IoT device includes an NB-IoT module, sensors, a microcontroller unit (MCU), a power management unit, and an antenna. The NB-IoT module is the core component responsible for communicating with the NB-IoT network, and typically integrates a baseband processor, an RF chip, and an antenna. Sensors are used to collect environmental or device data, such as temperature, humidity, pressure, light intensity, and location. The microcontroller is responsible for data processing and device control, and typically communicates with the NB-IoT module via a serial port or a serial peripheral interface (SPI). The power management unit provides a stable power supply, supporting battery power or an external power source. The antenna is used to transmit and receive wireless signals and is typically integrated into the module or used as an external component.
[0168] 2. IMS
[0169] IMS voice service is a voice communication service provided based on the IMS network. IMS is an IP-based core network architecture designed to support a variety of multimedia services, including voice, video, and messaging. IMS voice service is one of the core applications in the IMS network, often referred to as VoLTE (Voice over LTE) or VoNR (Voice over NR), depending on the radio access technology used (LTE or 5G NR).
[0170] For example, Figure 1 This is a schematic diagram of an IMS network architecture. Figure 1As shown, the user equipment (UE) communicates with the proxy-call session control function (P-CSCF) through the Gm interface (Gm); the P-CSCF communicates with the serving-call session control function (S-CSCS) through the Mw interface (Mw); the P-CSCF communicates with the IMS access gateway (IMS-AGW) through the Iq interface (Iq); the IMS-AGW communicates with the remote IMS, media function (MF), and UE through the Mb interface (Mb); the S-CSCF communicates with the home subscriber server (HSS) through the N70 / Cx interface (N70 / Cx); the S-CSCF communicates with the IMS application server (AS) through the ISC interface (ISC); and the IMS AS communicates with the HSS interface through the N71 / Sh interface (N71 / Sh). The AS communicates with the data channel signaling function (DCSF) via the DC1 interface (DC1); the IMS AS communicates with the MF via the DC2 interface (DC2); the DCSF communicates with the network exposure function (NEF) via the DC3 interface (DC3); the DCSF communicates with the data channel application server (DCAS) via the DC4 or MDC3 interface (DC3 or MDC3); the DCSF communicates with the DCAR via the DC5 interface (DC5); the DCSF communicates with the MF via the MDC1 interface (MDC1); the MF communicates with the DCAS via the MDC2 interface (MDC2); and the HSS communicates with the DCSF interface via the N72 / Sc interface (N72 / Sc). Furthermore, Figure 1 The functions shown, such as IMS AS, DCSF, MF, or NEF, interact using service-oriented interfaces. For example, the service-oriented interface provided by IMS AS is Nimsas; that of DCSF is Ndcsf; that of NEF is Nnef; and that of MF is Nmf.
[0171] The functions of each network element in this IMS network architecture are as follows:
[0172] P-CSCF: This is the entry node for SIP users to access the IMS network. It is mainly responsible for forwarding SIP signaling between SIP users and their home network.
[0173] S-CSCF: It is the central node of the IMS network, responsible for user registration, authentication, sessions, routing, and service triggering.
[0174] IMS-AGW: This is the IMS access gateway, primarily responsible for media plane communication between the user and network interfaces.
[0175] HSS: The main database for IMS user subscriptions is responsible for managing user subscription data and mobile user location information. It is responsible for storing the following main user-related subscription information: user identity (ID), such as IMS private identity (IMPI) and IMS public identity (IMPU); user authentication-related information; S-CSCF information registered by the user; and transparent data stored by the AS in the HSS, such as the UE's call forwarding number.
[0176] IMS AS: Generally refers to the server network element in an IMS network that processes upper-layer voice services, including basic audio and video services and supplementary services. Specifically, an AS may include the MMTel AS (processing basic audio and video services and supplementary services) and / or the Service Centralization and Continuity (SCC) AS (responsible for signaling control and called party access domain selection for single-mode service continuity (eSRVCC)). These two ASs can be configured independently or jointly.
[0177] DCSF: Provides signaling control functions for data channel control logic. DCSF supports the following functions: receiving event reports from the IMS AS and determining whether to allow data channel service during an IMS session; bootstrapping data channels and (if applicable) applying data channel resources at the MF or media resource function (MRF) via the IMS AS; supporting Hypertext Transfer Protocol (HTTP) web server functions to download data channel applications (bootstrapping) to the UE via MF and / or MRF based on the UE subscription; and downloading data channel applications from the data channel application repository.
[0178] MF: Provides media resource management and forwarding of data channel media services. MF supports the following functions: managing data channel media resources (bootstrapping and application data channel resources, if applicable) under the control of the IMS AS; terminating bootstrapping data channels from the UE and forwarding HTTP services between the UE and DCSF via MDC1; anchoring application data channels in peer-to-peer (P2P) scenarios if needed and forwarding application data services from the UE to the UE; relaying services on application-to-person (A2P) / person-to-application (P2A) application data channels between the UE and DC application server via MDC2.
[0179] NEF: Primarily used to support the opening of capabilities and events.
[0180] DCAS: Primarily used to provide services related to DC applications.
[0181] In the embodiments of this application, the above-mentioned functions can be referred to as entities or network elements. For example, P-CSCF can also be referred to as P-CSCF entity or P-CSCF network element, and S-CSCF can also be referred to as S-CSCF entity or S-CSCF network element. There is no limitation on this.
[0182] Currently, the terminal uses the terrestrial communication network to conduct IMS voice services with the IMS network. There are at least three DRBs between the terminal performing IMS voice services and the access network equipment, which are used to transmit data services, IMS voice signaling and IMS voice services respectively.
[0183] like Figure 2 As shown, taking a 5G communication system as an example, after the UE establishes an RRC connection with the next-generation Node-B (gNB), it will establish a QoS flow for transmitting data services with a default 5G QoS identifier (5QI) of 8 / 9 through the access and mobility management function (AMF), session management function (SMF), and user plane function (UPF) in the 5G core network. At this time, at least one DRB for transmitting data services is established between the UE and the gNB.
[0184] To support IMS voice services, the UE will also establish a QoS flow of 5QI=5 between the gNB and the 5G core network for transmitting IMS signaling services (SIP messages). At this time, a DRB for transmitting IMS signaling services is established between the UE and the gNB.
[0185] When IMS voice service is initiated, the UE also needs to establish a QoS flow of 5QI=1 between the gNB and the 5G core network for transmitting IMS voice service. At this time, a DRB for transmitting IMS voice service is established between the UE and the gNB. For example, the UE sends a SIP invite message to the P-CSCF in the IMS network through the gNB and the 5G core network user. The P-CSCF interacts with the policy and charging rules function (PCRF) to exchange abort session request (AAR) and abort session answer (AAA). The PCRF interacts with the UPF to exchange re-authentication request (RAR) and re-authentication answer (RAA). The UPF sends a Create Bearer Request to the AMF through the SMF. The AMF sends a Protocol Data Unit (PDU) Session Setup Request to the gNB. The gNB sends an RRC Configuration message to the UE. Accordingly, the UE sends an RRC Configuration Complete message to the gNB, the gNB sends a PDU Session Setup Response (voice stream establishment acceptance) to the AMF, and the AMF sends a Create Bearer Response (voice stream establishment acceptance) to the UPF through the SMF. The voice service between the UE and the P-CSCF is then established.
[0186] The inventors discovered that, under existing relevant standards and specifications, IoT devices (mainly referring to the aforementioned NB-IoT devices) only support two DRBs (Data Routers) with access network devices. After an IoT device establishes an RRC (Redirect Rating Control) connection with an access network device, at least one DRB for data service transmission is established by default. Therefore, it is impossible to establish an IMS (Important Management System) voice signaling DRB and an IMS voice service DRB to support IMS voice services. Similarly, similar problems exist for other types of service transmissions that require multiple DRBs. Therefore, how to enable more types of service transmission when IoT devices only support two DRBs needs to be studied. To solve the above problems, embodiments of this application provide a communication method and apparatus.
[0187] See Figure 3 This is a schematic diagram of the architecture of a communication system provided in an embodiment of this application. Figure 3 As shown, the communication system includes: a first communication device and a second communication device. Optionally, the communication system may also include a third communication device, the details of which can be found below. Figure 4 The relevant descriptions of the communication system shown are not repeated here.
[0188] In this embodiment, the first communication device is located on the terminal or user equipment side, and the number of DRBs activated by the first communication device does not exceed a first threshold. Taking the first communication device as an IoT communication device as an example, the first communication device supports IoT services and IMS services. The first communication device can be an IoT device or a module applicable to IoT devices (e.g., circuits, processors, chips, or chip systems), or a logical node, logical module, or software that can implement all or part of the functions of IoT devices. An IoT device can be called an IoT terminal. In this embodiment, IoT mainly refers to NB-IoT, so the IoT communication device can also be called an NB-IoT communication device. In addition, the first communication device can also be other types of communication devices, such as terminal devices; in this case, the first communication device can be a terminal device or a module applicable to terminal devices (e.g., circuits, processors, chips, or chip systems), or a logical node, logical module, or software that can implement all or part of the functions of terminal devices.
[0189] The second communication device is located on the wireless access network side, supports the access of the first communication device, and provides access services to the first communication device. The second communication device may be an access network device or a module (such as a circuit, processor, chip, or chip system) applicable to the access network device, or a logical node, logical module, or software that can implement all or part of the functions of the access network device.
[0190] In this embodiment, the access network device can be a terrestrial access network device or a non-terrestrial access network device. A non-terrestrial access network device can be, for example, deployed on an airborne platform or satellite, or other forms of access network device deployed at high altitudes, and can be structurally and functionally similar to a terrestrial access network device. The airborne platform can include at least one of the following: satellite, drone, hot air balloon, aircraft, or other flying vehicle. Examples of non-terrestrial access network devices include access network devices carried by or otherwise implemented in a drone, such as a high-altitude platform station (HAPS), and satellites.
[0191] Access network equipment, also known as radio access network (RAN) nodes, network devices, RAN entities, or access nodes, is located on the network side of the aforementioned communication system. It assists terminals in achieving wireless access and is a device with wireless transceiver capabilities, or a chip or chip system that can be installed in the device. Access network equipment can include, but is not limited to: base stations, evolved NodeBs (eNodeBs), access points (APs), transmission reception points (TRPs), gNBs, and base stations in future mobile communication systems. Access network equipment can be macro base stations, micro base stations or indoor stations, relay nodes or donor nodes, and radio controllers in open-radio access networks (O-RAN) or centralized-radio access networks (C-RAN) scenarios. Optionally, RAN nodes can also be servers, wearable devices, vehicles, or in-vehicle equipment. For example, in vehicle-to-everything (V2X) technology, the access network equipment can be a roadside unit (RSU). All or part of the functions of the access network device in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (such as a cloud platform). The access network device in this application can also be a logical node, logical module, or software capable of implementing all or part of the functions of the access network device.
[0192] In another possible scenario, multiple RAN nodes collaborate to assist the terminal in achieving wireless access, with each RAN node performing a portion of the base station's functions. For example, a RAN node can be a central unit (CU), a DU, a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). CUs and DUs can be separate entities or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs).
[0193] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an O-RAN system, CU can also be called O-CU (Open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.
[0194] See Figure 4 This is a schematic diagram of the architecture of another communication system provided in an embodiment of this application. Figure 4 As shown, the communication system includes a first communication device and a third communication device. Optionally, the communication system may also include a second communication device, the details of which are described above. Figure 3 The relevant information about the communication system shown is not repeated here.
[0195] For a detailed description of the first communication device, please refer to the above. Figure 3 The relevant information about the communication system shown is not repeated here.
[0196] The third communication device is a device deployed in the core network to provide services to the first communication device. Located in the control plane, it is used to implement access management and mobility management for the first communication device. For example, it is responsible for the status maintenance of terminal equipment, the reachability management of terminal equipment, the forwarding of non-access stratum (NAS) messages for mobility management (MM), the forwarding of session management (SM) N2 messages, etc. It also supports the transmission of IMS data, such as IMS signaling service data and IMS voice service data. The third communication device can be a mobility management network element or a module (e.g., circuit, processor, chip, or chip system) applicable to a mobility management network element, or a logical node, logical module, or software that can implement all or part of the mobility management network element functions.
[0197] Mobility management network element, for example, when the method of this application embodiment is applied to a 5G system, the mobility management network element can be the AMF in the 5G system. As another example, when the method of this application embodiment is applied to an LTE system, the mobility management network element can be a mobility management entity (MME).
[0198] It should be noted that the solutions in the embodiments of this application can also be applied to other communication systems, and the corresponding names can be replaced by the names of the corresponding functions in other communication systems.
[0199] For example, Figure 5 This is a schematic diagram illustrating a communication scenario applicable to the aforementioned communication system, provided as an embodiment of this application. For example... Figure 5 As shown, taking the application in a 5G network as an example, the terminal accesses the 5G base station (satellite base station) deployed on the satellite through the 5G New Radio interface. The 5G base stations are connected to each other through the Xn interface. The 5G base stations are connected to the ground station through the NG interface. The ground station is connected to the 5G user plane network element (UPF) and the 5G control plane network element (AMF and SMF) in the 5G core network, respectively. Both the user plane network element and the control plane network element are connected to the IMS network.
[0200] Among them, terminals can access the satellite network through the air interface and initiate services such as making calls and accessing the Internet. 5G base stations mainly provide wireless access services, allocate wireless resources to access terminals, and provide reliable wireless transmission protocols and data encryption protocols. Ground stations are responsible for forwarding signaling and service data between satellite base stations and the 5G core network. Ground stations are such as ground gateways.
[0201] The 5G core network is responsible for user access control, mobility management, session management, user security authentication, billing, and other services. It consists of multiple functional units, which can be divided into control plane and data plane functional entities. The AMF is responsible for user access management, security authentication, and mobility management, while the UPF is responsible for managing user plane data transmission, traffic statistics, and other functions.
[0202] The IMS network provides voice, video and other services.
[0203] The following will combine Figures 6-12 The communication method provided in the embodiments of this application will be described in detail.
[0204] For example, Figure 6 This is a flowchart illustrating a communication method provided in an embodiment of this application. The communication method uses... Figure 3 The communication between the first and second communication devices shown is illustrated using this example.
[0205] like Figure 6 As shown, the communication method includes:
[0206] S601. The first communication device and the second communication device establish M DRBs and deactivate N DRBs among the M DRBs so that at most T DRBs among the M DRBs are in an active state.
[0207] Where M ≥ 3 and is an integer, N is a positive integer and N ≤ M, T is a positive integer, and T equals the first threshold. For example, the first threshold is related to the maximum number of DRBs that the first communication device can support for transmission. For instance, the first threshold is the maximum number of DRBs that the first communication device can support for transmission; that is, the number of active DRBs among the initially established M DRBs cannot exceed the maximum number of DRBs that the first communication device can support for transmission. For example, if the first communication device is an NB-first communication device, and the NB-first communication device supports a maximum of 2 DRBs for data transmission, then the first threshold can be 2. The first threshold can also be determined by other factors, and this application does not limit the method of determining the first threshold. The first threshold can be predefined by the protocol, preconfigured by the first communication device, or obtained by the first communication device from the second communication device. This application does not limit how the first communication device obtains the first threshold.
[0208] After the first communication device and the second communication device complete the RRC establishment (RRC connection established successfully), the first communication device is in the RRC connection state. The first communication device and the second communication device can establish or configure M DRBs. These M DRBs can be considered as at least 3 default DRBs supported by the first communication device and the second communication device. Different DRBs are used to transmit or carry data of different service types, and each DRB corresponds to a QoS flow.
[0209] In one possible design, the M DRBs include at least one DRB for transmitting data services, one DRB for transmitting IMS voice signaling, and one DRB for transmitting IMS voice services. That is, the first communication device supports at least one type of data service and IMS voice service. It should be understood that the data services supported by the first communication device may include IoT services.
[0210] For example, after establishing an RRC connection, the second communication device sends an RRC Reconfiguration message to the first communication device. This RRC Reconfiguration message includes DRB configuration, which includes the DRB ID, Packet Data Convergence Protocol (PDCP) configuration (encryption / integrity protection algorithm, header compression, etc.), Radio Link Control (RLC) configuration, and logical channel configuration. Upon receiving the RRC Reconfiguration message, the first communication device establishes the Layer 2 entity of the DRB, configures the underlying logical channel and physical layer parameters, etc., based on the DRB configuration included in the RRC Reconfiguration message. After completing the DRB configuration, it sends an RRC Reconfiguration Complete message to the second communication device. Therefore, based on the above implementation, the first and second communication devices can establish or configure M DRBs, meaning both the first and second communication devices store the DRB configurations for M DRBs. In this embodiment of the application, the establishment of M DRBs between the first communication device and the second communication device can refer to the DRB configuration in which both the first communication device and the second communication device have configured M DRBs.
[0211] After establishing M DRBs, the first and second communication devices need to deactivate N DRBs out of the M DRBs, ensuring that at most T DRBs are active. Before deactivating N DRBs, i.e., after both the first and second communication devices have configured M DRBs, the first and second communication devices activate Z DRBs out of the M DRBs (e.g., establish corresponding DRB air interface links based on these Z DRBs), and then deactivate N DRBs from the activated Z DRBs. Here, ZN ≤ T and Z is a positive integer, Z ≤ M.
[0212] Optionally, the Z DRBs include at least one DRB used for transmitting data services.
[0213] Optionally, at least one of the N DRBs may be a DRB used for transmitting data services.
[0214] For example, if Z>T, then the first communication device and the second communication device can first activate T DRBs out of Z DRBs, then activate S1 DRBs out of the activated T DRBs, and then activate S2 DRBs out of the remaining ZT DRBs, such that S1+S2≤T, and so on, until at most T DRBs out of M DRBs are in the active state, i.e. ZN≤T.
[0215] For example, when Z = M, after the activation and deactivation operations described above, N out of the M DRBs are in a deactivated state, and MN out of the DRBs are in an activated state, with 0 ≤ MN ≤ T. For example, if M = 3, then T = 2; if M = 6, then T = 3.
[0216] For example, if MZ > 0, then the M DRBs include N deactivated DRBs, ZN activated DRBs, and MZ inactive DRBs. Subsequently, the first and second communication devices can select K DRBs to activate from the N deactivated DRBs and the MZ inactive DRBs.
[0217] A deactivated DRB indicates that the air interface link established between the first and second communication devices based on the DRB's context has been cancelled and cannot be used for data transmission. However, the first and second communication devices retain the DRB's context (i.e., carrying the configuration parameters of each protocol layer). An active DRB indicates that an air interface link has been established based on the DRB's context and can be used for data transmission. An inactive DRB indicates that the first and second communication devices have stored the DRB's context (i.e., carrying the configuration parameters of each protocol layer), but have not used the DRB's context to establish an air interface link.
[0218] The DRBs in the deactivated state mentioned above can also be called disabled DRBs, and the DRBs in the activated state can also be called enabled DRBs. There is no limitation on this.
[0219] When initially establishing M DRBs, the specific DRBs in the active state and the deactivated state can be configured by the second communication device to the first communication device, or it can be predefined by the protocol, or it can be determined through negotiation between the second communication device and the first communication device. There is no limitation on this.
[0220] In one possible scenario, among the M DRBs, the active DRBs include at least one DRB used for transmitting data services. Thus, when other types of service transmission are required, the first and second communication devices can deactivate the at least one DRB used for transmitting data services and activate the DRB corresponding to the service to be transmitted, so that the number of active DRBs does not exceed T.
[0221] In one possible scenario, the N DRBs include DRBs used for transmitting IMS voice services and / or DRBs used for transmitting IMS voice signaling. That is, when the first communication device transmits through the initially established M DRBs, the DRBs used for transmitting IMS voice services and / or DRBs used for transmitting IMS voice signaling are in an inactive state, preventing the first communication device from transmitting IMS data.
[0222] For example, if M=3, and the three DRBs include one DRB for transmitting data services, one DRB for transmitting IMS voice signaling, and one DRB for transmitting IMS voice services, then the DRB for transmitting data services is active, and the remaining two DRBs are deactivated. Alternatively, the DRB for transmitting data services and the DRB for transmitting IMS voice signaling are active, and the remaining DRB is deactivated.
[0223] Therefore, the first communication device can use the ZN DRBs that are in the active state among the initially established M DRBs to transmit data for the corresponding services, but it cannot use the N DRBs that are in the deactivated state to transmit data for the corresponding services.
[0224] S602, The second communication device sends a first signaling to the first communication device.
[0225] Correspondingly, the first communication device receives the first signaling from the second communication device.
[0226] The first signaling is used to activate K DRBs, where K ≤ T and are positive integers.
[0227] When it is necessary to use a deactivated DRB to transmit data for a corresponding service, the second communication device may proactively or be triggered by the first communication device to send a first signaling message to the first communication device to activate K DRBs selected from N deactivated DRBs and / or MZ inactive DRBs included in the M DRBs. Optionally, the second communication device may also send the first signaling message to the first communication device based on an instruction from the core network; there is no limitation on this.
[0228] The first communication device triggers the second communication device to send a first signaling message to the first communication device. For example, when the first communication device initiates a service corresponding to a DRB that is in a deactivated and / or inactive state, or when the first communication device needs to activate a service corresponding to a DRB that is in a deactivated and / or inactive state based on a paging request from the second communication device, the first communication device can send a second signaling message to the second communication device to trigger the second communication device to send the first signaling message according to the second signaling message. The second signaling message is used to request the activation of K DRBs. That is, the first communication device can send an activation request to the second communication device, thereby enabling the second communication device to send an activation signaling message based on the activation request sent by the first communication device.
[0229] The second signaling includes information for indicating K DRBs, such as K IDs of DRBs, i.e., K DRBIDs.
[0230] In a scenario where N out of the aforementioned M DRBs are in an inactive state, including DRBs used for transmitting IMS voice signaling and / or DRBs used for transmitting IMS voice services, when the first communication device needs to initiate an IMS voice service, or when the first communication device receives a paging request from the second communication device requiring the initiation of an IMS voice service, then K DRBs include those used for transmitting IMS voice signaling and / or DRBs used for transmitting IMS voice services. At this time, the first communication device can send a second signaling message to the second communication device. The second signaling message includes the DRB ID for transmitting IMS voice signaling and the DRB ID for transmitting IMS voice services. Upon receiving the second signaling message, the second communication device sends a first signaling message to the first communication device to activate the DRBs used for transmitting IMS voice signaling and / or DRBs used for transmitting IMS voice services.
[0231] In one possible design, the first signaling can be an RRC message. The first signaling can reuse an existing RRC message defined in the 3GPP protocol, adding an activation indication to it. This activation indication is used to indicate the activation of K DRBs. Alternatively, the first signaling can be a newly defined RRC message for activating DRBs, without limitation.
[0232] Similarly, the second signaling can be an RRC message. The second signaling can reuse the existing RRC message defined in the 3GPP protocol, and add an activation request indication to it. The activation request indication is used to indicate the request to activate K DRBs. Alternatively, the second signaling can be a newly defined RRC message for requesting the activation of DRBs. There are no restrictions on this.
[0233] For example, the first signaling message can be an RRC Reconfiguration message, an RRC Reestablishment message, an RRC Release message, an RRC Resume message, etc., wherein the first signaling message includes an activation indication. The second signaling message can be an RRC Reestablishment Request message, an RRC Resume Request message, etc., wherein the second signaling message includes an activation request indication.
[0234] For example, the aforementioned RRC re-establishment request / RRC re-establishment message is a message used by the first communication device when an RRC connection is lost, such as a radio link failure (RLF). That is, when the first communication device experiences an RRC connection loss, the first signaling can be an RRC re-establishment message, and the second signaling can be an RRC re-establishment request message.
[0235] For example, both the RRC recovery request and RRC recovery message are messages used when the first communication device transitions from the RRC connected state to the RRC inactive state or the RRC suspend state. That is, when the first communication device is in the RRC inactive state or the RRC suspend state, the first signaling can be an RRC recovery message, and the second signaling can be an RRC recovery request message.
[0236] S603, The first communication device activates K DRBs according to the first signaling.
[0237] Correspondingly, the second communication device activates K DRBs.
[0238] After receiving the first signaling, the first communication device can activate K DRBs selected from N deactivated DRBs and / or MZ inactive DRBs included in the M DRBs, thereby establishing an air interface link based on the activated K DRBs to transmit the corresponding service data.
[0239] Before activating K DRBs, if the M DRBs include at least one active DRB (i.e., the M DRBs contain non-zero (ZN≠0) active DRBs, and the number of the K DRBs to be activated plus the number of the ZN≠0 DRBs is greater than T), then the first communication device further activates L active DRBs out of the M DRBs (or ZN DRBs) according to the first signaling, such that at most T DRBs out of the M DRBs are active, where L is a positive integer and L≤MN. It can be understood that the first signaling also has the function of deactivating DRBs. That is, while ensuring that the number of active DRBs does not exceed T, K deactivated and / or inactive DRBs are activated. It can be understood that the K activated DRBs can include both active and inactive DRBs.
[0240] Optionally, the second communication device can send a third signaling message to the first communication device. This third signaling message is used to deactivate L active DRBs, allowing the first communication device to activate DRBs according to the first signaling message and deactivate them according to the second signaling message. This ensures that after the activation and deactivation operations, at most T of the M DRBs are in an active state. For example, the third signaling message can also be an RRC message, designed similarly to the first and second signaling messages described above, and is not limited thereto.
[0241] Correspondingly, after sending the first signaling, the second communication device also activates K DRBs and deactivates L DRBs that are already in the active state.
[0242] In other words, each time the first and second communication devices perform a DRB activation operation, they need to determine whether the number of DRBs in the active state after the DRB activation operation exceeds T. If it does, they also need to perform a deactivation operation on L of the MN DRBs that were in the active state before the DRB activation operation, so as to ensure that after the DRB activation operation, at most T of the M DRBs are still in the active state, and the remaining DRBs are in the deactivation state.
[0243] It should be understood that the DRB deactivation and activation operations when establishing M DRBs in this application embodiment can be considered as initialization / default operations, and the subsequent DRB deactivation and activation operations performed based on the first signaling are referred to as a DRB deactivation and activation operation.
[0244] Therefore, the first communication device can send data to the second communication device through the DRB in the active state, and the second communication device can then send the data to the user plane network element according to the QoS flow corresponding to the DRB in the active state. Conversely, the user plane network element can send the data corresponding to the DRB in the active state to the second communication device, and the second communication device can then send the data to the first communication device through the DRB in the active state.
[0245] For example, such as Figure 7 As shown, M=3, T=2, and the three DRBs include one DRB for transmitting data services, one DRB for transmitting IMS voice signaling, and one DRB for transmitting IMS voice services. They are mapped to QoS flows of 5QI=8 / 9, 5QI=5, and 5QI=1, respectively. Before the DRB activation operation is performed, the DRB for transmitting data services and the DRB for transmitting IMS voice signaling are in an active state, while the DRB for transmitting IMS voice services is in an inactive state. When an IMS voice service needs to be initiated, the first communication device and the second communication device need to activate the DRB for transmitting IMS voice services and deactivate the DRB for transmitting data services to ensure the normal transmission of IMS services.
[0246] Therefore, the first communication device can send SIP signaling to the second communication device through the active DRB used for transmitting IMS voice signaling. The second communication device then sends the SIP signaling to a user plane network element such as the UPF through a QoS flow of 5QI=5, and finally the UPF sends it to the IMS network. Alternatively, the first communication device can send IMS voice data to the second communication device through the active DRB used for transmitting IMS voice services. The second communication device then sends the IMS voice data to a user plane network element such as the UPF through a QoS flow of 5QI=1, and finally the UPF sends it to the IMS network. Of course, the IMS network can also send IMS data to the UPF, and the UPF then sends it to the second communication device through the corresponding QoS flow. Finally, the second communication device uses the corresponding DRB to send it to the first communication device, which will not be elaborated further.
[0247] exist Figure 6In the illustrated communication method, when establishing M DRBs between the first and second communication devices, N DRBs are deactivated, ensuring that at most T DRBs are active. This guarantees that at most T DRBs are used for data transmission of corresponding services between the first and second communication devices. When it is necessary to use deactivated and / or inactive DRBs for data transmission of corresponding services, the first communication device receives a first signaling from the second communication device to activate K DRBs. While ensuring that the number of active DRBs does not exceed T, K DRBs are activated according to the first signaling to perform data transmission of other types of services. M ≥ 3 and is an integer, N, T, and K are positive integers, and N ≤ M, T equals a first threshold, and K ≤ T. Therefore, based on the first communication device supporting only T DRBs for corresponding service transmission, DRBs for transmitting data of more types of services can be established. The activation and deactivation operations enable the first communication device to support data transmission of more types of services.
[0248] The above describes the implementation scheme of the first communication device transmitting more service types of data, such as IMS data, through DRB. The following describes a communication method to solve the technical problem that the first communication device does not support IMS voice service because it only supports two DRBs, and to transmit IMS data through signaling radio bearer (SRB).
[0249] For example, Figure 8 This is a flowchart illustrating another communication method provided in an embodiment of this application. The communication method uses... Figure 3 The communication between the first and second communication devices shown is illustrated using this example.
[0250] like Figure 8 As shown, the communication method includes:
[0251] S801, The first communication device sends a first message to the second communication device.
[0252] Correspondingly, the second communication device receives the first message from the first communication device.
[0253] The first message is used to request the transmission of multiple SIP messages based on SRB0. The first message includes a first NAS message, which in turn includes the first SIP message in the first SIP process.
[0254] Before the first communication device and the second communication device complete the RRC connection, an SRB0 is established. The first communication device can send a first message to request the transmission of an IMS process, i.e., the IMS voice signaling in the first SIP process, i.e., multiple SIP messages (including uplink and downlink), through the SRB0. For example, the first SIP process is a SIP registration process, a SIP session establishment process, etc.
[0255] The first SIP message in the first SIP process is one of multiple uplink SIP messages sent by the first communication device in the first SIP process.
[0256] The first message is used to request the transmission of multiple SIP messages based on SRB0. That is, the first message carries messages transmitted on SRB0, and multiple SIP messages included in a SIP process are exchanged on SRB0. The first communication device uses the NAS message as a container to contain the SIP messages, thereby including the first SIP message in the first NAS message (uplink NAS message), and sending the first NAS message containing the first SIP message in the first message.
[0257] In one possible design, the first message is a message (Msg)3 already defined in the existing 3GPP protocol. The first message also includes first indication information, which is used to indicate that multiple SIP message transmissions based on SRB0 are required. That is, the first communication device transmits SIP messages via Msg3 during random access. This Msg3 is the RRC message carried on SRB0. The protocol-defined Msg3 is reused, and the first indication information is added to indicate that multiple SIP message transmissions based on SRB0 are required.
[0258] In some designs, the first message can also be a newly added type of Msg3 message, such as the RRC_CP (Control Plane) Transmission Request message. The function of this newly added type of Msg3 message is to request the transmission of multiple SIP messages based on SRB0, and there is no limitation on this.
[0259] In one possible implementation, the first communication device may also use a dedicated Msg1 (preamble) to indicate the need for multiple SIP message transmissions based on SRB0, without limitation.
[0260] S802, the second communication device sends a second message to the first communication device.
[0261] Correspondingly, the first communication device receives a second message from the second communication device.
[0262] The second message is used to confirm the transmission of multiple SIP messages based on SRB0. The second message includes a second NAS message, which includes the second SIP message in the first SIP process.
[0263] After receiving the first message, the second communication device will send the first NAS message from the first message to the third communication device, such as the AMF, and send a second message to the first communication device. The second message is used to confirm the transmission of multiple SIP messages based on SRB0; that is, the second message is a message carried on SRB0. The second message can be considered a response to the first message.
[0264] It should be understood that after the third communication device receives the first NAS message, it parses the first SIP message from the first NAS message and sends the first SIP message to the user plane network element such as UPF. Finally, the user plane network element sends the first SIP message to the IMS network element such as P-CSCF network element in the IMS network.
[0265] Correspondingly, the second communication device carries a second NAS message (downlink NAS message) in the second message, which contains the second SIP message in the first SIP process. The second SIP message is one of the multiple downlink SIP messages sent from the IMS network in the first SIP process.
[0266] The second NAS message originates from the aforementioned third communication device. The third communication device receives the second SIP message from the IMS network from the user plane network element, includes the second SIP message in the second NAS message, and sends it to the second communication device. The second communication device then includes the second NAS message in the second message and sends it to the first communication device.
[0267] If the first message is Msg3, which is already defined in the existing 3GPP protocol, the second message can be Msg4, which is also already defined in the existing 3GPP protocol. The second message includes second indication information, which is used to indicate confirmation of the transmission of multiple SIP messages based on SRB0. That is, if the first communication device transmits uplink SIP messages via Msg3 during random access, the second communication device can transmit downlink SIP messages via Msg4. This Msg4 is the RRC message carried on SRB0, which reuses the already defined Msg3 and adds the second indication information to indicate confirmation of the transmission of multiple SIP messages based on SRB0.
[0268] In some designs, similar to the first message mentioned above, the second message can also be a newly added type of Msg4 message, such as the RRC_CP Transmission Response message. The function of this newly added type of Msg4 message is to acknowledge or respond to the transmission of multiple SIP messages based on SRB0, and there is no limitation on this.
[0269] Since the first and second communication devices need to continuously exchange SIP messages based on SRB0 for a SIP process, to avoid wasting air interface resources after the RRC connection is established, or preventing SIP message transmission due to the RRC connection failing to transition to the RRC idle state, the first communication device, upon receiving the second message, does not perform an RRC idle state or RRC connected state transition according to the second message. In other words, the first communication device does not trigger an RRC state change based on the second message, and remains in the state of SRB0 established but not SRB1 established until the SIP process ends, or an instruction is given to end SIP message transmission based on SRB0.
[0270] Therefore, the first communication device and the second communication device repeatedly execute S801 and S802 to exchange different uplink SIP messages and downlink SIP messages in the first SIP process until the first SIP process is completed based on SRB0, or to indicate the end of SIP message transmission based on SRB0.
[0271] In one possible design, the communication method may further include:
[0272] S803, the first communication device sends a third message to the second communication device.
[0273] Correspondingly, the second communication device receives a third message from the first communication device.
[0274] The third message includes a third indication message, which is used to indicate the end of SIP message transmission based on SRB0 or to indicate the end of the first SIP process.
[0275] That is, when the first communication device completes the first SIP process, or when the first communication device needs to end the SIP message transmission based on SRB0, the first communication device can send a third message to the second communication device and carry the first indication information in the third message, for example, the first indication information is an end mark.
[0276] S804, the second communication device sends a fourth message to the first communication device.
[0277] Correspondingly, the first communication device receives a fourth message from the second communication device.
[0278] The fourth message includes a fourth indication message, which is used to indicate that the second communication device switches to RRC idle state or RRC connected state.
[0279] After receiving the third message, the second communication device can send a fourth message based on the third message, and carry a fourth indication message in the fourth message to instruct the first communication device to perform an RRC state transition according to the fourth message. After the first communication device and the second communication device establish an RRC connection, they can then transmit SIP messages based on SRB1.
[0280] In one possible design, the third message is Msg3 and the fourth message is Msg4. That is, during the random access process, when SIP messages are sent based on SRB0, the first and second communication devices continuously interact with Msg3 and Msg4 to complete the transmission of SIP messages.
[0281] In a specific example, taking the first message as Msg3 and the second message as Msg4, as follows: Figure 9 As shown, the first communication device sends Msg1 to the second communication device, and correspondingly, the second communication device sends Msg2 to the first communication device based on Msg1. After receiving Msg2, the first communication device determines that it needs to initiate the first SIP process, and then sends 1st Msg3 (the first Msg3) to the second communication device. This 1st Msg3 includes a NAS message carrying uplink SIP message 1. Correspondingly, the second communication device sends 1st Msg4 to the first communication device. This 1st Msg4 includes a NAS message carrying downlink SIP message 1. For a period of time, the first and second communication devices continuously exchange Msg3 and Msg4 until the first communication device sends Nth Msg3 (the Nth Msg3, where N is a positive integer) carrying a NAS message containing uplink SIP message N, and then receives Nth Msg4 carrying a NAS message containing downlink SIP message N, thus completing the first SIP process. Then, the first communication device sends N+1th Msg3 carrying an end indication to the second communication device. Correspondingly, after receiving N+1th Msg3 carrying an end indication, the second communication device sends N+1th Msg4 carrying an RRC state transition indication to the first communication device, so as to instruct the first communication device to complete the RRC connection and transition from the RRC idle state to the RRC connected state.
[0282] exist Figure 8In the illustrated communication method, the first communication device sends a first message to the second communication device carrying a NAS message containing uplink SIP messages, and instructs the second communication device to request the transmission of multiple SIP messages based on SRB0. This allows the second communication device to send a second message to the first communication device carrying a NAS message containing downlink SIP messages, and to confirm the transmission of multiple SIP messages based on SRB0. Thus, the first communication device, supporting only two DRBs, can complete IMS voice signaling transmission by transmitting NAS messages based on SRB0, and by transmitting IMS voice signaling through the control plane, IMS voice services can be implemented.
[0283] For example, the first communication device transmits IMS voice signaling to the second communication device via SRB0, and then the second communication device sends it to the third communication device via the N2 interface, i.e., through the control plane. Meanwhile, the IMS voice service and data service are transmitted through the user plane via the two DRBs supported by the first communication device.
[0284] The above Figure 8 The communication method shown is based on SRB0 to support the implementation of IMS voice services. This application embodiment also provides a communication method based on SRB1 to support the implementation of IMS voice services.
[0285] For example, Figure 10 This is a flowchart illustrating another communication method provided in an embodiment of this application. The communication method uses... Figure 4 The communication between the first and third communication devices shown is illustrated using this example.
[0286] like Figure 10 As shown, the communication method includes:
[0287] S1001. After the first communication device and the second communication device establish an RRC connection, a first NAS message is generated.
[0288] The first NAS message includes the first IMS data after header compression, or the first NAS message includes the first IMS data, which is IMS voice signaling data or IMS voice service data.
[0289] After the first communication device establishes an RRC connection with the second communication device, an SRB1 is established between the first communication device and the second communication device. The first communication device can send a NAS message containing IMS data through the SRB1, that is, generate a first NAS message (uplink NAS message) including header-compressed first IMS data or header-uncompressed first IMS data. The first IMS data is the uplink IMS data, which is generated by the application layer of the first communication device.
[0290] The first IMS data after header compression refers to the data whose header protocol of the data packet containing the first IMS data is compressed. The header-compressed data includes IP protocol encapsulation header, user datagram protocol (UDP) encapsulation header, etc. For example, robust header compression (ROHC) of the first IMS data can be performed by the application layer of the first communication device, which then fills the first NAS message with the header compression of the first IMS data. Alternatively, the application layer of the first communication device can send the first IMS data to the NAS layer, and then the NAS layer performs header compression on the first IMS data. There is no limitation on which method is used.
[0291] The first NAS message includes the first IMS data, meaning the first IMS data is directly filled into the first NAS message without needing to be encapsulated by the transport layer and network layer (i.e., transmission control protocol (TCP) / IP, UDP / IP). The first IMS data with header compression, on the other hand, is encapsulated by the transport layer and network layer and then compressed with a header.
[0292] If the first NAS message includes header-compressed first IMS data, optionally, the first NAS message may also include header compression configuration information, such as header compression algorithm and header compression protocol. If there is default header compression configuration information between the first communication device and the third communication device, the first NAS message may not include header compression configuration information.
[0293] The configuration information for header compression can be predefined or pre-configured in the first communication device, or it can be obtained by the first communication device through negotiation between the second and third communication devices, without any limitation.
[0294] Regarding the negotiation method, in one possible design, the first communication device sends a first message to the second communication device, the first message including desired header compression configuration information. Correspondingly, the second communication device sends the desired header compression configuration information to the third communication device, and then receives confirmed header compression configuration information from the third communication device. It then sends a second message to the first communication device, the second message including the confirmed header compression configuration information. Subsequently, the first communication device receives the second message from the second communication device and obtains the confirmed header compression configuration information based on the second message. In this design, the desired header compression configuration information can be carried in the uplink NAS message, i.e., the first message includes the uplink NAS message containing the desired header compression configuration information. Similarly, the confirmed header compression configuration information can be carried in the downlink NAS message, i.e., the second message includes the downlink NAS message containing the confirmed header compression configuration information.
[0295] Optionally, the first message is Msg3 and the second message is Msg4. That is, during the random access process, the first communication device can negotiate the header compression configuration through the NAS message carried by Msg3 / 4. After SRB1 is established, the IMS data in the NAS message transmitted on SRB1 will be compressed and decompressed based on the negotiated header compression configuration.
[0296] Optionally, the first message may also include first IMS data without header compression, and the second message may also include second IMS data without header compression. The second IMS data originates from the IMS network element, meaning it is sent from the IMS network to the user plane network element, and then from the user plane network element to the third communication device. In other words, when negotiating header compression configuration via the NAS message carried by Msg3 / 4, Msg3 / 4 can exchange uplink IMS data without header compression by the first communication device and downlink IMS data without header compression by the third communication device.
[0297] like Figure 11As shown, the first communication device is in RRC idle state and initiates a random access procedure. After interacting with the second communication device via Msg1 and Msg2, when sending Msg3 to the second communication device, Msg3 carries a NAS message containing the desired header compression configuration information and uplink IMS data. Correspondingly, after receiving Msg3, the second communication device sends the NAS message containing the desired header compression configuration information and uplink IMS data to the third communication device, thereby enabling the third communication device to determine the header compression configuration information. The first communication device receives a NAS message containing the determined header compression configuration information and downlink IMS data from the third communication device, and then sends Msg4 to the first communication device, carrying a NAS message containing the determined header compression configuration information and downlink IMS data, thus completing the header compression configuration negotiation.
[0298] S1002, The first communication device sends a first NAS message to the third communication device.
[0299] Correspondingly, the third communication device receives the first NAS message from the first communication device.
[0300] The first communication device sends a first NAS message to the third communication device via the second communication device. Specifically, the first communication device sends an RRC message to the second communication device via SRB1. The RRC message includes the first NAS message. Correspondingly, the second communication device receives the RRC message from the first communication device via SRB1 and sends the first NAS message from the RRC message to the third communication device. For example, the RRC message may be an RRC reconfiguration request message.
[0301] For example, the bearer relationship between the header-compressed first IMS data / first IMS data, the first NAS message, and the RRC message is as follows: Figure 12 As shown, the first NAS message includes header-compressed first IMS data / first IMS data and dedicated info NAS, and the RRC message includes dedicated control channel (DCCH) service data unit (SDU) for RRC and the first NAS message.
[0302] For example, in NAS messages or NAS transport messages (including uplink and downlink), the configuration information for header compression is indicated by an information element (IE) as shown in Table 1 below, which includes the type of header compression.
[0303] Table 1
[0304]
[0305] Correspondingly, after receiving the first NAS message, if the first NAS message includes header-compressed first IMS data, the third communication device decompresses the header-compressed configuration information to obtain the first IMS data, and sends the first IMS data to the user plane network element according to the compressed IP address, and then the user plane network element sends it to the IMS network element.
[0306] When the first NAS message includes first IMS data, the first NAS message may also include the type of the first IMS data, which may include IMS signaling service data and IMS voice service data. For example, in a NAS message or NAS transport message (including uplink and downlink), the type of IMS data is indicated by the IE shown in Table 2 below, which indicates whether the type of IMS data is SIP-based IMS signaling service data or RTP-based IMS voice service data.
[0307] Table 2
[0308]
[0309] Therefore, the third communication device can send the first IMS data to the corresponding IMS network element according to the type of the first IMS data, based on the connection mapping relationship between the first and third communication devices and the connection mapping relationship between the third communication device and the IMS network element. Specifically, the connection mapping relationship between the first and third communication devices and the connection mapping relationship between the third communication device and the IMS network element can be established by the first communication device requesting the transmission of NAS-based voice signaling / service data from the third communication device through processes such as registration and service request. During this process, the third communication device registers its context (e.g., the first communication device's identifier) with the IMS, establishes a mapping relationship between the first-communication-third-communication-device connection and the third-communication-IMS connection, and stores it locally.
[0310] The above mainly describes the process of uplink IMS data transmission via NAS messages. Of course, the first communication device can also receive downlink IMS data transmitted via NAS messages. That is, the first communication device can also receive a second NAS message (downlink NAS message), which includes header-compressed second IMS data or the second IMS data itself, originating from the IMS network element. In other words, after the third communication device receives downlink IMS data from the IMS network element via the user plane network element, it can also perform operations similar to those of the first communication device. For example, it can header-compress the second IMS data and include it in the second NAS message, or directly include the second IMS data in the second NAS message, send the second NAS message to the second communication device, and then the second communication device includes the second NAS message in an RRC message, which is then transmitted to the first communication device on SRB1. Thus, the first communication device can obtain the second IMS data from the RRC message. If the second NAS message contains header-compressed second IMS data, the first communication device also needs to decompress the header-compressed second IMS data according to the header compression configuration information to obtain the IMS data. The transmission of downlink IMS data is similar to that of uplink IMS data, so it will not be described in detail here.
[0311] In some possible implementations, after the third communication device receives uplink IMS data from the first communication device, it can add transport layer and network layer (i.e., TCP / IP, UDP / IP) encapsulation to the uplink IMS data before sending it to the IMS network. Correspondingly, after the third communication device receives downlink IMS data from the IMS network, it can remove the transport layer and network layer (i.e., TCP / IP, UDP / IP) encapsulation before sending it to the first communication device via NAS.
[0312] If the above process is implemented by DRB, the PDCP layer in DRB removes the header compression function because there are no transport layer and network layer packet headers.
[0313] exist Figure 10 In the illustrated communication method, the first communication device can either compress the IMS data header and stuff it into the NAS message, or stuff it directly into the NAS message without header compression. It then sends the NAS message carrying the IMS data based on SRB1 to the third communication device, which then transmits the IMS data to the IMS network via the control plane. Thus, by supporting only two DRBs, the first communication device can transmit IMS voice signaling data or IMS voice service data based on SRB1 to complete the transmission of NAS messages, and transmit IMS voice signaling data or IMS voice service data via the control plane, thereby enabling IMS voice services.
[0314] For example, Figure 13 This application provides a schematic diagram of a protocol stack for transmitting IMS data via NAS messages between a first communication device, a second communication device, a third communication device, and an IMS network element, applicable to the above-mentioned... Figure 8 and Figure 10 The communication method shown includes the transmission of NAS messages containing IMS data. For example... Figure 13 As shown, the control plane protocol stacks corresponding to the first and second communication devices, from top to bottom, include the RRC layer, PDCP layer, RLC layer, medium / media access control (MAC) layer, and physical layer (PHY). The first communication device also has a corresponding SIP / RTP layer with the IMS network element, used to generate and process IMS voice signaling data (SIP signaling) / IMS voice service data, and a corresponding NAS layer with the third communication device. Therefore, during uplink IMS data transmission, the SIP / RTP layer in the first communication device generates uplink IMS data and sends it to the NAS layer. The NAS layer generates a NAS message containing the uplink IMS data. The first communication device sends this NAS message, containing the uplink IMS data, in an RRC message to the second communication device. The second communication device then sends the NAS message containing the uplink IMS data to the third communication device via an interface. The third communication device parses the NAS message according to the NAS layer to obtain the uplink IMS data and sends it to the IMS network element. The transmission of downlink IMS data is similar to that of uplink IMS data transmission, so it will not be described in detail here.
[0315] exist Figure 8 In the communication method shown, the first communication device and the second communication device transmit IMS data via SRB0, while Figure 10 In the illustrated communication method, the first communication device and the second communication device transmit IMS data via SRB1. Alternatively, the first and second communication devices can also transmit IMS data via SRB1bis, that is, by transmitting NAS messages containing IMS data based on SRB1bis, the transmission of IMS data is realized from the control plane, thereby achieving IMS voice service. The implementation process of transmitting IMS data based on SRB1bis is similar to that based on SRB1, and will not be described in detail here.
[0316] It should be understood that the embodiments of this application are mainly illustrated using SIP signaling as an example of IMS voice signaling. IMS voice signaling related to IMS voice services can also be other types of signaling, and there is no limitation on this.
[0317] It is understood that, in the above embodiments, the methods and / or steps implemented by the first communication device can also be implemented by components (e.g., processors, chips, chip systems, circuits, logic modules, or software) that can be used in the first communication device; the methods and / or steps implemented by the second communication device can also be implemented by components (e.g., processors, chips, chip systems, circuits, logic modules, or software) that can be used in the second communication device; and the methods and / or steps implemented by the third communication device can also be implemented by components (e.g., processors, chips, chip systems, circuits, logic modules, or software) that can be used in the third communication device.
[0318] The foregoing mainly describes the solutions provided in this application. Accordingly, this application also provides a communication device for implementing various methods in the above method embodiments. This communication device can be a first communication device in the above method embodiments, or a device containing a first communication device, or a component usable in the first communication device, such as a chip or chip system. Alternatively, the communication device can be a second communication device in the above method embodiments, or a device containing a second communication device, or a component usable in the second communication device, such as a chip or chip system. Alternatively, the communication device can be a third communication device in the above method embodiments, or a device containing a third communication device, or a component usable in the third communication device, such as a chip or chip system.
[0319] It is understood that, in order to achieve the aforementioned functions, the communication device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0320] This application embodiment can divide the communication device into functional modules according to the above method embodiment. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.
[0321] Taking the first, second, or third communication device in the above method embodiments as an example, Figure 14 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application. Figure 14 As shown, Figure 14 As shown, the communication device 1400 includes a processing module 1401 and a transceiver module 1402. The processing module 1401 is used to execute the processing functions of the first, second, or third communication device in the above method embodiments. The transceiver module 1402 is used to execute the transceiver functions of the first, second, or third communication device in the above method embodiments.
[0322] All relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.
[0323] In one possible design, in this embodiment of the application, the transceiver module 1402 may include a receiving module and a sending module. Figure 14 (Not shown in the image). The transmitting module and the receiving module are used to implement the transmitting and receiving functions of the communication device 1400, respectively.
[0324] In one possible design, the communication device 1400 may further include a storage module. Figure 14 (Not shown in the image), this storage module stores programs or instructions. When the processing module 1401 executes the program or instructions, it enables the communication device 1400 to perform operations. Figure 6 , Figure 8 The function of the first or second communication device in any of the methods shown, or enabling the communication device 1400 to perform... Figure 10 The method shown illustrates the function of the first or third communication device.
[0325] In some embodiments, the processing module 1401 involved in the communication device 1400 may be implemented by a processor or processor-related circuit components, and may be a processor or processing unit; the transceiver module 1402 may be implemented by a transceiver or transceiver-related circuit components, and may be a transceiver or transceiver unit.
[0326] For example, Figure 15 This is a schematic diagram of another communication device provided in an embodiment of this application. The communication device can be the first, second, or third communication device described in the above method embodiments, or it can be a chip (system) or other component or assembly that can be disposed in the second or third communication device. Figure 15As shown, the communication device 1500 may include a processor 1501, a bus 1502, a communication interface 1503, and a memory 1504. The processor 1501, the memory 1504, and the communication interface 1503 communicate with each other via the bus 1502. It should be understood that this application does not limit the number of processors and memories in the communication device 1500.
[0327] Bus 1502 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be divided into address buses, data buses, control buses, etc. For ease of representation, Figure 15 The bus 1502 may be represented by a single line, but this does not mean that there is only one bus or one type of bus. The bus 1502 may include a path for transmitting information between various components of the communication device 1500 (e.g., memory 1504, processor 1501, communication interface 1503).
[0328] Processor 1501 may include any one or more of the following processors: central processing unit (CPU), graphics processing unit (GPU), microprocessor (MP), or digital signal processing (DSP).
[0329] Memory 1504 may include volatile memory, such as random access memory (RAM). Processor 1501 may also include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid state drive (SSD).
[0330] The communication interface 1503 uses transceiver modules such as, but not limited to, network interface cards and transceivers to enable communication between the communication device 1500 and other devices or communication networks.
[0331] The memory 1504 stores executable program code, and the processor 1501 executes the executable program code to implement the functions of the first communication device, the second communication device, or the third communication device in the aforementioned method embodiments, respectively. That is, the memory 1504 stores instructions for executing the aforementioned communication methods.
[0332] In another aspect, embodiments of this application also provide a computer program product containing instructions, including computer program code, which, when run on a communication device, enables the communication device to execute the methods described in any of the above embodiments.
[0333] Furthermore, embodiments of this application also provide a computer-readable storage medium. This computer-readable storage medium stores a computer program or instructions that, when executed on a communication device, enable the communication device to perform the methods described in any of the above embodiments.
[0334] In another aspect, embodiments of this application also provide a communication system, including a first communication device and a second communication device for performing the above method embodiments.
[0335] In another aspect, embodiments of this application also provide a communication system, including a first communication device and a third communication device for performing the above method embodiments.
[0336] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software programs, implementation can be, in whole or in part, in the form of a computer program product. This computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or 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. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device containing one or more servers, data centers, etc., that can be integrated with the medium. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video disks, DVDs), or semiconductor media (e.g., SSDs), etc.
[0337] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0338] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.
[0339] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.
[0340] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0341] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.
[0342] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, a server, or an access network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.
[0343] Although this application has been described herein in conjunction with various embodiments, those skilled in the art, by reviewing the accompanying drawings, the disclosure, and the appended claims, will understand and implement other variations of the disclosed embodiments in carrying out the claimed application. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude multiple instances. A single processor or other unit can implement several functions listed in the claims. While different dependent claims may recite certain measures, this does not mean that these measures cannot be combined to produce good results.
[0344] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the spirit and scope of this application. Accordingly, this specification and drawings are merely exemplary illustrations of this application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from the spirit and scope of this application. Thus, if such modifications and modifications of this application fall within the scope of the claims of this application and their equivalents, this application is also intended to include such modifications and modifications.
Claims
1. A communication method, characterized in that, The method, using a first communication device, includes: Establish M data radio bearers (DRBs) with the second communication device; Deactivate N DRBs out of the M DRBs so that at most T DRBs out of the M DRBs are in an active state, where M ≥ 3 and is an integer, N is a positive integer N ≤ M, and T is equal to the first threshold. Receive a first signaling from the second communication device, the first signaling being used to activate K DRBs, where K ≤ T and is a positive integer; The K DRBs are activated according to the first signaling.
2. The method according to claim 1, characterized in that, The N DRBs include at least one DRB used for transmitting data services.
3. The method according to claim 2, characterized in that, Before deactivating the N DRBs, the method further includes: Activate Z DRBs out of the M DRBs, where the Z DRBs include at least one DRB for transmitting data services, Z≤M, ZN≤T, and Z is a positive integer.
4. The method according to any one of claims 1-3, characterized in that, When the M DRBs include at least one DRB in an active state, the method further includes: According to the first signaling, activate L of the M DRBs that are in the active state, so that at most T of the M DRBs are in the active state, where L is a positive integer.
5. The method according to any one of claims 1-4, characterized in that, The method further includes: Send a second signaling message to the second communication device, the second signaling message being used to request the activation of the K DRBs.
6. The method according to claim 5, characterized in that, When the first communication device is in the Radio Resource Control (RRC) inactive state or the RRC paused state, the second signaling is an RRC recovery request.
7. The method according to claim 5 or 6, characterized in that, The second signaling includes information for indicating the K DRBs.
8. The method according to any one of claims 1-7, characterized in that, The first signaling is an RRC message.
9. The method according to any one of claims 1-8, characterized in that, The N DRBs include at least one DRB for transmitting data services, one DRB for transmitting Internet Protocol Multimedia Subsystem (IMS) voice signaling, and one DRB for transmitting IMS voice services.
10. The method according to any one of claims 1-9, characterized in that, The first threshold is related to the capability of the first communication device.
11. The method according to any one of claims 1-10, characterized in that, The K DRBs include DRBs used for transmitting the IMS voice service and / or DRBs used for transmitting IMS voice signaling.
12. A communication method, characterized in that, Applied to a second communication device, the method includes: Establish M DRBs with the first communication device; Deactivate N DRBs out of the M DRBs so that at most T DRBs out of the M DRBs are in an active state, where M ≥ 3 and is an integer, N is a positive integer and N ≤ M, and T is equal to the first threshold. Send a first signaling message to the first communication device, the first signaling message being used to activate K DRBs, where K≤T and are positive integers; Activate the K DRBs.
13. The method according to claim 12, characterized in that, The N DRBs include at least one DRB used for transmitting data services.
14. The method according to claim 13, characterized in that, Before deactivating the N DRBs, the method further includes: Activate Z DRBs out of the M DRBs, where the Z DRBs include at least one DRB for transmitting data services, Z≤M, ZN≤T, and Z is a positive integer.
15. The method according to any one of claims 12-14, characterized in that, When the M DRBs include at least one DRB in an active state, the method further includes: Deactivate L of the M DRBs that are in an active state, such that at most T of the M DRBs are in an active state, where L is a positive integer.
16. The method according to any one of claims 12-15, characterized in that, The method further includes: Receive a second signaling from the first communication device, the second signaling being used to request the activation of the K DRBs.
17. The method according to claim 16, characterized in that, When the first communication device is in an RRC inactive state or an RRC paused state, the second signaling is an RRC recovery request.
18. The method according to claim 16 or 17, characterized in that, The second signaling includes information for indicating that the K are in the DRB.
19. The method according to any one of claims 12-18, characterized in that, The first signaling is an RRC message.
20. The method according to any one of claims 12-19, characterized in that, The M DRBs include at least one DRB for transmitting data services, one DRB for transmitting IMS voice signaling, and one DRB for transmitting IMS voice services.
21. The method according to any one of claims 12-20, characterized in that, The first threshold is related to the capability of the first communication device.
22. The method according to any one of claims 12-21, characterized in that, The K DRBs include DRBs used for transmitting the IMS voice service and / or DRBs used for transmitting IMS voice signaling.
23. A communication device, characterized in that, include: A module for performing the method as described in any one of claims 1-11, or a module for performing the method as described in any one of claims 12-22.
24. A communication device, characterized in that, include: processor; The processor is configured to run computer programs or instructions to enable the implementation of the method as described in any one of claims 1-11, or to enable the implementation of the method as described in any one of claims 12-22.
25. A communication chip, characterized in that, The chip stores instructions that, when the chip is running on a communication device, cause the method as described in any one of claims 1-11 to be implemented, or cause the method as described in any one of claims 12-22 to be implemented.
26. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or instructions that, when executed by a communication device, implement the method as described in any one of claims 1-11, or the method as described in any one of claims 12-22.
27. A computer program product, characterized in that, It includes computer program code, which, when run on a communication device, implements the method as described in any one of claims 1-11, or the communication device implements the method as described in any one of claims 12-22.