Communication method, apparatus, device, chip and medium

Abstract

The present disclosure provides a communication method, device, equipment, chip and medium, wherein the communication method comprises: determining a target slice associated with a first bearer, wherein the first bearer cannot maintain a service, and determining a condition according to the target slice, wherein the condition indicates that a handover to a second bearer is not supported, the second bearer is used to maintain the service, the first bearer and the second bearer are established through different networks, and the second bearer is established and switched to according to the target slice. Therefore, the service continuity can be effectively maintained to improve the service performance.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a communication method, apparatus, device, chip, and medium. Background Technology

[0002] In cellular networks, the service area covered by a provider is divided into multiple small geographical areas (or cells). Cellular networks can provide services not only to terminals but also to home and office networks. VoWiFi (Voiceover Wi-Fi) is a technology that transmits voice calls over a Wireless Local Area Network (WLAN). It allows users to make voice calls via Wi-Fi when connected to a Wireless Fidelity (Wi-Fi) network, without relying on a mobile operator's cellular network. Summary of the Invention

[0003] This disclosure aims to at least partially address one of the technical problems in the related art.

[0004] Therefore, this disclosure proposes a communication method, apparatus, communication equipment, chip, computer-readable storage medium, and computer program product that can effectively maintain business continuity and improve business performance.

[0005] The first aspect of this disclosure provides a communication method, comprising: determining a target slice associated with a first bearer, wherein the first bearer cannot maintain services; determining, based on the target slice, a condition is met, wherein the condition indicates that triggering a handover to a second bearer is not supported, the second bearer is used to maintain services, and the first bearer and the second bearer are established through different networks; and establishing and switching to the second bearer based on the target slice. A second aspect of this disclosure provides a communication apparatus, comprising: a first determining module for determining a target slice associated with a first bearer, wherein the first bearer cannot maintain services; a second determining module for determining, based on the target slice, a condition that is met, wherein the condition indicates that triggering a switch to a second bearer is not supported, the second bearer is used to maintain services, and the first bearer and the second bearer are established through different networks; and a processing module for establishing and switching to the second bearer based on the target slice. A third aspect of this disclosure provides a communication device, including: a processor and a memory communicatively connected to the processor; the memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory to implement the communication method as described in the above-described aspects of this disclosure.

[0006] A fourth aspect of this disclosure provides a chip including a processing circuit and an interface circuit; wherein the interface circuit is used to read instructions and send instructions to the processing circuit so that the processing circuit executes the communication method as proposed in the first aspect of this disclosure.

[0007] A fifth aspect of this disclosure provides a computer-readable storage medium storing computer-executable instructions that, when executed by a processor, are used to implement the communication method described above.

[0008] The communication method, apparatus, equipment, chip, computer-readable storage medium, and computer program product provided in this disclosure determine a target slice associated with a first bearer, wherein the first bearer cannot sustain services, and determine, based on the target slice, conditions that are met, wherein the conditions indicate that triggering a handover to a second bearer is not supported, the second bearer is used to sustain services, the first and second bearers are established through different networks, and establish and handover to the second bearer based on the target slice. This effectively maintains service continuity and improves service performance.

[0009] Additional aspects and advantages of this disclosure will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this disclosure. Attached Figure Description

[0010] The above and / or additional aspects and advantages of this disclosure will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, in which: Figure 1 This is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure; Figure 2 This is a flowchart illustrating a communication method provided in an embodiment of the present disclosure; Figure 3 This is a flowchart illustrating another communication method provided in an embodiment of the present disclosure; Figure 4 This is a schematic diagram of an application process in one embodiment of this disclosure; Figure 5 This is a flowchart illustrating yet another communication method provided in an embodiment of the present disclosure; Figure 6 This is a schematic diagram of another application process in an embodiment of this disclosure; Figure 7 This is a schematic diagram of the structure of a communication device provided in an embodiment of the present disclosure; Figure 8 A block diagram of an exemplary communication device suitable for implementing embodiments of the present disclosure is shown; Figure 9 This is a schematic diagram of the structure of a chip according to an embodiment of this disclosure; Figure 10 This is a schematic diagram of another chip structure proposed in an embodiment of this disclosure. Detailed Implementation

[0011] Embodiments of this disclosure are described in detail below, examples of which are illustrated in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this disclosure, and should not be construed as limiting this disclosure.

[0012] In embodiments of this disclosure, the communication device may be, for example, a terminal or a chip, and there is no limitation thereto.

[0013] Figure 1 This is a schematic diagram of the architecture of a communication system according to embodiments of this disclosure. Figure 1 As shown, the communication system 100 may include a terminal 101 and a network device 102. The network device 102 may include at least one of an access network device and a core network device.

[0014] In some embodiments, terminal 101 includes, for example, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal, augmented reality (AR) terminal, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical surgery, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, and wireless terminal in smart home, but is not limited thereto.

[0015] In some embodiments, the access network device is, for example, a node or device that connects a terminal to a wireless network. The access network device may include, but is not limited to, at least one of the following in a 5G communication system: evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), node B (NB), home node B (HNB), home evolved node B (HeNB), wireless backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in a 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in a WiFi system.

