WO2020001099A1 - Method for configuring terminal device by means of network device, and terminal device and network device - Google Patents

Abstract

Provided are a method for configuring a terminal device by means of a network device, and a terminal device and a network device. The network device can instruct the terminal device on whether to perform a mobile registration update operation before entering an idle state, thereby avoiding AMF re-allocation caused by the execution of mobile registration update, and thereby ensuring the use of an existing service for the terminal device. The method comprises: a terminal device receiving first information sent by a first network device, wherein the first information comprises first instruction information, and the first instruction information is used for instructing the terminal device not to perform a mobile registration update before entering an idle state, or for instructing the terminal device to use, in a first request for requesting the execution of the mobile registration update that is sent before entering the idle state, S-NSSAI of one or more established sessions as requested NSSAI.

Description

Method for configuring terminal equipment by network equipment, terminal equipment and network equipment

This application claims the priority of a Chinese patent application filed on June 25, 2018 with the Chinese Patent Office, application number 201810662476.X, and application name "Method for Configuring Terminal Equipment by Network Equipment, Terminal Equipment and Network Equipment", all of which are The contents are incorporated herein by reference.

Technical field

Embodiments of the present application relate to the field of communications technologies, and in particular, to a method, a terminal device, and a network device for configuring a terminal device by a network device.

Background technique

In a New Radio (NR) system, a terminal device in a Connection Management (CM) connection state may actively initiate a mobile registration update due to new service requirements before entering an idle state. However, at this time, The mobile registration update operation may trigger the access and mobility management function (AMF) re-allocation, and the new AMF cannot support the network slicing of the existing service, which will cause the existing service to Interrupted, unable to meet the communication needs of the NR system.

Summary of the invention

The embodiments of the present application provide a method, a terminal device, and a network device for configuring a terminal device by a network device. The network device can instruct the terminal device whether to perform a mobile registration update operation before entering an idle state, to avoid AMF caused by performing mobile registration update allocation, thereby ensuring the use of existing services on terminal equipment.

In a first aspect, a method for configuring a terminal device by a network device is provided, including:

Receiving, by a terminal device, first information sent by a network device, the first information including first indication information, the first indication information being used to instruct the terminal device not to perform a mobile registration update before entering an idle state, or Single-Network Slice Selection Information (Single-Network Slice Selection Information, S) that instructs the terminal device to send a first request for performing mobile registration update before entering the idle state. -NSSAI) as the requested network slice assistance information (Network Slice Selection Assistant Information (NSSAI)).

In a second aspect, a method for configuring a terminal device by a network device is provided, including:

The network device sends first information to the terminal device, where the first information includes first indication information, the first indication information is used to instruct the terminal device not to perform mobile registration update before entering the idle state, or is used to indicate In the first request sent by the terminal device before requesting to perform mobile registration update, the S-NSSAI of one or more established sessions is used as the requested NSSAI.

According to a third aspect, a network device configuration terminal device method is provided, including:

The network device determines whether the mobile registration update will cause the network device to reconfigure.

In a fourth aspect, a terminal device is provided for executing the method in the first aspect or the implementations thereof.

Specifically, the terminal device includes a functional module for executing the method in the above-mentioned first aspect or each implementation manner thereof.

In a fifth aspect, a network device is provided for performing the method in the above-mentioned second aspect or each implementation manner thereof.

Specifically, the network device includes a functional module for executing the method in the second aspect or the implementation manners thereof.

According to a sixth aspect, a network device is provided, which is configured to execute the method in the third aspect or the implementations thereof.

Specifically, the network device includes a functional module for executing the method in the third aspect or the implementations thereof.

According to a seventh aspect, a terminal device is provided, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, and execute the method in the first aspect or the implementations thereof.

In an eighth aspect, a network device is provided, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the second aspect or the implementations thereof.

In a ninth aspect, a network device is provided, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, and execute the method in the third aspect or the implementations thereof.

According to a tenth aspect, a chip is provided for implementing any one of the foregoing first to third aspects or a method in each implementation manner thereof.

Specifically, the chip includes a processor for invoking and running a computer program from the memory, so that the device installed with the chip executes any one of the first to third aspects described above or implementations thereof. method.

According to an eleventh aspect, a computer-readable storage medium is provided for storing a computer program that causes a computer to execute the method in any one of the first to third aspects described above or in its implementations.

In a twelfth aspect, a computer program product is provided, including computer program instructions that cause a computer to execute any one of the first to third aspects described above or a method in each implementation thereof.

