Wireless communication method, terminal device, access network device, and core network device

Abstract

Provided are a wireless communication method, a terminal device, an access network device, and a core network device. The method comprises: a terminal device registering with a first network and a second network on the basis of first information, the terminal device being a multi-access device, and the first information comprising one or more of the following: the corresponding relationship between a plurality of networks and radio access technologies RATs, the plurality of networks comprising the first network and the second network; and a trigger condition for registering with the second network. In the embodiments of the present application, first information is introduced, which helps the terminal device to perform network selection when the terminal device is a multi-access device.

Description

Wireless communication methods, terminal equipment, access network equipment, and core network equipment Technical Field

[0001] This application relates to the field of communication technology, and more specifically, to wireless communication methods, terminal equipment, access network equipment, and core network equipment. Background Technology

[0002] In the traditional network selection process, a terminal device selects a network and its corresponding wireless access technology for registration. However, for multi-access devices, they need to register with multiple different networks, or they need to access the same network using multiple wireless access technologies. Therefore, the traditional network selection method is not suitable for multi-access devices.

[0003] Summary of the Invention

[0004] This application provides a wireless communication method, a terminal device, an access network device, and a core network device. The various aspects covered in this application are described below.

[0005] In a first aspect, a wireless communication method is provided, comprising: a terminal device registering with a first network and a second network based on first information, wherein the terminal device is a multi-access device, and the first information includes one or more of the following: a correspondence between multiple networks and a Radio Access Technology (RAT), wherein the multiple networks include the first network and the second network; and triggering conditions for registering with the second network.

[0006] In a second aspect, a wireless communication method is provided, comprising: an access network device receiving second information or third information sent by a terminal device, wherein the terminal device is a multiple access device, wherein the second information is used to indicate a first network and a second network, and the third information is used to indicate a triggering condition for registering with the second network.

[0007] Thirdly, a wireless communication method is provided, comprising: a mobility management network element sending seventh information to a unified data management system, the seventh information being used to indicate a first network and / or a second network selected by a terminal device, wherein the terminal device is a multiple access device.

[0008] Fourthly, a terminal device is provided, comprising: a processing unit configured to register with a first network and a second network based on first information, wherein the terminal device is a multi-access device, wherein the first information includes one or more of the following: a correspondence between multiple networks and a Radio Access Technology (RAT), wherein the multiple networks include the first network and the second network; and triggering conditions for registering with the second network.

[0009] Fifthly, an access network device is provided, comprising: a receiving unit for receiving second information or third information sent by a terminal device, wherein the terminal device is a multi-access device, wherein the second information is used to indicate a first network and a second network, and the third information is used to indicate a triggering condition for registering with the second network.

[0010] In a sixth aspect, a core network device is provided, the core network device being a mobility management network element, comprising: a transmitting unit for transmitting seventh information to a unified data management network element, the seventh information being used to indicate a first network and / or a second network selected by a terminal device, wherein the terminal device is a multi-access device.

[0011] In a seventh aspect, a terminal device is provided, including a processor, a memory, and a communication interface, wherein the memory is used to store one or more computer programs, and the processor is used to invoke the computer programs in the memory to cause the terminal device to perform some or all of the steps in the method of the first aspect.

[0012] Eighthly, an access network device is provided, including a processor, a memory, and a transceiver, wherein the memory is used to store one or more computer programs, and the processor is used to invoke the computer programs in the memory to cause the network device to perform some or all of the steps in the method of the second aspect.

[0013] In a ninth aspect, a core network device is provided, including a processor, a memory, and a transceiver, wherein the memory is used to store one or more computer programs, and the processor is used to invoke the computer programs in the memory to cause the network device to perform some or all of the steps in the method of the third aspect.

[0014] In a tenth aspect, embodiments of this application provide a communication system that includes the aforementioned terminal device and / or network device (e.g., access network device and / or core network device). In another possible design, the system may further include other devices that interact with the terminal device or network device as described in the embodiments of this application.

[0015] Eleventhly, embodiments of this application provide a computer-readable storage medium storing a computer program that causes a communication device to perform some or all of the steps in the methods described above.

[0016] In a twelfth aspect, embodiments of this application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program operable to cause a communication device to perform some or all of the steps of the methods described in the foregoing aspects. In some implementations, the computer program product may be a software installation package.

[0017] In a thirteenth aspect, embodiments of this application provide a chip including a memory and a processor, the processor being able to call and run a computer program from the memory to implement some or all of the steps described in the methods of the foregoing aspects.

[0018] In this embodiment, first information is introduced to help the terminal device select a network when the terminal device is a multi-access device. Attached Figure Description

[0019] Figure 1 shows the wireless communication system 100 used in an embodiment of this application.

[0020] Figure 2 is a schematic diagram of the multi-access devices applicable to the embodiments of this application.

[0021] Figure 3 is a schematic flowchart of a wireless communication method according to an embodiment of this application.

[0022] Figures 4 to 7 are schematic flowcharts of the network registration scheme according to embodiments of this application.

[0023] Figure 8 is a schematic diagram of a terminal device according to an embodiment of this application.

[0024] Figure 9 is a schematic diagram of an access network device according to an embodiment of this application.

[0025] Figure 10 is a schematic diagram of the core network equipment in an embodiment of this application.

[0026] Figure 11 is a schematic structural diagram of a communication device according to an embodiment of this application. Detailed Implementation

[0027] The technical solutions in this application will now be described with reference to the accompanying drawings. For ease of understanding, a schematic diagram of the communication system architecture of an embodiment of this application will be introduced below with reference to Figure 1. Figure 1 is a schematic diagram of a communication system architecture applicable to an embodiment of this application. The network architecture may include terminal devices, access network (AN) nodes, and core network nodes.

[0028] It should be understood that the technical solutions of the embodiments of this application can be applied to various communication systems, such as: 5th generation (5G) systems or new radio (NR), long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, etc. The technical solutions provided in this application can also be applied to future communication systems, such as 6th generation mobile communication systems, satellite communication systems, and so on.

[0029] The terminal device in this application embodiment can also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal, remote station, remote terminal, mobile device, user terminal, terminal, wireless core network node, user agent, or user device. The terminal device in this application embodiment can be a device that provides voice and / or data connectivity to a user, and can be used to connect people, objects, and machines, such as a handheld device with wireless connectivity, vehicle-mounted device, etc. The terminal devices in the embodiments of this application can be mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, etc. Optionally, the terminal device can be used to act as a base station. For example, the terminal device can act as a dispatching entity, providing sidelink signals between terminal devices in vehicle-to-everything (V2X) or device-to-device (D2D) communications. For example, cellular phones and cars communicate with each other using sidelink signals. Cellular phones and smart home devices communicate without relaying communication signals through base stations.

[0030] Access network nodes can be access network devices. Access network devices are devices that terminals use to wirelessly access the network architecture. They are primarily responsible for air interface-side radio resource management, Quality of Service (QoS) management, data compression, and encryption. Access network devices can also be called radio access network (RAN) devices, such as base stations. A base station can broadly encompass, or be replaced by, various names including: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitting point (TP), master eNB (MeNB), secondary eNB (SeNB), multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, micro base station, relay node, donor node, or similar entities, or combinations thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. A base station can also be a mobile switching center, a device that performs base station functions in D2D, V2X, and machine-to-machine (M2M) communications, a network-side device in a 6G network, or a device that performs base station functions in future communication systems. A base station can support networks using the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the access network equipment.

[0031] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.

[0032] In some deployments, the access network device in this application embodiment may refer to a CU or a DU, or the access network device may include both a CU and a DU. The gNB may also include an AAU.

[0033] Core network nodes can be categorized into several types, including User Plane Function (UPF) nodes, Access and Mobility Management Function (AMF) nodes, Session Management Function (SMF) nodes, Policy Control Function (PCF) nodes, Application Function (AF) nodes, Data Network (DN) nodes, Network Slice Selection Function (NSSF) nodes, Authentication Server Function (AUSF) nodes, Unified Data Management (UDM) nodes, Network Exposure Function (NEF) nodes, Network Repository Function (NRF) nodes, and Network Slice-Specific Authentication and Authorization Function (NSSAAF) nodes. UPF nodes are primarily responsible for user data transmission, while the other nodes, often referred to as Control Plane Function nodes, are mainly responsible for authentication, authorization, registration management, session management, mobility management, and policy control to ensure reliable and stable user data transmission.

[0034] UPF nodes can be used to forward and receive data from terminals. For example, a UPF node can receive service data from the data network and transmit it to the terminal through access network equipment; a UPF node can also receive user data from the terminal through access network equipment and forward it to the data network. The transmission resources allocated and scheduled by the UPF node for the terminal are managed and controlled by the SMF node. The bearer between the terminal and the UPF node can include: the user plane connection between the UPF node and the access network equipment, and the establishment of a channel between the access network equipment and the terminal. The user plane connection is a QoS flow that can be established between the UPF node and the access network equipment for transmitting data.

[0035] AMF nodes can be used to manage terminal access to the core network, such as terminal location updates, network registration, access control, terminal mobility management, and terminal attachment and detachment. While providing services for a terminal's session, the AMF node can also provide control plane storage resources for that session to store the session identifier and the SMF node identifier associated with the session identifier.

[0036] SMF nodes can be used to select user plane nodes for terminals, redirect user plane nodes for terminals, assign Internet Protocol (IP) addresses to terminals, establish bearers (also known as sessions) between terminals and UPF nodes, modify and release sessions, and perform QoS control.

[0037] PCF nodes are used to provide policies to AMF and SMF nodes, such as QoS policies and slice selection policies.

[0038] AF nodes are used to interact with 3GPP core network nodes to support the routing of application-impacted data, access network exposure functions, and interact with PCF nodes for policy control, etc.

[0039] A Data Network (DN) can provide data services to users for networks such as IP Multimedia Service (IMS) and the Internet. A DN can contain various application servers (AS) that provide different application services, such as carrier services, Internet access, or third-party services. The AS can implement the functions of an Application Server (AF).

[0040] NSSF is used for network slice selection and supports the following functions: selecting a set of network slice instance examples to serve the end device; determining allowed network slice selection assistance information (NSSAI), and, when necessary, determining the mapping to the subscribed single-network slice selection assistance information (S-NSSAI); determining the configured NSSAI, and, when necessary, determining the mapping to the subscribed S-NSSAI; determining the set of AMFs that may be used to query the end device, or determining a list of candidate AMFs based on the configuration.

[0041] AUSF is used to receive AMF requests for terminal authentication. It requests a key from UDM and then forwards the issued key to AMF for authentication processing.

[0042] UDM includes functions such as generating and storing user subscription information and managing authentication data, and supports interaction with external third-party servers.

[0043] NEF is used for capability exposure, meaning that based on NEF, network capabilities can be exported to external networks. Untrusted external applications can access core network data through NEF to ensure network security. NEF can provide functions such as QoS capability exposure for external applications, event subscription, and AF request distribution.

[0044] The NRF (Network Request Framework) is used for core network node registration, management, and status monitoring, thereby enabling automated management of core network nodes. When a core network node starts up, it must register with the NRF to provide services. Registration information may include, for example, the core network node's type, address, and service list.

[0045] In addition, some networks (such as 5G networks) have added network data analytics function (NWDAF) to the core network. Based on NWDAF, data can be collected from various nodes in the core network, network management system, etc., and big data statistics, analysis or intelligent data analysis can be performed to obtain network-side analysis or prediction data, thereby assisting each node to more effectively control the access of terminal devices based on the data analysis results.

[0046] In some communication systems (such as 5G systems), core network nodes can also be called network functions (NFs).

[0047] The nodes in Figure 1 can be network elements in hardware devices, software functions running on dedicated hardware, or virtualization functions implemented on a platform (e.g., a cloud platform). It should be noted that the network architecture shown in the above figures is merely an illustrative representation of the nodes included in the overall network architecture. In this application embodiment, the number of nodes included in the entire network architecture is not limited.

[0048] Those skilled in the art will understand that the network architecture shown in Figure 1 does not constitute a limitation on the network architecture. In specific implementations, the network architecture may include more or fewer nodes than shown, or combine certain nodes, etc. It should be understood that AN or RAN is represented in Figure 1 as (R)AN.

[0049] In some scenarios, network devices and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites. This application does not limit the scenarios in which the network devices and terminal devices are located.

[0050] By way of example and not limitation, in the embodiments of this application, the network device may have mobility characteristics; for example, the network device may be a mobile device. In some embodiments of this application, the network device may be a satellite or a balloon station. For example, the satellite may be a low Earth orbit (LEO) satellite, a medium Earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. In some embodiments of this application, the network device may also be a base station located on land, water, or other similar locations.

[0051] In this embodiment, the network device can provide services to a cell. The terminal device communicates with the network device through the transmission resources (e.g., frequency domain resources, or spectrum resources) used by the cell. The cell can be the cell corresponding to the network device (e.g., a base station). The cell can belong to a macro base station or to a base station corresponding to a small cell. The small cell can include: metro cell, micro cell, pico cell, femto cell, etc. These small cells have the characteristics of small coverage area and low transmission power, and are suitable for providing high-speed data transmission services.

[0052] Public Land Mobile Network (PLMN) Selection and Roaming

[0053] MS typically operates on its home PLMN (HPLMN) or equivalent home PLMN (EH). In some scenarios, MS may choose to access a PLMN (VPLMN), for example, if the MS loses coverage. Currently, there are two PLMN selection modes: automatic mode and manual mode.

[0054] In some implementations, the automatic mode is based on a list of PLMN / radio access technology (RAT) combinations arranged in priority order, and the terminal device can select the highest priority PLMN / RAT combination that is available and allowed from the list of PLMN / RAT combinations.

[0055] In some implementations, manual mode means that the mobile station can indicate to the user which PLMNs (i.e., VPLMNs) are available. Accordingly, the mobile station only attempts to obtain normal service on the VPLMN when the user makes a manual selection.

[0056] In some scenarios, to prevent repeated attempts to obtain roaming service in prohibited areas (i.e., location areas (LA) or tracking areas (TA)), when a mobile station is informed that an area is prohibited, if the prohibited area is an LA, the area can be added to the mobile station's stored "Roaming Prohibited Location Areas" list; if the prohibited area is a TA, the area can be added to the mobile station's stored "Roaming Prohibited Tracking Areas" list. Typically, LA area restrictions always apply to the entire location area, regardless of any possible subdivisions into general packet radio service (GPRS) routing areas. The structure of the routing area identifier (see 3GPP TS23.003[22A]) supports LA-based area restrictions.

[0057] In some implementations, the above list will be deleted when the mobile station is turned off or the subscriber identity module (SIM) card is removed, and periodically (within a period of 12 to 24 hours).

[0058] In other scenarios, to prevent repeated attempts to obtain service on a PLMN via satellite Next Generation Radio Access Network (NG-RAN) or Evolved Universal Terrestrial Radio Access Network (E-UTRAN), when a mobile station receives an integrity protection rejection message with cause value #78 "PLMN not permitted at current UE location" from a satellite NG-RAN or E-UTRAN cell, the mobile station maintains a "PLMN not permitted at current UE location" list, which stores the PLMN ID of the rejected PLMN and its current geographic location (if known to the mobile station). A timer is started when the PLMN ID of the rejected PLMN is added to the "PLMN not permitted at current UE location" list. If a geographic location exists, a specific distance value for the mobile station to implement needs to be stored. The entry is removed from the list if the timer associated with the entry expires or if the mobile station successfully registers with the PLMN stored in the entry. If the current location of the terminal device is known, the geographical location can be stored for this PLMN entry. If the distance to the current location of the terminal device is greater than a specific value implemented by the mobile station, the entry in the list can be deleted.