[0016] In some embodiments, the technical solutions of this disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within access network devices involved in the embodiments of this disclosure can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.

[0017] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

[0018] In some embodiments, a core network device may be a single device including one or more network functions, or it may be multiple devices or a group of devices, each including all or part of one or more network functions. Network functions may be virtual or physical. The core network includes, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).

[0019] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.

[0020] The following embodiments of this disclosure can be applied to Figure 1 The communication system 100 shown, or a part thereof, but not limited to it. Figure 1 The entities shown are illustrative; a communication system may include... Figure 1 All or part of the main body, or may include Figure 1 Other entities besides the main body, the number and form of each entity are arbitrary, the connection relationship between the entities is illustrative, the entities may not be connected or may be connected, and the connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0021] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), 6th generation mobile communication system (6G), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0022] Optionally, in a cellular network, the service area covered by the provider is divided into multiple small geographical areas (or cells). Cellular networks can provide services not only to terminals but also to home and office networks. VoWiFi (Voice over Wi-Fi) is a technology that transmits voice calls over a Wireless Local Area Network (WLAN). It allows users to make voice calls via Wi-Fi when connected to a Wireless Fidelity (Wi-Fi) network, without relying on a mobile operator's cellular network.

[0023] Optional, Internet Protocol IP Multimedia Subsystem (IMS) Optionally, core network equipment may include one or more network functions. Network functions include, for example: an Evolved Packet Data Gateway (ePDG), used to handle non-3GPP access, providing users with access control, encryption, and Packet Data Network (PDN) establishment functions for packet data services; and an Access and Mobility Management Function (AMF). The AMF is a logical node function on the core network side, serving as the core network control plane access point for terminals and radio. It receives all connection and session-related information from user equipment and performs registration, connection, reachability, and mobility management. Furthermore, the AMF provides a session management message transmission channel for terminal equipment and Session Management Function (SMF) equipment, providing authentication and authorization functions for user access.

[0024] Optionally, the network can inform the terminal of the currently allowed slice list (including allowed Network Slice Selection Assistance Information (allowedNSSAI)) and the configured slice list (configured NSSAI) through messages such as successful registration. Slicing (or network slicing) is a core technology that uses virtualization to divide a single physical network into multiple logically isolated virtual subnets. Each subnet can be independently configured with resources, performance, and security policies, enabling "one network for multiple uses."

[0025] Optionally, if the terminal establishes a PDN via ePDG and the network allocates an associated slice, the terminal can store the slice information in the corresponding slice list. If the slice associated with the PDN established by the terminal via ePDG is not included in the allowed slice list, the terminal does not support requesting to switch the PDN to the cellular network.

[0026] In related technologies, after a terminal successfully registers on the cellular network, due to temporary reasons (such as an excessive number of temporary users accessing the slice causing network congestion), the network will notify the terminal that the allowed slice list includes slice 1 but not slice 2. Due to good Wi-Fi signal or VoWIFI priority, the terminal registers for IMS via Wi-Fi, establishing an IMS PDN. At this point, the network notifies the terminal that the associated slice is slice 2. Subsequently, the terminal makes a call via Wi-Fi. During the call, if the Wi-Fi signal weakens (e.g., Wi-Fi is turned off), for service continuity, the IMS PDN can be switched to the cellular network. However, because slice 2 is not in the allowed slice list, the terminal cannot initiate a handover, resulting in a dropped call. Meanwhile, slice 2 may have already been allowed access (e.g., fewer users are on slice 2).

[0027] The method provided in this disclosure, when applied to IMS services, allows a terminal to establish an IMS PDN on Wi-Fi, and the network to configure slices associated with the IMS PDN. When making a call over Wi-Fi, if the IMS PDN cannot continue to maintain the IMS service and cannot trigger (or initiate) a handover to the cellular network, the terminal can attempt to request an update registration or initiate a handover, thereby effectively reducing the call drop rate, maintaining service continuity, and improving service performance.

[0028] Figure 2 This is a flowchart illustrating a communication method provided in an embodiment of the present disclosure.

[0029] The communication method provided in this embodiment can be applied in a terminal. Optionally, the entity executing the communication method in this embodiment can be, for example, a terminal or a chip. The chip can be deployed in the terminal or in any other possible device, without limitation.

[0030] like Figure 2 As shown, the communication method includes: Step S201: Determine the target slice associated with the first bearer, wherein the first bearer is an unsustainable service.

[0031] The first bearer can be a PDN established through a Wi-Fi network, and there are no restrictions on this.

[0032] The slice associated with the first bearer can be referred to as the target slice.

[0033] Optionally, the service can be, for example, an IMS service. Of course, the service can also be any other possible type, such as location services, sensing services, etc. There are no restrictions on this. The primary bearer used for IMS services can also be called the IMS PDN.

[0034] Optionally, the first bearer cannot maintain services, which can be understood as the first bearer not supporting the continuity of services. For example, the Wi-Fi network may have poor signal quality or be shut down.

[0035] Optionally, if the terminal determines that the first bearer cannot maintain the service, it can determine the target slice associated with the first bearer, and then determine whether it can successfully switch to the second bearer based on the target slice. For details, please refer to the following description.

[0036] Optionally, the terminal may read and store the target slice configured by the network for the first bearer during the establishment of the first bearer, and obtain the stored target slice configured for the first bearer if it is determined that the first bearer cannot maintain the service.

[0037] Optionally, an example of the "process of establishing the first bearer" is given below: If a terminal has a need to use services through a Wi-Fi network, it can establish a first bearer through the Wi-Fi network. The first bearer can be used to carry service-related data.

[0038] Optionally, the terminal can establish a first bearer via the Wi-Fi network, provided that the Wi-Fi signal is good. This first bearer can be used to carry service-related data. For example, the terminal can establish the first bearer by interacting with the ePDG, and the first bearer can be used for services.

[0039] Optionally, during the establishment of the first bearer via the Wi-Fi network, the terminal can send a request message to the network to request the establishment of the first bearer via ePDG. The network can configure the associated slice for the first bearer and send a response message to the terminal to indicate that the first bearer has been successfully established and to indicate the slice associated with the first bearer. The network can be the core network.

[0040] Optionally, after successfully establishing the first bearer, the terminal can use the service through the first bearer. Subsequently, if it is determined during the use of the service that the first bearer does not support maintaining service continuity, the target slice associated with the first bearer can be determined, and then subsequent steps can be triggered.

[0041] Step S202: Based on the target slice, determine the conditions that are met, where the conditions indicate that triggering a switch to the second bearer is not supported. The second bearer is used to maintain services, and the first and second bearers are established through different networks.

[0042] Optionally, the terminal can determine whether a condition is met based on the target slice. The condition indicates that triggering a handover to the second bearer is not supported. In other words, the terminal can determine whether a handover to the second bearer can be triggered (or initiated) based on the target slice.

[0043] The second bearer can be a Protocol Data Unit (PDU) established through a cellular network. The first and second bearers are established through different networks. The second network can be, for example, a cellular network; there are no restrictions on this. The second bearer is used to maintain service. That is, if the first bearer cannot maintain service, and it is determined based on the target slice associated with the first bearer that it does not support triggering a handover to the second bearer, certain measures can be taken to achieve timely handover and ensure service continuity.

[0044] Optionally, the terminal can determine whether the target slice is allowed to access based on the target slice information. If the target slice is not allowed to access, then the target slice is determined to meet the conditions. Alternatively, the terminal can detect whether it can initiate a handover from the first bearer to the second bearer based on the target slice. If it cannot initiate a handover from the first bearer to the second bearer based on the target slice, then the conditions are determined to be met, and no restrictions are imposed on this.

[0045] Step S203: Based on the target slice, establish and switch to the second bearer.

[0046] Optionally, if it is determined that the first bearer cannot maintain the service, the target slice associated with the first bearer can be determined. If the condition is met based on the target slice, namely, it is determined that the handover to the second bearer is not supported, the second bearer can be established and switched to based on the target slice in order to maintain the continuity of the service through the second bearer.

[0047] In this embodiment, by determining the target slice associated with the first bearer, where the first bearer cannot sustain services, and by determining conditions based on the target slice, wherein the conditions indicate that triggering a handover to the second bearer is not supported, the second bearer is used to sustain services, the first and second bearers are established through different networks, and the handover to the second bearer is established and performed based on the target slice, service continuity can be effectively maintained, thereby improving service performance.

[0048] Figure 3 This is a flowchart illustrating another communication method provided in an embodiment of the present disclosure.

[0049] The communication method provided in this embodiment can be applied in a terminal. Optionally, the entity executing the communication method in this embodiment can be, for example, a terminal or a chip. The chip can be deployed in the terminal or in any other possible device, without limitation.

[0050] like Figure 3 As shown, the communication method includes: Step S301: Determine the target slice associated with the first bearer, wherein the first bearer cannot maintain services.

[0051] For a description of S301, please refer to the above embodiments, and it will not be repeated here.

[0052] Step S302: Obtain the first slice list, wherein the first slice list includes: information on slices that are allowed to access.

[0053] The first slice list is assigned during initial registration. The first slice list includes information about several slices. Specifically, each "slice" refers to a slice that is allowed to be accessed.

[0054] Optionally, the information about the slice that is allowed to be accessed can be, for example, the NSSAI that is allowed to be accessed.

[0055] Optionally, the first slice list, also known as the allowed slice list, can be configured for the terminal during initial registration. For example, the terminal can send an initial registration request to the network (e.g., the core network), and the network can send a registration acceptance message to the terminal, which may include: an allowed slice list and a rejected slice list. The rejected slice list may contain information about slices that are not allowed to access. The terminal can then receive the allowed slice list indicated by the network and, based on the allowed slice list, determine the information about slices that are allowed to access.

[0056] Step S303: Determine whether the target slice is allowed to be accessed based on the information of the target slice and the information of the allowed slice.

[0057] Optionally, after obtaining the first slice list, the system can determine whether a target slice is allowed access based on the target slice's information and the information of the allowed access slices. The target slice's information can be, for example, its NSSAI. For instance, it can be determined whether the target slice's NSSAI is the same as the allowed access slice's NSSAI. If they are the same, the target slice is allowed access; if they are different, the target slice is not allowed access.

[0058] Optionally, steps S302 and S303 can be omitted, and the determination of whether the target slice is allowed access can be based on the "information on slices not allowed to access" contained in the network-indicated rejected slice list. The "information on slices not allowed to access" can be, for example, the NSSAI of slices not allowed to access. For instance, it can be determined whether the NSSAI of the target slice is the same as the NSSAI of slices not allowed to access; if they are the same, the target slice is determined to be not allowed to access; if they are different, the target slice is determined to be allowed to access.

[0059] Step S304: If the target slice is not allowed to access, determine if the condition is met. The condition indicates that triggering a handover to the second bearer is not supported. The second bearer is used to maintain services. The first bearer and the second bearer are established through different networks.

[0060] Optionally, if it is determined that the target slice is not allowed to access, it means that switching to the second bearer based on the target slice is not supported.

[0061] Step S305: Obtain the second slice list, wherein the second slice list includes: information on slices that are allowed to be accessed.

[0062] Step S306: Determine that the information of the allowed access slices in the second slice list includes: the information of the target slice.

[0063] In other words, if it is determined that the target slice is not allowed to access, a second slice list can be obtained. This second slice list includes information about allowed slices, and the information about allowed slices includes the target slice's information. Specifically, if a second slice list is obtained, and this list includes information about allowed slices, which in turn includes the target slice's information, then the target slice is allowed to access.

[0064] Optionally, the second slice list, also known as the allowed slice list, can be obtained by updating the first slice list. For example, if it is determined that the information of the allowed slices in the first slice list does not include the information of the target slice, an update registration can be initiated to update the first slice list and obtain the second slice list, ensuring that the information of the target slice is included in the second slice list. After the update, the second slice list can be stored in local storage.

[0065] Optionally, when the terminal obtains the second slice list, it can obtain the second slice list from local storage. This can greatly improve the efficiency of obtaining the second slice list. When the second slice list is obtained, it can be indicated that the target slice is allowed to access, thereby greatly improving the handover efficiency.

[0066] Optionally, the terminal can also initiate an update registration to obtain a second slice list.

[0067] Optionally, the terminal can send a first message to the network, wherein the first message is used to request an update registration. The first message includes: information about the target slice, which is used to update the first slice list to obtain a second slice list, and the terminal receives the second slice list indicated by the network. This improves the flexibility of obtaining the second slice list, making it suitable for various communication scenarios and ensuring practicality.

[0068] For example, the first message could be a registration request, which could include slice 2 (an optional example of the target slice information mentioned above) and a slice request element. The slice request element is used to request the allocation of a slice, such as requesting to detect the access status of slice 2 and, if slice 2 is allowed to access, to add slice 2 to the allowed slice list. The allowed slice list before adding slice 2 is an optional example of the first slice list mentioned above, and the allowed slice list after adding slice 2 is an optional example of the second slice list mentioned above.

[0069] Step S307: Based on the target slice, establish and switch to the second bearer.

[0070] Optionally, if the second slice list is obtained and includes information on allowed slices, and the information on allowed slices includes information on the target slice, then the target slice is allowed to be accessed. Then, the second bearer can be established and switched to based on the target slice.

[0071] like Figure 4 As shown, Figure 4 This is a schematic diagram of an application process in an embodiment of this disclosure. Taking IMS service as the service and UE as the terminal, the first bearer is established via Wi-Fi, such as an IMS PDN, and the second bearer is established via a 5G cellular network, such as an IMS PDU, as an example. The network may also include a 5G core network, a 4G core network, and a 5G base station. The process includes the following steps: S401, the UE sends an initial registration request to the 5G core network.

[0072] S402, the 5G core network sends a registration acceptance message to the UE (carrying the allowed slice list (including slice 1) and the rejected slice list (including slice 2)).

[0073] The allowed slice list is an optional example of the first slice list mentioned above, and slice 1 included in the allowed slice list can be an optional example of the information of the allowed slices included in the first slice list. Slice 1 is allowed to access.

[0074] Slice 2 in the rejected slice list can be an example of a slice that is not allowed access. If slice 2 is indicated to be associated with an IMSPDN, then slice 2 can be an optional example of the target slice mentioned above.

[0075] S403, Wi-Fi signal is good, IMS needs to switch to Wi-Fi, UE determines to establish IMS bearer through Wi-Fi.

[0076] S404, UE initiates the establishment of IMS PDN based on ePDG to 4G core network.

[0077] S405 and 4G core network reported successful IMS PDN establishment, carrying slice 2.

[0078] Optionally, the IMS PDN established in S404 and S405 is an optional example of the first bearer mentioned above. The first bearer is then associated with slice 2.

[0079] S406, UE confirms that all subsequent IMS services will be implemented via Wi-Fi.

[0080] S407, Using IMS services.

[0081] S408: The UE determines that the Wi-Fi signal has deteriorated or been turned off and needs to switch to the 5G cellular network. Slice 2 is not in the allowed slice list, so it requests slice 2 through the registration process.

[0082] S409, the UE sends a registration request message to the 5G core network (carrying slice request information and slice 2 information).

[0083] The S410 and 5G core network determined that the number of users using slice 2 had not reached the maximum number, and therefore allowed the use of slice 2.

