Service Collision Handling Method and Apparatus, and Terminal

Abstract

A service collision handling method includes: in a case that multiple services of different types are initiating connection setup, determining, by a terminal, a connection setup mode according to a first rule, where the first rule is configured by a network-side device or defined by a protocol, and the first rule includes at least one of the following: using a connection setup cause value of a first specified service as a cause value of the connection setup mode; or using a connection setup procedure corresponding to a second specified service.

Claims

1. A service collision handling method, comprising: in a case that multiple services of different types are initiating connection setup, determining, by a terminal, a connection setup mode according to a first rule; wherein the first rule is configured by a network-side device or defined by a protocol, and the first rule comprises at least one of following: using a connection setup cause value of a first specified service as a cause value of the connection setup mode; or using a connection setup procedure corresponding to a second specified service.

2. The service collision handling method according to claim 1, further comprising: obtaining, by the terminal, configuration information for a direct data transfer mode; wherein the configuration information is configured by the network-side device or defined by a protocol, and the configuration information comprises at least one of following: a procedure of direct data transfer; or service indication information for using direct data transfer.

3. The service collision handling method according to claim 2, wherein the procedure of the direct data transfer comprises at least one of following: a direct data transmission procedure; or a direct data reception procedure.

4. The service collision handling method according to claim 3, wherein the direct data transmission procedure comprises at least one of following: transmitting data in Msg3 of a 4-step random access procedure; transmitting data in MsgA of a 2-step random access procedure; or transmitting data on a dedicated physical uplink shared channel resource configured by the network-side device.

5. The service collision handling method according to claim 3, wherein the direct data reception procedure comprises at least one of following: receiving data in Msg4 of a 4-step random access procedure; receiving data in MsgB of a 2-step random access procedure; or receiving data on a downlink resource corresponding to a dedicated uplink resource configured by the network-side device.

6. The service collision handling method according to claim 2, wherein the service indication information for using the direct data transfer comprises at least one of following: a bearer type for using direct data transfer; a bearer identifier for using direct data transfer; a service access category for using direct data transfer; a service access class for using direct data transfer; or a service type for using direct data transfer.

7. The service collision handling method according to claim 1, wherein a connection setup cause value of the first specified service is different from a service type corresponding to service data actually transferred.

8. The service collision handling method according to claim 3, wherein the connection setup procedure comprises at least one of following: a direct data transmission procedure; a direct data reception procedure; or a first connection setup procedure, in which no data is transmitted and only radio resource control signaling is transmitted.

9. The service collision handling method according to claim 1, wherein the first specified service and/or the second specified service is a highest-priority service in the multiple services of different types.

10. The service collision handling method according to claim 9, wherein a priority ordering rule for services comprises any one of following: an emergency service having a higher priority than a mobile originated data service; a high-priority access service having a higher priority than the mobile originated data service; a service that triggers a first connection setup procedure having a higher priority than a service that triggers a procedure of direct data transfer, wherein in the first connection setup procedure, no data is transmitted and only radio resource control signaling is transmitted; the service that triggers the first connection setup procedure having a lower priority than the service that triggers the procedure of direct data transfer; a mobile terminated service having a higher priority than a mobile originated service; a service that triggers a direct data transmission procedure having a higher priority than a service that triggers a direct data reception procedure; the service that triggers the direct data transmission procedure having a lower priority than the service that triggers the direct data reception procedure; a paging area update service having a higher priority than the service that triggers a procedure of direct data transfer; the paging area update service having a lower priority than the service that triggers the procedure of direct data transfer; the paging area update service having a higher priority than the mobile originated service; the paging area update service having a lower priority than the mobile originated service; the paging area update service having a higher priority than the mobile terminated service; and the paging area update service having a lower priority than the mobile terminated service.

11. A terminal, comprising a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or the instructions, when executed by the processor, causes the terminal to perform: in a case that multiple services of different types are initiating connection setup, determining, by a terminal, a connection setup mode according to a first rule; wherein the first rule is configured by a network-side device or defined by a protocol, and the first rule comprises at least one of following: using a connection setup cause value of a first specified service as a cause value of the connection setup mode; or using a connection setup procedure corresponding to a second specified service.

12. The terminal according to claim 11, wherein the program or the instruction, when executed by the processor, causes the terminal to further perform: obtaining, by the terminal, configuration information for a direct data transfer mode; wherein the configuration information is configured by the network-side device or defined by a protocol, and the configuration information comprises at least one of following: a procedure of direct data transfer; or service indication information for using direct data transfer.

13. The terminal according to claim 12, wherein the procedure of the direct data transfer comprises at least one of following: a direct data transmission procedure; or a direct data reception procedure; and/or the service indication information for using the direct data transfer comprises at least one of following: a bearer type for using direct data transfer; a bearer identifier for using direct data transfer; a service access category for using direct data transfer; a service access class for using direct data transfer; or a service type for using direct data transfer.

14. The terminal according to claim 13, wherein the direct data transmission procedure comprises at least one of following: transmitting data in Msg3 of a 4-step random access procedure; transmitting data in MsgA of a 2-step random access procedure; or transmitting data on a dedicated physical uplink shared channel resource configured by the network-side device; and/or the direct data reception procedure comprises at least one of following: receiving data in Msg4 of a 4-step random access procedure; receiving data in MsgB of a 2-step random access procedure; or receiving data on a downlink resource corresponding to a dedicated uplink resource configured by the network-side device.

15. The terminal according to claim 11, wherein a connection setup cause value of the first specified service is different from a service type corresponding to service data actually transferred.

16. The terminal according to claim 13, wherein the connection setup procedure comprises at least one of following: a direct data transmission procedure; a direct data reception procedure; or a first connection setup procedure, in which no data is transmitted and only radio resource control signaling is transmitted.

17. The terminal according to claim 11, wherein the first specified service and/or the second specified service is a highest-priority service in the multiple services of different types.