[0059] In some implementations, under the aforementioned automatic mode, if the mobile station detects that the PLMN in the satellite NG-RAN access technology is part of the "PLMNs not permitted at the current UE location" list, the mobile station should only consider the PLMN as a candidate for NG-RAN access technology if the current MS location is known, the geographical location of the PLMN entry is stored, and the distance to the current MS location is greater than a specific value implemented by the mobile station. It should be understood that this does not prevent the selection of such a PLMN in another RAT (if it is available in that other RAT).

[0060] In some implementations, a timer is started when the PLMN ID of the rejected PLMN is added to the list of "PLMNs not allowed at the current UE location".

[0061] In some implementations, under the aforementioned automatic mode, if the mobile station detects that the PLMN in the satellite E-UTRAN access technology is part of the "PLMNs not permitted at the current UE location" list, the mobile station should only consider the PLMN as a candidate for PLMN selection in the satellite E-UTRAN access technology if the current MS location is known, the geographical location for this PLMN entry is stored, and the distance to the current UE location is greater than a specific value implemented by the mobile station. It should be understood that this does not prevent the selection of such a PLMN in another RAT (if it is available in the other RAT).

[0062] PLMN Selection Process

[0063] If the mobile station can provide the services that require registration, registration on the PLMN should be performed. The concept of registration on the PLMN is used in both automatic and manual modes. Currently, the conditions for a mobile station to successfully register on the PLMN are: the mobile station has found a suitable cell and camped there; and the LR request issued by the mobile station is accepted within the registration area of ​​the cell where the mobile station is camped.

[0064] In some scenarios, when a mobile station is able to provide services requiring registration, it needs to register and register its location on a selected PLMN. When selecting a PLMN, the mobile station uses relevant information from its SIM card. This information may include one or more of the following: "Home PLMN selector and access technology," "User-controlled PLMN selector and access technology," "Prohibited PLMNs," and "Equivalent Home PLMN." Additionally, the mobile station uses a locally stored extended list of "Prohibited PLMNs." The mobile station should use either its locally stored "Operator-controlled PLMN selector and access technology" or the "Operator-controlled PLMN selector and access technology" stored in its SIM card for PLMN selection purposes.

[0065] In some implementations, the data file in the SIM card lists the relevant access technologies for each PLMN entry, arranged in priority. If an entry contains multiple access technologies, no priority is defined; it is determined by the device implementation. If an entry does not specify a particular access technology, it is assumed that all supported access technologies are applicable. If an entry only specifies unsupported access technologies, the entry is ignored. If an entry specifies at least one supported access technology, and certain conditions are met, that entry will be used for PLMN selection.

[0066] In some implementations, the mobile station also stores a list of "EPLMNs," which is updated at the end of each update or registration process. This list includes EPLMNs downloaded from the network and codes for registering PLMNs; all listed PLMNs are considered equivalent during PLMN selection and cell selection / reselection.

[0067] In some implementations, when a mobile station reselects a cell in a shared network, if the cell is suitable for multiple PLMN identities, the AS will indicate these identities to the NAS, and the mobile station should select one of them, with preference given to the registered PLMN.

[0068] In some implementations, the mobile station does not use the PLMN code from the "Home PLMN Selector and Access Technology" data file. The home network operator can identify the alternative network ID as the home PLMN. The existence and contents of the EHPLMN list affect the network selection procedure, prioritizing the highest priority EHPLMN available. If the EHPLMN list is empty or does not exist, the home PLMN derived from the IMSI is used.

[0069] In some implementations, mobile stations may support minimum interruption time (MINT), and different Global System for Mobile Communications (GSM) frequency bands are all considered GSM access technologies, but the GSM Compact system is considered a different access technology. The EHPLMN list may include home PLMNs derived from the IMSI, and their priority is determined by their position in the list.

[0070] In some implementations, upon powering on or recovering from insufficient coverage, the mobile station will select a network based on the following conditions and, if necessary (in the case of recovering from insufficient coverage), attempt to perform location registration.

[0071] Condition 1: If the network selection for signal strength enhancement is not applicable or the mobile station has stopped applying the selection, the mobile station will select a registered PLMN or EPLMN (if available), using all access technologies that the mobile station can use, regardless of the "signal threshold for each access technology controlled by the operator" stored in the USIM.

[0072] Condition 2: If the network selection for signal strength enhancement is applicable and the received signal quality meets the threshold set in the USIM, the mobile station will select the appropriate PLMN and access technology. If multiple PLMNs / access technologies meet the conditions, the specific implementation will determine which access technology to select.

[0073] In some implementations, the search can end if the mobile station finds a registered PLMN or EPLMN in automatic network selection mode. The mobile station can also use location information to determine the available PLMNs for its current location.

[0074] In some implementations, as an alternative, if a mobile station discovers EHPLMN coverage in automatic network selection mode, it can choose to register with the EHPLMN instead of returning to an already registered PLMN or EPLMN. If the EHPLMN list is unavailable or empty, and an HPLMN is available, the mobile station can also register with the HPLMN.

[0075] In some implementations, if registration is successful, the mobile station will indicate the selected PLMN. Conversely, if there is no registered PLMN, or registration fails due to the lack of an available PLMN, or if signal level enhanced network selection is enabled in the registered PLMN or the signal quality of all access technologies in the EPLMN is below a threshold, the mobile station will proceed according to its PLMN selection operating mode. Upon power-on, if the mobile station provides an option for selecting the user's preferred PLMN operating mode, this mode should be used. Otherwise, the mobile station should use the PLMN selection mode used before power-off.

[0076] In some implementations, if the mobile station is in manual mode and there is no available registered PLMN or EPLMN, but an EHPLMN is available, the mobile station can select and attempt to register to the highest priority EHPLMN. If the EHPLMN list is unavailable or empty, but an HPLMN is available, the mobile station can also select and attempt to register to an HPLMN.

[0077] In some implementations, if registration is successful, the currently serving PLMN will become a registered PLMN, and the mobile station will not store previously registered PLMNs for future use.

[0078] In some implementations, if a mobile station cannot register during coverage recovery due to the unavailability of a registered PLMN, a mobile station attached to GPRS service, a mobile station connected via E-UTRAN, or a mobile station registered via NG-RAN can choose to continue searching for a registered PLMN.

[0079] In some implementations, if the RPLMN is the PLMN for which the mobile station registers disaster roaming services at power-on, and the disaster-related information broadcast by the mobile station through a non-3GPP access or RPLMN NG-RAN cell connected to the 5GCN does not meet the requirements, the mobile station will ignore the RPLMN and its EPLMN.

[0080] In some implementations, when a user reselects a network, the user can request the mobile station to initiate a reselection and registration of an available PLMN at any time, based on either an automatic network selection mode or a manual network selection mode.

[0081] To facilitate understanding of the multi-access technologies applicable to the embodiments of this application, the following description combines dual-connectivity technology and the differences between dual-connectivity technology and multi-access devices.

[0082] Dual connectivity (DC)

[0083] In some implementations, EN-DC (E-UTRA-NR Dual Connectivity) is a technology that enables dual connectivity between LTE (4G) and NR (5G) in 5G networks. It allows user devices to connect to both LTE base stations (eNB) and NR base stations (gNB) simultaneously, thereby improving data transmission rates, enhancing network coverage, and optimizing network resource utilization.

[0084] In EN-DC technology, LTE base stations act as master nodes (MN), providing control plane connectivity to the core network, while NR base stations act as secondary nodes (SN), providing additional spectrum resources and data transmission capabilities. This architecture allows the LTE network to continue functioning while leveraging the high speed and low latency characteristics of 5G NR.

[0085] In some implementations, EN-DC involves the following five key technical aspects.

[0086] Technical point 1: Separation of control plane and user plane. Control plane signaling is processed by LTE base station (MeNB), while user plane data can be processed by both LTE and NR base stations, which helps to allocate resources and transmit data more flexibly.

[0087] Technical point 2, bearer separation, means that data can be separated between LTE and NR base stations according to different needs. For example, different data streams can be allocated to different base stations to optimize transmission efficiency.

[0088] Technical point 3, measurement and reporting, means that terminal devices need to measure LTE and NR base stations and report the measurement results so that the network can make optimal connection and resource allocation decisions.

[0089] Technical point 4, the Xx interface, means that LTE base stations (MeNB) and NR base stations (SeNB) are connected through the Xx interface, allowing them to work together and exchange control information and user data.

[0090] Technical point 5, carrier aggregation, that is, EN-DC technology can be used in combination with carrier aggregation technology to further improve data transmission rate.

[0091] In this way, EN-DC technology enables operators to leverage existing LTE infrastructure while providing 5G services, achieving smooth network evolution and rapid deployment.

[0092] The difference between multi-access technology and dual-connectivity technology

[0093] As can be seen from the above introduction, DC technology requires different access network devices to work together to exchange control information and user data. This is primarily controlled by the load signaling of the primary access network device. In other words, in a DC scenario, there is only one non-access stratum (NAS) connection between the terminal device and the core network, and the secondary access network device is not perceived by the core network. For the terminal device in the DC, there is only one next-generation access protocol (NGAP) connection.

[0094] For multiple access technologies, the multiple access network devices accessed by the terminal device are all connected to the core network, and the mobility management network element has an NGAP connection for each of the multiple access network devices.

[0095] In addition, for multi-access technology, the control signaling corresponding to multiple access network devices is independent of each other.

[0096] In addition, for multi-access technologies, the collaborative work between multiple connections mainly occurs on the network side.

[0097] In some implementations, devices that support multiple access technologies can be called multi-access devices or dual-access devices.

[0098] In some implementations, a multi-access device includes one or more of the following: a device that accesses multiple access networks; a device that registers with the core network through multiple access networks; a device that establishes connections with the core network through multiple access networks; and a device that has multiple NAS connections with mobility management network elements.

[0099] The following description, in conjunction with Figure 2, introduces the multi-access device applicable to the embodiments of this application. Referring to Figure 2, assuming the multi-access device is an MS, the MS may have one or more Universal Subscriber Identity Module (USIM) cards (e.g., USIM-1 and / or USIM-2 shown in Figure 2). That is to say, the multi-access device in the embodiments of this application can be a single-card terminal device.

[0100] In some implementations, the MS may include mobile equipment (ME), which can be understood as a mobile terminal without a USIM. The mobile terminal (MT) within the ME provides wireless transmission-related functions and / or provides physical connectivity to the network. Accordingly, the MT supports connecting various terminal equipment (TE) to the MT through terminal adaptation functions (TAF). The TE within the ME provides the user interface to implement end-to-end application functions.

[0101] In this application, the framework for multiple access devices is not limited. In some implementations, multiple access devices can deploy multiple MTs and one USIM, with different MTs supporting different protocol stacks, and each of the various protocol stacks corresponding to one NAS connection. In other implementations, multiple access devices can deploy one MT and one USIM, in which case one MT supports multiple different protocol stacks, and each of the various protocol stacks corresponding to one NAS connection.

[0102] As mentioned earlier, in the traditional network selection process, a terminal device selects a network and its corresponding wireless access technology for registration. However, for multi-access devices, they need to register with multiple different networks, or they need to access the same network using multiple wireless access technologies. Therefore, the traditional network selection method is not suitable for multi-access devices.

[0103] For example, in the traditional PLMN selection process, the terminal device selects a PLMN based on the PLMN-RAT correspondence and registers using the corresponding RAT. However, for multi-access devices, multiple access devices need to register with multiple different PLMNs, or multiple access devices need to access the same PLMN using multiple different RATs. Therefore, the traditional PLMN selection method is not suitable for multi-access devices.

[0104] Therefore, to address the above-mentioned problems, this application provides a wireless communication method that introduces first information to assist the terminal device in network selection when the terminal device is a multi-access device. The wireless communication method of this application embodiment is described below with reference to FIG3. The method shown in FIG3 includes step S310.

[0105] In step S310, the terminal device registers with the first network and the second network based on the first information. The terminal device is a multi-access device. For an introduction to multi-access devices, please refer to the above text.

[0106] In this embodiment, the types of the first and second networks are not limited. The types of the first and second networks may include a PLMN and / or a non-public network (NPN). For example, the first and second networks can be PLMNs. Alternatively, the first and second networks can be NPNs. Another example is that the first network is a PLMN and the second network is an NPN. Yet another example is that the second network is a PLMN and the first network is an NPN. Of course, in this embodiment, the first and / or second networks can also be stand-alone non-public (SNPN) networks or public network integrated non-public (PNI-NPN) networks.

[0107] In some implementations, the first network and the second network are the same network, and the RAT corresponding to the first network is different from the RAT corresponding to the second network. In other implementations, the first network and the second network are different networks. In this case, the RAT corresponding to the first network and the RAT corresponding to the second network can be the same or different, and this application does not limit this.

[0108] In some implementations, the first network and the second network being the same network may include the first network being a PLMN, the second network being a PLMN, and the PLMN ID of the first network being the same as the PLMN ID of the second network; or the first network being an NPN, the second network being an NPN, and the NPN ID of the first network being the same as the NPN ID of the second network; or the first network being an SNPN, the second network being an SNPN, and the SNPN ID of the first network being the same as the SNPN ID of the second network; or the first network being a PNI-NPN, the second network being a PNI-NPN, and the PNI-NPN ID of the first network being the same as the PNI-NPN ID of the second network.

[0109] In some implementations, the first network and the second network being different networks may include the first network being a PLMN, the second network being a PLMN, and the PLMN ID of the first network being different from the PLMN ID of the second network. This difference in the PLMN ID of the first network may include the mobile country code (MCC) and / or mobile network code (MNC) in the PLMN ID of the first network being different from the MCC and / or MNC in the PLMN ID of the second network. Alternatively, the first network being an NPN, the second network being an NPN, and the NPN ID of the first network being different from the NPN ID of the second network. Or, the first network being an SNPN, the second network being an SNPN, and the SNPN ID of the first network being different from the SNPN ID of the second network. This difference in the SNPN ID of the first network may include the PLMN ID and / or network identifier (NID) in the SNPN ID of the first network being different from the PLMN ID and / or NID in the SNPN ID of the second network. Alternatively, the first network is a PNI-NPN, the second network is a PNI-NPN, and the PNI-NPN ID of the first network is different from the PNI-NPN ID of the second network. The difference between the PNI-NPN ID of the first network and the PNI-NPN ID of the second network may include the PLMN ID and / or the closed access group (CAG) ID in the PNI-NPN ID of the first network being different from the PLMN ID and / or CAG ID in the PNI-NPN ID of the second network.

[0110] In this application embodiment, the RAT is not limited. In some implementations, the RAT can include two main categories of technologies: 3GPP and non-3GPP. 3GPP access technologies mainly include one or more of the following: NTN-based RAT, TN-based RAT, LTE, NR, and 6G. Non-3GPP access technologies can include one or more of the following: Wireless Fidelity (Wi-Fi), World Interoperability for Microwave Access (WiMAX), and Code Division Multiple Access (CDMA).