According to a thirteenth aspect, a computer program is provided which, when run on a computer, causes the computer to execute any one of the first to third aspects described above or a method in each implementation thereof.

Through the above technical solution, the network device can instruct the terminal device whether to perform a mobile registration update operation before entering the idle state, avoiding AMF re-allocation caused by performing mobile registration update, thereby ensuring the use of existing services of the terminal device.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application.

FIG. 2 is a schematic flowchart of a method for configuring a terminal device by a network device according to an embodiment of the present application.

FIG. 3 is a schematic flowchart of another method for configuring a terminal device by a network device according to an embodiment of the present application.

FIG. 4 is a schematic flowchart of still another method for configuring a terminal device by a network device according to an embodiment of the present application.

FIG. 5 is a schematic flowchart of still another method for configuring a terminal device by a network device according to an embodiment of the present application.

FIG. 6 is a schematic flowchart of still another method for configuring a terminal device by a network device according to an embodiment of the present application.

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

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

FIG. 9 is a schematic block diagram of another network device according to an embodiment of the present application.

FIG. 10 is a schematic block diagram of a communication device according to an embodiment of the present application.

FIG. 11 is a schematic block diagram of a chip according to an embodiment of the present application.

FIG. 12 is a schematic block diagram of a communication system according to an embodiment of the present application.

detailed description

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, but not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by a person of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System (GSM) system, Code Division Multiple Access (CDMA) system, and Wideband Code Division Multiple Access (Wideband Code Division Multiple Access) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system or 5G system, or a subsequent version of the communication system in.

Exemplarily, the communication system 100 applied in the embodiment of the present application is shown in FIG. 1. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with the terminal device 120 (or referred to as a communication terminal or terminal). The network device 110 may provide communication coverage for a specific geographic area, and may communicate with terminal devices located within the coverage area. Optionally, the network device 110 may be a base station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, or a base station (NodeB, NB) in a WCDMA system, or an evolved base station in an LTE system. (Evolutional NodeB, eNB or eNodeB), or a wireless controller in a Cloud Radio Access Network (CRAN), or the network device may be a mobile switching center, relay station, access point, vehicle equipment, Wearable devices, hubs, switches, bridges, routers, network-side devices in 5G networks, or network devices in public land mobile networks (PLMN) that will evolve in the future.

The communication system 100 further includes at least one terminal device 120 located within a coverage area of the network device 110. As the "terminal equipment" used herein includes, but is not limited to, connection via wired lines, such as via Public Switched Telephone Networks (PSTN), Digital Subscriber Line (DSL), digital cable, direct cable connection ; And / or another data connection / network; and / or via a wireless interface, such as for cellular networks, Wireless Local Area Networks (WLAN), such as Digital Video Broadcasting Handheld (DVB-H) ) Network of digital television networks, satellite networks, AM-FM (Amplitude Modulation-Frequency Modulation, AM-FM) broadcast transmitters; and / or another terminal device configured to receive / transmit communication signals; and / or Internet of Things (IoT) equipment. A terminal device configured to communicate through a wireless interface may be referred to as a “wireless communication terminal”, a “wireless terminal”, or a “mobile terminal”. Examples of mobile terminals include, but are not limited to, satellite or cellular phones; personal communications systems (PCS) terminals that can combine cellular radiotelephones with data processing, facsimile, and data communications capabilities; can include radiotelephones, pagers, Internet / internal PDA with network access, Web browser, notepad, calendar, BeiDou Navigation Satellite System (BDS) and Global Positioning System (GPS) receiver; and conventional laptop and / or palm Receiver or other electronic device including a radiotelephone transceiver. A terminal device can refer to an access terminal, user equipment (UE), user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or User device. The access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Processing Assistant (PDA), and wireless communication. Functional handheld devices, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminal devices in 5G networks, or terminal devices in future evolved PLMNs, etc.

Optionally, the terminal devices 120 may perform terminal direct connection (Device to Device, D2D) communication.

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

FIG. 1 exemplarily shows one network device and two terminal devices. Optionally, the communication system 100 may include multiple network devices and the coverage of each network device may include other numbers of terminal devices. The embodiment does not limit this.

Optionally, the communication system 100 may further include other network entities such as a network controller, a mobility management entity, and the like in this embodiment of the present application is not limited thereto.

It should be understood that the device having a communication function in the network / system in the embodiments 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 a network device 110 and a terminal device 120 having a communication function, and the network device 110 and the terminal device 120 may be specific devices described above, and will not be repeated here. The communication device may also include other devices in the communication system 100, such as other network entities such as a network controller and a mobile management entity, which are not limited in the embodiments of the present application.