18. The terminal according to claim 17, wherein a priority ordering rule for services comprises any one of following: an emergency service having a higher priority than a mobile originated data service; a high-priority access service having a higher priority than the mobile originated data service; a service that triggers a first connection setup procedure having a higher priority than a service that triggers a procedure of direct data transfer, wherein in the first connection setup procedure, no data is transmitted and only radio resource control signaling is transmitted; the service that triggers the first connection setup procedure having a lower priority than the service that triggers the procedure of direct data transfer; a mobile terminated service having a higher priority than a mobile originated service; a service that triggers a direct data transmission procedure having a higher priority than a service that triggers a direct data reception procedure; the service that triggers the direct data transmission procedure having a lower priority than the service that triggers the direct data reception procedure; a paging area update service having a higher priority than the service that triggers a procedure of direct data transfer; the paging area update service having a lower priority than the service that triggers the procedure of direct data transfer; the paging area update service having a higher priority than the mobile originated service; the paging area update service having a lower priority than the mobile originated service; the paging area update service having a higher priority than the mobile terminated service; and the paging area update service having a lower priority than the mobile terminated service.

19. A non-transitory readable storage medium, wherein the non-transitory readable storage medium stores a program or instructions, and the program or the instructions, when executed by a processor of a terminal, causes the processor of the terminal to perform: in a case that multiple services of different types are initiating connection setup, determining, by a terminal, a connection setup mode according to a first rule; wherein the first rule is configured by a network-side device or defined by a protocol, and the first rule comprises at least one of following: using a connection setup cause value of a first specified service as a cause value of the connection setup mode; or using a connection setup procedure corresponding to a second specified service.

20. A computer software product, wherein the computer software product is stored in a non-volatile storage medium, and the software product is configured to be executed by at least one processor of a terminal so as to implement steps of the method according to claim 1.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0017] To describe the technical solutions in the embodiments of this disclosure more clearly, the following briefly describes the accompanying drawings required for describing the embodiments of this disclosure. Apparently, the accompanying drawings in the following description show merely some embodiments of this disclosure, and persons of ordinary skill in the art may still derive other drawings from these accompanying drawings.

[0018] FIG. 1 is a schematic diagram of a wireless communications system;

[0019] FIG. 2 is a schematic flowchart of a service collision handling method according to an embodiment of this disclosure;

[0020] FIG. 3 is a schematic diagram of a structure of a service collision handling apparatus according to an embodiment of this disclosure; and

[0021] FIG. 4 is a schematic diagram of composition of a terminal according to an embodiment of this disclosure.

DESCRIPTION OF THE INVENTION

[0022] The following clearly describes the technical solutions in the embodiments of this disclosure with reference to the accompanying drawings in the embodiments of this disclosure. Apparently, the described embodiments are some but not all of the embodiments of this disclosure. All other embodiments obtained by persons of ordinary skill in the art based on the embodiments of this disclosure shall fall within the protection scope of this disclosure.

[0023] The terms “first”, “second”, and the like in this specification and claims of this disclosure are used to distinguish between similar objects rather than to describe a specific order or sequence. It should be understood that the data used in this way is interchangeable in appropriate circumstances such that the embodiments of this disclosure can be implemented in other orders than the order illustrated or described herein. In addition, “and/or” in the specification and claims represents at least one of connected objects, and the character “/” generally indicates that the associated objects have an “or” relationship.