[0111] In this application embodiment, the number of networks registered by the terminal device is not limited. In some implementations, the terminal device can register with two networks (i.e., the first network and the second network described above). In other implementations, the terminal device can register with multiple networks, in which case the first network and the second network can be two of multiple networks. For ease of description, the following description uses the first network and the second network as examples.

[0112] In some implementations, the first information includes one or more of the following: the correspondence between multiple networks and the RAT, and the triggering conditions for registering the second network. These will be described below in conjunction with Embodiment 1 and Embodiment 2, respectively.

[0113] Example 1: The first information includes the correspondence between multiple networks and RAT, wherein the multiple networks include the first network and the second network.

[0114] In some implementations, the above method may include: the terminal device selecting a first network and a second network based on the mapping relationship between multiple networks and the RAT. Then, the terminal device can register with the first network and the second network. Of course, in the embodiments of this application, step S310 can be replaced by the terminal device selecting the first network and the second network based on the mapping relationship between multiple networks and the RAT, or by the terminal device selecting the first network and the second network for registration based on first information.

[0115] In this embodiment, the order in which the terminal device selects the first network and the second network is not limited. In some implementations, the terminal device can select both the first network and the second network simultaneously. For example, assuming the correspondence includes multiple PLMN / RAT combinations arranged by priority, the terminal device can directly select the two highest-priority PLMN / RAT combinations as the first and second networks. In this embodiment, the above network selection method helps reduce the time required for network selection.

[0116] In other implementations, the terminal device can select a first network first, and then select a second network. For example, the terminal device can first select PLMN-1 (as an example of the first network) according to the traditional PLMN selection mechanism, and then select PLMN-2 (as an example of the second network) according to the same traditional PLMN selection mechanism. PLMN-1 and PLMN-2 can be the same PLMN. That is, the terminal device selects one or two PLMNs in the PLMN / RAT combination according to priority. In the embodiments of this application, the above network selection method helps to reduce modifications to traditional network selection schemes, thereby expanding the scenarios applicable to this network selection method.

[0117] In some implementations, the mapping between multiple networks and RATs can be used to indicate the RAT corresponding to each of the multiple networks. Taking a PLMN as an example, this mapping can be understood as a combination of each PLMN and RAT among multiple PLMNs (referred to as "PLMN / RAT combination" or "PLMN / RAT list"). For example, this mapping can be obtained through a list of PLMNs. Taking an NPN as an example, this mapping can be understood as a combination of each NPN and RAT among multiple NPNs.

[0118] In some implementations, the priorities of different correspondences between multiple networks and the RAT vary. Specifically, the priority of the correspondence containing the first network and the correspondence containing the second network are higher than or equal to the priorities of the other correspondences, which are those other than the correspondences of the first and second networks. The correspondence containing the first network can refer to the correspondence between the first network and the RAT, and the correspondence containing the second network can refer to the correspondence between the second network and the RAT.

[0119] For example, the first network and the second network can be the two highest priority networks among multiple networks. As another example, assuming the correspondence includes multiple PLMN / RAT combinations arranged by priority, then the first network and the second network can be the two highest priority PLMN / RAT combinations among these multiple PLMN / RAT combinations.

[0120] In this embodiment, the method of obtaining the above-mentioned correspondence is not limited. In some implementations, the above-mentioned correspondence can be stored in a module of the terminal device, wherein the module may include, for example, a SIM and / or a USIM. For example, assuming the terminal device has only one USIM card, the terminal device can select one or more PLMN networks from the PLMN / RAT list stored in the USIM card as the first network and the second network. As another example, assuming the terminal device has two USIM cards, the terminal device can select one network from the PLMN / RAT lists stored in the two USIM cards respectively as the first network and the second network. Of course, in this embodiment, the above-mentioned correspondence can also be configured by the network device. For example, the terminal device can also select two different EPLMNs as the first network and the second network using EPLMNs obtained from the network side.

[0121] In some implementations, after the terminal device selects a first network and a second network, the terminal device can indicate the selected network to the network. That is to say, the above method also includes: the terminal device sending second information to the access network device (also known as the first access network device), the second information being used to indicate the first network and the second network.

[0122] In some implementations, the second information carries one or more of the following: slice identification information; terminal device identification; first network identification; second network identification; information indicating the RAT corresponding to the first network; information indicating the RAT corresponding to the second network; and information indicating that the terminal device is a multi-access device.

[0123] Taking the second information carrying slice identification information as an example, the slice identification information is used to indicate the network slices supported by the terminal device. For example, the slice identification information may include network slice selection assistance information (NSSAI).

[0124] Taking the identification of the terminal device carried by the second information as an example, the identification information of the terminal device may include, for example, a 5G-S-Temporary mobile subscription identifier (5G-S-TMSI) or a globally unique temporary identifier (GUTI).

[0125] Taking the second information carrying the identifier of the first network as an example, if the first network is a PLMN, then the identifier of the first network is the PLMN ID. If the first network is an NPN, then the identifier of the first network is the NPN ID. Of course, in this embodiment of the application, if the first network is an SNPN, then the identifier of the first network may include both the PLMN ID and the NPN ID. If the first network is a PNI-NPN, then the identifier of the first network is the PNI-NPN ID, wherein the PNI-NPN ID includes the PLMN ID and the CAG ID, the PLMN ID is used to identify the network, and the CAG ID is used to identify the cell of the closed access group.

[0126] Taking the second information carrying the identifier of the second network as an example, if the second network is a PLMN, then the identifier of the second network is the PLMN ID. If the second network is an NPN, then the identifier of the second network is the NPN ID. Of course, in this embodiment of the application, if the second network is an SNPN, then the identifier of the second network may include both the PLMN ID and the NPN ID.

[0127] Taking the second information carrying information for indicating the RAT corresponding to the first network as an example, in some implementations, the identifier of the first network and the RAT corresponding to the first network can be represented by a combination of the first network and the RAT, for example, represented as (PLMN-1, RAT-1). Of course, in the embodiments of this application, the RAT corresponding to the first network can be represented by different information from the identifier of the first network.

[0128] Taking the second information carrying information for indicating the RAT corresponding to the second network as an example, in some implementations, the identifier of the second network and the RAT corresponding to the second network can be represented by a combination of the second network and the RAT, for example, represented as (PLMN-2, RAT-2). Of course, in the embodiments of this application, the RAT corresponding to the second network and the identifier of the second network can be represented by different information.

[0129] Taking the information carried in the second information as an example to indicate that the terminal device is a multi-access device, the information used to indicate that the terminal device is a multi-access device is also called "multi-access indication information". In some scenarios, multi-access indication information can be used to indicate that the terminal device is in a multi-access state, or, multi-access indication information can be used to indicate that the terminal device requests to switch to a multi-access state, or, multi-access indication information can be used to indicate that the terminal device has multi-access capability.

[0130] The content carried by the second information in the embodiments of this application has been introduced above. The transmission method of the second information in the embodiments of this application is described below in conjunction with implementation method 1 and implementation method 2.

[0131] In implementation method 1, the terminal device can indicate the first network and the second network to the access network device through the second information, which helps the access network device select the appropriate mobility management network element based on the first network and the second network. This will be described in conjunction with Figure 4 below.

[0132] In some implementations, the second information is carried in an access network (AN) message (e.g., a radio resource control (RRC) message) that carries the first request. The first request is used to request the terminal device to register with both the first and second networks. In some scenarios, the first request is also referred to as a "registration request".

[0133] In some implementations, if the mobility management network element selected by the access network device based on the second information can support both the first network and the second network, the access network device can send the identifiers of the first network and the second network to the mobility management network element. Of course, in this embodiment, the access network device can send the RAT corresponding to the first network and / or the RAT corresponding to the second network to the mobility management network element.

[0134] In other implementations, if the mobility management network element selected by the access network device based on the second information can only support the first network and cannot support the second network, the access network device can send the identifier of the first network to the mobility management network element. Of course, in this embodiment, the access network device can send the RAT corresponding to the first network to the mobility management network element.

[0135] In some implementations, the access network device can select a mobility management network element based on the network identifier of the second network. Then, the access network device can send the identifier of the second network to the mobility management network element that supports the second network. Of course, in this embodiment, the access network device can send the RAT corresponding to the second network to the mobility management network element.

[0136] In this application embodiment, the mobility management network element is not limited. In some implementations, the mobility management network element can be the AMF (Active Mobile Controller), in which case the access network device can communicate with the AMF via N2 messages. Of course, in this application embodiment, the mobility management network element can be the mobile management (MM) in a 6G network.

[0137] In some implementations, the above method further includes: the access network device sending fifth information to a third mobility management network element, the fifth information being used to instruct the terminal device to request access to the first network and the second network, wherein the third mobility management network element supports the first network and / or the second network.

[0138] In implementation method 2, the terminal device can indicate the first network to the access network device (also known as the first access network device) through the second information, and indicate the second network to the mobility management network element through the second information, which helps to reduce the modification of traditional solutions.

[0139] In other words, the identifier of the first network and / or the information indicating the RAT corresponding to the first network is carried in the AS message corresponding to the second information, and / or the identifier of the second network and / or the information indicating the RAT corresponding to the second network is carried in the NAS message corresponding to the second information. In this case, the information carried in the NAS message is transparently transmitted to the mobility management network element for the access network device, and the access network device does not read this information. The information carried in the AS message (e.g., RRC message) is readable by the access network device.

[0140] In some implementations, the second information is carried in an AN message that includes a first request, which is used to request the terminal device to register with the first network. In some scenarios, the first request is also referred to as a "registration request".

[0141] In some implementations, the access network device can select a mobility management network element (also known as the first mobility management network element) that supports the first network based on the first network. Then, the access network device can send an N2 message and / or a first request to the mobility management network element. The N2 message carries the identifier of the first network and / or the RAT information corresponding to the first network (as an example of the second information), and the first request carries the identifier of the second network and / or the RAT information corresponding to the second network. The first request is carried in a NAS message.

[0142] In some implementations, the first mobility management element is associated with a first network and / or a second network, that is, the first mobility management element supports the first network and / or the second network.

[0143] In some scenarios, a terminal device can register to both a first network and a second network through a first request. That is, a terminal device can register to multiple networks in a single registration process, as illustrated in Figure 4 or Figure 5 below. In other scenarios, the terminal device only registers to the first network through the first request. In this case, the terminal device also needs to send a second request to register to the second network. That is, the terminal device can register to different networks through multiple registration processes, as illustrated in Figure 6 or Figure 7 below.

[0144] In some implementations, step S310 includes: the terminal device sending a second request to the second access network device, the second request being used to request registration of the terminal device with the second network.

[0145] In some implementations, the identifier of the first network and / or information indicating the RAT corresponding to the first network is carried in the NAS message corresponding to the second request, and / or the identifier of the second network and / or information indicating the RAT corresponding to the second network is carried in the AS message corresponding to the second request. In this case, the information carried in the NAS message is transparently transmitted to the mobility management network element for the access network device, and the access network device does not read this information. The information carried in the AS message (e.g., the RRC message) is readable by the access network device.

[0146] In some implementations, the access network device can select a mobility management network element (also known as a second mobility management network element) that supports the second network based on the second network. Then, the access network device can send an N2 message and / or a second request to the mobility management network element. The N2 message carries the identifier of the second network and / or the RAT information corresponding to the second network, and the second request carries the identifier of the first network and / or the RAT information corresponding to the first network. The second request is carried in a NAS message.

[0147] In some implementations, the second mobility management element is associated with the first network and / or the second network; that is, the second mobility management element supports the first network and / or the second network.

[0148] As described above, the mobility management network element (e.g., the first mobility management network element, the second mobility management network element, and the third mobility management network element mentioned above) can learn the first network element and / or the second network element selected by the terminal device. Then, the mobility management network element can register the first network element and / or the second network element selected by the terminal device to the unified data management network element. Of course, in this embodiment, the mobility management network element can register the RAT corresponding to the first network element and / or the RAT corresponding to the second network element to the unified data management network element. That is, the above method also includes: the mobility management network element can send seventh information to the unified data management network element, wherein the seventh information is used to indicate the first network and / or the second network selected by the terminal device.

[0149] In some implementations, the unified data management network element can be the UDM introduced above, or it can be a network element with the same or similar functions in 6G.

[0150] In some implementations, the seventh information is used to indicate the RAT corresponding to the first network and / or the RAT corresponding to the second network. Of course, in the embodiments of this application, the seventh information may also be used to indicate one or more of the following: the network function type (NF type) (e.g., AMF) corresponding to the mobility network element; the NF ID (e.g., AMF ID) corresponding to the mobility network element; the terminal device identifier (e.g., SUPI); the RAT type of the RAT; the access type corresponding to the network (e.g., the first network or the second network); the registration type corresponding to the first request or the second request; and the identifier of the currently registered network.

[0151] In some scenarios, if the mobility management network element supports both a first network and a second network, it can inform the unified data management network element of the first and second networks selected by the terminal device. This helps the unified data management network element associate the first and second networks selected by the terminal device. This will be explained in conjunction with Figure 4 or Figure 5 below.

[0152] In other scenarios, if a terminal device accesses different networks through multiple registration processes, after successfully registering with the first network, during the registration process with the second network, the second mobility management element can indicate to the unified data management element the information of the second network currently registered by the terminal device (e.g., the identifier of the second network and / or the RAT corresponding to the second network), and indicate the network selected by the terminal device for multi-access capability (or, in other words, indicate the additional network selected by the terminal device for the second network (i.e., the "additional network registration indication information" described below)). This helps the unified data management element determine that the terminal device has selected a new network (the second network), rather than switching from the first network to the second network. This will be explained in conjunction with Figure 7 below.

[0153] In some implementations, after obtaining information about the first network and the second network selected by the terminal device, the unified data management network element can store the information in the terminal device context. For example, the terminal device context may include one or more of the following for each of the multiple accesses corresponding to the terminal device: the identifier of the serving mobility network element, the network identifier (e.g., the identifier of the registered PLMN and / or NID), and the RAT. See Table 1 for related details.

[0154] In some implementations, before informing the unified data management network element (UDN) of the first and / or second network selected by the terminal device, the mobility management network element (MMU) may determine whether to support the terminal device's multi-access capability based on the terminal device's subscription data and / or local configuration information. If the MMU determines that the terminal device's multi-access capability is supported, then the MMU informs the unified data management network element of the first and / or second network selected by the terminal device. Conversely, if the MMU determines that the terminal device's multi-access capability is not supported, the MMU may choose not to inform the unified data management network element of the first and / or second network selected by the terminal device.

[0155] Example 2: The first information includes the triggering conditions for registering with the second network.

[0156] In some implementations, the triggering condition for registering with the second network can be understood as follows: if the triggering condition is met, the terminal device registers with the second network. Conversely, if the triggering condition is not met, the terminal device does not register with the second network.

[0157] In some implementations, the terminal device registering with the second network may include the terminal device sending a registration request to the access network device to request registration with the second network.

[0158] In some implementations, the above triggering conditions are associated with one or more of the following: a first time; a first location; the communication quality of the terminal device in the first network; and the state of the terminal device in the first network.