[0084] S411, the 5G core network sends a registration acceptance message to the UE (carrying a list of allowed slices (including slice 1 and slice 2)).

[0085] Optionally, the allowed slice list carried in the registration acceptance message can be an example of the second slice list mentioned above. This step can be an example of updating the first slice list to obtain the second slice list.

[0086] S412, UE determines that slice 2 is in the list of allowed slices.

[0087] S413, The UE initiates a request to the 5G core network to establish an IMS PDU. The request includes information on (type (indicating handover) slice 2).

[0088] Among them, IMS PDU is an optional example of the second bearer mentioned above.

[0089] S414, Switch.

[0090] The S415 and 5G core network indicate to the UE that the IMS PDU handover was successful.

[0091] S416, Maintain IMS services.

[0092] In other words, when slice 2 associated with the IMS PDN established on Wi-Fi is not in the list of allowed slices notified by the 5G network, a request is made to the network through an update registration to allow slice 2 to access.

[0093] For example, when it is necessary to switch the IMS PDN established on Wi-Fi to the 5G network, and the slice associated with the IMS PDN is not in the allowed slice list, the terminal can initiate a registration request, carrying a slice request information element, which includes the slice associated with the IMS PDN.

[0094] For example, if the network includes "slice associated with IMS PDN" in the list of allowed slices carried in the registration acceptance message, the switching process continues.

[0095] For example, if a terminal successfully establishes an IMS PDN via Wi-Fi, it can identify that the slice associated with the IMS PDN is not in the allowed slice list, and then initiate a registration request carrying a slice request element, which includes the slice associated with the IMS PDN.

[0096] In this embodiment, by determining the target slice associated with the first bearer, where the first bearer cannot sustain services, and by determining the conditions met based on the target slice, wherein the conditions indicate that triggering a handover to the second bearer is not supported, the second bearer is used to maintain services, the first and second bearers are established through different networks, and a handover to the second bearer is established based on the target slice, service continuity can be effectively maintained, thereby improving service performance. By obtaining a first slice list, which includes information on allowed access slices, and by determining whether the target slice is allowed to access based on the target slice information and the information on allowed access slices, and by determining whether the conditions are met if the target slice is not allowed to access, it is possible to accurately and quickly determine whether a handover to the second bearer can be initiated based on the target slice, thus improving handover efficiency.

[0097] Figure 5 This is a flowchart illustrating another communication method provided in an embodiment of the present disclosure.

[0098] The communication method provided in this embodiment can be applied in a terminal. Optionally, the entity executing the communication method in this embodiment can be, for example, a terminal or a chip. The chip can be deployed in the terminal or in any other possible device, without limitation.

[0099] like Figure 5 As shown, the communication method includes: Step S501: Determine the target slice associated with the first bearer, wherein the first bearer is an unsustainable service.

[0100] Step S502: Based on the target slice, determine the conditions that are met, where the conditions indicate that triggering a switch to the second bearer is not supported. The second bearer is used to maintain services, and the first and second bearers are established through different networks.

[0101] The descriptions of S501-S502 can be found in the above embodiments, and will not be repeated here.

[0102] Step S503: Send a second message, wherein the second message is used to request the establishment and switching to the second bearer, and the second message includes: information about the target slice.

[0103] In other words, if it is determined based on the target slice that the terminal or chip does not support triggering a handover to the second bearer, a second message is still sent to the network. The second message is used to request the establishment and handover to the second bearer. The second message includes information about the target slice.

[0104] Optionally, the second message may be, for example, a PDU establishment request message.

[0105] Optionally, the network can receive the second message and check whether the target slice is allowed to access based on the information of the target slice in the second message. If so, the network initiates a handover, and after the handover is successful, sends a third message to the terminal. The third message is used to indicate that the handover to the second bearer has been successful.

[0106] Optionally, the third message may be, for example, a PDU establishment response message.

[0107] Step S504: Receive a third message, wherein the third message is used to indicate that the switch to the second bearer has been successful.

[0108] Optionally, upon receiving a third message, the terminal determines that it has successfully switched to the second bearer. In this case, services can be provided through the second bearer to maintain service continuity.

[0109] In other words, in this embodiment, if it is determined that the target slice does not support triggering a switch to the second bearer, the target slice associated with the first bearer is not processed. Instead, the process of establishing and switching to the second bearer is initiated directly, which can greatly improve the timeliness of the switch.

[0110] like Figure 6 As shown, Figure 6This is another application flow diagram in this disclosure embodiment. Taking the service as IMS service and the terminal as UE, the first bearer is established via Wi-Fi, such as an IMS PDN, and the second bearer is established via a 5G cellular network, such as an IMS PDU, as an example. The network may also include a 5G core network, a 4G core network, and a 5G base station. The steps include the following: S601, the UE sends an initial registration request to the 5G core network.

[0111] S602, the 5G core network sends a registration acceptance message to the UE (carrying the allowed slice list (including slice 1) and the rejected slice list (including slice 2)).

[0112] The allowed slice list is an optional example of the first slice list mentioned above, and slice 1 included in the allowed slice list can be an optional example of the information of the allowed slices included in the first slice list. Slice 1 is allowed to access.

