CN112042240B - Method for configuring terminal equipment by network equipment, terminal equipment and network equipment - Google Patents
Method for configuring terminal equipment by network equipment, terminal equipment and network equipment Download PDFInfo
- Publication number
- CN112042240B CN112042240B CN201980028743.0A CN201980028743A CN112042240B CN 112042240 B CN112042240 B CN 112042240B CN 201980028743 A CN201980028743 A CN 201980028743A CN 112042240 B CN112042240 B CN 112042240B
- Authority
- CN
- China
- Prior art keywords
- terminal device
- network device
- network
- information
- mobile registration
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
- H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
Abstract
The embodiment of the application provides a method for configuring a terminal device by a network device, the terminal device and the network device, wherein the network device can indicate whether the terminal device executes a mobile registration update operation before entering an idle state, and avoid AMF re-association caused by executing the mobile registration update, thereby ensuring the use of the existing service of the terminal device. The method comprises the following steps: the method comprises the steps that a terminal device receives first information sent by a network device, wherein the first information comprises first indication information, and the first indication information is used for indicating that the terminal device does not execute mobile registration updating before entering an idle state, or is used for indicating that the terminal device takes S-NSSAI of one or more established sessions as requested NSSAI in a first request sent by the terminal device before entering the idle state and used for requesting to execute the mobile registration updating.
Description
The present application claims priority of chinese patent application with application number 201810662476.X entitled "method for configuring terminal device by network device, terminal device and network device" filed in 2018, 25/6.2018, the entire contents of which are incorporated herein by reference.
Technical Field
The embodiment of the application relates to the technical field of communication, in particular to a method for configuring a terminal device by a network device, the terminal device and the network device.
Background
In a New Radio (NR) system, before a terminal device in a Connection Management (CM) Connection state enters an idle state, a mobile registration update may be actively initiated due to a New service requirement, however, at this time, performing a mobile registration update operation may trigger Access and Mobility Management Function (AMF) reconfiguration (re-allocation), and the New AMF cannot support a network slice of an existing service, thereby causing interruption of the existing service and failing to meet a communication requirement of the NR system.
Disclosure of Invention
The embodiment of the application provides a method for configuring a terminal device by a network device, the terminal device and the network device, wherein the network device can indicate whether the terminal device executes a mobile registration update operation before entering an idle state, and avoid AMF re-association caused by executing the mobile registration update, thereby ensuring the use of the existing service of the terminal device.
In a first aspect, a method for configuring a terminal device by a network device is provided, including:
the method comprises the steps that a terminal device receives first Information sent by a Network device, wherein the first Information comprises first indication Information, the first indication Information is used for indicating that the terminal device does not execute mobile registration updating before entering an idle state, or is used for indicating that Single-Network Slice Selection Assistance Information (S-NSSAI) of one or more established sessions is used as requested Network Slice Assistance Information (NSSAI) in a first request sent by the terminal device before entering the idle state and used for requesting to execute the mobile registration updating.
In a second aspect, a method for configuring a terminal device by a network device is provided, including:
the network equipment sends first information to terminal equipment, wherein the first information comprises first indication information, and the first indication information is used for indicating that the terminal equipment does not execute mobile registration updating before entering an idle state, or is used for indicating that the terminal equipment takes S-NSSAI of one or more established sessions as requested NSSAI in a first request sent by the terminal equipment before entering the idle state and used for requesting to execute the mobile registration updating.
In a third aspect, a method for configuring a terminal device by a network device is provided, including:
the network device determines whether the mobile registration update would cause a network device reconfiguration.
In a fourth aspect, a terminal device is provided, configured to perform the method in the first aspect or each implementation manner thereof.
Specifically, the terminal device includes a functional module for executing the method in the first aspect or each implementation manner thereof.
In a fifth aspect, a network device is provided for executing the method in the second aspect or its implementation manners.
In particular, the network device comprises functional modules for performing the methods of the second aspect or its implementations described above.
In a sixth aspect, a network device is provided for performing the method of the third aspect or its implementation manners.
In particular, the network device comprises functional modules for performing the method of the third aspect or its implementations.
In a seventh aspect, a terminal device is provided that includes 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 each implementation manner thereof.
In an eighth aspect, a network device is provided that includes 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 of the second aspect or each implementation mode thereof.
In a ninth aspect, a network device is provided that includes 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 third aspect or each implementation manner thereof.
A tenth aspect provides a chip for implementing the method of any one of the first to third aspects or implementations thereof.
Specifically, the chip includes: a processor configured to call and run the computer program from the memory, so that the device on which the chip is installed performs the method according to any one of the first to third aspects or the implementation manners thereof.
In an eleventh aspect, a computer-readable storage medium is provided for storing a computer program, which causes a computer to perform the method of any one of the first to third aspects or implementations thereof.
In a twelfth 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 third aspects or implementations thereof.
In a thirteenth 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 above first to third aspects or implementations thereof.
By the technical scheme, the network equipment can indicate whether the terminal equipment executes the mobile registration updating operation before entering the idle state, and AMF re-allocation caused by executing the mobile registration updating is avoided, so that the use of the existing service of the terminal equipment is ensured.
Drawings
Fig. 1 is a schematic diagram of a communication system architecture provided in 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 a 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 a 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 a 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 provided according to an embodiment of the present application.
Fig. 8 is a schematic block diagram of a network device provided according to an embodiment of the present application.
Fig. 9 is a schematic block diagram of another network device provided in accordance with an embodiment of the present application.
Fig. 10 is a schematic block diagram of a communication device provided according to an embodiment of the present application.
Fig. 11 is a schematic block diagram of a chip provided according to an embodiment of the present application.
Fig. 12 is a schematic block diagram of a communication system provided according to an embodiment of the present application.
Detailed Description
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, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The technical scheme of the embodiment of the application can be applied to various communication systems, for example: a Global System for Mobile communications (GSM) System, a Code Division Multiple Access (CDMA) System, a Wideband Code Division Multiple Access (WCDMA) System, a General Packet Radio Service (GPRS), a Long Term Evolution (Long Term Evolution, LTE) System, an LTE Frequency Division Duplex (FDD) System, an LTE Time Division Duplex (TDD) System, a Universal Mobile Telecommunications System (UMTS), a Worldwide Interoperability for Microwave Access (WiMAX) communication System or a 5G System, or a later-version communication System.
Illustratively, a 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 a terminal device 120 (or referred to as a communication terminal, a terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminal devices located within that coverage area. In an embodiment, the Network device 110 may be a Base Transceiver Station (BTS) in a GSM system or a CDMA system, a Base Station (NodeB, NB) in a WCDMA system, an evolved Node B (eNB or eNodeB) in an LTE system, or a wireless controller in a Cloud Radio Access Network (CRAN), or a Network device in a Mobile switching center, a relay Station, an Access point, a vehicle-mounted 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 Public Land Mobile Network (PLMN) for future evolution, or the like.
The communication system 100 further comprises at least one terminal device 120 located within the coverage area of the network device 110. As used herein, "terminal equipment" includes, but is not limited to, connections via wireline, such as Public Switched Telephone Network (PSTN), Digital Subscriber Line (DSL), Digital cable, direct cable connection; and/or another data connection/network; and/or via a Wireless interface, e.g., a Digital television Network such as a Digital Video Broadcasting-Handheld (DVB-H) Network, a satellite Network, an Amplitude Modulation-Frequency Modulation (AM-FM) broadcast transmitter for a cellular Network, a Wireless Local Area Network (WLAN), a Digital television Network such as a DVB-H Network; and/or means of another terminal device arranged to receive/transmit communication signals; and/or Internet of Things (IoT) devices. A terminal device arranged to communicate over a wireless interface may be referred to as a "wireless communication terminal", "wireless terminal", or "mobile terminal". Examples of mobile terminals include, but are not limited to, satellite or cellular telephones; personal Communications Systems (PCS) terminals that may combine cellular radiotelephones with data processing, facsimile, and data Communications capabilities; PDAs that may include radiotelephones, pagers, internet/intranet access, Web browsers, notepads, calendars, BeiDou Navigation Satellite systems (BDS), and Global Positioning System (GPS) receivers; and conventional laptop and/or palmtop receivers or other electronic devices that include a radiotelephone transceiver. Terminal Equipment 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 (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device having Wireless communication capabilities, a computing device or other processing device connected to a Wireless modem, a vehicle mounted device, a wearable device, a terminal device in a 5G network, or a terminal device in a future evolved PLMN, etc.
In one embodiment, direct-to-Device (D2D) communication between end devices 120 is possible.
In an embodiment, the 5G system or the 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, and in an embodiment, the communication system 100 may include a plurality of network devices and may include other numbers of terminal devices within a coverage area of each network device, which is not limited in this embodiment of the present application.
In an embodiment, the communication system 100 may further include other network entities such as a network controller, a mobility management entity, and the like, which is not limited in this embodiment.
It should be understood that a device having a communication function in a 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 the specific devices described above and are not described herein again; the communication device may also include other devices in the communication system 100, such as other network entities, for example, a network controller, a mobility management entity, and the like, which is not limited in this embodiment.
It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in 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 indication information, where the first indication information is used to indicate that the terminal device does not perform a mobile registration update before entering an idle state, or is used to indicate that the terminal device uses S-NSSAI of one or more established sessions as a requested NSSAI in a first request sent by the terminal device before entering the idle state to request to perform the mobile registration update.
In one embodiment, the terminal device is in a CM connected state.
In one embodiment, the network device is an AMF device.
In an embodiment, the one or more established sessions may be Protocol Data Unit (PDU) sessions.
In one embodiment, the network device sends the first information to the terminal device when an Allowed (Allowed) NSSAI needs to be updated 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 also include a new Allowed NSSAI.
In an embodiment, the first Indication information may be a new parameter or an existing Re-registration Request Indication (Re-registration Request Indication).
Specifically, when the first indication information is used to indicate that the terminal device does not 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 indication information.
That is, in order to avoid causing AMF re-allocation, when it is necessary to perform a mobile registration update, the terminal device does not perform the mobile registration update before entering the idle state and performs the mobile registration update after entering the idle state according to the first indication information transmitted by the AMF.
Specifically, when the first indication information is used to indicate that the terminal device uses S-NSSAI of one or more established sessions as a requested NSSAI in the first request sent before entering the idle state, and the terminal 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 indication information.
That is, the terminal device may trigger execution of a mobile registration update by the first request.
It should be appreciated that triggering the execution of a mobile registration update by this first request does not result in 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 a new service requirement, for example, update the terminal device capability, request to register a new slice, and so on. If the terminal device requests to register a new slice, AMF re-allocation may be caused because the slice is not supported by the existing AMF, and the slice of the existing service cannot be supported by the new AMF, resulting in interruption of the existing service.
Therefore, in the embodiment of the present application, the network device instructs the terminal device not to perform a mobile registration update before entering the idle state, or instructs the terminal device to use S-NSSAI of one or more established sessions as a requested NSSAI in a first request for requesting to perform a mobile registration update sent before entering the idle state, thereby avoiding AMF re-allocation caused by performing the mobile registration update, and further ensuring the use of the existing service of the terminal device.
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 indication information, where the first indication information is used to indicate that the terminal device does not perform a mobile registration update before entering an idle state, or is used to indicate that the terminal device uses S-NSSAI of one or more established sessions as a requested NSSAI in a first request for requesting to perform a mobile registration update sent before entering an idle state.
In one embodiment, the terminal device is in a CM connected state.
In one embodiment, the network device is an AMF.
In one embodiment, the network device determines that the terminal device is not allowed to trigger a network device reconfiguration before entering the idle state.
That is to say, the AMF determines that the terminal device is not allowed to trigger AMF re-allocation before entering the idle state, so that the use of the existing service of the terminal device can be ensured.
In an embodiment, when the first indication information is used to indicate that the terminal device uses S-NSSAI of one or more established sessions as the requested NSSAI in the first request sent before entering the idle state, and the terminal device needs to perform a mobile registration update before entering the idle state, the method 300 further includes:
the network equipment receives the first request sent by the terminal equipment;
in response to the first request, the network device performs a mobile registration update.
That is, when the first indication information is used to indicate that the terminal device uses S-NSSAI of one or more established sessions as the requested NSSAI in the first request sent before entering the idle state, the terminal device may perform a mobile registration update before proceeding to the idle state.
It should be understood that, for brevity, the steps in the method 300 for configuring a terminal device by a network device may refer to corresponding steps in the method 200 for configuring a terminal device by a network device, and are not described in detail herein.
Therefore, in the embodiment of the present application, the network device instructs the terminal device not to perform a mobile registration update before entering the idle state, or instructs the terminal device to use S-NSSAI of one or more established sessions as a requested NSSAI in a first request for requesting to perform a mobile registration update sent before entering the idle state, thereby avoiding AMF re-allocation caused by performing the mobile registration update, and further ensuring the use of the existing service of the terminal device.
As one example, method 400 shown in fig. 4. In the method 400, a terminal Equipment (UE) interacts with an AMF, and the method 400 includes:
s410, the UE is in a CM-CONNECTED state (CM-CONNECTED).
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, where the first indication information is used to indicate that the UE does not perform a mobile registration Update before entering the idle state, or is used to indicate that the UE uses S-NSSAI of one or more established sessions as a requested NSSAI in a first request for requesting to perform a mobile registration Update, which is sent before entering the idle state.
S430, the UE sends a UE Configuration Update Ack (UE Configuration Update Ack) to the AMF.
The UE does not perform a mobile Registration Update (Mobility Registration Update) according to the first indication information, or takes S-NSSAI of one or more established sessions as the requested NSSAI S440.
In an embodiment, when the first indication information is used to indicate that the UE does not perform a mobile registration update before entering the idle state, the UE does not perform the mobile registration update before entering the idle state according to the first indication information.
In an embodiment, when the first indication information is used to indicate that the UE uses S-NSSAI of one or more established sessions as a requested NSSAI in the first request sent before entering the idle state, and the UE needs to perform a mobile registration update before entering the idle state, the UE sends the first request to the AMF according to the first indication information.
S450, mobile registration update is executed between the UE and the AMF.
It should be understood that the mobile registration update does 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.
The network device determines whether the mobile registration update will cause the network device to reconfigure S510.
In one embodiment, the terminal device is in a CM connected state.
In one embodiment, the network device is an 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.
In one embodiment, when the network device determines that the mobile registration update would cause a network device reconfiguration, the method further comprises:
the network device sends second information to the terminal device, wherein the second information comprises first indication information, and the first indication information is used for indicating that the reason for rejecting the mobile registration update is that the network device is not allowed to be reconfigured before entering an idle state.
That is, the network device refuses to perform the mobile registration update when the network device determines that the mobile registration update would cause a network device reconfiguration.
In an embodiment, before the network device determines whether the mobile registration update would cause a network device reconfiguration, the method 500 further comprises:
the network equipment receives first information sent by the terminal equipment, and the first information is used for requesting mobile registration updating.
Therefore, in the embodiment of the application, when the terminal device requests to execute the mobile registration update, the network device determines whether the AMF re-association will be caused, and when the AMF re-association is determined to be caused, the network device refuses to execute the mobile registration update, and feeds back the refusal reason to the terminal device, so that the AMF re-association caused by executing the mobile registration update is avoided, and further, the use of the existing service of the terminal device is ensured.
Which may be one embodiment, is a method 600 as shown in fig. 6. In the method 600, a UE interacts with an AMF, the method 600 comprising:
s610, the UE is in a CM-CONNECTED state (CM-CONNECTED).
S620, the AMF sends a UE Configuration Update Command to the UE, which includes the new Allowed NSSAI.
S630, the UE sends a UE Configuration Update Ack (UE Configuration Update Ack) to the AMF.
S640, the UE transmits a mobile Registration Update request (Mobility Registration Update request) to the AMF.
Specifically, before the UE enters the idle state, if there is a need to perform mobile registration update, for example, updating UE capability, requesting to register a new slice, etc., the UE initiates a mobile registration update request to the AMF according to normal operation, where the mobile registration update request carries Requested NSSAI, etc.
The AMF determines whether the mobile registration update will cause AMF re-allocation S650.
In one embodiment, if the AMF determines that the mobile registration update does not cause AMF re-allocation, the AMF performs the mobile registration update.
In one embodiment, 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 Reject UE Configuration Update (UE Configuration Update Reject) to the UE, wherein the Reject UE Configuration Update includes an indication that the UE Reject reason is that AMF Re-allocation is not allowed before entering the idle state.
It should be appreciated that step S660 is a step performed when the AMF determines in S650 that the mobile registration update will cause AMF re-allocation.
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:
a communication unit 710, configured to receive first information sent by a network device, where the first information includes first indication information, where the first indication information is used to indicate that the terminal device does not perform a mobile registration update before entering an idle state, or is used to indicate that the terminal device uses S-NSSAI of one or more established sessions as a requested NSSAI in a first request sent by the terminal device before entering the idle state to request to perform the mobile registration update.
In one embodiment, the terminal device 700 further includes:
a processing unit 720, configured to, when the first indication information is used to indicate that the terminal device does not perform mobile registration update before entering the idle state, not perform mobile registration update before entering the idle state according to the first indication information; alternatively, the first and second electrodes may be,
the communication unit 710 is further configured to send the first request to the network device according to the first indication information when the first indication information is used to indicate that the terminal device sends the first request before entering the idle state, where the first request uses S-NSSAI of one or more established sessions as the requested NSSAI, and the terminal device needs to perform mobile registration update before entering the idle state.
In one embodiment, the terminal device is in a CM connected state.
In one embodiment, the network device is an AMF.
It should be understood that the above and other operations and/or functions of the modules in the terminal device 700 according to the embodiment of the present application are respectively for implementing the corresponding flows of the terminal device in the method 200 in fig. 2, and are not described herein again for brevity.
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:
a communication unit 810, configured to send first information to a terminal device, where the first information includes first indication information, where the first indication information is used to indicate that the terminal device does not perform a mobile registration update before entering an idle state, or is used to indicate that the terminal device uses S-NSSAI of one or more established sessions as a requested NSSAI in a first request sent before entering the idle state to request to perform the mobile registration update.
In one embodiment, the network device 800 further comprises:
a processing unit 820, configured to determine that the terminal device is not allowed to trigger the network device reconfiguration before entering the idle state.
In an embodiment, when the first indication information is used to indicate that the terminal device uses S-NSSAI of one or more established sessions as the requested NSSAI in the first request sent before entering the idle state, and the terminal device needs to perform a mobile registration update before entering 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, processing unit 820 is configured to perform a mobile registration update.
In one embodiment, the terminal device is in a CM connected state.
In one embodiment, the network device is an AMF.
It should be understood that the above and other operations and/or functions of the modules in the network device 800 according to the embodiment of the present application are respectively for implementing the corresponding flows of the network device in the method 300 in fig. 3, and are not described herein again for brevity.
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:
a processing unit 910 configured to determine whether the mobile registration update may cause network device reconfiguration.
In an embodiment, when the processing unit 910 determines that the mobile registration update may cause network device reconfiguration, the network device 900 further includes:
a communication unit 920, 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 reconfiguration of the network device is not allowed before entering the idle state.
In an embodiment, before the processing unit 910 determines whether the mobile registration update may cause network device reconfiguration, the network device 900 further includes:
a communication unit 920, configured to receive first information sent by the terminal device, where the first information is used to request a mobile registration update.
In an embodiment, before the processing unit 910 determines whether the mobile registration update may 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 an idle state.
In one embodiment, the terminal device is in a CM connected state.
In one embodiment, the network device is an AMF.
It should be understood that the above and other operations and/or functions of the modules in the network device 900 according to the embodiment of the present application are respectively for implementing the corresponding flows of the network device in the method 500 in fig. 5, and are not described herein again for brevity.
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 may call and execute a computer program from a memory to implement the method in the embodiment of the present application.
In an embodiment, as shown in fig. 10, the communication device 1000 may further include a memory 1020. From the memory 1020, the processor 1010 may call and execute a computer program to implement the method in the embodiment of the present application.
The memory 1020 may be a separate device from the processor 1010 or may be integrated into the processor 1010.
In an embodiment, 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 transmit information or data to the other devices or receive information or data transmitted by the other devices.
The transceiver 1030 may include a transmitter and a receiver, among others. The transceiver 1030 may further include an antenna, and the number of antennas may be one or more.
In an embodiment, the communication device 1000 may specifically be a network device in the embodiment of the present application, and the communication device 1000 may implement a corresponding process implemented by the network device in each method in the embodiment of the present application, and for brevity, no further description is given here.
In an embodiment, 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 a corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, and for brevity, details are not described here again.
Fig. 11 is a schematic structural diagram of a chip of 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.
In an embodiment, as shown in fig. 11, the chip 1100 may further include a memory 1120. From the memory 1120, the processor 1110 can call and run a computer program to implement the method in the embodiment of the present application.
The memory 1120 may be a separate device from the processor 1110, or may be integrated into the processor 1110.
In one embodiment, the chip 1100 may also include an input interface 1130. The processor 1110 may control the input interface 1130 to communicate with other devices or chips, and in particular, may obtain information or data sent by other devices or chips.
In an embodiment, 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, and in particular, may output information or data to the other devices or chips.
In an embodiment, the chip may be applied to a network device in this embodiment, and the chip may implement a corresponding process implemented by the network device in each method in this embodiment, which is not described herein again for brevity.
In an embodiment, the chip may be applied to the mobile terminal/terminal device in this embodiment, and the chip may implement a corresponding process implemented by the mobile terminal/terminal device in each method in this embodiment, which is not described herein again for brevity.
It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip or a system-on-chip, etc.
Fig. 12 is a schematic block diagram of a communication system 1200 provided in 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 configured to implement corresponding functions implemented by the terminal device in the foregoing method, and the network device 1220 may be configured to implement corresponding functions implemented by the network device in the foregoing method, which is not described herein again for brevity.
It should be understood that the processor of the embodiments 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 performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The 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 (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, or discrete hardware components. The various methods, steps, and logic blocks disclosed 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 directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.
It will be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of example, but not limitation, many forms of RAM are available, such as Static random access memory (Static RAM, SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), Double Data Rate Synchronous Dynamic random access memory (DDR SDRAM), Enhanced Synchronous SDRAM (ESDRAM), Synchronous link SDRAM (SLDRAM), and Direct Rambus 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 understood that the above memories are exemplary but not restrictive illustrations, for example, the memories in the embodiments of the present application may also be SRAM, DRAM, SDRAM, DDR SDRAM, ESDRAM, SLDRAM, and direct memory bus random access memory DR RAM, etc. That is, the memory in the 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 the computer program.
In an embodiment, the computer-readable storage medium may be applied to a network device in the embodiment of the present application, and the computer program enables a computer to execute corresponding processes implemented by the network device in each method in the embodiment of the present application, which is not described herein again for brevity.
In an embodiment, the computer-readable storage medium may be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein again for brevity.
Embodiments of the present application also provide a computer program product comprising computer program instructions.
In an embodiment, the computer program product may be applied to a network device in the embodiment of the present application, and the computer program instructions enable 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 again for brevity.
In an embodiment, the computer program product may be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program instructions enable the computer to execute corresponding processes implemented by the mobile terminal/terminal device in the methods in the embodiments of the present application, which are not described herein again for brevity.
The embodiment of the application also provides a computer program.
In an embodiment, the computer program may be applied to the network device in the embodiment of the present application, and when the computer program runs on a computer, the computer is enabled to execute corresponding processes implemented by the network device in the methods in the embodiment of the present application, and for brevity, details are not described here again.
In an embodiment, the computer program may be applied to the mobile terminal/terminal device in the embodiment of the present application, and when the computer program runs on a computer, the computer is enabled to execute a corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein again 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 implementation. 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 is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed 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 can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into 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 such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by 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 (20)
1. A method for configuring a terminal device by a network device is characterized by comprising the following steps:
the terminal device receives first information sent by the network device, wherein the first information comprises first indication information, and the first indication information is used for indicating that the terminal device uses single network slice auxiliary information S-NSSAI of one or more established sessions as requested network slice auxiliary information NSSAI in a first request sent by the terminal device before entering an idle state and used for requesting to execute mobile registration update;
wherein the method further comprises:
when the terminal device needs to perform mobile registration update before entering an idle state, the terminal device sends the first request to the network device according to the first indication information, so that the network device performs mobile registration update in response to the first request.
2. The method of claim 1, wherein the terminal device is in a Connection Management (CM) connected state.
3. Method according to claim 1 or 2, wherein the network device is an access and mobility management function, AMF.
4. A method for configuring a terminal device by a network device is characterized by comprising the following steps:
the network equipment sends first information to the terminal equipment, wherein the first information comprises first indication information, and the first indication information is used for indicating that the terminal equipment takes single network slice auxiliary information S-NSSAI of one or more established sessions as requested network slice auxiliary information NSSAI in a first request which is sent before entering an idle state and is used for requesting to execute mobile registration updating; when the terminal device needs to perform mobile registration update before entering the idle state, the method further includes:
the network equipment receives the first request sent by the terminal equipment;
in response to the first request, the network device performs a mobile registration update.
5. The method of claim 4, further comprising:
the network device determines that the terminal device is not allowed to trigger network device reconfiguration before entering an idle state.
6. The method according to claim 4 or 5, characterized in that the terminal device is in a connection management, CM, connected state.
7. The method according to claim 4 or 5, characterized in that the network device is an access and mobility management function, AMF.
8. 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 indicate that, in a first request for requesting to perform a mobile registration update, the terminal device sends single network slice assistance information S-NSSAI of one or more established sessions as requested network slice assistance information NSSAI before entering an idle state;
the communication unit is further configured to send the first request to the network device according to the first indication information when the terminal device needs to perform a mobile registration update before entering an idle state, so that the network device performs the mobile registration update in response to the first request.
9. The terminal device of claim 8, wherein the terminal device is in a Connection Management (CM) connected state.
10. A terminal device according to claim 8 or 9, characterized in that the network device is an access and mobility management function, AMF.
11. A network device, comprising:
a communication unit, configured to send first information to a terminal device, where the first information includes first indication information, where the first indication information is used to indicate that a single network slice assistance information S-NSSAI of one or more established sessions is used as a requested network slice assistance information NSSAI in a first request for requesting to perform a mobile registration update, which is sent by the terminal device before entering an idle state;
when the terminal device needs to perform mobile registration update before entering an idle state, the communication unit is further configured to receive the first request sent by the terminal device; and the network device further comprises a processing unit, responsive to the first request, for performing a mobile registration update.
12. The network device of claim 11, wherein the network device further comprises:
and the processing unit is used for determining that the terminal equipment is not allowed to trigger the reconfiguration of the network equipment before entering the idle state.
13. Network device according to claim 11 or 12, characterized in that said terminal device is in a connection management, CM, connected state.
14. Network device according to claim 11 or 12, wherein the network device is an access and mobility management function, AMF.
15. A terminal device, comprising: a processor and a memory for storing a computer program, the processor being configured to invoke and execute the computer program stored in the memory to perform the method of any of claims 1 to 3.
16. A network device, comprising: a processor and a memory for storing a computer program, the processor being configured to invoke and execute the computer program stored in the memory to perform the method of any of claims 4 to 7.
17. A chip, comprising: a processor for calling and running a computer program from a memory so that a device on which the chip is installed performs the method of any one of claims 1 to 3.
18. A chip, comprising: a processor for calling and running a computer program from a memory so that a device on which the chip is installed performs the method of any one of claims 4 to 7.
19. A computer-readable storage medium for storing a computer program which causes a computer to perform the method of any one of claims 1 to 3.
20. A computer-readable storage medium for storing a computer program which causes a computer to perform the method of any one of claims 4 to 7.
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810662476X | 2018-06-25 | ||
| CN201810662476 | 2018-06-25 | ||
| PCT/CN2019/079685 WO2020001099A1 (en) | 2018-06-25 | 2019-03-26 | Method for configuring terminal device by means of network device, and terminal device and network device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112042240A CN112042240A (en) | 2020-12-04 |
| CN112042240B true CN112042240B (en) | 2022-01-11 |
Family
ID=68985475
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201980028743.0A Active CN112042240B (en) | 2018-06-25 | 2019-03-26 | Method for configuring terminal equipment by network equipment, terminal equipment and network equipment |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN112042240B (en) |
| WO (1) | WO2020001099A1 (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2021163978A1 (en) * | 2020-02-20 | 2021-08-26 | Oppo广东移动通信有限公司 | Method for controlling state of secondary cell group, and terminal device |
| WO2021196185A1 (en) * | 2020-04-03 | 2021-10-07 | Oppo广东移动通信有限公司 | Wireless communication method, terminal device, and network device |
| CN114077448A (en) * | 2020-08-11 | 2022-02-22 | 深圳云天励飞技术股份有限公司 | Data management method and related equipment |
| CN114650147A (en) * | 2020-12-02 | 2022-06-21 | 成都鼎桥通信技术有限公司 | Login method and device |
| CN113810990A (en) * | 2021-09-23 | 2021-12-17 | 上海移远通信技术股份有限公司 | Communication method and device |
| CN113900412A (en) * | 2021-10-12 | 2022-01-07 | 武汉逸飞激光股份有限公司 | Synchronous shaft zero calibration method and device, control unit and readable storage medium |
| CN114598605A (en) * | 2022-03-28 | 2022-06-07 | 百富计算机技术（深圳）有限公司 | Multi-device management method, first device, center device and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101527899A (en) * | 2008-03-07 | 2009-09-09 | 大唐移动通信设备有限公司 | Method and system for initiating updating of tracking area in switching process and user equipment |
| CN105027605A (en) * | 2013-11-01 | 2015-11-04 | 华为技术有限公司 | Heterogeneous system measurement method, terminal and network device |
| CN106465323A (en) * | 2014-07-01 | 2017-02-22 | 夏普株式会社 | Base station device, first position management device, terminal device, communication control method, and communication system |
| CN107580324A (en) * | 2017-09-22 | 2018-01-12 | 中国电子科技集团公司第三十研究所 | A kind of method for GSM IMSI secret protections |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101848449B (en) * | 2009-03-24 | 2013-12-04 | 华为技术有限公司 | Method, device and system for user management and state maintenance |
-
2019
- 2019-03-26 CN CN201980028743.0A patent/CN112042240B/en active Active
- 2019-03-26 WO PCT/CN2019/079685 patent/WO2020001099A1/en active Application Filing
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101527899A (en) * | 2008-03-07 | 2009-09-09 | 大唐移动通信设备有限公司 | Method and system for initiating updating of tracking area in switching process and user equipment |
| CN105027605A (en) * | 2013-11-01 | 2015-11-04 | 华为技术有限公司 | Heterogeneous system measurement method, terminal and network device |
| CN106465323A (en) * | 2014-07-01 | 2017-02-22 | 夏普株式会社 | Base station device, first position management device, terminal device, communication control method, and communication system |
| CN107580324A (en) * | 2017-09-22 | 2018-01-12 | 中国电子科技集团公司第三十研究所 | A kind of method for GSM IMSI secret protections |
Non-Patent Citations (2)
| Title |
|---|
| Correction of UE configuration update procedure;OPPO;《3GPP TSG-SA WG2 Meeting #127 S2-183204》;20180420;第4.2.4.2节 * |
| Updating Rejected NSSAI;LG Electronics Inc.;《3GPP TSG-CT WG1 Meeting #110 C1-182371》;20180420;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112042240A (en) | 2020-12-04 |
| WO2020001099A1 (en) | 2020-01-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112042240B (en) | Method for configuring terminal equipment by network equipment, terminal equipment and network equipment | |
| CN111787590B (en) | Session management method, terminal device and network device | |
| CN113316148B (en) | Method and apparatus for network slice authentication | |
| CN112075093B (en) | Service processing method and device in switching process, terminal and network equipment | |
| CN111741479B (en) | Strategy determination method and device, terminal, chip and computer storage medium | |
| CN112673687B (en) | Registration method, terminal equipment and network equipment | |
| CN111885640B (en) | Control data transmission method, network equipment and storage medium | |
| CN111989984A (en) | Strategy determination method and device, and terminal | |
| CN113615314A (en) | Relay selection method and device and terminal equipment | |
| CN112088558B (en) | Method and device for configuring policy, network equipment and terminal | |
| US20220061075A1 (en) | Information transmission method and apparatus, and network device | |
| CN110720237B (en) | Information configuration method and device, and communication equipment | |
| CN112534738B (en) | Reference signal measurement configuration method, terminal equipment and network equipment | |
| CN110741681B (en) | Method for establishing connection, network equipment and terminal equipment | |
| CN111757551B (en) | Communication method in Internet of vehicles, terminal equipment and network equipment | |
| CN112205016A (en) | Terminal capability information interaction method, terminal equipment and network equipment | |
| CN111869266A (en) | Core network selection method and device, terminal equipment and network equipment | |
| CN113424639A (en) | Access control method and device, and terminal | |
| CN111867100A (en) | BWP switching method and device, and terminal device | |
| CN111869282A (en) | Window configuration method and device, terminal and network equipment | |
| CN111837419B (en) | Data transmission method, terminal equipment and network equipment | |
| CN115943653A (en) | Method and device for reporting terminal capability, terminal and network equipment | |
| CN113574936A (en) | Wireless communication method, terminal equipment and network equipment | |
| CN112956241A (en) | Service request method, electronic device and storage medium | |
| CN111972001A (en) | Signaling interaction method and device in switching process and network equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |