Communication method, device, equipment, chip and medium

Abstract

The invention provides a communication method and device, equipment, a chip and a medium, and the communication method comprises the steps: determining a target slice associated with a first bearer, the first bearer cannot maintain a service, determining that a condition is satisfied according to the target slice, the condition represents that triggering switching to a second bearer is not supported, the second bearer is used for maintaining the service, and the second bearer is used for maintaining the service; the first bearer and the second bearer are established through different networks, and the second bearer is established and switched according to the target slice. Therefore, the service continuity can be effectively maintained so as to improve the service performance.

Description

Technical Field

[0001] The present disclosure relates to the field of communication technologies, and in particular to a communication method, apparatus, device, chip, and medium. Background Art

[0002] In a cellular network, a provider's service area is divided into multiple small geographic areas (or cells). Cellular networks provide services not only to mobile devices 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 over Wi-Fi while connected to a Wireless Fidelity (Wi-Fi) network, without relying on the mobile operator's cellular network. Summary of the Invention

[0003] The present disclosure aims to solve one of the technical problems in the related art at least to a certain extent.

[0004] To this end, the present disclosure proposes a communication method, apparatus, communication equipment, chip, computer-readable storage medium, and computer program product, which can effectively maintain business continuity to improve business performance.

[0005] An embodiment of the first aspect of the present disclosure proposes a communication method, including: determining a target slice associated with a first bearer, wherein the first bearer cannot maintain services; determining, based on the target slice, that a condition is satisfied, wherein the condition indicates that triggering switching 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. An embodiment of the second aspect of the present disclosure proposes a communication device, including: a first determination module, used to determine a target slice associated with a first bearer, wherein the first bearer cannot maintain services; a second determination module, used to determine, based on the target slice, whether a condition is satisfied, wherein the condition indicates that triggering switching 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, used to establish and switch to the second bearer based on the target slice. The third aspect embodiment of the present disclosure 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 communication method proposed in the above-mentioned aspect embodiment of the present disclosure.

[0006] The fourth embodiment of the present disclosure proposes a chip, which includes a processing circuit and an interface circuit; wherein the interface circuit is used to read instructions, and the interface circuit sends the instructions to the processing circuit so that the processing circuit executes the communication method proposed in the first embodiment of the present disclosure.

[0007] The fifth embodiment of the present disclosure proposes a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement the communication method as described above.

[0008] The communication method, apparatus, communication device, chip, computer-readable storage medium, and computer program product provided by the present disclosure determine a target slice associated with a first bearer, wherein the first bearer cannot maintain services, and determine, based on the target slice, whether a condition is satisfied, wherein the condition indicates that triggering switching to a second bearer is not supported, the second bearer is used to maintain services, the first bearer and the second bearer are established via different networks, and establish and switch to the second bearer based on the target slice. Thus, service continuity can be effectively maintained to improve service performance.

[0009] Additional aspects and advantages of the present disclosure will be given in part in the following description and in part will be obvious from the following description, or will be learned through practice of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0012] In the embodiments of the present disclosure, the communication device may be, for example, a terminal or a chip, which is not limited.

[0013] Figure 1 FIG. 1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present 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, the terminal 101 includes, for example, at least one of a mobile phone, a wearable device, an Internet of Things device, a car with communication capabilities, a smart car, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, and a wireless terminal in a smart home, but is not limited thereto.

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

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

[0017] In some embodiments, the access network device may be composed of a centralized unit (CU) and a distributed unit (DU), where the CU may also be referred to as a control unit. The CU-DU structure may be used to separate the protocol layers of the access network device, with some functions of the protocol layers being centrally controlled by the CU, and the remaining functions of some or all of the protocol layers being distributed in the DU, which is centrally controlled by the CU, but is not limited thereto.

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

[0019] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.

[0020] The following embodiments of the present disclosure can be applied to Figure 1 The communication system 100, or a portion thereof, is shown but is not limited thereto. Figure 1 The various entities shown are examples, and the communication system may include Figure 1 All or part of the subject, and may also include Figure 1 For other entities other than the above, the number and form of each entity are arbitrary, and the connection relationship between each entity is an example. The entities may be connected or not connected, and the connection may be in any way, which may be direct or indirect, and may be wired or wireless.