[0113] Slice 2 in the rejected slice list can be an example of a slice that is not allowed access. If slice 2 is indicated to be associated with an IMSPDN, then slice 2 can be an optional example of the target slice mentioned above.

[0114] S603, Wi-Fi signal is good, IMS needs to switch to Wi-Fi, UE determines to establish IMS bearer through Wi-Fi.

[0115] S604, UE initiates the establishment of IMS PDN based on ePDG to 4G core network.

[0116] The S605 and 4G core network reported that the IMS PDN was successfully established, carrying slice 2.

[0117] Optionally, the IMS PDN established in S604 and S605 is an optional example of the first bearer mentioned above. The first bearer is then associated with slice 2.

[0118] S606 and UE have determined that all subsequent IMS services will be implemented via Wi-Fi.

[0119] S607, Using IMS services.

[0120] S608: The UE determines that the Wi-Fi signal has deteriorated or been turned off and needs to switch to the 5G cellular network. Slice 2 is not in the list of allowed slices, so the handover process is initiated.

[0121] S609, the UE sends a request message to the 5G core network (request to establish an IMS PDU, type (indicating handover), slice 2 information).

[0122] The S610 and 5G core network determined that the number of users using slice 2 had not reached the maximum number, and therefore allowed the use of slice 2.

[0123] S611, Switch.

[0124] The S612 and 5G core network indicate to the UE that the IMS PDU handover was successful.

[0125] S613, Maintain IMS services.

[0126] In other words, when it is necessary to switch the IMS PDN established on Wi-Fi to the 5G network, and the slice associated with the IMS PDN is not in the allowed slice list, the terminal can still initiate the handover process, carrying the associated slice. If the network allows access based on that slice, the handover is successful, and service continuity can be maintained.

[0127] Optionally, the request message above may not include information about slice 2.

[0128] In this embodiment, by determining the target slice associated with the first bearer (where the first bearer cannot sustain services) and determining, based on the target slice, conditions are met, where the conditions indicate that triggering a handover to the second bearer is not supported. The second bearer is used to maintain services, and the first and second bearers are established through different networks. A second message is sent, requesting the establishment and handover to the second bearer, and this second message includes information about the target slice. A third message is received, indicating that the handover to the second bearer has been successful. This effectively maintains service continuity and improves service performance. It also improves the timeliness of the handover, greatly ensuring service continuity.

[0129] Figure 7 This is a schematic diagram of the structure of a communication device provided in an embodiment of the present disclosure.

[0130] like Figure 7 As shown, the communication device 70 includes: The first determining module 701 is used to determine the target slice associated with the first bearer, wherein the first bearer is an unsustainable service.

[0131] The second determining module 702 is used to determine the conditions that are met based on the target slice. The conditions indicate that triggering a switch to the second bearer is not supported. The second bearer is used to maintain services. The first bearer and the second bearer are established through different networks.

[0132] Processing module 703 is used to create and switch to the second bearer based on the target slice.

[0133] Optionally, in some embodiments of this disclosure, the second determining module 702 is used for: Obtain the first slice list, which is allocated during initial registration and includes information on slices that are allowed to be accessed; Based on the information of the target slice and the information of the allowed slices, determine whether the target slice is allowed to be accessed; If the target slice is not allowed to be accessed, determine if the conditions are met.

[0134] Optionally, in some embodiments of this disclosure, the second determining module 702 is further configured to: Obtain the second slice list, which includes information about the slices that are allowed to be accessed; The information of the allowed access slices in the second slice list has been determined to include: the information of the target slice.

[0135] Optionally, in some embodiments of this disclosure, the second determining module 702 is used for: Send a first message, which is used to request an update to the registration. The first message includes: information about the target slice, which is used to update the first slice list to obtain the second slice list. Receive the second slice list.

[0136] Optionally, in some embodiments of this disclosure, the second determining module 702 is used for: Retrieve the second slice list from local storage, wherein the second slice list is obtained by updating the first slice list when the first bearer is established.

[0137] Optionally, in some embodiments of this disclosure, the processing module 703 is used for: Send a second message, wherein the second message is used to request the establishment and switching to the second bearer, and the second message includes: information about the target slice; Receive a third message, which indicates that the switch to the second bearer has been successful.

[0138] Optionally, in some embodiments of this disclosure, the service is Internet Protocol (IP) Multimedia Subsystem (IMS) service.

[0139] Optionally, in some embodiments of this disclosure, the first bearer includes a packet data network (PDN).

[0140] Optionally, in some embodiments of this disclosure, the second bearer includes a Protocol Data Unit (PDU).

[0141] It should be noted that the foregoing explanation of the communication method embodiment also applies to the communication device of this embodiment, and will not be repeated here.

[0142] In this embodiment, by determining the target slice associated with the first bearer, where the first bearer cannot sustain services, and by determining conditions based on the target slice, wherein the conditions indicate that triggering a handover to the second bearer is not supported, the second bearer is used to sustain services, the first and second bearers are established through different networks, and the handover to the second bearer is established and performed based on the target slice, service continuity can be effectively maintained, thereby improving service performance.

[0143] To implement the above embodiments, this disclosure also proposes a communication device, including: a processor and a memory communicatively connected to the processor; the memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory to implement the method provided in the foregoing embodiments.