It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and / or" in this document is only a kind of association relationship describing related objects, which means that there can be three kinds of relationships, for example, A and / or B can mean: A exists alone, A and B exist simultaneously, and exists alone B these three cases. In addition, the character "/" in this text generally indicates that the related objects are an "or" relationship.

FIG. 2 is a schematic flowchart of a method 200 for configuring a terminal device by a network device according to an embodiment of the present application.

S210. The terminal device receives first information sent by the network device, where the first information includes first instruction information, where the first instruction information is used to instruct the terminal device not to perform mobile registration update before entering the idle state, or is used to indicate In the first request sent by the terminal device before requesting to perform mobile registration update, the S-NSSAI of one or more established sessions is used as the requested NSSAI.

Optionally, the terminal device is in a CM connection state.

Optionally, the network device is an AMF device.

Optionally, one or more of the established sessions may be Protocol Data Unit (PDU) sessions.

Optionally, when the network device needs to update Allowed NSSAI to the terminal device, the network device sends the first information to the terminal device.

It should be noted that the first information may be a terminal device configuration update command (UE Configuration Update Command). The first information may further include a new Allowed NSSAI.

Optionally, the first indication information may be a new parameter or an existing re-registration request indication (Re-registration Request Indication).

Specifically, when the first instruction information is used to instruct the terminal device not to perform mobile registration update before entering the idle state, the terminal device does not perform mobile registration update before entering the idle state according to the first instruction information.

That is, in order to avoid causing AMF re-allocation, when mobile registration update needs to be performed, the terminal device does not perform mobile registration update before entering the idle state according to the first instruction information sent by the AMF, and executes after entering the idle state. Mobile registration update.

Specifically, the first indication information is used to instruct the terminal device to use the S-NSSAI of one or more established sessions as the requested NSSAI in the first request sent by the terminal device before entering the idle state, and the terminal device When the mobile registration update needs to be performed before entering the idle state, the terminal device sends the first request to the network device according to the first instruction information.

That is, the terminal device may trigger the execution of the mobile registration update by using the first request.

It should be understood that triggering the execution of the mobile registration update through this first request will not cause AMF re-allocation.

It should be noted that before entering the idle state, the terminal device may actively initiate a mobile registration update due to new service requirements, for example, updating the terminal device capability, requesting registration of a new slice, and the like. If the terminal device requests to register a new slice, the existing AMF does not support the slice, which may cause AMF re-allocation, and the new AMF cannot support the slice of the existing service, which causes the interruption of the existing service.

Therefore, in the embodiment of the present application, the network device instructs the terminal device not to perform the mobile registration update before entering the idle state, or instructs the terminal device to send the first request for performing the mobile registration update before the terminal device enters the idle state. The S-NSSAI of one or more established sessions is used as the requested NSSAI, thereby avoiding AMF re-allocation caused by performing mobile registration update, thereby ensuring the use of existing services of terminal equipment.

FIG. 3 is a schematic flowchart of a method 300 for configuring a terminal device by a network device according to an embodiment of the present application.

S310. The network device sends first information to the terminal device, where the first information includes first instruction information, where the first instruction information is used to instruct the terminal device not to perform a mobile registration update before entering the idle state, or is used to indicate the In the first request sent by the terminal device before requesting to perform mobile registration update, the S-NSSAI of one or more established sessions is used as the requested NSSAI.

Optionally, the terminal device is in a CM connection state.

Optionally, the network device is AMF.

Optionally, the network device determines that the terminal device is not allowed to trigger network device reconfiguration before entering the idle state.

In other words, the AMF determines that the terminal device is not allowed to trigger AMF re-allocation before entering the idle state, thereby ensuring the use of existing services of the terminal device.

Optionally, the first indication information is used to instruct the terminal device to use the S-NSSAI of one or more established sessions as the requested NSSAI in the first request sent by the terminal device before entering the idle state, and the terminal When the device needs to perform mobile registration update before entering the idle state, the method 300 further includes:

Receiving, by the network device, the first request sent by the terminal device;

In response to the first request, the network device performs a mobile registration update.

That is, when the first indication information is used to instruct the terminal device to use the S-NSSAI of one or more established sessions as the requested NSSAI in the first request sent by the terminal device before entering the idle state, the terminal The device can perform a mobile registration update before going idle.

It should be understood that, for steps in the method 300 for configuring a terminal device by a network device, reference may be made to corresponding steps in the method 200 for configuring a terminal device by a network device. For brevity, details are not described herein again.