[0159] Taking the association of triggering conditions with the first time as an example, the triggering conditions can include the terminal device within the first time, or in other words, the triggering conditions include reaching the first time. For example, if the second network is an NTN network, then if the first time is reached (i.e., the triggering conditions are met), due to the movement of satellites in the NTN network, the coverage area of ​​the satellites can include the area where the terminal device is located. At this time, the terminal device can register with the second network, where the first time can be determined based on the satellite's trajectory.

[0160] In the embodiments of this application, the implementation method of the first time is not limited. In some implementations, the first time may refer to a period of time, and correspondingly, the triggering condition may include entering the time period corresponding to the first time. In other implementations, the first time may refer to a point in time, and correspondingly, the triggering condition may include reaching the point in time corresponding to the first time.

[0161] Taking the association of triggering conditions with a first location as an example, the triggering conditions may include the terminal device being located within the first location, or in other words, the triggering conditions include the terminal device entering the first location. For example, if the terminal device is a mobile terminal, then if it reaches the first location (i.e., the triggering conditions are met), the terminal device is located within the coverage area of ​​the second network. At this time, the terminal device can register with the second network.

[0162] In this application embodiment, the implementation method of the first location is not limited. In some implementations, the first location may refer to a region, and correspondingly, the triggering condition may include the terminal device entering the region corresponding to the first location. In other implementations, the first location may refer to a location point, and correspondingly, the triggering condition may include the location point corresponding to the time when the terminal device arrives at the first location.

[0163] Taking the association between triggering conditions and the communication quality of the terminal device in the first network as an example, the triggering conditions include the terminal device's communication quality in the first network being lower than a threshold. That is to say, if the terminal device's communication quality in the first network is lower than the threshold, the terminal device can trigger registration in the second network, which helps to improve the terminal device's communication quality.

[0164] In some implementations, communication quality can be measured by one or more of the following metrics: reference signal receiving power (RSRP), signal to interference plus noise ratio (SINR), and reference signal receiving quality (RSRQ).

[0165] In some implementations, the communication quality of the terminal device in the first network is determined based on one or more of the following parameters: the maximum total data transmission rate supported by the terminal device in the first network (e.g., the maximum bit rate supported by the user equipment (UE AMBR)); the packet loss rate of the terminal device in the first network; and the signal strength of the terminal device communicating in the first network.

[0166] For example, if the data transmission rate of the terminal device in the first network is greater than the maximum total data transmission rate supported by the first network for terminal devices, then it can be determined that the communication quality of the terminal device in the first network is below a threshold. Similarly, if the packet loss rate of the terminal device in the first network is higher than a threshold, then it can be determined that the communication quality of the terminal device in the first network is below a threshold. And again, if the signal strength of the terminal device in the first network is lower than a threshold, then it can be determined that the communication quality of the terminal device in the first network is below a threshold.

[0167] Of course, in this embodiment, the communication quality of the terminal device in the first network can also be determined based on a variety of parameters described above. For example, if the packet loss rate of the terminal device in the first network is higher than a threshold, and the signal strength of the terminal device communicating in the first network is lower than a threshold, then it can be determined that the communication quality of the terminal device in the first network is lower than the threshold. As another example, if the data transmission rate of the terminal device in the first network is higher than the maximum total data transmission rate supported by the first network for terminal devices, and the packet loss rate of the terminal device in the first network is higher than a threshold, and the signal strength of the terminal device communicating in the first network is lower than a threshold, then it can be determined that the communication quality of the terminal device in the first network is lower than the threshold.

[0168] It should be noted that the threshold in the embodiments of this application can be determined based on one or more of the following: predefined information; preconfiguration information; configuration information sent by the network device.

[0169] Taking the association of triggering conditions with the terminal device's state in the first network (connected or idle) as an example, in some implementations, the triggering condition may include the terminal device being in a connected state in the first network. That is, if the terminal device is in a connected state in the first network, then the terminal device can register with the second network. In other implementations, the triggering condition may include the terminal device being in an idle state in the first network. That is, if the terminal device is in an idle state in the first network, then the terminal device can register with the second network.

[0170] The triggering conditions in the embodiments of this application have been introduced above. The following describes the method for obtaining the triggering conditions in the embodiments of this application. In some implementations, the triggering conditions may be configured by the access network device (also known as the third access network device) for the terminal device. That is to say, the above method also includes: the third access network device sending third information to the terminal device, the third information being used to indicate the triggering conditions.

[0171] In some scenarios, third information can be understood as the auxiliary terminal device initiating registration with the second network; therefore, third information can also be called "auxiliary information".

[0172] In some implementations, the third information can be carried in a registration response message, which is a response to a registration request made to the first network. For example, a mobility management network element can send a response message to a terminal device through an access network device, indicating acceptance of the terminal device's registration with the first network, wherein the response message carries the third information.

[0173] In some implementations, the above-described scheme of registering with the second network based on trigger conditions can be applied to scenarios where the terminal device registers with both the first and second networks through multiple registration processes. This will be described in conjunction with Figure 7 below.

[0174] In the embodiments of this application, Embodiment 1 and Embodiment 2 can be used independently or in combination. If Embodiment 1 and Embodiment 2 are used in combination, the terminal device can select the first network and the second network according to the scheme of Embodiment 1, and register with the second network when the triggering conditions are met. This helps multiple access devices access multiple networks, which helps to ensure service continuity and improve service throughput.

[0175] In some implementations, the above method further includes: the mobility management network element sending fourth information to the terminal device, the fourth information being used to configure parameters of the first network and / or parameters of the second network, wherein the parameters include one or more of the following: one or more EPLMNs; configured NSSAI.

[0176] In this embodiment, the parameters described above can be shared by both the first and second networks, which helps reduce the transmission overhead required for configuring the parameters. Alternatively, in this embodiment, the parameters can be configured separately for the first and second networks, which helps improve configuration flexibility.

[0177] In some implementations, the fourth information is a registration acceptance message. Of course, in the embodiments of this application, the fourth information can be dedicated information transmitted independently.

[0178] For ease of understanding, the network registration scheme of this application embodiment is described below with reference to Figures 4 to 7. It is assumed that the scheme shown in Figures 4 to 7 uses the registration of a terminal device with two networks as an example.

[0179] The method shown in Figure 4 illustrates a scheme where a terminal device, acting as a multi-access device, can simultaneously select two networks and inform the access network and core network of the selected network. The method shown in Figure 4 includes steps S410 to S460.

[0180] In step S410, the terminal device selects network 1 and network 2, where network 1 corresponds to RAT1 and network 2 corresponds to RAT2.

[0181] In some implementations, after the terminal device is powered on or recovers from an area lacking coverage, it can select network 1 and network 2 based on the correspondence described above. For information on network 1 and network 2, please refer to the previous description of the first network and the second network.

[0182] In step S420, the terminal device sends second information and request 1 to the access network device, wherein request 1 is used to request registration with the first network.

[0183] In some implementations, the second information may carry one or more of the following: slice identification information; terminal device identification; network 1 identification; network 2 identification; information indicating the RAT1 corresponding to network 1; information indicating the RAT1 corresponding to network 2; information indicating that the terminal device is a multi-access device. See the preceding text for related information.

[0184] It should be noted that if network 1 and network 2 are the same network, then RAT1 and RAT2 are different RATs. If network 1 and network 2 are different networks, then RAT1 and RAT2 can be the same or different.

[0185] In step S430, the access network device selects a mobility management network element based on the identifier of network 1 and the identifier of network 2.

[0186] In some implementations, if a mobility management network element (MLE) exists that supports both Network 1 and Network 2, the access network device can select an MLE that supports both Network 1 and Network 2. In other implementations, if no MLE exists that supports both Network 1 and Network 2, the terminal device can select an MLE based on either Network 1 or Network 2.

[0187] In step S440, the access network device sends the second information and request 1 to the mobility management network element.

[0188] In some implementations, the access network device can also send the location information of the terminal device and / or the identifier of the access network device to the mobility management network element.

[0189] In some implementations, information between the access network device and the mobility management network element can be transmitted via N2 messages.

[0190] In step S450, the mobility management network element sends a seventh message to the UDM, which is used to instruct network 1 and network 2.

[0191] In some implementations, the seventh information can also be used to indicate RAT1 for network 1 and RAT2 for network 2.

[0192] In some implementations, if the mobility management network element determines, based on the terminal device's subscription data and local network configuration, that it needs to support the terminal device's multi-access capability, then the mobility management network element registers the information of network 1 selected by the terminal device and the information of network 2 (for example, the information of network 1 may include the identifier of network 1 and / or the RAT1 corresponding to network 1, and the information of network 2 may include the identifier of network 2 and / or the RAT2 corresponding to network 2) into the UDM, in order to associate the information of network 1 selected by the terminal device with the information of network 2.

[0193] In some implementations, if the mobility management network element does not have the terminal device's subscription data, the mobility management network element can obtain the terminal device's subscription data from the UDM.

[0194] In step S460, the mobility management network element sends a registration acceptance message to the terminal device.

[0195] In some implementations, the registration acceptance message can be sent from the mobility management network element to the terminal device through the access network equipment.

[0196] In some implementations, the registration acceptance message may carry information indicating the multi-access capability of the accepting terminal device, which is also known as an indication of support for multi-access.

[0197] In some implementations, the registration acceptance message may include a list of NSSAI and / or EPLMN configured for the service PLMN.

[0198] It should be noted that the configuration NSSAI and / or EPLMN list of the aforementioned service PLMN can be configured for both network 1 and network 2. In this case, network 1 and network 2 can use the same configuration NSSAI and / or EPLMN list. However, in this embodiment, the configuration NSSAI and / or EPLMN list of the aforementioned service PLMN can be configured for network 1 and network 2 separately. In this case, network 1 can use the configuration NSSAI and / or EPLMN list of service PLMN 1, and network 2 can use the configuration NSSAI and / or EPLMN list of service PLMN 2.

[0199] The method shown in Figure 5 illustrates a scheme where a terminal device, acting as a multi-access device, can simultaneously select two networks and informs the access network device and core network device (e.g., a mobility management network element) of the selected networks respectively. It should be understood that the method shown in Figure 5 is illustrated using the example of a terminal device completing registration with multiple networks through a single registration process. The method shown in Figure 5 includes steps S510 to S570.

[0200] In step S510, the terminal device selects network 1 and network 2, where network 1 corresponds to RAT1 and network 2 corresponds to RAT2.

[0201] In some implementations, network 1 and network 2 are VPLMN and HPLMN, respectively, or network 1 and network 2 are PLMN and NPN, respectively.

[0202] In step S520, the terminal device sends the second information to the access network device.

[0203] In some implementations, the access network device can be an access network device that supports RAT1 corresponding to network 1.

[0204] In some implementations, the second information includes RRC messages and NAS messages, with the identifier of network 1 and / or the RAT1 corresponding to network 1 carried in the RRC message, and the identifier of network 2 and / or the RAT2 corresponding to network 2 carried in the NAS message.

[0205] In some implementations, the NAS message may include Request 1, which requests the registration of the terminal device. Additionally, Request 1 may carry information indicating that the terminal device is a multi-access device.

[0206] In step S530, the access network device selects a mobility management network element based on the identifier of network 1 and the RAT1 corresponding to network 1.

[0207] In step S540, the access network device sends the second information to the mobility management network element.

[0208] In some implementations, the second information includes an N2 message and a request 1, wherein the N2 message contains the identifier of network 1 and the RAT1 corresponding to network 1, and the request 1 is used to request the registration of the terminal device, and the request 1 carries the identifier of network 2 and the RAT2 corresponding to network 2.

[0209] In step S550, the mobility management network element sends a seventh message to the UDM, which is used to instruct network 1 and network 2.

[0210] In some implementations, the seventh information can also be used to indicate RAT1 for network 1 and RAT2 for network 2.

[0211] In some implementations, if the mobility management network element determines, based on the terminal device's subscription data and local network configuration, that it needs to support the terminal device's multi-access capability, then the mobility management network element registers the information of network 1 selected by the terminal device and the information of network 2 (for example, the information of network 1 may include the identifier of network 1 and / or the RAT1 corresponding to network 1, and the information of network 2 may include the identifier of network 2 and / or the RAT2 corresponding to network 2) into the UDM, in order to associate the information of network 1 selected by the terminal device with the information of network 2.

[0212] In step S560, the UDM stores in the context of the terminal device the identifier and / or RAT of the network corresponding to each access in the multiple access devices.

[0213] In some implementations, the network information stored in the context of the terminal device can be seen in Table 1. Assume the terminal device, as a multi-access device, supports the first access corresponding to network 1 and the second access corresponding to network 2. Taking network 1 and network 2 as PLMNs as examples, the terminal device's context can store one or more of the following parameters corresponding to the access: the serving AMF identifier for the first access, the registered PLMN identifier for the first access, the RAT1 information for the first access, the serving AMF identifier for the second access, the registered PLMN identifier for the second access, and the RAT2 information for the second access.

[0214] Table 1

[0215] It should be noted that, in the embodiments of this application, the parameters corresponding to the first access and the parameters corresponding to the second access may be the same or different. That is to say, for the first access and the second access, the service AMF identifier, registration PLMN identifier, and RAT shown in Table 1 may be the same or different.

[0216] In some implementations, mobility management network elements can subscribe to changes in the context of UDM terminal devices.

[0217] In step S570, the mobility management network element sends a registration acceptance message to the terminal device.

[0218] In some implementations, the registration acceptance message can be sent from the mobility management network element to the terminal device through the access network equipment.

[0219] In some implementations, the registration acceptance message may carry information indicating the multi-access capability of the accepting terminal device, which is also known as an indication of support for multi-access capability.

[0220] In some implementations, the registration acceptance message may include a list of NSSAI and / or EPLMN configured for the service PLMN.

[0221] It should be noted that the configuration NSSAI and / or EPLMN list of the aforementioned service PLMN can be configured for both network 1 and network 2. In this case, network 1 and network 2 can use the same configuration NSSAI and / or EPLMN list. However, in this embodiment, the configuration NSSAI and / or EPLMN list of the aforementioned service PLMN can be configured for network 1 and network 2 separately. In this case, network 1 can use the configuration NSSAI and / or EPLMN list of service PLMN 1, and network 2 can use the configuration NSSAI and / or EPLMN list of service PLMN 2.

[0222] In this embodiment of the application, the terminal device can register the information of the selected network (for example, see Table 1) into the network, which helps the core network device to associate multiple connections of multiple access devices based on the network identifier, thereby allowing the core network device to transmit data of different services on a specific network / RAT based on the network identifier / RAT.

[0223] Figure 6 illustrates a method where a terminal device, acting as a multi-access device, can simultaneously select two networks and inform the access network device and core network device of the selected networks respectively. It should be understood that the method shown in Figure 6 is applicable to completing registration with multiple networks through multiple registration processes. The method of this application embodiment is applicable to scenarios where different networks correspond to different mobility management network elements, or in other words, it is applicable to scenarios where multiple accesses of the terminal device are managed by different mobility management network elements. The method shown in Figure 6 includes steps S610 to S670.

[0224] In step S610, the terminal device selects network 1 and network 2, where network 1 corresponds to RAT1 and network 2 corresponds to RAT2.

[0225] In some implementations, network 1 and network 2 are VPLMN and HPLMN, respectively, or network 1 and network 2 are PLMN and NPN, respectively.

[0226] In step S615, the terminal device sends the second information to the access network device 1.

[0227] In some implementations, access network device 1 can be an access network device that supports RAT1 corresponding to network 1.