[0144] Alternatively, in some embodiments, the communication device may be, for example, a terminal or a chip, without limitation.

[0145] Figure 8 A block diagram of an exemplary communication device suitable for implementing embodiments of the present disclosure is shown. Figure 8 The communication device 12 shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments disclosed herein. The communication device may be, for example, a terminal, and there is no limitation thereto.

[0146] like Figure 8 As shown, the communication device 12 is presented in the form of a general-purpose computing device. The components of the communication device 12 may include, but are not limited to: one or more processors or processing units 16, memory 28, and bus 18 connecting different system components (including memory 28 and processing unit 16).

[0147] Bus 18 represents one or more of several bus architectures, including a memory bus or memory controller, a peripheral bus, a graphics acceleration port, a processor, or a local bus using any of the various bus architectures. Examples of these architectures include, but are not limited to, the Industry Standard Architecture (ISA) bus, the Micro Channel Architecture (MAC) bus, the Enhanced ISA bus, the Video Electronics Standards Association (VESA) local bus, and the Peripheral Component Interconnect (PCI) bus.

[0148] The communication device 12 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by the communication device 12, including volatile and non-volatile media, and removable and non-removable media.

[0149] Memory 28 may include computer system readable media in the form of volatile memory, such as Random Access Memory (RAM) 30 and / or cache 32. Communication device 12 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, storage system 34 may be used to read and write non-removable, non-volatile magnetic media (… Figure 8 Not shown; usually referred to as a "hard drive".

[0150] although Figure 8 As not shown, a disk drive for reading and writing to a removable non-volatile disk (e.g., a "floppy disk") and an optical disc drive for reading and writing to a removable non-volatile optical disc (e.g., a compact disc read-only memory (CD-ROM), a digital video disc read-only memory (DVD-ROM), or other optical media) may be provided. In these cases, each drive may be connected to bus 18 via one or more data media interfaces. Memory 28 may include at least one program product having a set (e.g., at least one) of program modules configured to perform the functions of the embodiments of this disclosure.

[0151] A program / utility 40 having a set (at least one) of program modules 42 may be stored, for example, in memory 28. Such program modules 42 include, but are not limited to, an operating system, one or more application programs, other program modules, and program data. Each or some combination of these examples may include an implementation of a network environment. Program modules 42 typically perform the functions and / or methods described in the embodiments of this disclosure.

[0152] The communication device 12 can also communicate with one or more external devices 14 (e.g., keyboard, pointing device, display 24, etc.), and with one or more devices that enable human interaction with the communication device 12, and / or with any device that enables the communication device 12 to communicate with one or more other computing devices (e.g., network card, modem, etc.). This communication can be performed via input / output (I / O) interface 22. Furthermore, the communication device 12 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 20. As shown, network adapter 20 communicates with other modules of the communication device 12 via bus 18. It should be understood that, although not shown in the figures, other hardware and / or software modules can be used in conjunction with the communication device 12, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0153] The processing unit 16 executes various functional applications and data processing by running programs stored in the memory 28, such as implementing the methods mentioned in the foregoing embodiments.

[0154] To implement the above embodiments, this disclosure also proposes a chip, including: the chip includes processing circuitry configured to perform the methods provided in the foregoing embodiments.

[0155] Figure 9 This is a schematic diagram of the structure of a chip according to an embodiment of this disclosure. See also... Figure 9 The diagram shown is a schematic representation of the structure of chip 900, but it is not limited to this.

[0156] Chip 900 includes processing circuit 901 and interface circuit 902. Interface circuit 902 is used to read instructions and send instructions to processing circuit 901 so that processing circuit 901 executes the method in the above embodiment.

[0157] Optionally, such as Figure 10 As shown, Figure 10 This is a schematic diagram of another chip structure proposed in an embodiment of this disclosure. The chip 900 may further include: a memory 903 for storing instructions, and an interface circuit 902 for reading the instructions stored in the memory 903.

[0158] Optionally, the interface circuit 902 is connected to the memory 903. The interface circuit 902 can be used to receive signals from the memory 903 or other devices, and can also be used to send signals to the memory 903 or other devices. For example, the interface circuit 902 can read instructions stored in the memory 903 and send those instructions to the processing circuit 901.

[0159] Optionally, the number of memories 903 can be one or more. The number of interface circuits 902 can also be one or more.

[0160] In some embodiments, the interface circuit 902 performs at least one of the communication steps such as sending and / or receiving in the above method, and the processing circuit 901 performs other steps.

[0161] In some embodiments, the terms interface circuit, interface, transceiver pin, transceiver, etc., can be used interchangeably.

[0162] Alternatively, all or part of the memory 903 may be located outside of the chip 900.

[0163] To implement the above embodiments, this disclosure also proposes a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the methods proposed in the foregoing embodiments of this disclosure.

[0164] To implement the above embodiments, this disclosure also proposes a computer program product that, when instructions in the computer program product are executed by a processor, performs the method proposed in the foregoing embodiments of this disclosure. The collection, storage, use, processing, transmission, provision, and disclosure of user personal information involved in this disclosure all comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0165] It should be noted that personal information collected from users should be used for legitimate and reasonable purposes and should not be shared or sold outside of these legitimate uses. Furthermore, such collection / sharing should only be conducted after receiving the user's informed consent, including but not limited to notifying the user to read the user agreement / user notice and sign an agreement / authorization that includes authorization of relevant user information before the user uses the function. In addition, any necessary steps must be taken to protect and safeguard access to such personal information data and ensure that others with access to personal information data comply with their privacy policies and procedures.

