CN113574936B

CN113574936B - Wireless communication method, terminal equipment and network equipment

Info

Publication number: CN113574936B
Application number: CN201980094203.2A
Authority: CN
Inventors: 许阳; 杨宁
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2019-08-02
Filing date: 2019-08-02
Publication date: 2024-07-09
Anticipated expiration: 2039-08-02
Also published as: WO2021022428A1; CN113574936A

Abstract

A method of wireless communication, a terminal device and a network device, the method comprising: the terminal equipment determines a preferred core network type according to first information or second information, wherein the first information is information configured by the network equipment and used for core network selection, and the second information is history information selected by the core network of the terminal equipment; the terminal device preferably initiates a registration procedure to the core network of the preferred core network type.

Description

Wireless communication method, terminal equipment and network equipment

Technical Field

The embodiment of the application relates to the field of communication, in particular to a wireless communication method, terminal equipment and network equipment.

Background

In a New Radio (NR) system, two modes of independent (Standalone, SA) networking and Non-independent (Non-standalone, NSA) networking are supported, wherein the core network is a 5G core network (5G core,5 gc) for SA networks and a packet core evolution (Evolved Packet Core, EPC) for NSA networks.

When the area where the terminal device is located includes two networks, namely, SA and NSA, that is, the network device is covered by 5GC and EPC, the probability of the terminal device selecting which core network to access for registration to improve the registration success is a problem to be solved.

Disclosure of Invention

The embodiment of the application provides a wireless communication method, terminal equipment and network equipment, which are beneficial to improving the probability of successful registration of a core network.

In a first aspect, a method of wireless communication is provided, comprising: the terminal equipment determines a preferred core network type according to first information or second information, wherein the first information is information configured by the network equipment and used for core network selection, and the second information is history information selected by the core network of the terminal equipment; the terminal device preferably initiates a registration procedure to the core network of the preferred core network type.

In a second aspect, there is provided a method of wireless communication, comprising: the network equipment sends first information to the terminal equipment, wherein the first information is used for determining a preferred core network type by the terminal equipment, and the first information is information configured by the network equipment and used for core network selection.

In a third aspect, a terminal device is provided for performing the method of the first aspect or any possible implementation of the first aspect. In particular, the terminal device comprises means for performing the method of the first aspect or any of the possible implementations of the first aspect.

In a fourth aspect, a network device is provided for performing the method of the second aspect or any possible implementation of the second aspect. In particular, the network device comprises means for performing the method of the second aspect or any of the possible implementations of the second aspect.

In a fifth aspect, there is provided a terminal device comprising: including a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory and executing the method in the first aspect or various implementation manners thereof.

In a sixth aspect, there is provided a network device comprising: including a processor and a memory. The memory is for storing a computer program and the processor is for calling and running the computer program stored in the memory for performing the method of the second aspect or implementations thereof described above.

A seventh aspect provides a chip for implementing the method of any one of the first to second aspects or each implementation thereof.

Specifically, the chip includes: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method as in any one of the first to second aspects or implementations thereof described above.

In an eighth aspect, a computer-readable storage medium is provided for storing a computer program that causes a computer to perform the method of any one of the above-described first to second aspects or implementations thereof.

In a ninth aspect, there is provided a computer program product comprising computer program instructions for causing a computer to perform the method of any one of the first to second aspects or implementations thereof.

In a tenth aspect, there is provided a computer program which, when run on a computer, causes the computer to perform the method of any one of the first to second aspects or implementations thereof.

Based on the technical scheme, the terminal equipment can register the core network according to the network equipment configuration or the history information of the core network selection, thereby being beneficial to reducing the probability of core network registration failure and improving the user experience.

Drawings

Fig. 1 is a schematic diagram of an application scenario provided in an embodiment of the present application.

Fig. 2 is a schematic diagram of one way of connecting SA and NAS networking.

Fig. 3 is a schematic flow chart of core network registration by a terminal device.

Fig. 4 is a schematic diagram of a method of wireless communication provided by an embodiment of the present application.

Fig. 5 is a schematic diagram of another method of wireless communication provided by an embodiment of the present application.

Fig. 6 is a schematic block diagram of a terminal device according to an embodiment of the present application.

Fig. 7 is a schematic block diagram of a network device according to an embodiment of the present application.

Fig. 8 is a schematic block diagram of a communication device provided in another embodiment of the present application.

Fig. 9 is a schematic block diagram of a chip provided in an embodiment of the present application.

Fig. 10 is a schematic block diagram of a communication system in accordance with an embodiment of the present application.

Detailed Description

The following description of the technical solutions according to the embodiments of the present application will be given with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.

The technical scheme of the embodiment of the application can be applied to various communication systems, such as: global system for mobile communications (Global System of Mobile communication, GSM), code division multiple access (Code Division Multiple Access, CDMA), wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA), general Packet Radio Service (GPRS), long term evolution (Long Term Evolution, LTE), LTE frequency division duplex (Frequency Division Duplex, FDD), LTE time division duplex (Time Division Duplex, TDD), universal mobile telecommunications system (Universal Mobile Telecommunication System, UMTS), worldwide interoperability for microwave access (Worldwide Interoperability for Microwave Access, wiMAX) or 5G systems, and the like.

An exemplary communication system 100 to which embodiments of the present application may be applied is shown in fig. 1. The communication system 100 may include an access network device 110, and the access network device 110 may be a device that communicates with a terminal device 120 (or referred to as a communication terminal, terminal). The access network device 110 may provide communication coverage for a particular geographic area and may communicate with terminal devices located within the coverage area. Alternatively, the access network device 110 may be a base station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, a base station (NodeB, NB) in a WCDMA system, an evolved base station (Evolutional Node B, eNB or eNodeB) in an LTE system, or a radio controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or the network device may be a mobile switching center, a relay station, an access point, a vehicle device, a wearable device, a hub, a switch, a bridge, a router, a network-side device in a 5G network, or a network device in a future evolved public land mobile network (Public Land Mobile Network, PLMN), etc.