[0228] In some implementations, the second information includes RRC messages and NAS messages, with the identifier of network 1 and / or the RAT1 corresponding to network 1 carried in the RRC message, and the identifier of network 2 and / or the RAT2 corresponding to network 2 carried in the NAS message.

[0229] In some implementations, the NAS message may include Request 1 (as an example of a first request), which requests the registration of the terminal device. Additionally, Request 1 may carry information indicating that the terminal device is a multi-access device.

[0230] In step S620, access network device 1 selects mobility management network element 1 based on the identifier of network 1 and the RAT1 corresponding to network 1.

[0231] In step S625, access network device 1 sends second information to mobility management network element 1.

[0232] In some implementations, the second information includes an N2 message and a request 1, wherein the N2 message contains the identifier of network 1 and the RAT1 corresponding to network 1, and the request 1 is used to request the registration of the terminal device, and the request 1 carries the identifier of network 2 and the RAT1 corresponding to network 2.

[0233] In step S630, mobility management element 1 sends seventh information to UDM, which is used to instruct network 1 and network 2.

[0234] In some implementations, the seventh information can also be used to indicate RAT1 for network 1 and RAT2 for network 2.

[0235] In some implementations, if the mobility management network element 1 determines, based on the terminal device's subscription data and local network configuration, that it needs to support the terminal device's multi-access capability, then the mobility management network element 1 registers the information of network 1 selected by the terminal device and the information of network 2 (for example, the information of network 1 may include the identifier of network 1 and / or the RAT1 corresponding to network 1, and the information of network 2 may include the identifier of network 2 and / or the RAT2 corresponding to network 2) into the UDM, in order to associate the information of network 1 selected by the terminal device with the information of network 2.

[0236] In step S635, the UDM stores in the context of the terminal device the identifier and / or RAT of the network corresponding to each access in the multiple access devices.

[0237] In some implementations, the network information stored in the context of the terminal device can be seen in Table 1. Assume the terminal device, as a multi-access device, supports the first access corresponding to network 1 and the second access corresponding to network 2. Taking network 1 and network 2 as PLMNs as examples, the terminal device's context can store one or more of the following parameters corresponding to the access: the serving AMF identifier for the first access, the registered PLMN identifier for the first access, the RAT1 information for the first access, the serving AMF identifier for the second access, the registered PLMN identifier for the second access, and the RAT2 information for the second access.

[0238] It should be noted that, in the embodiments of this application, the parameters corresponding to the first access and the parameters corresponding to the second access may be the same or different. That is to say, for the first access and the second access, the service AMF identifier, registration PLMN identifier, and RAT shown in Table 1 may be the same or different.

[0239] In some implementations, the mobility management element 1 can subscribe to changes in the UDM terminal device context.

[0240] In step S640, mobility management network element 1 sends a registration acceptance message 1 to the terminal device.

[0241] In some implementations, the registration acceptance message 1 may carry information indicating the multi-access capability of the accepting terminal device, which is also known as an indication of support for multi-access capability.

[0242] In some implementations, the registration acceptance message 1 may contain a list of NSSAI and / or EPLMN configured for the service PLMN.

[0243] It should be noted that the configuration NSSAI and / or EPLMN list of the aforementioned service PLMN can be configured for both network 1 and network 2. In this case, network 1 and network 2 can use the same configuration NSSAI and / or EPLMN list. However, in this embodiment, the configuration NSSAI and / or EPLMN list of the aforementioned service PLMN can be configured for network 1 and network 2 separately. In this case, network 1 can use the configuration NSSAI and / or EPLMN list of service PLMN 1, and network 2 can use the configuration NSSAI and / or EPLMN list of service PLMN 2.

[0244] In step S645, the terminal device sends the second information to the access network device 2.

[0245] In some implementations, access network device 2 can be an access network device that supports RAT2 corresponding to network 2.

[0246] In some implementations, the second information includes RRC messages and NAS messages, with the identifier of network 2 and / or the RAT2 corresponding to network 2 carried in the RRC message, and the identifier of network 1 and / or the RAT1 corresponding to network 1 carried in the NAS message.

[0247] In some implementations, the NAS message may include request 2 (as an example of a second request), which requests the registration of the terminal device. Additionally, request 2 may carry information indicating that the terminal device is a multi-access device.

[0248] In step S650, access network device 2 selects mobility management network element 2 based on the identifier of network 2 and the RAT2 corresponding to network 2.

[0249] In step S655, the access network device 2 sends the second information to the mobility management network element 2.

[0250] In some implementations, the second information includes an N2 message and a request 2, wherein the N2 message contains the identifier of network 2 and the RAT2 corresponding to network 2, and the request 2 is used to request the registration of the terminal device, and the request 2 carries the identifier of network 1 and the RAT1 corresponding to network 1.

[0251] In step S660, mobility management element 2 sends a seventh message to UDM, which is used to instruct network 1 and network 2.

[0252] In some implementations, the seventh information can also be used to indicate RAT1 for network 1 and RAT2 for network 2.

[0253] In some implementations, if the mobility management network element 2 determines that it needs to support the multi-access capability of the terminal device based on the terminal device's subscription data and local network configuration, then the mobility management network element 2 registers the information of network 1 selected by the terminal device and the information of network 2 (for example, the information of network 1 may include the identifier of network 1 and / or the RAT1 corresponding to network 1, and the information of network 2 may include the identifier of network 2 and / or the RAT2 corresponding to network 2) into the UDM, so as to associate the information of network 1 selected by the terminal device with the information of network 2.

[0254] In step S665, the UDM stores in the context of the terminal device the identifier and / or RAT of the network corresponding to each access in the multiple access devices.

[0255] In some implementations, the network information stored in the context of the terminal device can be seen in Table 1. Assume the terminal device, as a multi-access device, supports the first access corresponding to network 1 and the second access corresponding to network 2. Taking network 1 and network 2 as PLMNs as examples, the terminal device's context can store one or more of the following parameters corresponding to the access: the serving AMF identifier for the first access, the registered PLMN identifier for the first access, the RAT1 information for the first access, the serving AMF identifier for the second access, the registered PLMN identifier for the second access, and the RAT2 information for the second access.

[0256] It should be noted that, in the embodiments of this application, the parameters corresponding to the first access and the parameters corresponding to the second access may be the same or different. That is to say, for the first access and the second access, the service AMF identifier, registration PLMN identifier, and RAT shown in Table 1 may be the same or different.

[0257] In some implementations, if the UDM verifies that the network information in the locally stored terminal device context differs from the identifier and / or RAT of the network corresponding to each access in the multi-access device indicated in step S660, the terminal device is considered to have re-selected two networks for registration. In this case, the UDM can update the locally stored terminal device context. Additionally, if Mobility Management Element 1 has subscribed to updates to the terminal device context, the UDM can notify Mobility Management Element 1 that the terminal device's context has been updated.

[0258] In step S670, the mobility management network element 2 sends a registration acceptance message 2 to the terminal device.

[0259] In some implementations, the registration acceptance message 2 may carry information indicating the multi-access capability of the accepting terminal device, which is also known as an indication of support for multi-access capability.

[0260] In some implementations, the registration acceptance message 2 may contain a list of NSSAI and / or EPLMN configured for the service PLMN.

[0261] It should be noted that the configuration NSSAI and / or EPLMN list of the aforementioned service PLMN can be configured for both network 1 and network 2. In this case, network 1 and network 2 can use the same configuration NSSAI and / or EPLMN list. However, in this embodiment, the configuration NSSAI and / or EPLMN list of the aforementioned service PLMN can be configured for network 1 and network 2 separately. In this case, network 1 can use the configuration NSSAI and / or EPLMN list of service PLMN 1, and network 2 can use the configuration NSSAI and / or EPLMN list of service PLMN 2.

[0262] In this embodiment of the application, the terminal device can register the information of the selected network (for example, see Table 1) into the network, which helps the core network device to associate multiple connections of multiple access devices based on the network identifier, thereby allowing the core network device to transmit data of different services on a specific network / RAT based on the network identifier / RAT.

[0263] On the other hand, Mobility Management Element 1 and / or Mobility Management Element 2 can send information about multiple networks selected by the terminal device to the UDM. This helps to prevent the UDM from mistakenly believing that the registration process for registering with Network 2 is triggered by the terminal device reselecting a network when multiple connections of the terminal device are managed by different Mobility Management Element, thereby deregistering the Mobility Management Element associated with Network 1 and causing the terminal device to be unable to continue communicating with the network through multiple connections.

[0264] It should be noted that in the scheme described above, access network device 1 and access network device 2 can be different or the same access network devices. Correspondingly, mobility management network element 1 and mobility management network element 2 can be different or the same mobility management network element. If access network device 1 and access network device 2 are the same access network devices, and correspondingly, mobility management network element 1 and mobility management network element 2 are the same mobility management network element, it can be understood that regardless of whether the mobility management network elements and / or access network devices corresponding to the multiple accesses of the terminal device are the same, the terminal device needs to register with different networks in multiple networks through multiple registration processes, which helps to reduce the modification of the traditional registration process.

[0265] The method shown in Figure 7 describes a scheme in which a terminal device initiates registration with network 2 based on the triggering conditions of network 2 after selecting network 1. The method shown in Figure 7 includes steps S710 to S760.

[0266] In step S710, the terminal device selects network 1, where network 1 corresponds to RAT1.

[0267] In some implementations, network 1 can be a PLMN or an NPN.

[0268] In step S715, the terminal device sends information 1 (as an example of the second information) to the access network device 1.

[0269] In some implementations, access network device 1 can be an access network device that supports RAT1 corresponding to network 1.

[0270] In some implementations, information 1 can be an AN message.

[0271] In some implementations, information 1 may include request 1 and an identifier of network 1, wherein the identifier of network 1 may be, for example, a PLMN-1 ID or a combination of the PLMN-1 ID and NID-1. Additionally, request 1 is used to request registration of the terminal device. Furthermore, request 1 may also carry information indicating that the terminal device is a multi-access device.

[0272] In step S720, access network device 1 selects mobility management network element 1 based on the identifier of network 1.

[0273] In step S725, access network device 1 sends information 2 to mobility management network element 1.

[0274] In some implementations, message 2 can be an N2 message.

[0275] In some implementations, information 2 may include request 1 and an identifier of network 1, wherein the identifier of network 1 may be, for example, a PLMN-1 ID or a combination of PLMN-1 ID and NID-1. Additionally, request 1 is used to request registration of the terminal device. Furthermore, request 1 may also carry information indicating that the terminal device is a multi-access device.

[0276] In step S730, mobility management element 1 sends seventh information to UDM, which is used to instruct network 1.

[0277] In some implementations, the seventh information may be used to indicate one or more of the following: the network function type (NF type) (e.g., AMF) corresponding to mobility network element 1; the NF ID (e.g., AMF ID) corresponding to mobility network element 1; the terminal device identifier (e.g., SUPI); the RAT type of RAT1; the access type corresponding to network 1; the registration type corresponding to request 1; and the identifier of the currently registered network.

[0278] In some implementations, the mobility management network element can determine the RAT type of RAT1 based on the identifier of access network device 1 and the location information (e.g., TAI) of the terminal device indicated to it by access network device 1.

[0279] In some implementations, the access type can include 3GPP access or non-3GPP access.

[0280] In some implementations, the registration type indicated by the seventh information can be initial registration.

[0281] In some implementations, the identifier of the currently registered network is the identifier of network 1.

[0282] In some implementations, if the mobility management network element determines that it needs to support the multi-access capability of the terminal device based on the terminal device's subscription data and local network configuration, the mobility management network element will register the information of the network 1 selected by the terminal device (e.g., the identifier of network 1 and / or the RAT1 corresponding to network 1) in the UDM.

[0283] In step S735, the mobility management network element 1 sends third information to the terminal device to indicate the triggering conditions for registering with the network 2. For an introduction to the triggering conditions, please refer to Embodiment 2 above.

[0284] In some implementations, the third information can be carried in the registration accept message sent by the mobility management network element to the terminal device in response to request 1. In other implementations, the third information can be carried in the terminal device configuration update.

[0285] In some implementations, the triggering condition can be obtained by the mobility management element from the terminal device subscription data stored in the UDM. In other implementations, the triggering condition can be obtained after the mobility management element interacts with other mobility management elements.

[0286] In some implementations, the third information can also be used to indicate multiple networks selected for network 2. These multiple networks may include mobility management network element 1 and multiple networks supported by mobility management network element 2. In this case, triggering conditions can be indicated for each of the multiple networks.

[0287] In some implementations, multiple networks are represented by multiple PLMNs, which can be represented by a PLMN list. For example, multiple PLMNs in the PLMN list can be arranged according to priority. Alternatively, the PLMN list can reuse a traditional EPLMN list. Another example is that the PLMN list can include combinations of multiple networks and RATs, and these combinations can be arranged according to priority. Yet another example is that the PLMN list can include multiple RATs arranged according to priority, and multiple RATs can be used to access a single PLMN.

[0288] In step S740, the terminal device selects network 2 based on the third information, and sends information 3 to access network device 2 when the triggering condition is met.

[0289] In some implementations, when the triggering condition is met, the terminal device can select an additional network as network 2 based on the multiple networks indicated in the third information, and register with the network through the RAT corresponding to network 2 without changing the registration status of network 1.

[0290] In some implementations, request 2 can be an AN message.

[0291] In some implementations, request 2 may include request 2 and an identifier of network 2, wherein the identifier of network 2 may be, for example, a PLMN-2 ID or a combination of the PLMN-2 ID and NID-2. Additionally, request 2 is used to request registration of the terminal device. Furthermore, request 2 may also carry information indicating that the terminal device is a multi-access device.

[0292] In step S745, access network device 2 selects mobility management network element 2 based on the identifier of network 2.

[0293] In step S750, access network device 2 sends information 4 to mobility management network element 2.

[0294] In some implementations, message 4 can be an N2 message.

[0295] In some implementations, information 4 may include an identifier for network 4, where the identifier for network 2 may be, for example, a PLMN-2 ID or a combination of the PLMN-2 ID and NID-2. Additionally, request 2 is used to request registration of the terminal device. Furthermore, request 2 may also carry information indicating that the terminal device is a multi-access device.

[0296] In step S755, the mobility management network element 2 sends the seventh information to the UDM, which is used to instruct the network 2.

[0297] In some implementations, the seventh information may be used to indicate one or more of the following: the network function type (NF type) (e.g., AMF) corresponding to mobility network element 2; the NF ID (e.g., AMF ID) corresponding to mobility network element 2; the terminal device identifier (e.g., SUPI); the RAT type of RAT2; the access type corresponding to network 2; the registration type corresponding to request 2; the identifier of the currently registered network; and network 2 as an additional network selected by the terminal device.

[0298] In some implementations, the mobility management network element 2 can determine the RAT type of RAT2 based on the identifier of the access network device 2 and the location information (e.g., TAI) of the terminal device indicated to it by the access network device 2.

[0299] In some implementations, the access type can include 3GPP access or non-3GPP access.

[0300] In some implementations, the registration type indicated by the seventh information can be either initial registration or registration update.

[0301] In some implementations, the identifier of the currently registered network is the identifier of network 2.