Therefore, in the embodiment of the present application, the network device instructs the terminal device not to perform the mobile registration update before entering the idle state, or instructs the terminal device to send the first request for performing the mobile registration update before the terminal device enters the idle state. The S-NSSAI of one or more established sessions is used as the requested NSSAI, thereby avoiding AMF re-allocation caused by performing mobile registration update, thereby ensuring the use of existing services of terminal equipment.

Optionally, as an embodiment, the method 400 shown in FIG. 4 may be used. In the method 400, a terminal equipment (User Equipment) interacts with the AMF. The method 400 includes:

S410: The UE is in a CM-CONNECTED state.

S420. The AMF sends a UE configuration update command (UE Configuration Update Command) to the UE.

The UE Configuration Update Command includes first indication information, the first indication information is used to instruct the UE not to perform mobile registration update before entering the idle state, or is used to instruct the UE to send In the first request for performing mobile registration update, the S-NSSAI of one or more established sessions is used as the requested NSSAI.

S430: The UE sends a UE configuration update acknowledgement (UE Configuration Update Ack) to the AMF.

S440. The UE does not perform mobile registration update (Mobility Registration Update) according to the first instruction information, or uses the S-NSSAI of one or more established sessions as the requested NSSAI.

Optionally, when the first indication information is used to instruct the UE not to perform mobile registration update before entering the idle state, the UE does not perform mobile registration update before entering the idle state according to the first instruction information.

Optionally, the first indication information is used to indicate that the S-NSSAI of one or more established sessions is used as the requested NSSAI in the first request sent by the UE before entering the idle state, and the UE is in When the mobile registration update needs to be performed before entering the idle state, the UE sends the first request to the AMF according to the first instruction information.

S450: A mobile registration update is performed between the UE and the AMF.

It should be understood that the mobile registration update will not trigger AMF re-allocation.

FIG. 5 is a schematic flowchart of a method 500 for configuring a terminal device by a network device according to an embodiment of the present application.

S510: The network device determines whether the mobile registration update will cause the network device to reconfigure.

Optionally, the terminal device is in a CM connection state.

Optionally, the network device is AMF.

It should be noted that the network device determines that the terminal device is not allowed to trigger the network device reconfiguration before entering the idle state.

Optionally, when the network device determines that the mobile registration update will cause network device reconfiguration, the method further includes:

The network device sends second information to the terminal device, the second information includes first indication information, and the first indication information is used to indicate that the reason for rejecting the mobile registration update is that the network device is not allowed to reconfigure before entering the idle state.

That is, when the network device determines that the mobile registration update will cause network device reconfiguration, the network device refuses to perform the mobile registration update.

Optionally, before the network device determines whether the mobile registration update will cause network device reconfiguration, the method 500 further includes:

The network device receives first information sent by the terminal device, and the first information is used to request a mobile registration update.

Therefore, in the embodiment of the present application, when the terminal device requests to perform mobile registration update, the network device judges whether it will cause AMF re-allocation, and when it is confirmed that it will cause AMF re-allocation, it refuses to perform mobile registration update, and sends the mobile registration update The device feedbacks the reason for rejection, thereby avoiding AMF re-allocation caused by performing mobile registration update, thereby ensuring the use of existing services of terminal equipment.

Optionally, as an embodiment, the method 600 shown in FIG. 6 may be used. In the method 600, the UE interacts with the AMF. The method 600 includes:

S610: The UE is in a CM-CONNECTED state.

S620. The AMF sends a UE Configuration Update Command to the UE, which includes a new Allowed NSSAI.

S630. The UE sends a UE configuration update acknowledgement (UE Configuration Update Ack) to the AMF.

S640: The UE sends a mobile registration update request (Mobility Registration Update Requested) to the AMF.

Specifically, before the UE enters the idle state, if there is a need to perform mobile registration update, for example, updating the UE capability, requesting registration of new slices, etc., the UE initiates a mobile registration update request to the AMF according to normal operations, which includes Requested NSSAI and the like.

S650, the AMF determines whether the mobile registration update will cause AMF re-allocation.

Optionally, if the AMF determines whether the mobile registration update will cause AMF re-allocation, the AMF performs the mobile registration update.

Optionally, if the AMF determines that the mobile registration update will cause AMF re-allocation, the AMF refuses to perform the mobile registration update.

S660: The AMF sends a UE configuration update update (UE) to the UE, which includes Cause to indicate that the reason for the UE rejection is that the AMF is not allowed to be re-allocated before entering the idle state.

It should be understood that step S660 is a step performed when the AMF determines that the mobile registration update will cause AMF re-allocation in S650.