The communication system 100 further comprises at least one terminal device 120 located within the coverage area of the access network device 110. "terminal device" as used herein includes, but is not limited to, a connection via a wireline, such as via a public-switched telephone network (Public Switched Telephone Networks, PSTN), a digital subscriber line (Digital Subscriber Line, DSL), a digital cable, a direct cable connection; and/or another data connection/network; and/or via a wireless interface, e.g., for a cellular network, a wireless local area network (wireless Local Area Network, wLAN), a digital television network such as a DVB-H network, a satellite network, an AM-FM broadcast transmitter; and/or means of the other terminal device arranged to receive/transmit communication signals; and/or an internet of things (Internet of Things, ioT) device. Terminal devices arranged to communicate over a wireless interface may be referred to as "wireless communication terminals", "wireless terminals" or "mobile terminals". Examples of mobile terminals include, but are not limited to, satellites or cellular telephones; a personal communications system (Personal Communications System, PCS) terminal that may combine a cellular radiotelephone with data processing, facsimile and data communications capabilities; a PDA that may include a radiotelephone, pager, internet/intranet access, web browser, organizer, calendar, and/or a global positioning system (Global Positioning System, GPS) receiver; and conventional laptop and/or palmtop receivers or other electronic devices that include a radiotelephone transceiver. A terminal device may refer to an access terminal, user Equipment (UE), subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or User Equipment. An access terminal may be a cellular telephone, a cordless telephone, a session initiation protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a Personal digital assistant (Personal DIGITAL ASSISTANT, PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a 5G network or a terminal device in a future evolved PLMN, etc.

Alternatively, direct terminal (D2D) communication may be performed between the terminal devices 120.

Alternatively, the 5G system or 5G network may also be referred to as a New Radio (NR) system or NR network.

Optionally, in some scenarios, the communication system 100 may further include an access network device 130, and the access network device 130 may also provide network services for the terminal device 120. For example, the access network device 120 and the access network device 130 may provide services to terminal devices through multiple connections (DC), and as an example, the access network device 120 may be a primary access network device and the access network device 130 may be a secondary access network device. Optionally, the communication system may further comprise a plurality of secondary access network devices. The terminal device may establish a connection with the primary access network device and the secondary access network device simultaneously. The connection established between the terminal equipment and the main access network equipment is the main connection, and the connection established between the terminal equipment and the auxiliary access network equipment is the auxiliary connection. The control signaling of the terminal device can be transmitted through the main connection, and the data of the terminal device can be transmitted through the main connection and the auxiliary connection at the same time, or can be transmitted through the auxiliary connection only.

As an example, the access network device 120 may be an access network device of an LTE network, e.g., an evolved UMTS terrestrial radio access network (E-UMTS Terrestrial Radio Access Network, E-UTRAN), and the access network device 130 may be an access network device of an NR network. As another example, the access network device 120 may be an access network device of an NR network and the access network device 130 may be an access network device of an LTE network. Or the access network device 120 and the access network device 130 are both access network devices of an NR network, or are both access network devices of an LTE network, etc.

In other embodiments, the access network device 120 and the access network device 130 may also be access network devices in a 2G or 3G network, for example, the access network device 120 may be an access network device of a GSM network, an access network device of a CDMA network, or the like, and the access network device 130 may also be an access network device of a GSM network, an access network device of a CDMA network, or the like.

In some embodiments, the communication system may further comprise a core network device 140, which core network device 140 may be, for example, a core network of an LTE network, i.e. a packet core evolution (Evolved Packet Core, EPC), e.g. a Mobility management entity (Mobility MANAGEMENT ENTITY, MME), and also e.g. a serving gateway (SERVING GATEWAY, SGW), etc.

In some embodiments, the communication system may further comprise a core network device 150, which core network device 150 may be, for example, a 5G core network (5G Core Network,5GC), e.g., an access and mobility management function (ACCESS AND Mobility Management Function, AMF), further e.g., an authentication server function (Authentication Server Function, AUSF), further e.g., a user plane function (User Plane Function, UPF), etc.

Fig. 1 illustrates four network devices and one terminal device by way of example, and the communication system 100 may alternatively include more network devices and may include other numbers of terminal devices within the coverage area of each network device, as embodiments of the application are not limited in this regard.

In some scenarios, the deployment of the network may include independent (Standalone, SA) networking and Non-independent (Non-standalone, NSA) networking, and FIG. 2 shows a schematic diagram of one way of connecting SA networking and NAS networking.

For the SA networking approach, as an example, a next generation access network (Next Generation Radio Access Network, NG-RAN) is connected to a core network of the 5G network, i.e. the 5GC, and the NR-RAN may include, for example, an E-UTRAN (i.e. an access network device of the LTE network) and an access network device of the NR network, where the E-UTRAN and the 5GC may communicate through N2/N3 messages, and the NR and the 5GC may communicate through N2/N3 messages. The terminal device may initiate a registration procedure with the 5GC using an N1 Non-Access Stratum (NAS) message.

In the SA network, a terminal device using a 5GC network may be referred to as an N1 UE, and the N1 UE may transmit control information or data only through the E-UTRAN, or may transmit control information or data only through the NR access network, or may transmit control information or data through the E-UTRAN and the NR access network.

For NSA networking, as an example, the E-UTRAN may be connected to the EPC as a primary access network device (or anchor node), and the access network device of the NR network may provide data transmission over the air as a secondary access network device, where the E-UTRAN and the EPC may communicate via S1 messages, and the NR and the E-UTRAN may communicate via the X2 interface. The terminal device may initiate a registration procedure with the EPC using the EPC NAS message.

In NSA networks, terminal devices using EPC networks may be referred to as EPC UEs, which may transmit control plane and user plane data only through E-UTRAN, or may transmit user plane data through E-UTRAN and NR access networks.

Optionally, in the SA network and NSA network, EPC and 5GC may also be connected to a co-located network element of a home subscriber server (Home Subscriber Server, HSS) and Unified data management (Unified DATA MANAGEMENT, UDM), i.e. the co-located network element has functions of both HSS and UDM, and the co-located network element of HSS and UDM may be used to authenticate and store the identity of a user and manage the authentication data of the user.

For different operators, there are differences in network deployment, e.g. in the early stages of 5G network deployment, since different networks may support different services, e.g. part of the services do not have support in the SA network, the terminal Device still needs to perform these services in the LTE network, e.g. the 5G SA network may support only enhanced mobile ultra wideband (Enhance Mobile Broadband, eMBB) services, while for other services, e.g. cellular physical network (Cellular Internet of Things, CIoT), vehicle-to-other devices (Vehicle to Everything, V2X), terminal-to-terminal (D2D) services, still need to be performed under the EPC network.

When the area where the terminal device is located includes both SA and NSA networks, i.e. the network device is covered by the 5GC and EPC, the terminal device may initiate a registration procedure to the 5GC and may also initiate an attach procedure to the EPC, but any selection of the core network to be accessed may cause access failure. Fig. 3 is a schematic flow chart of a scenario in which a terminal device performs core network registration.

Step 21, the ue selects a core network for registration, for example, the terminal device selects to send a registration request to the 5 GC;

correspondingly, the 5GC receives the registration request and determines that the terminal device is not allowed to use the 5GC.

Further in step 22, the 5GC sends a registration request rejection message to the UE, the registration request rejection message including a specific cause value, e.g., the 5GC should not be used.

In step 23, the UE initiates a registration request to another core network after receiving the specific cause value, e.g. the terminal device may initiate a registration request to the EPC, which may also be referred to as an attach request for the EPC network.

In step 24, the EPC sends an attach request reply message to the UE indicating that the UE attached the EPC successfully.

In other embodiments, the UE may first choose to initiate a registration request to the EPC, and after the registration fails, may further initiate a registration request to the 5GC, and if the registration is successful, the terminal device may use the 5GC to perform communication.

The core network registration failure may cause multiple interactions, bring unnecessary signaling overhead, increase the time for accessing the network by the UE, and affect the user experience.

In view of this, the embodiment of the present application provides a method for wireless communication, where a terminal device may register a core network according to network device configuration or history information of core network selection, so as to reduce probability of core network registration failure and improve user experience.

It should be understood that, the application scenario of the technical solution in the embodiment of the present application is not limited, and the embodiment of the present application may be applied to a scenario where multiple networking modes coexist, where the multiple networking modes include, but are not limited to, the networking mode shown in fig. 2, or may also be applied to other scenarios where multiple core networks coexist and need to perform core network selection, for example, a scenario where a core network is selected to perform session connection establishment, and so on.

It should be understood that a device having a communication function in a network/system according to an embodiment of the present application may be referred to as a communication device. Taking the communication system 100 shown in fig. 1 as an example, the communication device may include an access network device, a terminal device, and a core network device with communication functions, where the access network device, the terminal device, and the core network device may be the specific devices described above, which are not described herein again.

It should be understood that the terms "system" and "network" are used interchangeably herein. The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.

Fig. 4 is a schematic flow chart of a method of wireless communication according to an embodiment of the present application. The method 200 may be performed by a terminal device in the communication system shown in fig. 1, and as shown in fig. 4, the method 200 may include at least part of the following:

S210, the terminal equipment determines a preferred core network type according to first information or second information, wherein the first information is information configured by the network equipment and used for core network selection, and the second information is history information selected by the core network of the terminal equipment;

S220, the terminal equipment preferentially selects to initiate a registration process to the core network of the preferred core network type.

It should be understood that the embodiments of the present application may be applied to core network selection during core network registration, or may also be applied to other scenarios where core network selection is required, such as a session establishment scenario, where session establishment may also be referred to as protocol data unit (Protocol Data Unit, PDU) connection establishment, PDU session establishment, or the like in a 5G network.

Therefore, in the embodiment of the present application, after determining the preferred core network type, the terminal device may preferably perform subsequent NAS actions with the core network of the preferred core network type, for example, may initiate a registration procedure with the core network of the preferred core network type, or may also initiate a session establishment procedure with the core network of the preferred core network type, which is described below by taking a core network registration scenario as an example, but the present application is not limited thereto.

It should be understood that in the embodiment of the present application, there may be a plurality of core network types, and the plurality of core network types may include core networks of different networks, for example, at least two of the following, a core network in an LTE network (i.e., EPC), a core network in an NR network (i.e., 5 GC), a core network in a 2G or 3G network, a core network in an SA network (i.e., EPC), and a core network in an NSA network (5 GC), which is not limited by the embodiment of the present application.

In the embodiment of the present application, the EPC may be a core network in a single LTE network, or may be a core network in NSA, and the EPC may be connected to only an LTE base station, or may also be connected to the EPC by a dual connection manner between the LTE base station and an NR base station.

Optionally, in the embodiment of the present application, preferentially selecting to initiate the registration procedure with the core network of the preferred core network type may refer to preferentially selecting to initiate the registration procedure with the core network of the preferred core network type, and in case of registration failure with the core network of the preferred core network type, may select to initiate the registration procedure with the core networks of other core network types. Or preferably initiates the registration procedure with the core network of the preferred core network type may also mean that only the core network of the preferred core network type is able to initiate the registration procedure.

It should be noted that, in the embodiment of the present application, the terminal device may also determine, according to the first information or the second information, a NAS message type that is preferably used for performing core network registration, further, may preferably use the NAS message type to initiate a core network registration process, and in the case of registration failure, may use other NAS message types to initiate a core network registration process, and a manner of determining the NAS message type may refer to the specific implementation of determining the preferred core network type hereinafter.

The manner in which the preferred core network type is determined is described below in connection with specific embodiments.

Example 1: the terminal device may determine a preferred core network type among the plurality of core networks based on the first information configured by the network device.

Optionally, in some embodiments, the first information is used to indicate at least one of:

1. The prioritization of the core network types, or the use prioritization of the core network types, i.e. which core network type is used preferentially, or may be the priority information of the core network types.

Taking the example that the core network type includes 5GC and EPC, the priority order of the core network type may be arranged in order from high to low, for example, may be 5GC and EPC, which indicates that the priority of 5GC is higher than EPC, and may be EPC and 5GC, which indicates that the priority of EPC is higher than 5GC; or may be arranged in a low-to-high order, and will not be described in detail herein.

As an example, the priority information of the core network type may be that the priority of 5GC is a first priority, the priority of EPC is a second priority, where the first priority may be higher than the second priority, or the first priority may be lower than the second priority;

2. The priority of the use of the NAS message types of the non-access stratum, or the priority of the use of the NAS message types, i.e. which NAS message type is used preferentially, or may be priority information of the NAS message types.

Taking the example that the NAS message types include an N1 NAS message and an EPC NAS message, the priority ordering of the NAS message types may be arranged in order from high to low, for example, may be an N1 NAS message and an EPC NAS message, which indicate that the priority of the N1 NAS message is higher than that of the EPC NAS message, or may be an EPC NAS message and an N1 NAS message, which indicate that the priority of the EPC NAS message is higher than that of the N1 NAS message; or may be arranged in a low-to-high order, and will not be described in detail herein.

As an example, the priority information of the NAS message type may be that the priority of the N1 NAS message is a first priority, and the priority of the EPC NAS message is a second priority, where the first priority may be higher than the second priority, or the first priority may be lower than the second priority.

3. The priority orders of the access SA network and the NSA network, or the use priority orders of different networking modes, i.e. which networking mode core network is preferentially used, or the priority information of the networking modes may also be used.

The priority order of the access SA network and the NSA network may be arranged in the order from high to low, for example, the access SA network and the NSA network may be represented by the priority of the access SA network being higher than the NSA network, or the access SA network and the NSA network may be represented by the priority of the access NSA network being higher than the SA network; or may be arranged in a low-to-high order, and will not be described in detail herein.

As an example, the priority information of the networking manner may be that the priority of the SA network is a first priority, and the priority of the NSA network is a second priority, where the first priority may be higher than the second priority, or the first priority may be lower than the second priority.

4. A particular core network type, e.g., 5GC or EPC;

Alternatively, the specific core network type may be a core network type that allows the terminal device to register, or a core network type that the terminal device is expected to access, or a core network type that the terminal device can only access or must access,

5. A particular NAS message type, e.g., N1 NAS or EPC NAS;

Alternatively, the specific NAS message type may be a NAS message type that is allowed to be used by the terminal device, a NAS message type that is expected to be used by the terminal device, or a NAS message type that can only be used or must be used by the terminal device, etc.

6. Specific networking means, such as SA or NSA.

Alternatively, the specific networking mode may be a networking mode that allows the terminal device to use, a networking mode that is expected to be used by the terminal device, a networking mode that can only be used or must be used by the terminal device, or the like.

It should be understood that in the embodiment of the present application, the NAS message type may have a correspondence with the core network type, for example, the N1 NAS message may correspond to a core network type of 5gc, and the core network type corresponding to EPC NAS is EPC.

Optionally, in some embodiments, the network device determines the first information according to information such as a service condition supported by a core network, subscription information of a terminal device, service information supported by the terminal device, a congestion condition of a current network, a number of users supported by the core network, and the like.

The specific description will be given taking as an example the determination of a preferred core network type among the first core network type and the second core network type.

For example, if the terminal device does not sign up for the first core network type and signs up for the second core network type, the first information may indicate that the second core network type has a higher priority than the first core network type, or that NAS messages of the second core network type have a higher priority than NAS messages of the first core network type.

For another example, if the terminal device supports the first service, the first core network type supports the first service, and the second core network type does not support the first service, the first information may indicate that the priority of the first core network type is higher than that of the second core network type, or that the priority of the NAS message type corresponding to the first core network type is higher than that of the NAS message type of the second core network type.

For another example, if the number of users supported by the first core network type is larger, the number of users supported by the second core network type is smaller, that is, the first core network type supports access of more terminal devices, the first information may indicate that the priority of the first core network type is higher than that of the second core network type, or that the priority of the NAS message type corresponding to the first core network type is higher than that of the NAS message type corresponding to the second core network type.

As an embodiment, if the first information indicates a usage prioritization of core network types, the terminal device may determine, according to the usage prioritization of core network types, a core network type with a highest priority as a preferred core network type.

For example, if the first information indicates that the priority of 5GC is higher than EPC, the terminal device may determine that 5GC is the target core network type.

As another embodiment, if the first information indicates the usage prioritization of NAS message types, the terminal device may determine, according to the usage prioritization of NAS message types, a core network type corresponding to a NAS message type with a highest priority as a preferred core network type.

For example, if the first information indicates that the priority of the N1 NAS message is higher than that of the EPC NAS message, the terminal device may determine that the core network type corresponding to the N1 NAS message is the preferred core network type. Or if the first information indicates that the priority of the N1 NAS message is higher than that of the EPC NAS message, the terminal device may directly use the N1 NAS message to initiate a registration procedure to the 5 GC.

As still another embodiment, if the first information indicates the priority order of accessing the SA network and the NAS network, the terminal device may determine the core network type corresponding to the networking mode with the highest priority as the preferred core network type.

For example, if the priority of accessing the SA network is higher than the priority of accessing the NSA network, the terminal device determines the core network type of the SA network as the preferred core network type; for another example, if the priority of accessing the SA network is lower than the priority of accessing the NSA network, the terminal device determines the core network type of the NSA network as the preferred core network type.

As still another embodiment, if the first information indicates a core network type for which the terminal device is allowed to register, the terminal device may determine the core network type for which the terminal device is allowed to register as a preferred core network type.

As still another embodiment, if the first information indicates a NAS message type that is allowed to be used by the terminal device, the terminal device may determine a core network type corresponding to the NAS message type that is allowed to be used by the terminal device as a preferred core network type. Or the terminal device may initiate the registration procedure directly using the NAS message type.

As still another embodiment, if the first information indicates a networking mode that allows the terminal device to access, the terminal device may determine a core network type corresponding to the networking mode that allows the terminal device to access as a preferred core network type.

For example, if the terminal device is allowed to access the SA network, the terminal device may determine the core network type of the SA network as a preferred core network type; for another example, if the terminal device is allowed to access the NSA network, the terminal device determines the core network type of the NSA network as a preferred core network type.

The following describes a configuration manner of the first information with reference to a specific embodiment.

As an embodiment, the first information may be sent by a core network device, for example, the core network device may send the first information to a terminal device through a downlink NAS message. Specifically, the NAS of the terminal device may receive a NAS message sent by the NAS of the core network device, where the NAS message may include the first information.

Optionally, the core network device is a core network device registered by the terminal device. As an example, the core network device may be a core network device that the terminal device last registered.

For example, the core network device may send the first information to the terminal device during a registration process of the terminal device, where the registration process may be an initial registration process or may be a registration process caused by a location update of the terminal device. For example, the core network device may carry the first information through a registration request reply message or a location update request reply message.

For another example, the core network device may send a first message to the terminal device after the terminal device is successfully registered, in which case the first message may be transmitted through any one of the downlink NAS messages.

As another embodiment, the first information may be sent by an access network device, for example, the access network device may send the first information to a terminal device through an RRC message or a broadcast message or other downlink message or downlink channel. Specifically, an Access Stratum (AS) of the terminal device may receive the first information sent by an AS of an Access network device.

Optionally, the access network device is an access network device where the terminal device resides. As an example, the access network device may be an access network device where the terminal device last resides.

For example, the access network device may send the first information to the terminal device during a radio resource control (Radio Resource Control, RRC) connection Setup procedure, e.g., the access network device may carry the first information through an RRC connection Setup (ConnectionSetup) message, which may alternatively be referred to as an RRC Setup (Setup) message.

For another example, the access network device may send a first message to the terminal device after the RRC connection establishment is successful, in which case the first message may be transmitted via any one of the downlink RRC messages.

Further, after the AS of the terminal device receives the first information sent by the access network device, the AS of the terminal device may further send the first information to the NAS of the terminal device, and further, the NAS of the terminal device may determine the preferred core network type according to the first information, where a specific determination manner refers to the foregoing related description.

Example 2: the history information of the core network selection, i.e. the second information, stored by the terminal device determines a preferred core network type among a plurality of core network types.

In some embodiments, the second information is used to indicate at least one of:

a core network type which is successfully registered or a NAS message type corresponding to the core network type;

the number of successful registrations to the core network type of successful registrations;

a core network type with failed registration or a NAS message type corresponding to the core network type;

the core network type that failed the first registration but that was successful again;

the number of registration failures to the core network type for which registration failed;

a cause of a registration failure to the core network type of registration failure;

the network type corresponding to the core network type which is successfully registered, such as an SA network or an NAS network;

The network type corresponding to the core network type of registration failure.

Optionally, in some embodiments, if the terminal device initiates a registration procedure with a core network of a first core network type, and if the registration fails, initiates a registration procedure with a core network of a second core network type, and if the registration is successful, the core network type that fails to register for the first time but that registers successfully again may be the second core network type, for example, for the example shown in fig. 3, if the terminal device fails to register with a 5GC and then registers successfully with an EPC, the second information may include information of the EPC, or if the terminal device fails to register with an EPC first and then registers successfully with a 5GC, the second information may include information of the 5 GC.

It should be noted that, here, the core network type that is successfully registered may include core network types that are successfully registered in the SA network and the NAS network, that is, core network types that are successfully registered in a scenario in which a plurality of networking modes coexist, or core network types that are successfully registered in a case in which a plurality of networks coexist (are independent between different networks), and similarly, core network types that are failed in registration may also include core network types that are failed in a scenario in which a plurality of networking modes coexist.

Specifically, after registering with the core network, the terminal device may save the registration result to obtain the second information, where the second information may include registered type information of the core network, and a registration result of the core network type, that is, whether the registration is successful or failed, and optionally, the number of times of registration success, or the number of times of registration failure, and a reason for registration failure, for example, may be that the UE cannot use the core network type.

Optionally, as an embodiment, if the second information indicates that the core network type of the successful registration is a first core network type, the terminal device determines the first core network type as the preferred core network type.

Optionally, as another embodiment, if the number of times of successful registration with the first core network type indicated by the second information is greater than or equal to a first threshold, the terminal device determines the first core network type as the preferred core network type.

Alternatively, as yet another embodiment, the terminal device may also determine a core network type that fails the first registration but that is successful in re-registration as the preferred core network type.

Further, in some embodiments, the terminal device may update the second information according to a registration result with the core network of the preferred core network type, i.e. whether the registration is successful or failed.

In the embodiment of the present application, if the preferred core network type is a packet core evolved EPC, the NAS of the terminal device may preferably initiate a registration request to the EPC using an EPC NAS message; or (b)

And if the type of the preferred core network is 5GC, the NAS of the terminal equipment preferably uses an N1 NAS message to send a registration request to the 5 GC.

In some embodiments, a terminal device initiating a registration request to the EPC using an EPC NAS message may trigger the terminal device to establish a connection with only an LTE base station, and in other embodiments, the terminal device initiating a registration request to the EPC using an EPC NAS message may trigger establishment of a dual connection between the terminal device and both an LTE base station and an NR base station.

It should be understood that the above embodiments 1 and 2 may be implemented separately or may be combined, for example, when the first information indicates that the EPC has a higher priority than 5GC, but the second information indicates that the number of registration failures of 5GC is higher, the terminal device may determine that the preferred core network type is EPC, and may further initiate a registration procedure with the EPC.

Therefore, according to the wireless communication method provided by the embodiment of the application, the terminal equipment can register the core network according to the network equipment configuration or the history information of the core network selection, thereby being beneficial to reducing the probability of core network registration failure and improving the user experience.

The method of wireless communication according to an embodiment of the present application is described in detail above in connection with fig. 4 from the perspective of a terminal device, and the method of wireless communication according to another embodiment of the present application is described in detail below in connection with fig. 5 from the perspective of a network device. It should be understood that the description on the network device side corresponds to the description on the terminal device side, and similar descriptions may be referred to above, and are not repeated here for avoiding repetition.

Fig. 5 is a schematic flow chart of a method 300 of wireless communication according to another embodiment of the present application, the method 300 being executable by a network device in the communication system shown in fig. 1, the method 300 comprising, as shown in fig. 5:

And S310, the network equipment sends first information to the terminal equipment, wherein the first information is used for determining a preferred core network type by the terminal equipment, and the first information is information configured by the network equipment and used for core network selection.

prioritization of usage of core network types;

prioritization of use of non-access stratum NAS message types;

Priority ordering of access to independent SA network and non-independent NSA network;

a core network type allowing the terminal device to register;

a NAS message type allowing the terminal device to use;

allowing access to either the SA network or the NSA network.

Optionally, in some embodiments, the network device is a core network device, and the network device sends the first information to the terminal device, including:

and the core network equipment sends NAS information to the terminal equipment, wherein the NAS information comprises the first information.

Optionally, in some embodiments, the core network device is a core network device registered by the terminal device.

Optionally, in some embodiments, the NAS message is a registration request reply message or a location update request reply message.

Optionally, in some embodiments, the network device is an access network device, and the network device sends the first information to a terminal device, including:

And the access network equipment sends the first information to the terminal equipment.

Optionally, in some embodiments, the access network device is an access network device where the terminal device resides.

Optionally, in some embodiments, the first information is included in a radio resource control, RRC, message or a broadcast message.

The method embodiments of the present application are described in detail above with reference to fig. 4 to 5, and the apparatus embodiments of the present application are described in detail below with reference to fig. 6 to 10, it being understood that the apparatus embodiments and the method embodiments correspond to each other, and similar descriptions may refer to the method embodiments.

Fig. 6 shows a schematic block diagram of a terminal device 400 according to an embodiment of the application. As shown in fig. 6, the terminal device 400 includes:

A processing module 410, configured to determine a preferred core network type according to first information or second information, where the first information is information configured by a network device and used for core network selection, and the second information is history information of core network selection of the terminal device;

a communication module 420, configured to preferentially select to initiate a registration procedure with a core network of the preferred core network type.

prioritization of usage of core network types;

prioritization of use of non-access stratum NAS message types;

a core network type allowing the terminal device to register;

a NAS message type allowing the terminal device to use;

allowing access to either the SA network or the NSA network.

Optionally, in some embodiments, the processing module 410 is specifically configured to:

and determining the core network type with the highest priority as the preferred core network type according to the use priority ordering of the core network types.

and according to the use priority ordering of the NAS message types, determining the core network type corresponding to the NAS message type with the highest priority as the preferred core network type.

If the priority of the access SA network is higher than that of the access NSA network, determining the core network type of the SA network as the preferred core network type; or (b)

And if the priority of the access SA network is lower than the priority of the access NSA network, determining the core network type of the NSA network as the preferred core network type.

and determining the core network type allowing the terminal equipment to register as the preferred core network type.

and determining the core network type corresponding to the NAS message type allowed to be used by the terminal equipment as the preferred core network type.

if the access to the SA network is allowed, determining the core network type of the SA network as the preferred core network type; or (b)

If access to the NSA network is allowed, the core network type of the NSA network is determined as the preferred core network type.

Optionally, in some embodiments, the communication module 420 is further configured to:

and receiving NAS information sent by NAS of the core network equipment at the NAS, wherein the NAS information comprises the first information.

Optionally, in some embodiments, the communication module 420 is specifically configured to:

and receiving the first information sent by the AS of the access network equipment at the access layer AS.

Optionally, in some embodiments, the processing module 410 is further configured to:

And sending the first information to the NAS of the terminal equipment at the AS, wherein the first information is used for determining the type of the preferred core network by the NAS of the terminal equipment.

Optionally, in some embodiments, the second information is used to indicate at least one of:

The number of registration failures to the core network type for which registration failed.

If the second information indicates that the core network type successfully registered is a first core network type, determining the first core network type as the preferred core network type; or (b)

And if the second information indicates that the number of times of successful registration with the first core network type is greater than or equal to a first threshold value, determining the first core network type as the preferred core network.

And updating the second information according to whether the registration to the target core network type is successful.

Optionally, in some embodiments, the communication module 410 is further configured to:

If the target core network type is a packet core evolution EPC, preferably using an EPC NAS message to initiate a registration request to the EPC; or (b)

If the target core network is a 5G core network 5GC, preferably, an N1 NAS message is used to send a registration request to the 5 GC.

It should be understood that the terminal device 400 according to the embodiment of the present application may correspond to the terminal device in the embodiment of the method of the present application, and the foregoing and other operations and/or functions of each unit in the terminal device 400 are respectively for implementing the corresponding flow of the terminal device in the method 200 shown in fig. 2, and are not described herein for brevity.

Fig. 7 is a schematic block diagram of a network device according to an embodiment of the present application. The network device 500 of fig. 7 includes:

a communication module 510, configured to send first information to a terminal device, where the first information is used by the terminal device to determine a preferred core network type, and the first information is information configured by a network device and used for core network selection.

prioritization of usage of core network types;

prioritization of use of non-access stratum NAS message types;

a core network type allowing the terminal device to register;

a NAS message type allowing the terminal device to use;

allowing access to either the SA network or the NSA network.

Optionally, the network device is a core network device, and the communication module 510 is specifically configured to: and sending NAS information to the NAS of the terminal equipment at the NAS, wherein the NAS information comprises the first information.

Optionally, in some embodiments, the network device is an access network device, and the communication module 510 is specifically configured to: and sending the first information to the AS of the terminal equipment at the AS.

It should be understood that the network device 500 according to the embodiment of the present application may correspond to the terminal device in the embodiment of the method of the present application, and the above and other operations and/or functions of each unit in the network device 500 are respectively for implementing the corresponding flow of the network device in the method 300 shown in fig. 5, which is not described herein for brevity.

Fig. 8 is a schematic block diagram of a communication device 600 according to an embodiment of the present application. The communication device 600 shown in fig. 8 comprises a processor 610, from which the processor 610 may call and run a computer program to implement the method in an embodiment of the application.

Optionally, as shown in fig. 8, the communication device 600 may further comprise a memory 620. Wherein the processor 610 may call and run a computer program from the memory 620 to implement the method in an embodiment of the application.

The memory 620 may be a separate device from the processor 610 or may be integrated into the processor 610.

Optionally, as shown in fig. 8, the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, and in particular, may send information or data to other devices, or receive information or data sent by other devices.

The transceiver 630 may include a transmitter and a receiver, among others. Transceiver 630 may further include antennas, the number of which may be one or more.

Optionally, the communication device 600 may be specifically a network device according to the embodiment of the present application, and the communication device 600 may implement a corresponding flow implemented by the network device in each method according to the embodiment of the present application, which is not described herein for brevity.

Optionally, the communication device 600 may be specifically a mobile terminal/terminal device according to an embodiment of the present application, and the communication device 600 may implement corresponding processes implemented by the mobile terminal/terminal device in each method according to the embodiment of the present application, which are not described herein for brevity.

Fig. 9 is a schematic structural view of a chip of an embodiment of the present application. The chip 700 shown in fig. 9 includes a processor 710, and the processor 710 may call and run a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, as shown in fig. 9, chip 700 may also include memory 720. Wherein the processor 710 may call and run a computer program from the memory 720 to implement the method in an embodiment of the application.

Wherein the memory 720 may be a separate device from the processor 710 or may be integrated into the processor 710.

Optionally, the chip 700 may also include an input interface 730. The processor 710 may control the input interface 730 to communicate with other devices or chips, and in particular, may obtain information or data sent by other devices or chips.

Optionally, the chip 700 may further include an output interface 740. The processor 710 may control the output interface 740 to communicate with other devices or chips, and in particular, may output information or data to other devices or chips.

Optionally, the chip may be applied to the network device in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the chip may be applied to a mobile terminal/terminal device in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein for brevity.

It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, or the like.

Fig. 10 is a schematic block diagram of a communication system 900 provided by an embodiment of the present application. As shown in fig. 10, the communication system 900 includes a terminal device 910 and a network device 920.

The terminal device 910 may be configured to implement the corresponding functions implemented by the terminal device in the above method, and the network device 920 may be configured to implement the corresponding functions implemented by the network device in the above method, which are not described herein for brevity.

It should be appreciated that the processor of an embodiment of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The Processor may be a general purpose Processor, a digital signal Processor (DIGITAL SIGNAL Processor, DSP), an Application SPECIFIC INTEGRATED Circuit (ASIC), an off-the-shelf programmable gate array (Field Programmable GATE ARRAY, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be embodied directly in the execution of a hardware decoding processor, or in the execution of a combination of hardware and software modules in a decoding processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.

It will be appreciated that the memory in embodiments of the application may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as external cache memory. By way of example, and not limitation, many forms of RAM are available, such as static random access memory (STATIC RAM, SRAM), dynamic random access memory (DYNAMIC RAM, DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate Synchronous dynamic random access memory (Double DATA RATE SDRAM, DDR SDRAM), enhanced Synchronous dynamic random access memory (ENHANCED SDRAM, ESDRAM), synchronous link dynamic random access memory (SYNCHLINK DRAM, SLDRAM), and Direct memory bus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

It should be appreciated that the above memory is exemplary but not limiting, and for example, the memory in the embodiments of the present application may also be static random access memory (STATIC RAM, SRAM), dynamic random access memory (DYNAMIC RAM, DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate synchronous dynamic random access memory (doubledata RATE SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (ENHANCED SDRAM, ESDRAM), synchronous link dynamic random access memory (SYNCH LINK DRAM, SLDRAM), direct Rambus RAM (DR RAM), and the like. That is, the memory in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

The embodiment of the application also provides a computer readable storage medium for storing a computer program.

Optionally, the computer readable storage medium may be applied to a network device in the embodiment of the present application, and the computer program causes a computer to execute a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the computer readable storage medium may be applied to a mobile terminal/terminal device in the embodiment of the present application, and the computer program causes a computer to execute a corresponding procedure implemented by the mobile terminal/terminal device in each method of the embodiment of the present application, which is not described herein for brevity.

The embodiment of the application also provides a computer program product comprising computer program instructions.

Optionally, the computer program product may be applied to a network device in the embodiment of the present application, and the computer program instructions cause a computer to execute corresponding processes implemented by the network device in each method in the embodiment of the present application, which are not described herein for brevity.

Optionally, the computer program product may be applied to a mobile terminal/terminal device in the embodiment of the present application, and the computer program instructions cause a computer to execute corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiment of the present application, which are not described herein for brevity.

The embodiment of the application also provides a computer program.

Optionally, the computer program may be applied to a network device in the embodiment of the present application, and when the computer program runs on a computer, the computer is caused to execute a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the computer program may be applied to a mobile terminal/terminal device in the embodiment of the present application, and when the computer program runs on a computer, the computer is caused to execute corresponding processes implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein for brevity.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method of wireless communication, comprising:

the terminal equipment determines a preferred core network type according to first information, wherein the first information is information for core network selection, which is configured by the network equipment according to the number of users supported by the core network;

The terminal equipment preferentially selects to initiate a registration process to a core network of the preferred core network type;

the network equipment comprises core network equipment which is registered by the terminal equipment last time; the method further comprises the steps of:

The terminal equipment receives NAS information sent by the core network equipment, wherein the NAS information comprises the first information;

the first information is used to indicate at least one of:

prioritization of usage of core network types;

prioritization of use of non-access stratum NAS message types;

Prioritization of access to independent SA networks and dependent NSA networks.

2. The method according to claim 1, wherein the determining, by the terminal device, a preferred core network type based on the first information comprises:

and the terminal equipment determines the core network type with the highest priority as the preferred core network type according to the use priority ordering of the core network types.

3. The method according to claim 1, wherein the determining, by the terminal device, a preferred core network type based on the first information comprises:

and the terminal equipment determines the core network type corresponding to the NAS message type with the highest priority as the preferred core network type according to the use priority ordering of the NAS message types.

4. The method according to claim 1, wherein the determining, by the terminal device, a preferred core network type based on the first information comprises:

If the priority of the access SA network is higher than that of the access NSA network, the terminal equipment determines the core network type of the SA network as the preferred core network type; or (b)

And if the priority of the access SA network is lower than the priority of the access NSA network, the terminal equipment determines the core network type of the NSA network as the preferred core network type.

5. The method according to any of claims 1 to 4, wherein the NAS message is a registration request reply message or a location update request reply message.

6. The method according to any of claims 1 to 5, wherein the terminal device preferentially selects to initiate a registration procedure with a core network of the preferred core network type, comprising:

if the target core network type is packet core evolution EPC, the terminal equipment preferably uses an EPC NAS message to initiate a registration request to the EPC; or (b)

If the target core network type is 5G core network 5GC, the terminal device preferably uses N1 NAS message to send a registration request to the 5 GC.

7. A method of wireless communication, comprising:

the network equipment sends first information to the terminal equipment, wherein the first information is used for the terminal equipment to determine the type of the preferred core network, and the first information is information which is configured by the network equipment according to the number of users supported by the core network and used for selecting the core network;

The network equipment comprises core network equipment which is registered by the terminal equipment last time; the network device sends first information to a terminal device, including:

The core network device sends an NAS message to the terminal device, wherein the NAS message comprises the first information;

the first information is used to indicate at least one of:

prioritization of usage of core network types;

prioritization of use of non-access stratum NAS message types;

Prioritization of access to independent SA networks and dependent NSA networks.

8. The method of claim 7, wherein the NAS message is a registration request reply message or a location update request reply message.

9. A terminal device, comprising:

The processing module is used for determining the type of the preferred core network according to first information, wherein the first information is information for selecting the core network, which is configured by the network equipment according to the number of users supported by the core network;

a communication module, configured to preferentially select to initiate a registration procedure to a core network of the preferred core network type;

The network equipment comprises core network equipment which is registered by the terminal equipment last time; the communication module is further configured to: receiving NAS information sent by NAS of the core network equipment at NAS, wherein the NAS information comprises the first information;

the first information is used to indicate at least one of:

prioritization of usage of core network types;

prioritization of use of non-access stratum NAS message types;

Prioritization of access to independent SA networks and dependent NSA networks.

10. The terminal device according to claim 9, wherein the processing module is specifically configured to:

11. The terminal device according to claim 9, wherein the processing module is specifically configured to:

12. The terminal device according to claim 9, wherein the processing module is specifically configured to:

13. The terminal device according to any of claims 9 to 12, wherein the NAS message is a registration request reply message or a location update request reply message.

14. The terminal device according to any of the claims 9 to 13, characterized in that the communication module is further adapted to:

If the target core network type is 5G core network 5GC, preferably, an N1 NAS message is used to send a registration request to the 5 GC.

15. A network device, comprising:

The communication module is used for sending first information to the terminal equipment, wherein the first information is used for determining a preferred core network type by the terminal equipment, and the first information is information which is configured by the network equipment according to the number of users supported by the core network and used for selecting the core network;

the network equipment comprises core network equipment which is registered by the terminal equipment last time; the communication module is specifically used for: sending NAS information to the NAS of the terminal equipment at the NAS, wherein the NAS information comprises the first information;

the first information is used to indicate at least one of:

prioritization of usage of core network types;

prioritization of use of non-access stratum NAS message types;

Prioritization of access to independent SA networks and dependent NSA networks.

16. The network device of claim 15, wherein the NAS message is a registration request reply message or a location update request reply message.

17. A terminal device, comprising: a processor and a memory for storing a computer program, the processor being adapted to invoke and run the computer program stored in the memory for performing the method according to any of claims 1 to 6.

18. A network device, comprising: a processor and a memory for storing a computer program, said processor being adapted to invoke and run the computer program stored in said memory for performing the method according to claim 7 or 8.

19. A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any one of claims 1 to 6, or the method of claim 7 or 8.

20. A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 1 to 6 or the method of claim 7 or 8.