[0302] In some implementations, if the mobility management network element determines that it needs to support the multi-access capability of the terminal device based on the terminal device's subscription data and local network configuration, the mobility management network element will register the information of the network 2 selected by the terminal device (e.g., the identifier of network 2 and / or the RAT2 corresponding to network 2) in the UDM.

[0303] In some implementations, the information in the seventh piece of information that indicates the network additionally selected by network 2 for the terminal device can also be called additional network registration indication information. This allows the UDM to confirm, based on this additional network registration indication information and the terminal device's subscription data (e.g., support for multiple access capabilities), that the terminal device has selected a network to support multiple access capabilities, rather than switching from network 1 to network 2. This helps prevent the UDM from mistakenly believing that the terminal device has switched from network 1 to network 2 and registering the terminal device in network 1. For example, by deleting the parameters related to the first access in Table 1.

[0304] In step S760, the mobility management network element 2 sends a registration acceptance message 2 to the terminal device.

[0305] In some implementations, if the UDM authorizes the terminal device to register with multiple networks based on the terminal device's subscription message, the UDM can send a registration acceptance message to the terminal device through Mobility Management Element 2. Conversely, the UDM can send a registration rejection message to the terminal device through Mobility Management Element 2 to refuse the terminal device's registration with Network 2.

[0306] In some implementations, the registration acceptance message 2 may carry information indicating the multi-access capability of the accepting terminal device, which is also known as an indication of support for multi-access capability.

[0307] In some implementations, the registration acceptance message 2 may contain a list of NSSAI and / or EPLMN configured for the service PLMN.

[0308] It should be noted that the configuration NSSAI and / or EPLMN list of the aforementioned service PLMN can be configured for both network 1 and network 2. In this case, network 1 and network 2 can use the same configuration NSSAI and / or EPLMN list. However, in this embodiment, the configuration NSSAI and / or EPLMN list of the aforementioned service PLMN can be configured for network 1 and network 2 separately. In this case, network 1 can use the configuration NSSAI and / or EPLMN list of service PLMN 1, and network 2 can use the configuration NSSAI and / or EPLMN list of service PLMN 2.

[0309] The method embodiments of this application have been described in detail above with reference to Figures 1 to 7. The apparatus embodiments of this application will be described in detail below with reference to Figures 8 to 11. It should be understood that the descriptions of the method embodiments correspond to the descriptions of the apparatus embodiments. Therefore, any parts not described in detail can be referred to the foregoing method embodiments.

[0310] Figure 8 is a schematic diagram of a terminal device according to an embodiment of this application. The terminal device 800 shown in Figure 8 includes a processing unit 810.

[0311] The processing unit 810 is used to register with a first network and a second network based on first information. The terminal device is a multi-access device. The first information includes one or more of the following: the correspondence between multiple networks and Radio Access Technologies (RATs), the multiple networks including the first network and the second network; and the triggering conditions for registering with the second network.

[0312] In some implementations, the first network and the second network are the same network, and the RAT corresponding to the first network is different from the RAT corresponding to the second network; or the first network and the second network are different networks.

[0313] In some implementations, the first network and the second network are public land mobile networks (PLMNs) and / or non-public networks (NPNs).

[0314] In some implementations, the different correspondences between the multiple networks and the RAT have different priorities. The priority of the correspondence between the first network and the second network is higher than or equal to the priority of the other correspondences, which are the correspondences between the multiple networks and the RAT other than the correspondence between the first network and the second network.

[0315] In some implementations, the first information includes the correspondence, and the processing unit is further configured to: select the first network and the second network based on the correspondence between the plurality of networks and the RAT.

[0316] In some implementations, the terminal device further includes: a first sending unit, configured to send second information to a first access network device, the second information being used to indicate the first network and the second network.

[0317] In some implementations, the second information carries one or more of the following: slice identification information; the identifier of the terminal device; the identifier of the first network; the identifier of the second network; information indicating the RAT corresponding to the first network; information indicating the RAT corresponding to the second network; and information indicating that the terminal device is the multi-access device.

[0318] In some implementations, the second information is carried in an access network message that carries a first request, which is used to request the registration of the terminal device with the first network and the second network.

[0319] In some implementations, the identifier of the first network and / or the information used to indicate the RAT corresponding to the first network is carried in the access stratum AS message corresponding to the second information, and / or the identifier of the second network and / or the information used to indicate the RAT corresponding to the second network is carried in the non-access stratum NAS message corresponding to the second information.

[0320] In some implementations, the second information is carried in an access network message that carries a first request, which is used to request the terminal device to register with the first network.

[0321] In some implementations, the processing unit is configured to send a second request to the second access network device, the second request being used to request the terminal device to register with the second network.

[0322] In some implementations, the identifier of the first network and / or the information used to indicate the RAT corresponding to the first network is carried in the NAS message corresponding to the second request, and / or the identifier of the second network and / or the information used to indicate the RAT corresponding to the second network is carried in the AS message corresponding to the second request.

[0323] In some implementations, the triggering condition is associated with one or more of the following: a first time; a first location; the communication quality of the terminal device in the first network; and the state of the terminal device in the first network.

[0324] In some implementations, the communication quality of the terminal device in the first network is determined based on one or more of the following parameters: the maximum total data transmission rate supported by the terminal device in the first network; the packet loss rate of the terminal device in the first network; and the signal strength of the terminal device communicating in the first network.

[0325] In some implementations, the triggering conditions include one or more of the following: the terminal device is in the first time period; the terminal device is located in the first position; the communication quality of the terminal device in the first network is lower than a threshold; the state of the terminal device in the first network is connected or idle.

[0326] In some implementations, the terminal device further includes: a first receiving unit, configured to receive third information sent by a third access network device, the third information being used to indicate the triggering condition.

[0327] In some implementations, the terminal device further includes: a second receiving unit, configured to receive fourth information sent by a mobility management network element, the fourth information being used to configure parameters of the first network and / or parameters of the second network, wherein the parameters include one or more of the following: one or more EPLMNs; configured NSSAI.

[0328] In some implementations, the fourth piece of information is a registration acceptance message.

[0329] In some implementations, the multi-access device includes one or more of the following: a device that accesses multiple access networks; a device that registers with the core network through multiple access networks; a device that establishes a connection with the core network through multiple access networks; and a device that has multiple NAS connections with the mobility management network element.

[0330] Figure 9 is a schematic diagram of an access network device according to an embodiment of this application. The access network device 900 shown in Figure 9 includes: a receiving unit 910.

[0331] The receiving unit 910 is used to receive second information or third information sent by a terminal device, wherein the terminal device is a multi-access device, wherein the second information is used to indicate a first network and a second network, and the third information is used to indicate the triggering conditions for registering with the second network.

[0332] In some implementations, the first network and the second network are the same network, and the RAT corresponding to the first network is different from the RAT corresponding to the second network; or the first network and the second network are different networks.

[0333] In some implementations, the first network and the second network are public land mobile networks (PLMNs) and / or non-public networks (NPNs).

[0334] In some implementations, the first network and the second network are selected based on a correspondence between multiple networks and Radio Access Technologies (RATs), wherein the multiple networks include the first network and the second network.

[0335] In some implementations, the different correspondences between the multiple networks and the RAT have different priorities. Specifically, the priority of the correspondence between the first network and the second network is higher than or equal to the priority of the other correspondences, which are the correspondences between the multiple networks and the RAT other than the correspondence between the first network and the second network.

[0336] In some implementations, the second information carries one or more of the following: slice identification information; the identifier of the terminal device; the identifier of the first network; the identifier of the second network; information indicating the RAT corresponding to the first network; information indicating the RAT corresponding to the second network; and information indicating that the terminal device is the multi-access device.

[0337] In some implementations, the identifier of the first network and / or the information used to indicate the RAT corresponding to the first network is carried in the AS message corresponding to the second information, and / or the identifier of the second network and / or the information used to indicate the RAT corresponding to the second network is carried in the NAS message corresponding to the second information.

[0338] In some implementations, the two pieces of information are carried in a first request, which is used to request the terminal device to register with the first network.

[0339] In some implementations, the access network device further includes: a first sending unit, configured to send the first request to a first mobility management network element, the first mobility management network element being associated with the first network and / or the second network.

[0340] In some implementations, the receiving unit is configured to receive a second request sent by the terminal device, the second request being for requesting the terminal device to register with the second network.

[0341] In some implementations, the identifier of the first network and / or the information used to indicate the RAT corresponding to the first network is carried in the NAS message corresponding to the second request, and / or the identifier of the second network and / or the information used to indicate the RAT corresponding to the second network is carried in the AS message corresponding to the second request.

[0342] In some implementations, the access network device further includes: a second sending unit, configured to send the second request to a second mobility management network element, the second mobility management network element being associated with the first network and / or the second network.

[0343] In some implementations, the first request is used to request the registration of the terminal device with the first network and the second network.

[0344] In some implementations, the access network device further includes: a third sending unit, configured to send fifth information to a third mobility management network element, the fifth information being used to instruct the terminal device to request access to the first network and the second network, wherein the third mobility management network element supports the first network and / or the second network.

[0345] In some implementations, the fifth information includes one or more of the following: the identifier of the first network; the identifier of the second network; the identifier information of the terminal device; the location information of the terminal device; the identifier information of the access network device; and information indicating that the terminal device is a multi-access device.

[0346] In some implementations, the fifth piece of information is used to request registration of the terminal device.

[0347] In some implementations, the triggering condition is associated with one or more of the following: a first time; a first location; the communication quality of the terminal device in the first network; and the state of the terminal device in the first network.

[0348] In some implementations, the communication quality of the terminal device in the first network is determined based on one or more of the following parameters: the maximum total data transmission rate supported by the terminal device in the first network; the packet loss rate of the terminal device in the first network; and the signal strength of the terminal device communicating in the first network.

[0349] In some implementations, the triggering conditions include one or more of the following: the terminal device is in the first time period; the terminal device is located in the first position; the communication quality of the terminal device in the first network is lower than a threshold; the state of the terminal device in the first network is connected or idle.

[0350] In some implementations, the sending unit is further configured to send sixth information to a fourth mobility management network element, the sixth information being used to instruct the terminal device to register with the first network, and the mobility management network element being associated with the second network.

[0351] In some implementations, the sixth information includes one or more of the following: the identifier of the first network; information indicating that the terminal device is a multi-access device.

[0352] In some implementations, the multi-access device includes one or more of the following: a device that accesses multiple access networks; a device that registers with the core network through multiple access networks; a device that establishes a connection with the core network through multiple access networks; and a device that has multiple NAS connections with the mobility management network element.

[0353] Figure 10 is a schematic diagram of the core network device according to an embodiment of this application. The core network device 1000 shown in Figure 10 is a mobility management network element, and the core network device 1000 includes: a transmission unit 1010.

[0354] The sending unit 1010 is used to send seventh information to the unified data management network element. The seventh information is used to indicate the first network and / or the second network selected by the terminal device, wherein the terminal device is a multi-access device.

[0355] In some implementations, the seventh information is used to indicate the RAT corresponding to the first network and / or the RAT corresponding to the second network.

[0356] In some implementations, the first network and the second network are the same network, and the RAT corresponding to the first network is different from the RAT corresponding to the second network; or the first network and the second network are different networks.

[0357] In some implementations, the core network device further includes: a first receiving unit, configured to receive second information sent by the access network device, the second information being used to indicate the first network and the second network, wherein the mobility management network element is associated with the first network and / or the second network.

[0358] In some implementations, the second information carries one or more of the following: slice identification information; the identifier of the terminal device; the identifier of the first network; the identifier of the second network; information indicating the RAT corresponding to the first network; information indicating the RAT corresponding to the second network; and information indicating that the terminal device is the multi-access device.

[0359] In some implementations, the identifier of the first network and / or the information used to indicate the RAT corresponding to the first network is carried in the AS message corresponding to the second information, and / or the identifier of the second network and / or the information used to indicate the RAT corresponding to the second network is carried in the NAS message corresponding to the second information.

[0360] In some implementations, the second information is carried in an access network message that carries a first request, which is used to request the terminal device to register with the first network.

[0361] In some implementations, the core network device further includes: a second receiving unit, configured to receive a second request sent by the access network device, the second request being used to request registration of the terminal device with a second network, wherein the mobility management network element is associated with the first network and / or the second network.

[0362] In some implementations, the identifier of the first network and / or the information used to indicate the RAT corresponding to the first network is carried in the NAS message corresponding to the second request, and / or the identifier of the second network and / or the information used to indicate the RAT corresponding to the second network is carried in the AS message corresponding to the second request.

[0363] In some implementations, the core network device further includes: a third receiving unit, configured to receive fifth information sent by the access network device, the fifth information being used to instruct the terminal device to request access to the first network and the second network, wherein the third mobility management network element supports the first network and / or the second network.

[0364] In some implementations, the fifth information includes one or more of the following: the identifier of the first network; the identifier of the second network; the identifier information of the terminal device; the location information of the terminal device; the identifier information of the access network device; and information indicating that the terminal device is a multi-access device.

[0365] In some implementations, the core network device further includes: a fourth receiving unit, configured to receive sixth information sent by the access network device, the sixth information being used to instruct the terminal device to register to the first network, and the mobility management network element being associated with the second network.

[0366] In some implementations, the sixth information includes one or more of the following: the identifier of the first network; information indicating that the terminal device is a multi-access device.

[0367] In some implementations, the sending unit is used to send third information to the terminal device, the third information being used to indicate the triggering conditions for accessing the second network.

[0368] In some implementations, the triggering condition is associated with one or more of the following: a first time; a first location; the communication quality of the terminal device in the first network; and the state of the terminal device in the first network.

[0369] In some implementations, the communication quality of the terminal device in the first network is determined based on one or more of the following parameters: the maximum total data transmission rate supported by the terminal device in the first network; the packet loss rate of the terminal device in the first network; and the signal strength of the terminal device communicating in the first network.

[0370] In some implementations, the triggering conditions include one or more of the following: the terminal device is in the first time period; the terminal device is located in the first position; the communication quality of the terminal device in the first network is lower than a threshold; the state of the terminal device in the first network is connected or idle.

[0371] In some implementations, the third information is carried in a message accepting the terminal device's registration with the first network element, or the third information is carried in a terminal device configuration update message.

[0372] In some implementations, the sending unit is further configured to send fourth information to the terminal device, the fourth information being used to configure parameters of the first network and / or parameters of the second network, wherein the parameters include one or more of the following: one or more EPLMNs; configured NSSAI.

[0373] In some implementations, the fourth piece of information is a registration acceptance message.

[0374] In an optional embodiment, the processing unit 810 may be a processor 1110. The terminal device 900 may also include a transceiver 1130 and a memory 1120, as shown in FIG11.

[0375] In an optional embodiment, the receiving unit 910 may be a transceiver 1130. The access network device 900 may also include a processor 1110 and a memory 1120, as shown in FIG11.

[0376] In an optional embodiment, the transmitting unit 1010 may be a transceiver 1130. The core network device 1000 may also include a processor 1110 and a memory 1120, as shown in FIG11.

[0377] Figure 11 is a schematic structural diagram of a communication device according to an embodiment of this application. The dashed lines in Figure 11 indicate that the unit or module is optional. This device 1100 can be used to implement the methods described in the above method embodiments. Device 1100 can be a chip, a terminal device, or a network device.