[0024] The technologies described herein are not limited to long term evolution (LTE)/LTE-Advanced (LTE-A) systems, but may also be used in various wireless communications systems, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), single-carrier frequency division multiple access (SC-FDMA), and other systems. The terms “system” and “network” are usually used interchangeably. The CDMA system may implement radio technologies such as CDMA2000 and universal terrestrial radio access (UTRA). UTRA includes wideband CDMA (WCDMA) and other CDMA variants. A TDMA system may implement radio technologies such as the global system for mobile communications (GSM). The OFDMA system can implement radio technologies such as ultra mobile broadband (UMB), evolved UTRA (Evolution-UTRA, E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, and Flash-OFDM. UTRA and E-UTRA are parts of the universal mobile telecommunications system (UMTS). LTE and more advanced LTE (for example, LTE-A) are new UMTS releases using E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named “3rd Generation Partnership Project” (3GPP). CDMA2000 and UMB are described in documents from an organization named “3rd Generation Partnership Project 2” (3GPP2). The technologies described herein are applicable not only to the above-mentioned systems and radio technologies, but also to other systems and radio technologies. However, in the following descriptions, a new radio (NR) system is described for illustrative purposes, and NR terms are used in most of the following descriptions, although these technologies may also be applied to other applications than the NR system application.

[0025] Examples provided in the following description are not intended to limit the scope, applicability, or configuration described in the claims. Functions and arrangements of discussed elements may be changed without departing from the spirit and scope of this disclosure. Various examples may be omitted or replaced or various procedures or components may be added, as appropriate. For example, the described method may be performed in an order different from the order described, and steps may be added, omitted, or combined. In addition, features described with reference to some examples may be combined in other examples.

[0026] Refer to FIG. 1. FIG. 1 is a block diagram of a wireless communications system to which embodiments of this disclosure may be applied. The wireless communications system includes a terminal 11 and a network-side device 12. The terminal 11 may also be referred to as a terminal device or user equipment (UE). The terminal 11 may be a terminal side device such as a mobile phone, a tablet personal computer, a laptop computer, a personal digital assistant (PDA), a mobile internet device (MID), a wearable device, or an in-vehicle device. It should be noted that the terminal 11 is not limited to any type in the embodiments of this disclosure. The network-side device 12 may be a base station or a core network, where the base station may be a base station of 5G (5.sup.th Generation) or a later release (for example, gNB or 5G NR NB), or a base station in other communications systems (for example, eNB, WLAN (wireless local area network) access point, or other access points), or a location server (for example, E-SMLC (Evolved Serving Mobile Location Centre) or LMF (Location Manager Function)). The base station may be referred to as a NodeB, an evolved NodeB, an access point, a base transceiver station (BTS), a radio base station, a radio transceiver, a basic service set (BSS), an extended service set (ESS), a Node B, an evolved node B (evolved Node B, eNB), a home NodeB, a home evolved NodeB, a WLAN access point, a wireless fidelity (Wi-Fi) node, or other appropriate terms in the art in discussion. As long as the same technical effect is achieved, the base station is not limited to any technical term. It should be noted that only the base station in the NR system is taken as an example in the embodiments of this disclosure, but the type of base station and communications system are not limited in the embodiments of this disclosure.

[0027] In the related art, when a UE service capable of triggering a direct data transmission procedure has data arriving, the UE is possibly also having other services with arriving data which require a connection resume procedure. In this case, which service is used by the UE to initiate connection setup so as to allow faster setup of connection for a higher-priority service is a problem that needs to be solved.

[0028] An embodiment of this disclosure provides a service collision handling method. As shown in FIG. 2, the method includes the following steps.

[0029] Step 101: in a case that multiple services of different types are initiating connection setup, a terminal determines a connection setup mode according to a first rule, where the first rule is configured by a network-side device or defined by a protocol, and the first rule includes at least one of the following:

[0030] using a connection setup cause value of a first specified service as a cause value of the connection setup mode; or

[0031] using a connection setup procedure corresponding to a second specified service.

[0032] In this embodiment of this disclosure, when multiple services of different types are initiating connection setup, the terminal can determine the connection mode according to the first rule configured by the network-side device or defined by a protocol. For example, the terminal can use a connection setup procedure corresponding to a higher-priority service to perform connection setup, thus allowing faster setup of a connection for the higher-priority service, and reducing service connection setup latency or service data transmission latency.

[0033] The connection setup includes initial connection setup and connection resume after the initial connection setup, meaning that the connection setup mode actually includes an initial connection setup mode and a connection resume mode.

[0034] In some embodiments, the first specified service and/or the second specified service is a highest-priority service in the multiple services of different types. In this way, the terminal can use a connection setup procedure corresponding to the higher-priority service and/or a connection setup cause value of the higher-priority service, thus allowing faster setup of a connection for the higher-priority service, and reducing service connection setup latency or service data transmission latency.

[0035] It should be noted that for small data transmission (Small Data Transmission, SDT), according to resources configured by the network-side device, when the UE is in an idle state or inactive state, the UE may directly transmit data to the network side in the following ways:

[0036] (1) via Msg3 of a 4-step random access procedure for initial access;

[0037] (2) via MsgA of a 2-step random access procedure for initial access; and

[0038] (3) via a dedicated physical uplink shared channel (PUSCH) resource configured by the network-side device, including pre-configured PUSCH; or via a pre-allocated uplink resource (PUR).

[0039] In addition, the network side may directly transmit data to the UE in the following ways:

[0040] (1) via Msg4 of a 4-step random access procedure for initial access;

[0041] (2) via MsgB of a 2-step random access procedure for initial access; and

[0042] (3) via a downlink feedback resource corresponding to a dedicated uplink resource configured by the network-side device.

[0043] Before the connection is set up, the terminal may receive hold-configuration-context indication information transmitted by the network-side device, where the indication information indicates that the UE holds its context configuration, for example, data radio bearer (data radio bearer, DRB) configuration and security configuration. The context configuration is used for the UE to resume connection and/or resume data transmission/reception. For example, the network-side device transmits suspend indication information in a radio resource control (RRC) release message, and when the UE is released from the connected state to the idle or inactive state, the UE can use the context configuration to resume connection and/or resume data transmission/reception.

[0044] In some embodiments, the method further includes:

[0045] obtaining, by the terminal, configuration information for a direct data transfer mode, where the configuration information is configured by the network-side device or defined by a protocol, and the configuration information includes at least one of the following:

[0046] a procedure of direct data transfer; or

[0047] service indication information for using direct data transfer.

[0048] In some embodiments, the procedure of direct data transfer includes at least one of the following:

[0049] a direct data transmission procedure, for example, uplink data transmission; or

[0050] a direct data reception procedure, for example, downlink data reception.

[0051] In some embodiments, the direct data transmission procedure includes at least one of the following:

[0052] transmitting data in Msg3 of a 4-step random access procedure;

[0053] transmitting data in MsgA of a 2-step random access procedure; or

[0054] transmitting data on a dedicated physical uplink shared channel resource configured by the network-side device.

[0055] In some embodiments, the direct data reception procedure includes at least one of the following:

[0056] receiving data in Msg4 of a 4-step random access procedure;

[0057] receiving data in MsgB of a 2-step random access procedure; or

[0058] receiving data on a downlink resource corresponding to a dedicated uplink resource configured by the network-side device; for example, after the UE transmits DRB data or a signaling radio bearer (SRB) request message on a dedicated PUSCH resource, the UE monitors physical downlink control channel (PDCCH) resources for a UE-particular identifier (for example, x-radio network temporary identity (RNTI) so as to obtain physical downlink shared channel (PDSCH) scheduling information, where the PDSCH includes DRB downlink data received by the UE.

[0059] In some embodiments, the service indication information for using the direct data transfer includes at least one of the following:

[0060] a bearer type for using direct data transfer;

[0061] a bearer identifier for using direct data transfer;

[0062] a service access category for using direct data transfer, for example, access category-1;

[0063] a service access class for using direct data transfer, for example, access class-1; or

[0064] a service type for using direct data transfer.

[0065] In some embodiments, the bearer type for using direct data transfer includes at least one of the following:

[0066] master cell group (MCG) DRB;

[0067] secondary cell group (SCG) DRB;

[0068] MCG split DRB; or

[0069] SCG Split DRB.

[0070] The MCG split DRB means that the bearer has its packet data convergence protocol (PDCP) on MCG, and two radio link layer control protocols (RLC) sublayers on MCG and SCG respectively; the SCG split DRB means that the bearer has its PDCP on SCG, and two RLC sublayers on MCG and SCG respectively.

[0071] In some embodiments, the bearer identifier for using the direct data transfer includes at least one of the following:

[0072] a DRB identifier;

[0073] a quality of service flow (QoS flow) identifier;

[0074] a protocol data unit (PDU) session identifier; or

[0075] a cell group identifier, for example, MCG identifier or SCG identifier.

[0076] In related art, a connection resume procedure for an inactive UE is triggered by the following services:

[0077] an emergency service;

[0078] a high priority access service;

[0079] a mobile terminated access (mt-Access) service;

[0080] a mobile originated signaling (mo-Signalling) service;

[0081] a mobile originated data (mo-Data) service;

[0082] a mobile originated voice call (mo-VoiceCall) service;

[0083] a mobile originated video call (mo-VideoCall) service;

[0084] a mobile originated short message (mo-SMS) service;

[0085] a access network paging area update (ma-Update) service;

[0086] a multimedia priority access (mps-PriorityAccess) service; or

[0087] a multimedia emergency access (mcs-PriorityAccess) service.

[0088] In some embodiments, the service type for using the direct data transfer also includes at least one of the following:

[0089] an emergency service;

[0090] a high priority access service;

[0091] a mobile terminated access (mt-Access) service;

[0092] a mobile originated signaling (mo-Signalling) service;

[0093] a mobile originated data (mo-Data) service;

[0094] a mobile originated voice call (mo-VoiceCall) service;

[0095] a mobile originated video call (mo-VideoCall) service;

[0096] a mobile originated short message (mo-SMS) service;

[0097] an access network paging area update (ma-Update) service;

[0098] a multimedia priority access (mps-PriorityAccess) service; or

[0099] a multimedia emergency access (mcs-PriorityAccess) service.

[0100] In the embodiments of this disclosure, according to the configuration information obtained above for the direct data transfer mode, when a service corresponding to service data to be transmitted or received by the UE corresponds to the “service indication information for using direct data transfer”, and when the data transmission satisfies a “trigger condition for a direct data reception or transmission procedure”, the UE uses the “direct data reception or transmission procedure” to transmit or receive the corresponding service data. For example, a service type of uplink data arriving at the UE is service access category-1 (or DRB-1), and access category-1 (or DRB-1) supports direct data transmission. A trigger condition for a direct data reception or transmission procedure as configured by the network side is that a data size is less than a threshold of 50 bytes, and a size of the uplink data is 10 bytes, which is less than the data size threshold of 50 bytes for triggering direct data transmission. In this case, the UE uses the “direct data transmission procedure” to transmit the corresponding service data.

[0101] In some embodiments, the connection setup cause value includes at least one of the following:

[0102] an emergency;

[0103] a high priority access;

[0104] a mobile terminated access (mt-Access);

[0105] a mobile originated signaling (mo-Signalling);

[0106] a mobile originated data (mo-Data);

[0107] a mobile originated voice call (mo-VoiceCall);

[0108] a mobile originated video call (mo-VideoCall);

[0109] a mobile originated short message (mo-SMS);

[0110] an access network paging area update (ma-Update);

[0111] a multimedia priority access (mps-PriorityAccess); or

[0112] a multimedia emergency access (mcs-PriorityAccess).

[0113] In some embodiments, the first specified service and/or the second specified service is a highest-priority service in the multiple services of different types. In this way, the terminal can determine the connection setup mode according to the highest-priority service, allowing faster setup of a connection for the highest-priority service, thereby reducing service connection setup latency or service data transmission latency.

[0114] In a case that the connection setup cause value of the first specified service is used as the cause value of the connection setup mode, in a example, as specified by the protocol, “mobile terminated service” has a higher priority than “mobile originated service”, and therefore, when the UE has both a “mobile terminated service” indicated by paging and a “mobile originated service” capable of triggering direct data transmission, the UE uses the “mobile terminated service” as a cause value for connection resume. For example, the UE may set resumeCause to “mt-Access”. In this way, the terminal can determine the connection setup mode using the connection setup cause value of the higher-priority service, thus allowing faster setup of a connection for the higher-priority service, reducing service connection setup latency or service data transmission latency.

[0115] In some embodiments, a connection setup cause value of the first specified service is the same as or different from a service type corresponding to service data actually transferred. For example, in a connection resume procedure, the UE may use the direct data transmission mode to transmit DRB-1 data, where the data corresponds to “mobile originated service”. However, because the UE also has a “mobile terminated service”, and the protocol specifies that “mobile terminated service” has a higher priority, resumeCause may be set to the connection setup cause value of “mobile terminated service”, that is, to “mt-Access”.

[0116] In a case that the connection setup procedure corresponding to the second specified service is used as the connection setup mode, in a example, as specified by the protocol, “mobile terminated service” has a higher priority than “mobile originated service”, and therefore, in a case that the UE has both a “mobile terminated service” indicated by paging and a “mobile originated service” capable of triggering direct data transmission, as only a normal connection resume procedure can be used for the “mobile terminated service” indicated by paging (rather than the direct data transmission or reception procedure), the UE uses the “normal connection resume procedure”. In another example, as specified by the protocol, “emergency service” has a higher priority than “mobile originated data service”, and therefore, in a case that the UE has both an “emergency service” and a “mobile originated service” capable of triggering direct data transmission, because only a normal connection resume procedure can be used for the “emergency service” (rather than the direct data transmission or reception procedure), the UE uses the “normal connection resume procedure”. With the foregoing solution, the terminal can perform connection setup according to a connection setup procedure corresponding to the higher-priority service, thus allowing faster setup of a connection for the higher-priority service, reducing service connection setup latency or service data transmission latency.

[0117] In some embodiments, the connection setup procedure includes at least one of the following:

[0118] a direct data transmission procedure;

[0119] a direct data reception procedure; or

[0120] a first connection setup procedure, where only radio resource control signaling is transmitted in the first connection setup procedure, meaning a normal connection setup procedure; for example, in an initial access procedure, DRB data is not directly transmitted and only RRC control signaling (for example, RRCResumeRequest message) is transmitted.

[0121] In some embodiments, a priority ordering rule for services includes any one of the following:

[0122] an emergency service having a higher priority than a mobile originated data service;

[0123] a high-priority access service having a higher priority than the mobile originated data service;

[0124] a service that triggers a first connection setup procedure having a higher priority than a service that triggers a procedure of direct data transfer, wherein in the first connection setup procedure, no data is transmitted and only radio resource control signaling is transmitted;

[0125] the service that triggers the first connection setup procedure having a lower priority than the service that triggers the procedure of direct data transfer;

[0126] a mobile terminated service having a higher priority than a mobile originated service;

[0127] a service that triggers a direct data transmission procedure having a higher priority than a service that triggers a direct data reception procedure;

[0128] the service that triggers the direct data transmission procedure having a lower priority than the service that triggers the direct data reception procedure;

[0129] a paging area update service having a higher priority than the service that triggers a procedure of direct data transfer;

[0130] the paging area update service having a lower priority than the service that triggers the procedure of direct data transfer;

[0131] the paging area update service having a higher priority than the mobile originated service;

[0132] the paging area update service having a lower priority than the mobile originated service;

[0133] the paging area update service having a higher priority than the mobile terminated service; and

[0134] the paging area update service having a lower priority than the mobile terminated service.

[0135] It should be noted that the service collision handling method provided in the embodiments of this disclosure may be executed by a service collision handling apparatus or a module in the service collision handling apparatus for executing a loaded service collision handling method. In the embodiments of this disclosure, the service collision handling method according to the embodiments of this disclosure is described with a service collision handling apparatus for executing a loaded a service collision handling method used as an example.

[0136] An embodiment of this disclosure provides a service collision handling apparatus. As shown in FIG. 3, the apparatus 300 includes:

[0137] a handling module 310, configured to, in a case that multiple services of different types are initiating connection setup, determine a connection setup mode according to a first rule, where the first rule is configured by a network-side device or defined by a protocol, and the first rule includes at least one of the following:

[0138] using a connection setup cause value of a first specified service as a cause value of the connection setup mode; or

[0139] using a connection setup procedure corresponding to a second specified service.

[0140] In this embodiment of this disclosure, when multiple services of different types are initiating connection setup, a terminal may determine a connection mode according to a first rule configured by the network-side device or defined by a protocol. For example, the terminal may use a connection setup procedure corresponding to a higher-priority service to perform connection setup, such that a connection can be set up faster for the higher-priority service, thereby reducing service connection setup latency or service data transmission latency.

[0141] The connection setup includes initial connection setup and connection resume after the initial connection setup, meaning that the connection setup mode actually includes an initial connection setup mode and a connection resume mode.

[0142] In some embodiments, the apparatus further includes:

[0143] an obtaining module, configured to obtain configuration information for a direct data transfer mode, where the configuration information is configured by the network-side device or defined by a protocol, and the configuration information includes at least one of the following:

[0144] a procedure of direct data transfer; or

[0145] service indication information for using direct data transfer.

[0146] In some embodiments, the procedure of direct data transfer includes at least one of the following:

[0147] a direct data transmission procedure; or

[0148] a direct data reception procedure.

[0149] In some embodiments, the direct data transmission procedure includes at least one of the following:

[0150] transmitting data in Msg3 of a 4-step random access procedure;

[0151] transmitting data in MsgA of a 2-step random access procedure; or

[0152] transmitting data on a dedicated physical uplink shared channel resource configured by the network-side device.

[0153] In some embodiments, the direct data reception procedure includes at least one of the following:

[0154] receiving data in Msg4 of a 4-step random access procedure;

[0155] receiving data in MsgB of a 2-step random access procedure; or

[0156] receiving data on a downlink resource corresponding to a dedicated uplink resource configured by the network-side device; for example, after the UE transmits DRB data or a signaling radio bearer (SRB) request message on a dedicated PUSCH resource, the UE monitors physical downlink control channel (PDCCH) resources for a UE-particular identifier (for example, x-radio network temporary identity (RNTI) so as to obtain physical downlink shared channel (PDSCH) scheduling information, where the PDSCH includes DRB downlink data received by the UE.

[0157] In some embodiments, the service indication information for using the direct data transfer includes at least one of the following:

[0158] a bearer type for using direct data transfer;

[0159] a bearer identifier for using direct data transfer;

[0160] a service access category for using direct data transfer, for example, access category-1;

[0161] a service access class for using direct data transfer, for example, access class-1; or

[0162] a service type for using direct data transfer.

[0163] In some embodiments, the bearer type for using direct data transfer includes at least one of the following:

[0164] MCG DRB;

[0165] SCG DRB;

[0166] MCG Split DRB; or

[0167] SCG Split DRB.

[0168] The MCG split DRB means that the bearer has its packet data convergence protocol (Packet Data Convergence Protocol, PDCP) on MCG, and two radio link layer control protocols (Radio Link Control, RLC) sublayers on MCG and SCG respectively; the SCG split DRB means that the bearer has its PDCP on SCG, and two RLC sublayers on MCG and SCG respectively.

[0169] In some embodiments, the bearer identifier for using the direct data transfer includes at least one of the following:

[0170] a DRB identifier;

[0171] a QoS flow identifier;

[0172] a PDU session identifier; or

[0173] a cell group identifier.

[0174] In some embodiments, the service type for using the direct data transfer includes at least one of the following:

[0175] an emergency service;

[0176] a high priority access service;

[0177] a mobile terminated access (mt-Access) service;

[0178] a mobile originated signaling (mo-Signalling) service;

[0179] a mobile originated data (mo-Data) service;

[0180] a mobile originated voice call (mo-VoiceCall) service;

[0181] a mobile originated video call (mo-VideoCall) service;

[0182] a mobile originated short message (mo-SMS) service;

[0183] an access network paging area update (ma-Update) service;

[0184] a multimedia priority access (mps-PriorityAccess) service; or

[0185] a multimedia emergency access (mcs-PriorityAccess) service.

[0186] In this embodiment of this disclosure, according to the configuration information obtained above for the direct data transfer mode, when a service corresponding to service data to be transmitted or received by the UE corresponds to the “service indication information for using direct data transfer”, and when the data transmission satisfies a “trigger condition for a direct data reception or transmission procedure”, the UE uses the “direct data reception or transmission procedure” to transmit or receive the corresponding service data. For example, a service type of uplink data arriving at the UE is service access category-1 (or DRB-1), and access category-1 (or DRB-1) supports direct data transmission. A trigger condition for a direct data reception or transmission procedure as configured by the network side is that a data size is less than a threshold of 50 bytes, and a size of the uplink data is 10 bytes, which is less than the data size threshold of 50 bytes for triggering direct data transmission. In this case, the UE uses the “direct data transmission procedure” to transmit the corresponding service data.

[0187] In some embodiments, the connection setup cause value includes at least one of the following:

[0188] an emergency;

[0189] a high priority access;

[0190] a mobile terminated access (mt-Access);

[0191] a mobile originated signaling (mo-Signalling);

[0192] a mobile originated data (mo-Data);

[0193] a mobile originated voice call (mo-VoiceCall);

[0194] a mobile originated video call (mo-VideoCall);

[0195] a mobile originated short message (mo-SMS);

[0196] an access network paging area update (ma-Update);

[0197] a multimedia priority access (mps-PriorityAccess); or

[0198] a multimedia emergency access (mcs-PriorityAccess).

[0199] When the connection setup cause value of the first specified service is used as the cause value of the connection setup mode, in a example, as specified in the protocol, “mobile terminated service” has a higher priority than “mobile originated service”. Therefore, when the UE has both a “mobile terminated service” indicated by paging and a “mobile originated service” capable of triggering direct data transmission, the UE uses the “mobile terminated service” as the cause value of connection resume. For example, the UE may set resumeCause to “mt-Access”. In this way, the terminal can determine the connection setup mode using a connection setup cause value of the higher-priority service, thus allowing faster setup of a connection for the higher-priority service, reducing service connection setup latency or service data transmission latency.

[0200] In some embodiments, a connection setup cause value of the first specified service is the same as or different from a service type corresponding to service data actually transferred. For example, in a connection resume procedure, the UE may use the direct data transmission mode to transmit DRB-1 data, where the data corresponds to “mobile originated service”. However, because the UE also has a “mobile terminated service”, and the protocol specifies that “mobile terminated service” has a higher priority, resumeCause may be set to the connection setup cause value of “mobile terminated service”, that is, to “mt-Access”.

[0201] When the connection setup procedure corresponding to the second specified service is used as the connection setup mode, in a example, as specified by the protocol, “mobile terminated service” has a higher priority than “mobile originated service”, and therefore, when the UE has both a “mobile terminated service” indicated by paging and a “mobile originated service” capable of triggering direct data transmission, as only a normal connection resume procedure can be used for the “mobile terminated service” indicated by paging (rather than the direct data transmission or reception procedure), the UE uses the “normal connection resume procedure”. In another example, as specified by the protocol, “emergency service” has a higher priority than “mobile originated data service”, and therefore, when the UE has both an “emergency service” and a “mobile originated service” capable of triggering direct data transmission, because only a normal connection resume procedure can be used for the “emergency service” (rather than the direct data transmission or reception procedure), the UE uses the “normal connection resume procedure”. With the foregoing solution, the terminal can perform connection setup according to a connection setup procedure corresponding to the higher-priority service, thus allowing faster setup of a connection for the higher-priority service, reducing service connection setup latency or service data transmission latency.

[0202] In some embodiments, the connection setup procedure includes at least one of the following:

[0203] a direct data transmission procedure;

[0204] a direct data reception procedure; or

[0205] a first connection setup procedure, where only radio resource control signaling is transmitted in the first connection setup procedure, meaning a normal connection setup procedure; for example, in an initial access procedure, DRB data is not directly transmitted and only RRC control signaling (for example, RRCResumeRequest message) is transmitted.

[0206] In some embodiments, the first specified service and/or the second specified service is a highest-priority service in the multiple services of different types.

[0207] In some embodiments, a priority ordering rule for services includes any one of the following:

[0208] an emergency service having a higher priority than a mobile originated data service;

[0209] a high-priority access service having a higher priority than the mobile originated data service;

[0210] a service that triggers a first connection setup procedure having a higher priority than a service that triggers a procedure of direct data transfer, wherein in the first connection setup procedure, no data is transmitted and only radio resource control signaling is transmitted;

[0211] the service that triggers the first connection setup procedure having a lower priority than the service that triggers the procedure of direct data transfer;

[0212] a mobile terminated service having a higher priority than a mobile originated service;

[0213] a service that triggers a direct data transmission procedure having a higher priority than a service that triggers a direct data reception procedure;

[0214] the service that triggers the direct data transmission procedure having a lower priority than the service that triggers the direct data reception procedure;

[0215] a paging area update service having a higher priority than the service that triggers a procedure of direct data transfer;

[0216] the paging area update service having a lower priority than the service that triggers the procedure of direct data transfer;

[0217] the paging area update service having a higher priority than the mobile originated service;

[0218] the paging area update service having a lower priority than the mobile originated service;

[0219] the paging area update service having a higher priority than the mobile terminated service; and

[0220] the paging area update service having a lower priority than the mobile terminated service.

[0221] The service collision handling apparatus in the embodiments of this disclosure may be an apparatus, or may be a component, an integrated circuit, or a chip in a terminal. The apparatus may be a mobile electronic device or a non-mobile electronic device. For example, the mobile electronic device may be a mobile phone, a tablet computer, a notebook computer, a palmtop computer, a vehicle-mounted electronic device, a wearable device, an ultra-mobile personal computer (UMPC), a netbook, or a personal digital assistant (PDA), and the non-mobile electronic device may be a network attached storage (NAS), a personal computer (PC), a television (TV), a teller machine, a self-service machine, or the like. This is not limited in the embodiments of this disclosure.

[0222] The service collision handling apparatus in the embodiments of this disclosure may be an apparatus having an operating system. The operating system may be an Android operating system, an iOS operating system, or other possible operating systems. This is not limited in the embodiments of this disclosure.

[0223] Optionally, an embodiment of this disclosure further provides a terminal, including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, where when the program or instructions are executed by the processor, the processes of the foregoing service collision handling method embodiment are implemented, with the same technical effects achieved. To avoid repetition, details are not further described herein.

[0224] It should be noted that the terminal in this embodiment of this disclosure includes the above-mentioned mobile electronic device and non-mobile electronic device.

[0225] FIG. 4 is a schematic diagram of a hardware structure of a terminal for implementing the embodiments of this disclosure. The terminal 50 includes but is not limited to components such as a radio frequency unit 51, a network module 52, an audio output unit 53, an input unit 54, a sensor 55, a display unit 56, a user input unit 57, an interface unit 58, a memory 59, a processor 510, and a power supply 511. Persons skilled in the art can understand that the structure of the terminal shown in FIG. 4 does not constitute any limitation on the terminal, and the terminal may include more or fewer components than shown in the diagram, or combine some of the components, or have different arrangements of the components. In this embodiment of this disclosure, the terminal includes but is not limited to a mobile phone, a tablet computer, a laptop computer, a palmtop computer, a vehicle-mounted mobile terminal, a wearable device, a pedometer, or the like.

[0226] It should be understood that in this embodiment of this disclosure, the radio frequency unit 51 may be configured to receive and transmit information, or to receive and transmit a signal in a call process, and specially, after receiving downlink data from a base station, transmit the downlink data to the processor 510 for processing; and also transmit uplink data to the base station. Generally, the radio frequency unit 51 includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, the radio frequency unit 51 may also communicate with a network and other devices via a wireless communications system.

[0227] The memory 59 may be configured to store software programs and various data. The memory 59 may mainly include a program storage area and a data storage area. The program storage area may store an operating system, an application program required for at least one function (for example, a sound play function and an image play function), and the like. The data storage area may store data created based on use of the mobile phone (for example, audio data and a phone book), and the like. In addition, the memory 59 may include a high-speed random access memory, or may further include a non-volatile memory, for example, at least one magnetic disk storage device, flash memory, or other volatile solid-state storage devices.

[0228] The processor 510 is a control center of the terminal, and is connected to all components of the terminal by using various interfaces and lines. By executing software programs and/or modules stored in the memory 59 and invoking data stored in the memory 59, the processor 510 executes various functions of the terminal and processes data, so as to perform overall monitoring on the terminal. The processor 510 may include one or more processing units. Illustratively, the processor 510 may integrate an application processor and a modem processor. The application processor mainly processes the operating system, a user interface, an application program, and the like. The modem processor mainly processes wireless communication. It can be understood that the modem processor may alternatively not be integrated in the processor 510.

[0229] The terminal 50 may further include the power supply 511 (such as a battery) supplying power to the components. Illustratively, the power supply 511 may be logically connected to the processor 510 via a power management system, so that functions such as charge and discharge management and power consumption management are implemented via the power management system.

[0230] In addition, the terminal 50 includes some functional modules that are not shown, which are not further described herein.

[0231] The processor 510 is configured to, in a case that multiple services of different types are initiating connection setup, determine a connection setup mode according to a first rule, where the first rule is configured by a network-side device or defined by a protocol, and the first rule includes at least one of the following:

[0232] using a connection setup cause value of a first specified service as a cause value of the connection setup mode; or

[0233] using a connection setup procedure corresponding to a second specified service.

[0234] In some embodiments, the processor 510 is further configured to obtain configuration information for a direct data transfer mode, where the configuration information is configured by the network-side device or defined by a protocol, and the configuration information includes at least one of the following:

[0235] a procedure of direct data transfer; or

[0236] service indication information for using direct data transfer.

[0237] In some embodiments, the procedure of the direct data transfer includes at least one of the following:

[0238] a direct data transmission procedure; or

[0239] a direct data reception procedure.

[0240] In some embodiments, the direct data transmission procedure includes at least one of the following:

[0241] transmitting data in Msg3 of a 4-step random access procedure;

[0242] transmitting data in MsgA of a 2-step random access procedure; or

[0243] transmitting data on a dedicated physical uplink shared channel resource configured by the network-side device.

[0244] In some embodiments, the direct data reception procedure includes at least one of the following:

[0245] receiving data in Msg4 of a 4-step random access procedure;

[0246] receiving data in MsgB of a 2-step random access procedure; or

[0247] receiving data on a downlink resource corresponding to a dedicated uplink resource configured by the network-side device.

[0248] In some embodiments, the service indication information for using the direct data transfer includes at least one of the following:

[0249] a bearer type for using direct data transfer;

[0250] a bearer identifier for using direct data transfer;

[0251] a service access category for using direct data transfer;

[0252] a service access class for using direct data transfer; or

[0253] a service type for using direct data transfer.

[0254] In some embodiments, the bearer type for using direct data transfer includes at least one of the following:

[0255] MCG DRB;

[0256] SCG DRB;

[0257] MCG Split DRB; or

[0258] SCG Split DRB.

[0259] In some embodiments, the bearer identifier for using the direct data transfer includes at least one of the following:

[0260] a DRB identifier;

[0261] a QoS flow identifier;

[0262] a PDU session identifier; or

[0263] a cell group identifier.

[0264] In some embodiments, the service type for using the direct data transfer includes at least one of the following:

[0265] an emergency service;

[0266] a high priority access service;

[0267] a mobile terminated access (mt-Access) service;

[0268] a mobile originated signaling (mo-Signalling) service;

[0269] a mobile originated data (mo-Data) service;

[0270] a mobile originated voice call (mo-VoiceCall) service;

[0271] a mobile originated video call (mo-VideoCall) service;

[0272] a mobile originated short message (mo-SMS) service;

[0273] a access network paging area update (ma-Update) service;

[0274] a multimedia priority access (mps-PriorityAccess) service; or

[0275] a multimedia emergency access (mcs-PriorityAccess) service.

[0276] In some embodiments, the connection setup cause value includes at least one of the following:

[0277] an emergency;

[0278] a high priority access;

[0279] a mobile terminated access (mt-Access);

[0280] a mobile originated signaling (mo-Signalling);

[0281] a mobile originated data (mo-Data);

[0282] a mobile originated voice call (mo-VoiceCall);

[0283] a mobile originated video call (mo-VideoCall);

[0284] a mobile originated short message (mo-SMS);

[0285] an access network paging area update (ma-Update);

[0286] a multimedia priority access (mps-PriorityAccess); and

[0287] a multimedia emergency access (mcs-PriorityAccess).

[0288] In some embodiments, a connection setup cause value the first specified service the same as or different from a service type corresponding to service data actually transferred.

[0289] In some embodiments, the connection setup procedure includes at least one of the following:

[0290] a direct data transmission procedure;

[0291] a direct data reception procedure; or

[0292] a first connection setup procedure, in which only radio resource control signaling is transmitted.

[0293] In some embodiments, the first specified service and/or the second specified service is a highest-priority service in the multiple services of different types.

[0294] In some embodiments, a priority ordering rule for services includes any one of the following:

[0295] an emergency service having a higher priority than a mobile originated data service;

[0296] a high-priority access service having a higher priority than the mobile originated data service;

[0297] a service that triggers a first connection setup procedure having a higher priority than a service that triggers a procedure of direct data transfer, wherein in the first connection setup procedure, no data is transmitted and only radio resource control signaling is transmitted;

[0298] the service that triggers the first connection setup procedure having a lower priority than the service that triggers the procedure of direct data transfer;

[0299] a mobile terminated service having a higher priority than a mobile originated service;

[0300] a service that triggers a direct data transmission procedure having a higher priority than a service that triggers a direct data reception procedure;

[0301] the service that triggers the direct data transmission procedure having a lower priority than the service that triggers the direct data reception procedure;

[0302] a paging area update service having a higher priority than the service that triggers a procedure of direct data transfer;

[0303] the paging area update service having a lower priority than the service that triggers the procedure of direct data transfer;

[0304] the paging area update service having a higher priority than the mobile originated service;

[0305] the paging area update service having a lower priority than the mobile originated service;

[0306] the paging area update service having a higher priority than the mobile terminated service; and

[0307] the paging area update service having a lower priority than the mobile terminated service.

[0308] An embodiment of this disclosure further provides a non-transitory readable storage medium, where the non-transitory readable storage medium stores a program or instructions, and when the program or instructions are executed by a processor, the processes of the foregoing service collision handling method embodiment are implemented, with the same technical effect achieved. To avoid repetition, details are not described herein again.

[0309] The processor is the processor in the terminal described in the foregoing embodiment. The non-transitory readable storage medium includes a non-transitory computer-readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disc.

[0310] Another embodiment of this disclosure provides a chip, where the chip includes a processor and a communications interface, the communications interface is coupled to the processor, and the processor is configured to execute a program or instructions to implement the processes of the foregoing service collision handling method embodiment, with the same technical effects achieved. To avoid repetition, details are not described herein again.

[0311] It should be understood that the chip in the embodiments of this disclosure may also be referred to as a system-level chip, a system chip, a chip system, a system on chip, or the like.

[0312] It should be noted that in this specification, the terms “include” and “comprise”, or any of their variants are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements not only includes those elements but also includes other elements that are not expressly listed, or further includes elements inherent to such process, method, article, or apparatus. In absence of more constraints, an element preceded by “includes a . . . ” does not preclude the existence of other identical elements in the process, method, article, or apparatus that includes the element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this disclosure is not limited to performing the functions in the order shown or discussed, but may also include performing the functions in a substantially simultaneous manner or in a reverse order depending on the functions involved. For example, the described method may be performed in an order different from the order described, and steps may be added, omitted, or combined. In addition, features described with reference to some examples may be combined in other examples.

[0313] Persons of ordinary skill in the art may realize that units and algorithm steps of various examples described with reference to the embodiments disclosed in this specification can be implemented by using electronic hardware or a combination of computer software and electronic hardware. Whether the functions are performed by hardware or software depends on particular applications and design constraints of the technical solutions. Persons skilled in the art may use a different method for each particular application to implement the described functions, but it should not be considered that such implementation goes beyond the scope of this disclosure.

[0314] It may be clearly understood by persons skilled in the art that, for the purpose of convenient and brief description, for a detailed working process of the foregoing system, apparatus, and unit, reference may be made to a corresponding process in the foregoing method embodiments, and details are not described herein again.

[0315] In the embodiments provided in this disclosure, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the described apparatus embodiments are merely examples. For example, the unit division is merely logical function division and may be other division in actual implementation. For example, a plurality of units or components may be combined or integrated into another system, or some features may be ignored or may not be performed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections may be indirect couplings or communication connections via some interfaces, apparatuses or units, and may be in electrical, mechanical, or other forms.

[0316] The units described as separate parts may or may not be physically separate. Parts displayed as units may or may not be physical units, meaning that they may be located in one place or distributed on a plurality of network elements. Some or all of the units may be selected as appropriate to actual needs to achieve the objectives of the solutions of the embodiments.

[0317] In addition, functional units in the embodiments of this disclosure may be integrated into one processing unit, or each of the units may exist alone physically, or two or more units are integrated into one unit.

[0318] From the description of the foregoing embodiments, persons skilled in the art can clearly understand that the method in the foregoing embodiments may be implemented by software plus a necessary universal hardware platform or by hardware only. In most cases, the former is a preferred implementation. Based on such an understanding, the technical solutions of this disclosure essentially, or the part contributing to the prior art may be implemented in a form of a software product. The software product is stored in a storage medium (for example, ROM/RAM, a magnetic disk, or an optical disc), and includes several instructions for instructing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, a network device, or the like) to perform the method described in the embodiments of this disclosure.

[0319] It can be understood that the embodiments described in the embodiments of this disclosure may be implemented by hardware, software, firmware, middleware, microcode, or a combination thereof. For implementation by hardware, modules, units, and subunits may be implemented in one or more application specific integrated circuits (ASIC), digital signal processors (DSP), digital signal processing devices (DSPD), programmable logic devices (PLD), field-programmable gate array (FPGA), general-purpose processors, controllers, microcontrollers, microprocessors, or other electronic units for implementing the functions described in this disclosure, or a combination thereof.

[0320] For software implementation, the techniques described in the embodiments of this disclosure may be implemented by modules (for example, processes or functions) that implement the functions described in the embodiments of this disclosure. Software code may be stored in the memory and executed by the processor. The memory may be implemented in or outside the processor.

[0321] The foregoing describes the embodiments of this disclosure with reference to the accompanying drawings. However, this disclosure is not limited to these embodiments. The embodiments are merely illustrative rather than restrictive. Inspired by this disclosure, persons of ordinary skill in the art may develop many other forms without departing from the principle of this disclosure and the protection scope of the claims, and all such forms fall within the protection scope of this disclosure.