FIG. 7 is a schematic block diagram of a terminal device 700 according to an embodiment of the present application. As shown in FIG. 7, the terminal device 700 includes:

The communication unit 710 is configured to receive first information sent by a network device, where the first information includes first indication information, and the first indication information is used to instruct the terminal device not to perform a mobile registration update before entering an idle state, or, The S-NSSAI of one or more established sessions is used as the requested NSSAI in the first request for instructing the mobile registration update to be sent by the terminal device before entering the idle state.

Optionally, the terminal device 700 further includes:

A processing unit 720, configured to: when the first instruction information is used to instruct the terminal device not to perform mobile registration update before entering the idle state, perform no mobile registration update before entering the idle state according to the first instruction information; or,

The communication unit 710 is further configured to use the S-NSSAI of one or more established sessions as the requested NSSAI in the first request sent by the first instruction information to instruct the terminal device to enter an idle state. And when the terminal device needs to perform a mobile registration update before entering the idle state, the terminal device sends the first request to the network device according to the first instruction information.

Optionally, the terminal device is in a CM connection state.

Optionally, the network device is AMF.

It should be understood that the foregoing and other operations and / or functions of each module in the terminal device 700 according to the embodiment of the present application are respectively to implement the corresponding process of the terminal device in the method 200 in FIG. .

FIG. 8 is a schematic block diagram of a network device 800 according to an embodiment of the present application. As shown in FIG. 8, the network device 800 includes:

The communication unit 810 is configured to send first information to the terminal device, where the first information includes first instruction information, and the first instruction information is used to instruct the terminal device not to perform mobile registration update before entering an idle state, or Instruct the terminal device to use the S-NSSAI of one or more established sessions as the requested NSSAI in the first request sent by the terminal device before requesting to perform mobile registration update.

Optionally, the network device 800 further includes:

The processing unit 820 is configured to determine that the terminal device is not allowed to trigger network device reconfiguration before entering the idle state.

Optionally, the first indication information is used to instruct the terminal device to use the S-NSSAI of one or more established sessions as the requested NSSAI in the first request sent by the terminal device before entering the idle state, and the terminal When the device needs to perform mobile registration update before the device enters the idle state, the network device 800 further includes:

The communication unit 810 is further configured to receive the first request sent by the terminal device;

In response to the first request, the processing unit 820 is configured to perform a mobile registration update.

Optionally, the terminal device is in a CM connection state.

Optionally, the network device is AMF.

It should be understood that the above and other operations and / or functions of each module in the network device 800 according to the embodiment of the present application are respectively to implement the corresponding process of the network device in the method 300 in FIG. .

FIG. 9 is a schematic block diagram of a network device 900 according to an embodiment of the present application. As shown in FIG. 9, the network device 900 includes:

The processing unit 910 is configured to determine whether the mobile registration update will cause network device reconfiguration.

Optionally, when the processing unit 910 determines that the mobile registration update will cause network device reconfiguration, the network device 900 further includes:

The communication unit 920 is configured to send second information to the terminal device, where the second information includes first indication information, and the first indication information is used to indicate that the reason for rejecting the mobile registration update is that the network device is not allowed to restart before entering the idle state Configuration.

Optionally, before the processing unit 910 determines whether the mobile registration update will cause network device reconfiguration, the network device 900 further includes:

The communication unit 920 is configured to receive first information sent by the terminal device, where the first information is used to request a mobile registration update.

Optionally, before the processing unit 910 determines whether the mobile registration update will cause network device reconfiguration, the processing unit 910 is further configured to determine that the terminal device is not allowed to trigger network device reconfiguration before entering the idle state.

Optionally, the terminal device is in a CM connection state.

Optionally, the network device is AMF.

It should be understood that the foregoing and other operations and / or functions of each module in the network device 900 according to the embodiment of the present application are respectively to implement the corresponding process of the network device in the method 500 in FIG. .

FIG. 10 is a schematic structural diagram of a communication device 1000 according to an embodiment of the present application. The communication device 1000 shown in FIG. 10 includes a processor 1010, and the processor 1010 can 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. 10, the communication device 1000 may further include a memory 1020. The processor 1010 may call and run a computer program from the memory 1020 to implement the method in the embodiment of the present application.

The memory 1020 may be a separate device independent of the processor 1010, or may be integrated in the processor 1010.

Optionally, as shown in FIG. 10, the communication device 1000 may further include a transceiver 1030, and the processor 1010 may control the transceiver 1030 to communicate with other devices, and specifically, may send information or data to other devices or receive other Information or data sent by the device.