[0166] This disclosure is intended to provide implementation schemes for users to selectively prevent the use or access to their personal information data. Specifically, this disclosure is intended to provide hardware and / or software to prevent or block access to such personal information data. Once personal information data is no longer needed, risks can be minimized by restricting data collection and deleting data. Furthermore, where applicable, such personal information is de-identified to protect user privacy.

[0167] In the foregoing descriptions of the embodiments, the terms "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., refer to specific features, structures, materials, or characteristics described in connection with that embodiment or example, which are included in at least one embodiment or example of this disclosure. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0168] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this disclosure, "a plurality of" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0169] Any process or method description in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or more executable instructions for implementing custom logic functions or processes, and the scope of preferred embodiments of this disclosure includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functions involved, as will be understood by those skilled in the art to which embodiments of this disclosure pertain.

[0170] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-included system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of computer-readable media include: an electrical connection having one or more wires (electronic device), a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Alternatively, the computer-readable medium may be paper or other suitable media on which the program can be printed, since the program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in a computer memory.

[0171] It should be understood that various parts of this disclosure can be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0172] Those skilled in the art will understand that all or part of the steps of the methods in the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, the program includes one or a combination of the steps of the method embodiments.

[0173] Furthermore, the functional units in the various embodiments of this disclosure can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into a module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium.

[0174] The storage medium mentioned above can be a read-only memory, a disk, or an optical disk, etc. Although embodiments of the present disclosure have been shown and described above, it is to be understood that the above embodiments are exemplary and should not be construed as limiting the present disclosure. Those skilled in the art can make changes, modifications, substitutions, and variations to the above embodiments within the scope of the present disclosure.

Claims

1. A communication method, characterized in that, include: Determine the target slice associated with the first bearer, wherein the first bearer cannot maintain services; Based on the target slice, conditions are determined to be met, wherein the conditions indicate that triggering a handover to the second bearer is not supported, the second bearer is used to maintain the service, and the first bearer and the second bearer are established through different networks; Based on the target slice, establish and switch to the second bearer; The step of determining whether the conditions are met based on the target slice includes: Obtain the first slice list, wherein the first slice list is allocated during initial registration, and the first slice list includes: information on slices that are allowed to access; Based on the information of the target slice and the information of the allowed access slice, determine whether the target slice is allowed to be accessed; If the target slice is not allowed to be accessed, it is determined that the condition is met; The method further includes: Obtain a second slice list, wherein the second slice list includes: information on slices that are allowed to be accessed; The information of the allowed access slices in the second slice list includes: the information of the target slice.

2. The method according to claim 1, characterized in that, The process of obtaining the second slice list includes: Send a first message, wherein the first message is used to request an update to the registration, and the first message includes: information about the target slice, the information about the target slice being used to update the first slice list to obtain the second slice list; Receive the second slice list.

3. The method according to claim 1, characterized in that, The process of obtaining the second slice list includes: The second slice list is obtained from local storage, wherein the second slice list is obtained by updating the first slice list when the first bearer is established.

4. The method according to claim 1, characterized in that, The step of establishing and switching to the second bearer based on the target slice includes: Send a second message, wherein the second message is used to request the establishment and switching to the second bearer, and the second message includes: information about the target slice; A third message is received, wherein the third message is used to indicate that the switch to the second bearer has been successful.

5. The method according to any one of claims 1-4, characterized in that, The service in question is the Internet Protocol IP Multimedia Subsystem (IMS) service.

6. The method according to any one of claims 1-4, characterized in that, The first bearer includes: a packet data network (PDN).

7. The method according to any one of claims 1-4, characterized in that, The second bearer includes: Protocol Data Unit (PDU).

8. A communication device, characterized in that, include: The first determining module is used to determine the target slice associated with the first bearer, wherein the first bearer cannot maintain services; The second determining module is used to determine, based on the target slice, that a condition is met, wherein the condition indicates that triggering a switch to the second bearer is not supported, the second bearer is used to maintain the service, and the first bearer and the second bearer are established through different networks; The processing module is used to establish and switch to the second bearer based on the target slice; The second determining module is specifically used to obtain a first slice list, wherein the first slice list is allocated during initial registration and includes information on slices that are allowed to be accessed; Based on the information of the target slice and the information of the allowed access slice, determine whether the target slice is allowed to be accessed; If the target slice is not allowed to be accessed, it is determined that the condition is met; The second determining module is further configured to obtain a second slice list, wherein the second slice list includes: information on slices that are allowed to be accessed; The information of the allowed access slices in the second slice list includes: the information of the target slice.

9. A communication device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1-7.

11. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method of any one of claims 1-7.

12. A chip, said chip comprising a processing circuit and an interface circuit; wherein, The interface circuit is used to read instructions and sends the instructions to the processing circuit so that the processing circuit performs the method as described in any one of claims 1-7.

Images