[0021] The embodiments of the present disclosure 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 (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (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 based on and extending these. Furthermore, multiple systems can be combined for application (for example, combining LTE or LTE-A with 5G).

[0022] Optionally, in a cellular network, the service area covered by a provider is divided into multiple small geographic areas (or cells). Cellular networks provide services not only to mobile devices 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 over Wi-Fi while connected to a Wireless Fidelity (Wi-Fi) network, without relying on the mobile operator's cellular network.

[0023] Optional, Internet Protocol‌ IP Multimedia Subsystem (IMS) Optionally, the core network device may include one or more network functions. Examples of network functions include: Evolved Packet Data Gateway (ePDG), which is used to handle non-3rd Generation Partnership Project (3GPP) access and provide users with access control, encryption, Packet Data Network (PDN) establishment and other functions for packet data services. Access and mobility management function (AMF). AMF is a logical node function on the core network side. It is the access point for the terminal and wireless core network control plane. It receives all connection and session-related information from user equipment and performs registration, connection, reachability, and mobility management. In addition, AMF provides a session management message transmission channel for terminal equipment and session management function (SMF) equipment, and provides 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 (configuredNSSAI) through messages such as successful registration. Slicing (or network slicing) is a core technology that uses virtualization technology to divide a single physical network into multiple logically isolated virtual subnets. Each subnet can independently configure resources, performance, and security policies, achieving "one network for multiple uses."

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

[0026] In the related art, the terminal successfully registers on the cellular network. Due to temporary reasons (for example, the number of temporary users accessing the slice is too large, causing the network to start the congestion mechanism), the network will notify the terminal that the allowed slice list contains: slice 1, but not slice 2. Due to reasons such as good Wi-Fi signal or VoWIFI priority, the terminal registers for IMS through Wi-Fi, and the terminal establishes an IMS PDN through Wi-Fi. At this time, the network notifies that the associated slice is slice 2, and then the terminal makes a call through Wi-Fi. During the call, the Wi-Fi signal deteriorates (for example, Wi-Fi is turned off). For business continuity, the IMS PDN can be switched to the cellular network. However, since slice 2 is not in the allowed slice list, the terminal cannot initiate a switch, resulting in a dropped call, and at this time slice 2 may have been allowed to access (for example, the number of users on slice 2 has decreased).

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

[0028] Figure 2 A flow chart of a communication method provided by an embodiment of the present disclosure.

[0029] The communication method provided in this embodiment can be applied in a terminal. Optionally, the execution subject of the communication method in this embodiment can be, for example, a terminal or a chip, wherein 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 a target slice associated with a first bearer, wherein the first bearer cannot maintain service.

[0031] The first bearer may be a PDN established through a Wi-Fi network, and there is no limitation on this.

[0032] Among them, the slice associated with the first bearer can be called a target slice.

[0033] Optionally, the service may be, for example, an IMS service. Of course, the service may also be any other possible type, such as a positioning service, a sensing service, etc., without limitation. The first bearer for the IMS service may also be referred to as an IMS PDN.

[0034] Optionally, the first bearer cannot maintain the service, which can be understood as the first bearer not supporting the continuity of the service, for example, the signal quality of the Wi-Fi network is poor, the Wi-Fi network is shut down, and so on.

[0035] Optionally, when it is determined that the first bearer cannot maintain the service, the terminal 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 subsequent description.

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

[0037] Optionally, an example of the "process of establishing a first bearer" is as follows: if the terminal has a need to use a service through a Wi-Fi network, a first bearer can be established through the Wi-Fi network, and the first bearer can be used to carry service-related data.

[0038] Optionally, the terminal may establish a first bearer through the Wi-Fi network when determining that the Wi-Fi network signal is good, and the first bearer may be used to carry service-related data. For example, the terminal may interact with the ePDG to establish the first bearer, and the first bearer may be used for the service.

[0039] Optionally, during the process of establishing the first bearer through the Wi-Fi network, the terminal may send a request message to the network to request establishment of the first bearer through the ePDG. The network may configure an associated slice for the first bearer and send a response message to the terminal to indicate that the first bearer is successfully established and to indicate the slice associated with the first bearer. The network may be a core network.

[0040] Optionally, after determining that the first bearer is successfully established, the terminal can use the service through the first bearer. Then, during the use of the service, if it is determined 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: Determine whether a condition is met based on the target slice, where the condition indicates that triggering switching 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.

[0042] Optionally, the terminal may 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 may determine whether a handover to the second bearer can be triggered (or initiated) based on the target slice.

[0043] The second bearer may be a protocol data unit (PDU) established via a cellular network. The first bearer and the second bearer are established via different networks. The second network may be, for example, a cellular network, without limitation. The second bearer is used to maintain services. In other words, if the first bearer cannot maintain services, and the target slice associated with the first bearer determines that triggering a handover to the second bearer is not supported, countermeasures can be implemented to enable a timely handover to ensure service continuity.

[0044] Optionally, the terminal may determine whether the target slice is allowed to access based on the information of the target slice. If the target slice is not allowed to access, it is determined that the target slice meets the conditions. Alternatively, the terminal may detect whether it is possible to initiate a handover from the first bearer to the second bearer based on the target slice. If it is not possible to initiate a handover from the first bearer to the second bearer based on the target slice, it is determined that the conditions are met. There is no restriction on this.

[0045] Step S203: Establish and switch to the second bearer according to the target slice.

[0046] Optionally, in the case where it is determined that the first bearer cannot maintain the service, the target slice associated with the first bearer can be determined, and the conditions are determined to be met based on the target slice, that is, it is determined that triggering switching to the second bearer is not supported, and then the second bearer can be established and switched based on the target slice to maintain service continuity through the second bearer.

[0047] In this embodiment, a target slice associated with a first bearer is determined, wherein the first bearer cannot maintain services, and a condition is determined based on the target slice, wherein the condition indicates that triggering handover to a second bearer is not supported, the second bearer is used to maintain services, the first bearer and the second bearer are established via different networks, and then a handover to the second bearer is established based on the target slice. In this way, service continuity can be effectively maintained to improve service performance.

[0048] Figure 3 A flowchart of another communication method provided by an embodiment of the present disclosure.

[0049] The communication method provided in this embodiment can be applied in a terminal. Optionally, the execution subject of the communication method in this embodiment can be, for example, a terminal or a chip, wherein 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 a target slice associated with a first bearer, wherein the first bearer cannot maintain service.

[0051] The description of S301 can be found in the above embodiment and will not be repeated here.

[0052] Step S302: Obtain a first slice list, where the first slice list includes: information of slices that are allowed to be accessed.

[0053] The first slice list is allocated during initial registration. The first slice list includes information about several slices. The "slice" specifically refers to the slice that is allowed to be accessed.

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

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

[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 slices allowed to be accessed.

[0057] Optionally, after obtaining the first slice list, it can be determined whether the target slice is allowed to be accessed based on the information of the target slice and the information of the slices allowed to be accessed. The information of the target slice can be, for example, the NSSAI of the target slice. For example, it can be determined whether the NSSAI of the target slice and the NSSAI of the slice allowed to be accessed are the same. If they are the same, it is determined that the target slice is allowed to be accessed; if they are different, it is determined that the target slice is not allowed to be accessed.

[0058] Optionally, S302 and S303 may not be performed, and access to the target slice may be determined based on the "information on the slice not allowed to be accessed" included in the denied slice list indicated by the network. The "information on the slice not allowed to be accessed" may be, for example, the NSSAI of the slice not allowed to be accessed. For example, it may be determined whether the NSSAI of the target slice and the NSSAI of the slice not allowed to be accessed are the same. If they are the same, it is determined that access to the target slice is not allowed; if they are different, it is determined that access to the target slice is allowed.

[0059] Step S304: When the target slice is not allowed to access, determine whether a condition is met, where the condition indicates that triggering switching 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.

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

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

[0062] Step S306: Determine whether the information of the slices allowed to be accessed in the second slice list includes information of the target slice.

[0063] That is, if it is determined that the target slice is not allowed to be accessed, a second slice list may be obtained, wherein the second slice list includes information about slices allowed to be accessed, and the information about slices allowed to be accessed includes information about the target slice. That is, if the second slice list is obtained, and the second slice list includes information about slices allowed to be accessed, and the information about slices allowed to be accessed includes information about the target slice, then access to the target slice is allowed.

[0064] Optionally, the second slice list can also be called an allowed slice list. The second slice list can be obtained by updating the first slice list. For example, when it is determined that the information of the allowed access 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 to obtain a 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, thereby greatly improving the efficiency of obtaining the second slice list. When the second slice list is obtained, it means that the target slice is allowed to access, which can greatly improve the efficiency of switching.

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

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

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

[0069] Step S307: Establish and switch to the second bearer according to the target slice.

[0070] Optionally, when the second slice list is obtained, and the second slice list includes: information on slices that are allowed to be accessed, and the information on slices that are allowed to be accessed includes: information on the target slice, it means that the target slice is allowed to be accessed, and then, the second bearer can be established and switched according to the target slice.

[0071] like Figure 4 As shown, Figure 4 This is a schematic diagram of an application flow in an embodiment of the present disclosure. For example, the service is an IMS service, the terminal is a 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. The network may also include a 5G core network, a 4G core network, and a 5G base station. The following steps are included: 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 an allowed slice list (including slice 1) and a rejected slice list (including slice 2)).

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

[0074] Among them, the slice 2 included in the rejected slice list may be not allowed to be accessed. If the slice 2 is indicated to be associated with the IMS PDN, the slice 2 may be an optional example of the above-mentioned target slice.

[0075] S403: The Wi-Fi signal is good, the IMS needs to be switched to Wi-Fi, and the UE determines to establish an IMS bearer through Wi-Fi.

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

[0077] S405. The 4G core network reports that the IMS PDN is successfully established and carries slice 2.

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

[0079] S406: The UE determines that all subsequent IMS services are implemented through Wi-Fi.

[0080] S407: Use IMS services.

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

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

[0083] S410, the 5G core network determines that the number of users using slice 2 has not reached the maximum number and allows the use of slice 2.

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

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

[0086] S412. The UE determines that slice 2 is in the allowed slice list.

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

[0088] The IMS PDU is an optional example of the second bearer.

[0089] S414, switch.

[0090] S415. The 5G core network indicates to the UE that the IMS PDU switching is successful.

[0091] S416. Maintain IMS services.

[0092] That is to say, when slice 2 associated with the IMS PDN established on Wi-Fi is not in the list of slices allowed by the 5G network notification, access to slice 2 is allowed by requesting the network through updated registration.

[0093] For example, when the IMS PDN established on Wi-Fi needs to be switched 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 element, which includes the slice associated with the IMS PDN.

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

[0095] For example, when the IMS PDN is successfully established through Wi-Fi, the terminal can identify that the slice associated with the IMS PDN is not in the allowed slice list, that is, initiate a registration request, carrying a slice request information element, which includes the slice associated with the IMS PDN.

[0096] In this embodiment, by determining the target slice associated with the first bearer, wherein the first bearer cannot maintain the service, and according to the target slice, determining whether the condition is met, wherein the condition indicates that triggering switching to the 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 according to the target slice, establishing and switching to the second bearer. In this way, service continuity can be effectively maintained to improve service performance. By obtaining the first slice list, wherein the first slice list includes: information of slices allowed to be accessed, and according to the information of the target slice and the information of the slices allowed to be accessed, determining whether the target slice is allowed to be accessed, and determining whether the condition is met when the target slice is not allowed to be accessed. In this way, it is possible to accurately and quickly determine whether switching to the second bearer can be initiated based on the target slice, thereby improving the efficiency of switching.

[0097] Figure 5 A flowchart of another communication method provided by an embodiment of the present disclosure.

[0098] The communication method provided in this embodiment can be applied in a terminal. Optionally, the execution subject of the communication method in this embodiment can be, for example, a terminal or a chip, wherein 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 a target slice associated with a first bearer, wherein the first bearer cannot maintain service.

[0100] Step S502: Determine whether a condition is met based on the target slice, where the condition indicates that triggering switching 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.

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

[0102] Step S503: Send a second message, where the second message is used to request to establish and switch to a second bearer, and the second message includes: information of the target slice.

[0103] That is to say, if it is determined based on the target slice that the terminal or chip does not support triggering switching to the second bearer, a second message is still sent to the network. The second message is used to request to establish and switch to the second bearer. The second message includes: information about the target slice.

[0104] Optionally, the second message is, 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 be accessed based on the information of the target slice in the second message. If so, the network initiates switching, and after the switching is successful, sends a third message to the terminal. The third message is used to indicate that the switch to the second bearer has been successful.

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

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

[0108] Optionally, when receiving the third message, the terminal determines that it has successfully switched to the second bearer. At this time, the service can be implemented through the second bearer to maintain service continuity.

[0109] That is to say, in this embodiment, when it is determined based on the target slice that triggering switching to the second bearer is not supported, the target slice associated with the first bearer is not processed, but the process of establishing and switching to the second bearer is directly initiated. Therefore, the timeliness of the switching can be greatly improved.

[0110] like Figure 6 As shown, Figure 6This is another application flow diagram in an embodiment of the present disclosure. For example, the service is an IMS service, the terminal is a 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. The network may also include a 5G core network, a 4G core network, and a 5G base station. The following steps are included: 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 an allowed slice list (including slice 1) and a rejected slice list (including slice 2)).

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

[0113] Among them, the slice 2 included in the rejected slice list may be not allowed to be accessed. If the slice 2 is indicated to be associated with the IMS PDN, the slice 2 may be an optional example of the above-mentioned target slice.

[0114] S603: The Wi-Fi signal is good, the IMS needs to be switched to Wi-Fi, and the UE determines to establish an IMS bearer through Wi-Fi.

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

[0116] S605. The 4G core network reports that the IMS PDN is successfully established and carries slice 2.

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

[0118] S606: The UE determines that all subsequent IMS services are implemented through Wi-Fi.

[0119] S607: Use IMS services.

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

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

[0122] S610, the 5G core network determines that the number of users using slice 2 has not reached the maximum number and allows the use of slice 2.

[0123] S611, switch.

[0124] S612. The 5G core network indicates to the UE that the IMS PDU switching is successful.

[0125] S613. Maintain IMS services.

[0126] In other words, when an IMS PDN established on Wi-Fi needs to be switched to a 5G network, and the slice associated with the IMS PDN is not in the list of allowed slices, the terminal can still initiate the handover process and carry the associated slice. If the network allows access based on the slice, the handover is successful and service continuity can be maintained.

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

[0128] In this embodiment, a target slice associated with a first bearer is determined, wherein the first bearer cannot maintain the service, and based on the target slice, a condition is determined to be satisfied, wherein the condition indicates that triggering switching 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 a second message is sent, wherein the second message is used to request establishment and switching to the second bearer, the second message includes: information about the target slice, and a third message is received, wherein the third message is used to indicate that the switching to the second bearer has been successful. In this way, service continuity can be effectively maintained to improve service performance. It can also improve the timeliness of switching, greatly ensuring service continuity.

[0129] Figure 7 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 determination module 701 is used to determine a target slice associated with a first bearer, wherein the first bearer cannot maintain service.

[0131] The second determination module 702 is used to determine whether a condition is met based on the target slice, wherein the condition indicates that triggering switching 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.

[0132] The processing module 703 is configured to establish and switch to a second bearer according to the target slice.

[0133] Optionally, in some embodiments of the present disclosure, the second determining module 702 is configured to: Obtaining a first slice list, where the first slice list is allocated during initial registration, and the first slice list includes: information about slices that are allowed to be accessed; Determine whether access to the target slice is allowed based on the information of the target slice and the information of the slices allowed to be accessed; In the event that the target slice is not allowed to be accessed, it is determined that the condition is met.

[0134] Optionally, in some embodiments of the present disclosure, the second determining module 702 is further configured to: Obtaining a second slice list, wherein the second slice list includes: information of slices that are allowed to be accessed; Determine that the information of the slices allowed to be accessed in the second slice list includes: information of the target slice.

[0135] Optionally, in some embodiments of the present disclosure, the second determining module 702 is configured to: Sending a first message, where the first message is used to request registration update, and the first message includes: information of a target slice, where the information of the target slice is used to update the first slice list to obtain a second slice list; Receive a second slice list.

[0136] Optionally, in some embodiments of the present disclosure, the second determining module 702 is configured to: A 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.

[0137] Optionally, in some embodiments of the present disclosure, the processing module 703 is configured to: Sending a second message, where the second message is used to request establishment and switching to a second bearer, and the second message includes: information about a target slice; A third message is received, where the third message is used to indicate that the handover to the second bearer has been successful.

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

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

[0140] Optionally, in some embodiments of the present disclosure, the second bearer includes: a protocol data unit PDU.

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

[0142] In this embodiment, a target slice associated with a first bearer is determined, wherein the first bearer cannot maintain services, and a condition is determined based on the target slice, wherein the condition indicates that triggering handover to a second bearer is not supported, the second bearer is used to maintain services, the first bearer and the second bearer are established via different networks, and then a handover to the second bearer is established based on the target slice. In this way, service continuity can be effectively maintained to improve service performance.

[0143] In order to implement the above embodiments, the present 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 by the above embodiments.

[0144] Optionally, in some embodiments, the communication device may be, for example, a terminal or a chip, which is not limited.

[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 only an example and should not limit the functionality and scope of use of the embodiments of the present disclosure. The communication device may be, for example, a terminal, which is not limited thereto.

[0146] like Figure 8 As shown, the communication device 12 is implemented as a general-purpose computing device. Components of the communication device 12 may include, but are not limited to, one or more processors or processing units 16, a memory 28, and a bus 18 that connects various system components (including the memory 28 and the processing unit 16).

[0147] Bus 18 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor, or a local bus using any of a variety of 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 Interconnection (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, removable and non-removable media.

[0149] The 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. The communication device 12 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, the storage system 34 may be configured to read and write non-removable, non-volatile magnetic media ( Figure 8 Not shown, usually called a "hard drive").

[0150] although Figure 8 Although not shown, a disk drive for reading and writing to a removable non-volatile disk (e.g., a floppy disk) and an optical disk drive for reading and writing to a removable non-volatile optical disk (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 various embodiments of the present 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 of which, or some combination thereof, may include an implementation of a network environment. Program modules 42 generally implement the functions and / or methodologies described in the embodiments of the present disclosure.

[0152] The communication device 12 can also communicate with one or more external devices 14 (e.g., a keyboard, pointing device, display 24, etc.), one or more devices that enable human interaction with the communication device 12, and / or any device that enables the communication device 12 to communicate with one or more other computing devices (e.g., a network card, a modem, etc.). This communication can occur via an input / output (I / O) interface 22. Furthermore, the communication device 12 can communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN), and / or a public network such as the Internet) via a network adapter 20. As shown, the network adapter 20 communicates with the other modules of the communication device 12 via the bus 18. It should be understood that, although not shown, other hardware and / or software modules may 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 the programs stored in the memory 28 , such as implementing the methods mentioned in the above embodiments.

[0154] In order to implement the above embodiments, the present disclosure further proposes a chip, including: the chip includes a processing circuit, and the processing circuit is configured to execute the method provided in the above embodiments.

[0155] Figure 9 This is a schematic diagram of the structure of a chip proposed in an embodiment of the present disclosure. Figure 9 The structure of the chip 900 is shown, but is not limited thereto.

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

[0157] Alternatively, as Figure 10 As shown, Figure 10 The chip 900 may further include a memory 903 for storing instructions, and the interface circuit 902 may be used to read 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 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 the instructions to the processing circuit 901.

[0159] Optionally, the number of memories 903 can be one or more, and 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 the other steps.

[0161] In some embodiments, terms such as interface circuit, interface, transceiver pin, and transceiver may be used interchangeably.

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

[0163] In order to implement the above embodiments, the present disclosure further proposes a non-transitory computer-readable storage medium having a computer program stored thereon, which implements the method proposed in the above embodiments of the present disclosure when the program is executed by a processor.

[0164] In order to implement the above embodiments, the present disclosure further proposes a computer program product. When instructions in the computer program product are executed by a processor, the method proposed in the above embodiments of the present disclosure is executed. The collection, storage, use, processing, transmission, provision and disclosure of user personal information involved in this disclosure are in compliance with relevant laws and regulations and do not violate public order and good morals.

[0165] It is important to note that personal information collected from users should be used for legitimate and reasonable purposes and should not be shared or sold beyond these legitimate uses. Furthermore, such collection / sharing should be conducted only 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 the relevant user information before using the feature. Furthermore, any necessary steps must be taken to safeguard and secure access to such personal information and ensure that others with access to personal information comply with its privacy policy and procedures.

[0166] This disclosure contemplates providing implementations that allow users to selectively block the use or access of personal information data. Specifically, this disclosure contemplates providing hardware and / or software to prevent or block access to such personal information data. Risks can be minimized by limiting data collection and deleting data once it is no longer needed. Furthermore, where applicable, such personal information can be de-identified to protect user privacy.

[0167] In the descriptions of the aforementioned embodiments, the reference terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" mean that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present disclosure. In this specification, the schematic expressions of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described can be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art can combine and combine different embodiments or examples described in this specification and features of different embodiments or examples without contradiction.

[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 being referred to. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. Throughout the present disclosure, "plurality" means at least two, such as two, three, etc., unless otherwise specifically defined.

[0169] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, segment or portion of code comprising one or more executable instructions for implementing the steps of a custom logical function or process, and the scope of the preferred embodiments of the present disclosure includes additional implementations in which functions may be performed out of the order shown or discussed, including performing functions in a substantially simultaneous manner or in the reverse order depending on the functions involved, which should be understood by those skilled in the art to which the embodiments of the present disclosure belong.

[0170] The logic and / or steps represented in a flowchart or otherwise described herein, for example, can be considered a sequenced list of executable instructions for implementing the 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 (e.g., a computer-based system, a system including a processor, or other system that can fetch and execute instructions from an instruction execution system, apparatus, or device). For purposes of this specification, a "computer-readable medium" is any device that can contain, store, communicate, propagate, or transport a program for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (not exhaustive) of computer-readable media include: an electrical connection with one or more wires (electronic devices), a portable computer disk cartridge (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and programmable read-only memory (EPROM or flash memory), fiber optic devices, and a portable compact disc read-only memory (CDROM). Furthermore, the computer-readable medium may even be paper or other suitable medium on which the program is printed, since the program may be obtained electronically, for example, by optically scanning the paper or other medium and then editing, interpreting or processing it in another suitable manner if necessary, and then storing it in a computer memory.

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

[0172] Those skilled in the art will understand that all or part of the steps in the method of the above embodiment can be completed by instructing related hardware through a program, and the program can be stored in a computer-readable storage medium. When the program is executed, it includes one or a combination of the steps of the method embodiment.

[0173] In addition, the functional units in the various embodiments of the present disclosure may be integrated into a single processing module, or each unit may exist physically separately, or two or more units may be integrated into a single module. The aforementioned integrated modules may be implemented in the form of hardware or in the form of software functional modules. If the integrated modules are implemented in the form of software functional modules and sold or used as independent products, they may also be stored in a computer-readable storage medium.

[0174] The storage medium mentioned above may be a read-only memory, a magnetic disk, or an optical disk, etc. Although the embodiments of the present disclosure have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present disclosure. A person of ordinary skill in the art may 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: Determining a target slice associated with a first bearer, wherein the first bearer cannot maintain a service; Determining, according to the target slice, that a condition is met, wherein the condition indicates that triggering switching to a 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; According to the target slice, establish and switch to the second bearer.

2. The method according to claim 1, characterized in that The determining, based on the target slice, that a condition is satisfied includes: Obtaining a first slice list, wherein the first slice list is allocated during initial registration, and the first slice list includes: information about slices that are allowed to be accessed; Determining whether access to the target slice is allowed according to the information of the target slice and the information of the access-allowed slice; In a case where the target slice is not allowed to be accessed, it is determined that the condition is met.

3. The method according to claim 2, characterized in that The method further comprises: Acquire a second slice list, wherein the second slice list includes: information of slices that are allowed to be accessed; Determine that the information of the slices allowed to be accessed in the second slice list includes: information of the target slice.

4. The method according to claim 3, characterized in that The obtaining of the second slice list includes: Sending a first message, wherein the first message is used to request registration update, and the first message includes: information of the target slice, and the information of the target slice is used to update the first slice list to obtain the second slice list; The second slice list is received.

5. The method according to claim 3, characterized in that The obtaining of 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.

6. The method according to claim 1, characterized in that The establishing and switching to the second bearer according to the target slice includes: Sending a second message, where the second message is used to request establishment and switching to the second bearer, and the second message includes: information about the target slice; A third message is received, where the third message is used to indicate that the handover to the second bearer has been successful.

7. The method according to any one of claims 1 to 6, characterized in that The service is an Internet Protocol (IP) Multimedia Subsystem (IMS) service.

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

9. The method according to any one of claims 1 to 6, characterized in that: The second bearer includes: a protocol data unit PDU.

10. A communication device, characterized in that: include: A first determining module is configured to determine a target slice associated with a first bearer, wherein the first bearer cannot maintain a service; A second determining module is configured to determine, based on the target slice, whether a condition is satisfied, wherein the condition indicates that triggering switching to a 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; A processing module is used to establish and switch to the second bearer according to the target slice.

11. A communication device, characterized in that: include: 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 according to any one of claims 1 to 9.

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

13. A computer program product, characterized in that The invention comprises a computer program, which implements the method according to any one of claims 1 to 9 when being executed by a processor.

14. A chip comprising a processing circuit and an interface circuit; wherein: The interface circuit is used to read instructions, and the interface circuit sends the instructions to the processing circuit, so that the processing circuit executes the method according to any one of claims 1 to 9.

Images