[0378] Apparatus 1100 may include one or more processors 1110. The processor 1110 may support apparatus 1100 in implementing the methods described in the preceding method embodiments. The processor 1110 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0379] The apparatus 1100 may further include one or more memories 1120. The memories 1120 store a program that can be executed by the processor 1110, causing the processor 1110 to perform the methods described in the preceding method embodiments. The memories 1120 may be independent of the processor 1110 or integrated within the processor 1110.

[0380] The device 1100 may also include a transceiver 1130. The processor 1110 can communicate with other devices or chips via the transceiver 1130. For example, the processor 1110 can send and receive data with other devices or chips via the transceiver 1130.

[0381] This application also provides a computer-readable storage medium for storing a program. This computer-readable storage medium can be applied to a terminal or network device provided in this application, and the program causes a computer to execute the methods performed by the terminal or network device in various embodiments of this application.

[0382] This application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to a terminal or network device provided in this application embodiment, and the program causes a computer to execute the methods performed by the terminal or network device in various embodiments of this application.

[0383] This application also provides a computer program. This computer program can be applied to the terminal or network device provided in this application, and the computer program causes the computer to execute the methods performed by the terminal or network device in various embodiments of this application.

[0384] It should be understood that the terms "system" and "network" in this application can be used interchangeably. Furthermore, the terminology used in this application is only for explaining specific embodiments of the application and is not intended to limit the application. The terms "first," "second," "third," and "fourth," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. In addition, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion.

[0385] In the embodiments of this application, the term "instruction" can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.

[0386] In the embodiments of this application, "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information.

[0387] In the embodiments of this application, the term "correspondence" can indicate a direct or indirect correspondence between two things, or an association between two things, or a relationship such as instruction and being instructed, configuration and being configured.

[0388] In this application embodiment, "predefined" or "preconfigured" can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices). This application does not limit the specific implementation method. For example, predefined can refer to what is defined in the protocol.

[0389] In this application embodiment, the "protocol" may refer to a standard protocol in the field of communication, such as the LTE protocol, the NR protocol, and related protocols applied to future communication systems. This application does not limit this.

[0390] In the embodiments of this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0391] In the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0392] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0393] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0394] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0395] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can read or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs, DVDs) or semiconductor media (e.g., solid-state disks, SSDs), etc.

[0396] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for wireless communication, characterized in that, include: The terminal device registers with a first network and a second network based on first information. The terminal device is a multi-access device, wherein the first information includes one or more of the following: The correspondence between multiple networks and Radio Access Technology (RAT), wherein the multiple networks include the first network and the second network; The triggering conditions for registering with the second network.

2. The method as described in claim 1, characterized in that, The first network and the second network are the same network, and the RAT corresponding to the first network is different from the RAT corresponding to the second network; or The first network and the second network are different networks.

3. The method as described in claim 1 or 2, characterized in that, The first network and the second network are public land mobile networks (PLMNs) and / or non-public networks (NPNs).

4. The method according to any one of claims 1-3, characterized in that, The different correspondences between the various networks and RATs have different priorities. Wherein, the priority of the correspondence to which the first network is located and the priority of the correspondence to which the second network is located are both higher than or equal to the priority of other correspondences, and the other correspondences are the correspondences between the plurality of networks and the RAT other than the correspondences to the first network and the second network.

5. The method according to any one of claims 1-4, characterized in that, The first information includes the correspondence, and the method further includes: The terminal device selects the first network and the second network based on the correspondence between the multiple networks and the RAT.

6. The method according to any one of claims 1-5, characterized in that, The method further includes: The terminal device sends second information to the first access network device, the second information being used to indicate the first network and the second network.

7. The method as described in claim 6, characterized in that, The second information carries one or more of the following: Slice identification information; The identifier of the terminal device; The identifier of the first network; The identifier of the second network; Information used to indicate the RAT corresponding to the first network; Information used to indicate the RAT corresponding to the second network; Information used to indicate that the terminal device is the multi-access device.

8. The method as described in claim 6 or 7, characterized in that, The second information is carried in an access network message that carries a first request, which is used to request the registration of the terminal device with the first network and the second network.

9. The method according to any one of claims 6-8, characterized in that, The identifier of the first network and / or the information indicating the RAT corresponding to the first network is carried in the access layer AS message corresponding to the second information, and / or The identifier of the second network and / or the information used to indicate the RAT corresponding to the second network are carried in the non-access stratum (NAS) message corresponding to the second information.

10. The method as described in claim 9, characterized in that, The second information is carried in an access network message that carries a first request, which is used to request the terminal device to register with the first network.

11. The method as described in claim 9 or 10, characterized in that, The terminal device registers with the first network and the second network based on the first information, including: The terminal device sends a second request to the second access network device, the second request being used to request registration of the terminal device with the second network.

12. The method as described in claim 11, characterized in that, The identifier of the first network and / or information indicating the RAT corresponding to the first network is carried in the NAS message corresponding to the second request, and / or The identifier of the second network and / or information indicating the RAT corresponding to the second network is carried in the AS message corresponding to the second request.

13. The method as described in claim 1 or 2, characterized in that, The triggering condition is associated with one or more of the following: First time; First position; The communication quality of the terminal device in the first network; The status of the terminal device in the first network.

14. The method as described in claim 13, characterized in that, The communication quality of the terminal device in the first network is determined based on one or more of the following parameters: The maximum total data transmission rate supported by the terminal device in the first network; The packet loss rate of the terminal device in the first network; The signal strength of the terminal device communicating in the first network.

15. The method as described in claim 13 or 14, characterized in that, The triggering conditions include one or more of the following: The terminal device is within the first time period; The terminal device is located in the first position; The communication quality of the terminal device in the first network is lower than a threshold. The terminal device is in a connected state or an idle state in the first network.

16. The method according to any one of claims 13-15, characterized in that, The method further includes: The terminal device receives third information sent by the third access network device, the third information being used to indicate the triggering condition.

17. The method according to any one of claims 1-16, characterized in that, The method further includes: The terminal device receives fourth information sent by a mobility management network element. The fourth information is used to configure parameters of the first network and / or parameters of the second network, wherein the parameters include one or more of the following: One or more EPLMNs; NSSAI configuration.

18. The method as described in claim 17, characterized in that, The fourth piece of information is the registration acceptance message.

19. The method according to any one of claims 1-18, characterized in that, The multi-access device includes one or more of the following: Devices that connect to multiple access networks; Devices that register with the core network through multiple access networks; Devices that establish connections with the core network through multiple access networks; A device with multiple NAS connections to the mobility management network element.

20. A method for wireless communication, characterized in that, include: The access network device receives second or third information sent by the terminal device, wherein the terminal device is a multi-access device. The second information is used to indicate the first network and the second network, and the third information is used to indicate the triggering conditions for registering with the second network.

21. The method as described in claim 20, characterized in that, The first network and the second network are the same network, and the RAT corresponding to the first network is different from the RAT corresponding to the second network; or The first network and the second network are different networks.

22. The method as described in claim 20 or 21, characterized in that, The first network and the second network are public land mobile networks (PLMNs) and / or non-public networks (NPNs).

23. The method as described in claim 20 or 21, characterized in that, The first network and the second network are selected based on the correspondence between multiple networks and Radio Access Technologies (RATs), and the multiple networks include the first network and the second network.

24. The method as described in claim 23, characterized in that, The different correspondences between the various networks and RATs have different priorities. Wherein, the priority of the correspondence to which the first network is located and the priority of the correspondence to which the second network is located are both higher than or equal to the priority of other correspondences, and the other correspondences are the correspondences between the plurality of networks and the RAT other than the correspondences to the first network and the second network.

25. The method according to any one of claims 20-24, characterized in that, The second information carries one or more of the following: Slice identification information; The identifier of the terminal device; The identifier of the first network; The identifier of the second network; Information used to indicate the RAT corresponding to the first network; Information used to indicate the RAT corresponding to the second network; Information used to indicate that the terminal device is the multi-access device.

26. The method as described in claim 24 or 25, characterized in that, The identifier of the first network and / or the information indicating the RAT corresponding to the first network is carried in the AS message corresponding to the second information, and / or The identifier of the second network and / or the information used to indicate the RAT corresponding to the second network are carried in the NAS message corresponding to the second information.

27. The method as described in claim 26, characterized in that, The second information is carried in an access network message that carries a first request, which is used to request the terminal device to register with the first network.

28. The method as described in claim 26 or 27, characterized in that, The method further includes: The access network device sends the first request to the first mobility management element, which is associated with the first network and / or the second network.

29. The method according to any one of claims 20-28, characterized in that, The method further includes: The access network device receives a second request sent by the terminal device, the second request being used to request the terminal device to register with the second network.

30. The method according to any one of claims 20-29, characterized in that, The identifier of the first network and / or information indicating the RAT corresponding to the first network is carried in the NAS message corresponding to the second request, and / or The identifier of the second network and / or information indicating the RAT corresponding to the second network is carried in the AS message corresponding to the second request.

31. The method according to any one of claims 20-30, characterized in that, The method further includes: The access network device sends the second request to the second mobility management element, which is associated with the first network and / or the second network.

32. The method according to any one of claims 20-25, characterized in that, The first request is used to request the registration of the terminal device with the first network and the second network.

33. The method as described in claim 32, characterized in that, The method further includes: The access network device sends a fifth message to the third mobility management network element, the fifth message being used to instruct the terminal device to request access to the first network and the second network. The third mobility management network element supports the first network and / or the second network.

34. The method as described in claim 33, characterized in that, The fifth piece of information includes one or more of the following: The identifier of the first network; The identifier of the second network; The identification information of the terminal device; The location information of the terminal device; The identification information of the access network device; Information used to indicate that the terminal device is a multi-access device.

35. The method as described in claim 33 or 34, characterized in that, The fifth piece of information is used to request registration of the terminal device.

36. The method according to any one of claims 20-22, characterized in that, The triggering condition is associated with one or more of the following: First time; First position; The communication quality of the terminal device in the first network; The status of the terminal device in the first network.

37. The method as described in claim 36, characterized in that, The communication quality of the terminal device in the first network is determined based on one or more of the following parameters: The maximum total data transmission rate supported by the terminal device in the first network; The packet loss rate of the terminal device in the first network; The signal strength of the terminal device communicating in the first network.

38. The method as described in claim 36 or 37, characterized in that, The triggering conditions include one or more of the following: The terminal device is within the first time period; The terminal device is located in the first position; The communication quality of the terminal device in the first network is lower than a threshold. The terminal device is in a connected state or an idle state in the first network.

39. The method according to any one of claims 36-38, characterized in that, The method further includes: The access network device sends a sixth message to the fourth mobility management element, the sixth message being used to instruct the terminal device to register with the first network, and the mobility management element being associated with the second network.

40. The method as described in claim 39, characterized in that, The sixth piece of information includes one or more of the following: The identifier of the first network; Information used to indicate that the terminal device is a multi-access device.

41. The method according to any one of claims 20-40, characterized in that, The multi-access device includes one or more of the following: Devices that connect to multiple access networks; Devices that register with the core network through multiple access networks; Devices that establish connections with the core network through multiple access networks; A device with multiple NAS connections to the mobility management network element.

42. A method for wireless communication, characterized in that, include: The mobility management network element sends a seventh message to the unified data management system. The seventh message is used to indicate the first network and / or the second network selected by the terminal device, wherein the terminal device is a multi-access device.

43. The method as described in claim 42, characterized in that, The seventh piece of information is used to indicate the RAT corresponding to the first network and / or the RAT corresponding to the second network.

44. The method as described in claim 42 or 43, characterized in that, The first network and the second network are the same network, and the RAT corresponding to the first network is different from the RAT corresponding to the second network; or The first network and the second network are different networks.

45. The method according to any one of claims 42-44, characterized in that, The method further includes: The mobility management network element receives second information sent by the access network device. The second information is used to indicate the first network and the second network. The mobility management network element is associated with the first network and / or the second network.

46. ​​The method as described in claim 45, characterized in that, The second information carries one or more of the following: Slice identification information; The identifier of the terminal device; The identifier of the first network; The identifier of the second network; Information used to indicate the RAT corresponding to the first network; Information used to indicate the RAT corresponding to the second network; Information used to indicate that the terminal device is the multi-access device.

47. The method according to any one of claims 42-46, characterized in that, The identifier of the first network and / or the information indicating the RAT corresponding to the first network is carried in the AS message corresponding to the second information, and / or The identifier of the second network and / or the information used to indicate the RAT corresponding to the second network are carried in the NAS message corresponding to the second information.

48. The method as described in claim 47, characterized in that, The second information is carried in an access network message that carries a first request, which is used to request the terminal device to register with the first network.

49. The method according to any one of claims 42-48, characterized in that, The method further includes: The mobility management network element receives a second request sent by the access network device. The second request is used to request the registration of the terminal device with the second network. The mobility management network element is associated with the first network and / or the second network.

50. The method as described in claim 49, characterized in that, The identifier of the first network and / or information indicating the RAT corresponding to the first network is carried in the NAS message corresponding to the second request, and / or The identifier of the second network and / or information indicating the RAT corresponding to the second network is carried in the AS message corresponding to the second request.

51. The method according to any one of claims 42-44, characterized in that, The method further includes: The mobility management network element receives a fifth message sent by the access network device, the fifth message being used to instruct the terminal device to request access to the first network and the second network. The mobility management network element supports the first network and / or the second network.

52. The method as described in claim 51, characterized in that, The fifth piece of information includes one or more of the following: The identifier of the first network; The identifier of the second network; The identification information of the terminal device; The location information of the terminal device; The identification information of the access network device; Information used to indicate that the terminal device is a multi-access device.

53. The method according to any one of claims 42-44, characterized in that, The method further includes: The mobility management network element receives a sixth message sent by the access network device. The sixth message is used to instruct the terminal device to register with the first network. The mobility management network element is associated with the second network.

54. The method as described in claim 53, characterized in that, The sixth piece of information includes one or more of the following: The identifier of the first network; Information used to indicate that the terminal device is a multi-access device.

55. The method as described in claim 53 or 54, characterized in that, The method further includes: The mobility management network element sends third information to the terminal device, the third information being used to indicate the triggering conditions for accessing the second network.

56. The method as described in claim 55, characterized in that, The triggering condition is associated with one or more of the following: First time; First position; The communication quality of the terminal device in the first network; The status of the terminal device in the first network.

57. The method as described in claim 56, characterized in that, The communication quality of the terminal device in the first network is determined based on one or more of the following parameters: The maximum total data transmission rate supported by the terminal device in the first network; The packet loss rate of the terminal device in the first network; The signal strength of the terminal device communicating in the first network.

58. The method as described in claim 56 or 57, characterized in that, The triggering conditions include one or more of the following: The terminal device is within the first time period; The terminal device is located in the first position; The communication quality of the terminal device in the first network is lower than a threshold. The terminal device is in a connected state or an idle state in the first network.

59. The method according to any one of claims 55-58, characterized in that, The third information is carried in a message accepting the terminal device's registration with the first network element, or the third information is carried in a terminal device configuration update message.

60. The method according to any one of claims 42-59, characterized in that, The method further includes: The mobility management network element sends fourth information to the terminal device, the fourth information being used to configure parameters of the first network and / or parameters of the second network, wherein the parameters include one or more of the following: One or more EPLMNs; NSSAI configuration.