The transceiver 1030 may include a transmitter and a receiver. The transceiver 1030 may further include antennas, and the number of antennas may be one or more.

Optionally, the communication device 1000 may specifically be a network device according to an embodiment of the present application, and the communication device 1000 may implement a corresponding process implemented by a network device in each method of the embodiments of the present application. For brevity, details are not described herein. .

Optionally, the communication device 1000 may specifically be a mobile terminal / terminal device in the embodiment of the present application, and the communication device 1000 may implement the corresponding process implemented by the mobile terminal / terminal device in each method in the embodiments of the present application. , Will not repeat them here.

FIG. 11 is a schematic structural diagram of a chip according to an embodiment of the present application. The chip 1100 shown in FIG. 11 includes a processor 1110, and the processor 1110 can 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. 11, the chip 1100 may further include a memory 1120. The processor 1110 may call and run a computer program from the memory 1120 to implement the method in the embodiment of the present application.

The memory 1120 may be a separate device independent of the processor 1110, or may be integrated in the processor 1110.

Optionally, the chip 1100 may further include an input interface 1130. The processor 1110 may control the input interface 1130 to communicate with other devices or chips. Specifically, the processor 1110 may obtain information or data sent by other devices or chips.

Optionally, the chip 1100 may further include an output interface 1140. The processor 1110 may control the output interface 1140 to communicate with other devices or chips. Specifically, the processor 1110 may output information or data to the 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 the corresponding process implemented by the network device in each method of the embodiment of the present application. For brevity, details are not described herein.

Optionally, the chip can be applied to the mobile terminal / terminal device in the embodiment of the present application, and the chip can implement the corresponding process implemented by the mobile terminal / terminal device in each method of the embodiment of the present application. For simplicity, here No longer.

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

FIG. 12 is a schematic block diagram of a communication system 1200 according to an embodiment of the present application. As shown in FIG. 12, the communication system 1200 includes a terminal device 1210 and a network device 1220.

The terminal device 1210 may be used to implement the corresponding functions implemented by the terminal device in the foregoing method, and the network device 1220 may be used to implement the corresponding functions implemented by the network device in the foregoing method. For brevity, details are not repeated here. .

It should be understood that the processor in the embodiment of the present application may be an integrated circuit chip and has a signal processing capability. In the implementation process, each step of the foregoing method embodiment may be completed by using an integrated logic circuit of hardware in a processor or an instruction in a form of software. The above processor may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA), or other Programming logic devices, discrete gate or transistor logic devices, discrete hardware components. Various methods, steps, and logical block diagrams disclosed in the embodiments of the present application may be implemented or executed. 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 combination with the embodiments of the present application may be directly implemented by a hardware decoding processor, or may be performed by using a combination of hardware and software modules in the decoding processor. A software module may be located in a mature storage medium such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, and the like. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

It can be understood that the memory in the embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), and an electronic memory. Erase programmable read-only memory (EPROM, EEPROM) or flash memory. The volatile memory may be Random Access Memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (Synchlink DRAM, SLDRAM ) And direct memory bus random access memory (Direct Rambus RAM, DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

It should be understood that the foregoing memory is exemplary but not restrictive. For example, the memory in the embodiment of the present application may also be a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (SDRAM), double data rate Synchronous dynamic random access memory (Double SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM), direct memory bus random access memory (Direct RAMbus RAM, DR RAM) and so on. That is, the memories in the embodiments of the present application are intended to include, but not limited to, these and any other suitable types of memories.

An embodiment of the present application further provides a computer-readable storage medium for storing a computer program.

Optionally, the computer-readable storage medium can be applied to the network device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the network device in each method in the embodiment of the present application. For brevity, here No longer.

Optionally, the computer-readable storage medium can be applied to the mobile terminal / terminal device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the mobile terminal / terminal device in each method in the embodiment of the present application For the sake of brevity, I won't repeat them here.

An embodiment of the present application further provides a computer program product, including computer program instructions.

Optionally, the computer program product can be applied to a network device in the embodiment of the present application, and the computer program instruction causes a computer to execute a corresponding process implemented by the network device in each method in the embodiment of the present application. More details.

Optionally, the computer program product may be applied to a mobile terminal / terminal device in the embodiments of the present application, and the computer program instructions cause a computer to execute a corresponding process implemented by the mobile terminal / terminal device in each method of the embodiments of the present application, For brevity, I will not repeat them here.

The embodiment of the present application also provides a computer program.

Optionally, the computer program may be applied to a network device in the embodiment of the present application. When the computer program is run on a computer, the computer is caused to execute a corresponding process implemented by the network device in each method in the embodiment of the present application. , Will not repeat them here.

Optionally, the computer program can be applied to a mobile terminal / terminal device in the embodiment of the present application, and when the computer program is run on a computer, the computer executes each method in the embodiment of the application by the mobile terminal / terminal device. The corresponding processes are not repeated here for brevity.

Those of ordinary skill in the art may realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. A professional technician may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the foregoing method embodiments, and are not repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner. For example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, which may be electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objective of the solution of this embodiment.

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

When the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially a part that contributes to the existing technology or a part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in the embodiments of the present application. The foregoing storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory) ROM, random access memory (Random Access Memory, RAM), magnetic disks or optical disks and other media that can store program codes .