61. The method as described in claim 60, characterized in that, The fourth piece of information is the registration acceptance message.

62. A terminal device, characterized in that, include: A processing unit is configured to register with a first network and a second network based on first information, wherein the terminal device is a multi-access device, and the first information includes one or more of the following: The correspondence between multiple networks and Radio Access Technology (RAT), wherein the multiple networks include the first network and the second network; The triggering conditions for registering with the second network.

63. The terminal device as described in claim 62, characterized in that, The first network and the second network are the same network, and the RAT corresponding to the first network is different from the RAT corresponding to the second network; or The first network and the second network are different networks.

64. The terminal device as described in claim 62 or 63, characterized in that, The first network and the second network are public land mobile networks (PLMNs) and / or non-public networks (NPNs).

65. The terminal device as described in any one of claims 62-64, characterized in that, The different correspondences between the various networks and RATs have different priorities. Wherein, the priority of the correspondence to which the first network is located and the priority of the correspondence to which the second network is located are both higher than or equal to the priority of other correspondences, and the other correspondences are the correspondences between the plurality of networks and the RAT other than the correspondences to the first network and the second network.

66. The terminal device as described in any one of claims 62-65, characterized in that, The first information includes the correspondence, and the processing unit is further configured to: select the first network and the second network based on the correspondence between the plurality of networks and the RAT.

67. The terminal device as described in any one of claims 62-66, characterized in that, The terminal device also includes: The first sending unit is configured to send second information to the first access network device, the second information being used to indicate the first network and the second network.

68. The terminal device as described in claim 67, characterized in that, The second information carries one or more of the following: Slice identification information; The identifier of the terminal device; The identifier of the first network; The identifier of the second network; Information used to indicate the RAT corresponding to the first network; Information used to indicate the RAT corresponding to the second network; Information used to indicate that the terminal device is the multi-access device.

69. The terminal device as described in claim 67 or 68, characterized in that, The second information is carried in an access network message that carries a first request, which is used to request the registration of the terminal device with the first network and the second network.

70. The terminal device as described in any one of claims 67-69, characterized in that, The identifier of the first network and / or the information indicating the RAT corresponding to the first network is carried in the access layer AS message corresponding to the second information, and / or The identifier of the second network and / or the information used to indicate the RAT corresponding to the second network are carried in the non-access stratum (NAS) message corresponding to the second information.

71. The terminal device as described in claim 70, characterized in that, The second information is carried in an access network message that carries a first request, which is used to request the terminal device to register with the first network.

72. The terminal device as described in claim 70 or 71, characterized in that, The processing unit is configured to send a second request to the second access network device, the second request being used to request the terminal device to register with the second network.

73. The terminal device as described in claim 72, characterized in that, The identifier of the first network and / or information indicating the RAT corresponding to the first network is carried in the NAS message corresponding to the second request, and / or The identifier of the second network and / or information indicating the RAT corresponding to the second network is carried in the AS message corresponding to the second request.

74. The terminal device as described in claim 62 or 63, characterized in that, The triggering condition is associated with one or more of the following: First time; First position; The communication quality of the terminal device in the first network; The status of the terminal device in the first network.

75. The terminal device as described in claim 74, characterized in that, The communication quality of the terminal device in the first network is determined based on one or more of the following parameters: The maximum total data transmission rate supported by the terminal device in the first network; The packet loss rate of the terminal device in the first network; The signal strength of the terminal device communicating in the first network.

76. The terminal device as described in claim 74 or 75, characterized in that, The triggering conditions include one or more of the following: The terminal device is within the first time period; The terminal device is located in the first position; The communication quality of the terminal device in the first network is lower than a threshold. The terminal device is in a connected state or an idle state in the first network.

77. The terminal device as described in any one of claims 74-76, characterized in that, The terminal device also includes: The first receiving unit is used to receive third information sent by the third access network device, the third information being used to indicate the triggering condition.

78. The terminal device as described in any one of claims 62-77, characterized in that, The terminal device also includes: The second receiving unit is configured to receive fourth information sent by the mobility management network element, the fourth information being used to configure parameters of the first network and / or parameters of the second network, wherein the parameters include one or more of the following: One or more EPLMNs; NSSAI configuration.

79. The terminal device as described in claim 78, characterized in that, The fourth piece of information is the registration acceptance message.

80. The terminal device as described in any one of claims 62-79, characterized in that, The multi-access device includes one or more of the following: Devices that connect to multiple access networks; Devices that register with the core network through multiple access networks; Devices that establish connections with the core network through multiple access networks; A device with multiple NAS connections to the mobility management network element.

81. An access network device, characterized in that, include: The receiving unit is used to receive second or third information sent by a terminal device, wherein the terminal device is a multi-access device. The second information is used to indicate the first network and the second network, and the third information is used to indicate the triggering conditions for registering with the second network.

82. The access network device as described in claim 81, characterized in that, The first network and the second network are the same network, and the RAT corresponding to the first network is different from the RAT corresponding to the second network; or The first network and the second network are different networks.

83. The access network equipment as described in claim 81 or 82, characterized in that, The first network and the second network are public land mobile networks (PLMNs) and / or non-public networks (NPNs).

84. The access network equipment as described in claim 81 or 82, characterized in that, The first network and the second network are selected based on the correspondence between multiple networks and Radio Access Technologies (RATs), and the multiple networks include the first network and the second network.

85. The access network device as described in claim 84, characterized in that, The different correspondences between the various networks and RATs have different priorities. Wherein, the priority of the correspondence to which the first network is located and the priority of the correspondence to which the second network is located are both higher than or equal to the priority of other correspondences, and the other correspondences are the correspondences between the plurality of networks and the RAT other than the correspondences to the first network and the second network.

86. The access network equipment as described in any one of claims 81-85, characterized in that, The second information carries one or more of the following: Slice identification information; The identifier of the terminal device; The identifier of the first network; The identifier of the second network; Information used to indicate the RAT corresponding to the first network; Information used to indicate the RAT corresponding to the second network; Information used to indicate that the terminal device is the multi-access device.

87. The access network equipment as described in claim 85 or 86, characterized in that, The identifier of the first network and / or the information indicating the RAT corresponding to the first network is carried in the AS message corresponding to the second information, and / or The identifier of the second network and / or the information used to indicate the RAT corresponding to the second network are carried in the NAS message corresponding to the second information.

88. The access network device as described in claim 87, characterized in that, The second information is carried in an access network message that carries a first request, which is used to request the terminal device to register with the first network.

89. The access network equipment as described in claim 87 or 88, characterized in that, The access network equipment also includes: The first sending unit is configured to send the first request to a first mobility management network element, the first mobility management network element being associated with the first network and / or the second network.

90. The access network device as described in any one of claims 81-89, characterized in that, The receiving unit is configured to receive a second request sent by the terminal device, the second request being used to request the terminal device to register with the second network.

91. The access network equipment as described in any one of claims 81-90, characterized in that, The identifier of the first network and / or information indicating the RAT corresponding to the first network is carried in the NAS message corresponding to the second request, and / or The identifier of the second network and / or information indicating the RAT corresponding to the second network is carried in the AS message corresponding to the second request.

92. The access network equipment as described in any one of claims 81-91, characterized in that, The access network equipment also includes: The second sending unit is configured to send the second request to a second mobility management network element, the second mobility management network element being associated with the first network and / or the second network.

93. The access network equipment as described in any one of claims 81-86, characterized in that, The first request is used to request the registration of the terminal device with the first network and the second network.

94. The access network device as described in claim 93, characterized in that, The access network equipment also includes: The third sending unit is configured to send fifth information to the third mobility management network element, the fifth information being used to instruct the terminal device to request access to the first network and the second network. The third mobility management network element supports the first network and / or the second network.

95. The access network device as described in claim 94, characterized in that, The fifth piece of information includes one or more of the following: The identifier of the first network; The identifier of the second network; The identification information of the terminal device; The location information of the terminal device; The identification information of the access network device; Information used to indicate that the terminal device is a multi-access device.

96. The access network equipment as described in claim 94 or 95, characterized in that, The fifth piece of information is used to request registration of the terminal device.

97. The access network equipment as described in any one of claims 81-83, characterized in that, The triggering condition is associated with one or more of the following: First time; First position; The communication quality of the terminal device in the first network; The status of the terminal device in the first network.

98. The access network device as described in claim 97, characterized in that, The communication quality of the terminal device in the first network is determined based on one or more of the following parameters: The maximum total data transmission rate supported by the terminal device in the first network; The packet loss rate of the terminal device in the first network; The signal strength of the terminal device communicating in the first network.

99. The access network equipment as described in claim 97 or 98, characterized in that, The triggering conditions include one or more of the following: The terminal device is within the first time period; The terminal device is located in the first position; The communication quality of the terminal device in the first network is lower than a threshold. The terminal device is in a connected state or an idle state in the first network.

100. The access network equipment as described in any one of claims 97-99, characterized in that, The sending unit is further configured to send sixth information to the fourth mobility management network element, the sixth information being used to instruct the terminal device to register with the first network, and the mobility management network element being associated with the second network.

101. The access network device as described in claim 100, characterized in that, The sixth piece of information includes one or more of the following: The identifier of the first network; Information used to indicate that the terminal device is a multi-access device.

102. The access network device as described in any one of claims 81-101, characterized in that, The multi-access device includes one or more of the following: Devices that connect to multiple access networks; Devices that register with the core network through multiple access networks; Devices that establish connections with the core network through multiple access networks; A device with multiple NAS connections to the mobility management network element.

103. A core network device, characterized in that, The core network equipment is a mobility management network element, including: The sending unit is used to send seventh information to the unified data management network element. The seventh information is used to indicate the first network and / or the second network selected by the terminal device, wherein the terminal device is a multi-access device.

104. The core network equipment as described in claim 103, characterized in that, The seventh piece of information is used to indicate the RAT corresponding to the first network and / or the RAT corresponding to the second network.

105. The core network equipment as described in claim 103 or 104, characterized in that, The first network and the second network are the same network, and the RAT corresponding to the first network is different from the RAT corresponding to the second network; or The first network and the second network are different networks.

106. The core network equipment as described in any one of claims 103-105, characterized in that, The core network equipment also includes: The first receiving unit is configured to receive second information sent by the access network device, the second information being used to indicate the first network and the second network, wherein the mobility management network element is associated with the first network and / or the second network.

107. The core network equipment as described in claim 106, characterized in that, The second information carries one or more of the following: Slice identification information; The identifier of the terminal device; The identifier of the first network; The identifier of the second network; Information used to indicate the RAT corresponding to the first network; Information used to indicate the RAT corresponding to the second network; Information used to indicate that the terminal device is the multi-access device.

108. The core network equipment as described in any one of claims 103-107, characterized in that, The identifier of the first network and / or the information indicating the RAT corresponding to the first network is carried in the AS message corresponding to the second information, and / or The identifier of the second network and / or the information used to indicate the RAT corresponding to the second network are carried in the NAS message corresponding to the second information.

109. The core network equipment as described in claim 108, characterized in that, The second information is carried in an access network message that carries a first request, which is used to request the terminal device to register with the first network.

110. The core network equipment as described in any one of claims 103-109, characterized in that, The core network equipment also includes: The second receiving unit is configured to receive a second request sent by the access network device, the second request being used to request registration of the terminal device with the second network, wherein the mobility management network element is associated with the first network and / or the second network.

111. The core network equipment as described in claim 110, characterized in that, The identifier of the first network and / or information indicating the RAT corresponding to the first network is carried in the NAS message corresponding to the second request, and / or The identifier of the second network and / or information indicating the RAT corresponding to the second network is carried in the AS message corresponding to the second request.

112. The core network equipment as described in any one of claims 103-105, characterized in that, The core network equipment also includes: The third receiving unit is configured to receive fifth information sent by the access network device, the fifth information being used to instruct the terminal device to request access to the first network and the second network. The third mobility management network element supports the first network and / or the second network.

113. The core network equipment as described in claim 112, characterized in that, The fifth piece of information includes one or more of the following: The identifier of the first network; The identifier of the second network; The identification information of the terminal device; The location information of the terminal device; The identification information of the access network device; Information used to indicate that the terminal device is a multi-access device.

114. The core network equipment as described in any one of claims 103-105, characterized in that, The core network equipment also includes: The fourth receiving unit is used to receive the sixth information sent by the access network device. The sixth information is used to instruct the terminal device to register with the first network, and the mobility management network element is associated with the second network.

115. The core network equipment as described in claim 114, characterized in that, The sixth piece of information includes one or more of the following: The identifier of the first network; Information used to indicate that the terminal device is a multi-access device.

116. The core network equipment as described in claim 114 or 115, characterized in that, The sending unit is used to send third information to the terminal device, the third information being used to indicate the triggering conditions for accessing the second network.

117. The core network equipment as described in claim 116, characterized in that, The triggering condition is associated with one or more of the following: First time; First position; The communication quality of the terminal device in the first network; The status of the terminal device in the first network.

118. The core network equipment as described in claim 117, characterized in that, The communication quality of the terminal device in the first network is determined based on one or more of the following parameters: The maximum total data transmission rate supported by the terminal device in the first network; The packet loss rate of the terminal device in the first network; The signal strength of the terminal device communicating in the first network.

119. The core network equipment as described in claim 117 or 118, characterized in that, The triggering conditions include one or more of the following: The terminal device is within the first time period; The terminal device is located in the first position; The communication quality of the terminal device in the first network is lower than a threshold. The terminal device is in a connected state or an idle state in the first network.

120. The core network equipment as described in any one of claims 116-119, characterized in that, The third information is carried in a message accepting the terminal device's registration with the first network element, or the third information is carried in a terminal device configuration update message.

121. The core network equipment as described in any one of claims 103-120, characterized in that, The sending unit is further configured to send fourth information to the terminal device, the fourth information being used to configure parameters of the first network and / or parameters of the second network, wherein the parameters include one or more of the following: One or more EPLMNs; NSSAI configuration.

122. The core network equipment as described in claim 121, characterized in that, The fourth piece of information is the registration acceptance message.

123. A terminal device, characterized in that, The device includes a transceiver, a memory, and a processor. The memory stores a program, and the processor invokes the program in the memory and controls the transceiver to receive or send signals so that the terminal device performs the method as described in any one of claims 1-19.

124. An access network device, characterized in that, The device includes a transceiver, a memory, and a processor. The memory stores a program, and the processor invokes the program in the memory and controls the transceiver to receive or transmit signals so that the network device performs the method as described in any one of claims 20-41.

125. A core network device, characterized in that, The device includes a transceiver, a memory, and a processor. The memory stores a program, and the processor invokes the program in the memory and controls the transceiver to receive or transmit signals so that the network device performs the method as described in any one of claims 42-61.

126. An apparatus, characterized in that, Includes a processor for calling a program from memory to cause the device to perform the method as described in any one of claims 1-61.

127. A chip, characterized in that, Includes a processor for calling a program from memory, causing a device on which the chip is mounted to perform the method as described in any one of claims 1-61.

128. A computer-readable storage medium, characterized in that, It contains a program that causes a computer to perform the method as described in any one of claims 1-61.

129. A computer program product, characterized in that, Includes a program that causes a computer to perform the method as described in any one of claims 1-61.

130. A computer program, characterized in that, The computer program causes the computer to perform the method as described in any one of claims 1-61.

Images