The above is only a specific implementation of this application, but the scope of protection of this application is not limited to this. Any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in this application. It should be covered by the protection scope of this application. Therefore, the protection scope of this application shall be subject to the protection scope of the claims.

Claims (45)

A method for configuring a terminal device by a network device, comprising: Receiving, by a terminal device, first information sent by a network device, the first information including first indication information, the first indication information being used to instruct the terminal device not to perform a mobile registration update before entering an idle state, or Instructs the terminal device to use the single network slice auxiliary information S-NSSAI of the one or more established sessions as the requested network slice auxiliary information in the first request for requesting mobile registration update to be sent before entering the idle state NSSAI. The method according to claim 1, further comprising: When the first instruction information is used to instruct the terminal device not to perform mobile registration update before entering the idle state, the terminal device does not perform mobile registration update before entering the idle state according to the first instruction information; or, The first indication information is used to instruct the terminal device to use the S-NSSAI of one or more established sessions as the requested NSSAI in the first request sent by the terminal device before entering the idle state, and the terminal When the device needs to perform mobile registration update before entering the idle state, the terminal device sends the first request to the network device according to the first instruction information. The method according to claim 1 or 2, wherein the terminal device is in a connection management CM connection state. The method according to any one of claims 1 to 3, wherein the network device is an access and mobility management function AMF. A method for configuring a terminal device by a network device, comprising: The network device sends first information to the terminal device, where the first information includes first indication information, the first indication information is used to instruct the terminal device not to perform mobile registration update before entering the idle state, or is used to indicate In the first request for performing mobile registration update sent by the terminal device before entering the idle state, the single network slice auxiliary information S-NSSAI of one or more established sessions is used as the requested network slice auxiliary information NSSAI . The method according to claim 5, further comprising: The network device determines that the terminal device is not allowed to trigger network device reconfiguration before entering the idle state. The method according to claim 5 or 6, wherein the first indication information is used to instruct the terminal device to send one or more established requests in the first request before entering the idle state. When the S-NSSAI of the session is used as the requested NSSAI, and the terminal device needs to perform a mobile registration update before entering the idle state, the method further includes: Receiving, by the network device, the first request sent by the terminal device; In response to the first request, the network device performs a mobile registration update. The method according to any one of claims 5 to 7, wherein the terminal device is in a connection management CM connection state. The method according to any one of claims 5 to 8, wherein the network device is an access and mobility management function AMF. A method for configuring a terminal device by a network device, comprising: The network device determines whether the mobile registration update will cause the network device to reconfigure. The method according to claim 10, wherein when the network device determines that the mobile registration update will cause network device reconfiguration, the method further comprises: The network device sends second information to the terminal device, the second information includes first indication information, and the first indication information is used to indicate that the reason for rejecting the mobile registration update is that the network is not allowed before entering the idle state Device reconfiguration. The method according to claim 10 or 11, before the network device determines whether the mobile registration update will cause network device reconfiguration, the method further comprises: The network device receives first information sent by the terminal device, where the first information is used to request a mobile registration update. The method according to any one of claims 10 to 12, wherein before the network device determines whether the mobile registration update will cause network device reconfiguration, the method further comprises: The network device determines that the terminal device is not allowed to trigger network device reconfiguration before entering the idle state. The method according to any one of claims 10 to 13, wherein the terminal device is in a connection management CM connection state. The method according to any one of claims 10 to 14, wherein the network device is an access and mobility management function AMF. A terminal device, comprising: A communication unit, configured to receive first information sent by a network device, where the first information includes first indication information, and the first indication information is used to instruct the terminal device not to perform mobile registration update before entering an idle state, or For instructing the terminal device to use the single network slice auxiliary information S-NSSAI of one or more established sessions as the requested network in the first request for requesting mobile registration update to be sent before the terminal device enters the idle state Slice auxiliary information NSSAI. The terminal device according to claim 16, wherein the terminal device further comprises: A processing unit, configured to: when the first instruction information is used to instruct the terminal device not to perform mobile registration update before entering the idle state, perform no mobile registration update before entering the idle state according to the first instruction information; or , The communication unit is further configured to use the S-NSSAI of one or more established sessions as the first request sent by the first instruction information to instruct the terminal device to enter an idle state. When the requested NSSAI and the terminal device needs to perform mobile registration update before entering the idle state, send the first request to the network device according to the first instruction information. The terminal device according to claim 16 or 17, wherein the terminal device is in a connection management CM connection state. The terminal device according to any one of claims 16 to 18, wherein the network device is an access and mobility management function AMF. A network device, comprising: A communication unit, configured to send first information to a terminal device, where the first information includes first instruction information, and the first instruction information is used to instruct the terminal device not to perform mobile registration update before entering an idle state, or A single network slice auxiliary information S-NSSAI of one or more established sessions is used as a requested network slice in a first request for instructing mobile registration update to be sent by the terminal device before entering an idle state. Auxiliary information NSSAI. The network device according to claim 20, wherein the network device further comprises: A processing unit, configured to determine that the terminal device is not allowed to trigger reconfiguration of the network device before entering the idle state. The network device according to claim 20 or 21, wherein, in the first request information used to instruct the terminal device to enter an idle state, one or more When the S-NSSAI of the established session is used as the requested NSSAI, and the terminal device needs to perform a mobile registration update before entering the idle state, the network device further includes: The communication unit is further configured to receive the first request sent by the terminal device; In response to the first request, a processing unit is configured to perform a mobile registration update. The network device according to any one of claims 20 to 22, wherein the terminal device is in a connection management CM connection state. The network device according to any one of claims 20 to 23, wherein the network device is an access and mobility management function AMF. A network device, comprising: A processing unit for determining whether a mobile registration update will cause a reconfiguration of a network device. The network device according to claim 25, wherein when the processing unit determines that the mobile registration update will cause network device reconfiguration, the network device further comprises: A communication unit, configured to send second information to the terminal device, where the second information includes first indication information, and the first indication information is used to indicate that the reason for rejecting the mobile registration update is not allowed before entering the idle state Network device reconfiguration. The network device according to claim 25 or 26, wherein before the processing unit determines whether the mobile registration update will cause network device reconfiguration, the network device further comprises: The communication unit is configured to receive first information sent by the terminal device, where the first information is used to request a mobile registration update. The network device according to any one of claims 25 to 27, wherein before the processing unit determines whether the mobile registration update will cause network device reconfiguration, the processing unit is further configured to determine the The terminal device must not trigger network device reconfiguration before entering the idle state. The network device according to any one of claims 25 to 28, wherein the terminal device is in a connection management CM connection state. The network device according to any one of claims 25 to 29, wherein the network device is an access and mobility management function AMF. A terminal device, comprising: a processor and a memory, where the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and execute any one of claims 1 to 4 The method of one item. A network device, comprising: a processor and a memory, where the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, and execute any one of claims 5 to 9. The method of one item. A network device, comprising: a processor and a memory, where the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and execute any one of claims 10 to 15 The method of one item. A chip, comprising: a processor, configured to call and run a computer program from a memory, so that a device having the chip installed executes the method according to any one of claims 1 to 4. A chip, comprising: a processor, configured to call and run a computer program from a memory, so that a device having the chip installed executes the method according to any one of claims 5 to 9. A chip, comprising: a processor, configured to call and run a computer program from a memory, so that a device having the chip installed executes the method according to any one of claims 10 to 15. A computer-readable storage medium, which is used for storing a computer program that causes a computer to execute the method according to any one of claims 1 to 4. A computer-readable storage medium, which is used to store a computer program that causes a computer to execute the method according to any one of claims 5 to 9. A computer-readable storage medium, for storing a computer program, which causes a computer to execute the method according to any one of claims 10 to 15. A computer program product, comprising computer program instructions that cause a computer to execute the method according to any one of claims 1 to 4. A computer program product, comprising computer program instructions, the computer program instructions causing a computer to execute the method according to any one of claims 5 to 9. A computer program product, comprising computer program instructions that cause a computer to execute the method according to any one of claims 10 to 15. A computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 4. A computer program, wherein the computer program causes a computer to execute the method according to any one of claims 5 to 9. A computer program, wherein the computer program causes a computer to execute the method according to any one of claims 10 to 15.

Images