CN115606247A

CN115606247A - Wireless communication method and apparatus

Info

Publication number: CN115606247A
Application number: CN202080100923.8A
Authority: CN
Inventors: 付喆; 王淑坤; 杨皓睿
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2020-07-27
Filing date: 2020-07-27
Publication date: 2023-01-13
Also published as: WO2022021004A1

Abstract

A wireless communication method and apparatus are provided, the method comprising: and the access network equipment determines the result of recovering the context of the user equipment UE or the access control result according to the slice information. The slice information is considered in the process of determining and recovering the RRC connection by the access network equipment, namely, the access control is carried out based on the slice information, and under the condition that the slice of the terminal equipment is not supported by the access network equipment, the RRC connection resource of the UE is prevented from being released after the terminal equipment is accessed into the network, so that the time delay and the signaling overhead can be reduced.

Description

Wireless communication method and apparatus

Technical Field

The embodiments of the present application relate to the field of communications, and more particularly, to a wireless communication method and apparatus.

Background

Currently, an access network device determines success or failure of recovering a User Equipment (UE) context only according to the UE context, and then determines whether an RRC connection can be recovered.

However, even if the access network device can acquire the context of the user equipment, the RRC connection may need to be released for other reasons, which increases the delay and signaling overhead.

Disclosure of Invention

The wireless communication method and the wireless communication equipment avoid releasing the UE context after acquiring the UE context under the condition that the slice of the terminal equipment is not supported by the access network equipment, and can reduce time delay and signaling overhead.

In a first aspect, a wireless communication method is provided, including:

and the access network equipment determines the result of recovering the context of the user equipment UE or the access control result according to the slice information.

In a second aspect, an access network device is provided for executing the method in the first aspect or its implementation manners. Specifically, the network device includes a functional module configured to execute the method in the first aspect or its implementation manner.

In a third aspect, an access network device is provided that includes a processor and a memory. The memory is configured to store a computer program, and the processor is configured to call and execute the computer program stored in the memory to perform the method in the first aspect or each implementation manner thereof.

In a fourth aspect, a chip is provided for implementing the method in the first aspect or its implementation manners. Specifically, the chip includes: a processor, configured to call and run a computer program from a memory, so that a device in which the chip is installed performs the method according to the first aspect or each implementation manner thereof.

In a fifth aspect, a computer-readable storage medium is provided for storing a computer program, the computer program causing a computer to execute the method of the first aspect or its implementation modes.

A sixth aspect provides a computer program product comprising computer program instructions for causing a computer to perform the method of the first aspect or its implementations.

In a seventh aspect, a computer program is provided, which, when run on a computer, causes the computer to perform the method of the first aspect or its implementations.

Based on the technical scheme, slice information is considered in the process of determining and recovering RRC connection by the access network equipment, namely, access control is carried out based on the slice information, and under the condition that the slice of the terminal equipment is not supported by the access network equipment, the condition that the terminal equipment releases RRC connection resources of UE after accessing the network is avoided, so that time delay and signaling overhead can be reduced.

Drawings

Fig. 1 is an example of an application scenario of the present application.

Fig. 2 to 7 are schematic flowcharts of a wireless communication method provided in an embodiment of the present application.

Fig. 8 is a schematic block diagram of an access network device provided in an embodiment of the present application.

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

Fig. 10 is a schematic block diagram of a chip provided in 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, 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.

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

As shown in fig. 1, communication system 100 may include a terminal device 110 and a network device 120. Network device 120 may communicate with terminal device 110 over the air. Multi-service transport is supported between terminal device 110 and network device 120.

It should be understood that the embodiment of the present application is only illustrated as the communication system 100, but the embodiment of the present application is not limited thereto. That is to say, the technical solution of the embodiment of the present application can be applied to various communication systems, for example: a Long Term Evolution (LTE) System, a Time Division Duplex (TDD) System, a Universal Mobile Telecommunications System (UMTS), a 5G communication System (also referred to as a New Radio (NR) communication System), a future communication System, or the like.

In communication system 100 shown in fig. 1, network device 120 may be an access network device that communicates with terminal device 110. An access network device may provide communication coverage for a particular geographic area and may communicate with terminal devices 110 (e.g., UEs) located within the coverage area.

The Network device 120 may be an evolved Node B (eNB or eNodeB) in a Long Term Evolution (Long Term Evolution, LTE) system, or a Next Generation Radio Access Network (NG RAN) device, or a base station (gNB) in an NR system, or a wireless controller in a Cloud Radio Access Network (CRAN), or the Network device 120 may be a relay station, an Access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, or a Network device in a Public Land Mobile Network (PLMN) for future Evolution, or the like.

Terminal device 110 may be any terminal device including, but not limited to, terminal devices that employ wired or wireless connections with network device 120 or other terminal devices.

For example, the terminal Equipment 110 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 device. 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 evolution network, etc.

The terminal Device 110 may be used for Device-to-Device (D2D) communication.

The wireless communication system 100 may further include a core network device 130 in communication with the base station, and the core network device 130 may be a 5G core (5G core,5 gc) device, such as an Access and Mobility Management Function (AMF), an Authentication Server Function (AUSF), a User Plane Function (User upplane Function (SMF), or a Session Management Function (SMF). Alternatively, the Core network device 130 may also be an Evolved Packet Core (EPC) device of the LTE network, for example, a Session Management Function + Core Packet Gateway (SMF + PGW-C) device of the Core network. It is understood that SMF + PGW-C may perform the functions that SMF and PGW-C can perform simultaneously. In the network evolution process, the core network device may also be called by other names, or a new network entity is formed by dividing the functions of the core network, which is not limited in this embodiment of the present application.

Communication between the functional units in the communication system 100 may also be implemented by establishing a connection through a next generation Network (NG) interface.

For example, the terminal device establishes an air interface connection with the access network device through the NR interface, and is used to transmit user plane data and control plane signaling; the terminal equipment can establish control plane signaling connection with the AMF through an NG interface 1 (N1 for short); an access network device, such as a next generation radio access base station (gNB), may establish a user plane data connection with a UPF through an NG interface 3 (N3 for short); the access network equipment can establish control plane signaling connection with the AMF through an NG interface 2 (N2 for short); the UPF can establish a control plane signaling connection with the SMF through an NG interface 4 (N4 for short); the UPF can interact user plane data with a data network through an NG interface 6 (N6 for short); the AMF can establish a control plane signaling connection with the SMF through an NG interface 11 (N11 for short); the SMF may establish a control plane signaling connection with the PCF via NG interface 7 (N7 for short).

Fig. 1 exemplarily shows one base station, one core network device, and two terminal devices, alternatively, the wireless communication system 100 may include a plurality of base station devices and may include other numbers of terminal devices within the coverage area of each base station, which is not limited in this embodiment of the present invention.

It should be understood that, in the embodiments of the present application, devices having a communication function in a network/system may be referred to as communication devices. Taking the communication system 100 shown in fig. 1 as an example, the communication device may include a network device 120 and a terminal device 110 having a communication function, and the network device 120 and the terminal device 110 may be the 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 also 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.

It should be noted that, in the present application, the RRC CONNECTED state of the terminal device may include an RRC _ INACTIVE state, an RRC _ IDLE state, and an RRC _ CONNECTED state. In the RRC _ IDLE state, mobility is UE-based cell selection reselection, paging is initiated by a Core Network (CN), and a paging area is configured by the CN. The base station side does not have the context of the UE Access Stratum (AS) and does not have RRC connection. In the RRC _ CONNECTED state, an RRC connection exists, and a UE AS context exists for the base station and the UE. The network device knows that the location of the UE is cell-specific. Mobility is network device controlled mobility. Unicast data may be transmitted between the UE and the base station. Under RRC _ INACTIVE, mobility is cell selection and reselection based on UE, connection between CN-NR exists, UE AS context exists on a certain base station, paging is triggered by a Radio Access Network (RAN), a paging area based on the RAN is managed by the RAN, and Network equipment knows that the position of the UE is based on the paging area level of the RAN.

In the process of the terminal device recovering from the RRC deactivated state to the RRC connected state, a process of requesting the serving access network device receiving the RRC recovery request to request a context (context) from the last serving access network device (last serving gNB) may be involved. The RRC recovery request (rrcredumerequest, or rrcredumerequest 1) message carries the Identifier of the terminal device, and identifies an identity Radio Network Temporary Identifier (I-RNTI) I-RNTI. And the request service access network equipment receiving the RRC recovery request determines the identifier of the last service access network equipment through the identifier of the terminal equipment and requests the last service access network equipment to acquire the context. For example, a resume UE context request may be sent to the last serving access network device. Finally, the service access network device may respond to a restore UE CONTEXT RESPONSE (restore UE CONTEXT RESPONSE) or a restore UE CONTEXT failure (restore UE CONTEXT failure).

In other words, after the terminal device sends the RRC resume request (rrcredumerequest), the requesting serving access network device sends a retrieve UE context request to the last serving access network device. Finally, the serving access network device may send a RETRIEVE UE CONTEXT RESPONSE or a RETRIEVE UE CONTEXT failure.

Fig. 2 shows a schematic flow diagram of a wireless communication method 200 according to an embodiment of the application, which method 200 can be performed interactively by a terminal device, a requesting serving access network device, a last serving access network device and an AMF. The terminal device shown in fig. 2 may be a terminal device as shown in fig. 1, and the requesting serving access network device and the last serving access network device shown in fig. 2 may be access network devices as shown in fig. 1. The AMF shown in fig. 3 may be the core network device shown in fig. 1.

The procedure for the terminal device to successfully recover the RRC connection is described below with reference to the method 200.

As shown in fig. 2, the method 200 may include some or all of the following:

s210, the terminal device sends RRCresumRequest to the request service access network device, and provides an I-RNTI in the resume request, wherein the I-RNTI can be allocated to the terminal device by the last service access network device.

S220, if the service access network device can be addressed to the last service access network device according to the I-RNTI, the service access network device is requested to send a UE context restoring request to the last service access network device, so as to request the last service access network device to provide a UE context (context), where the UE context may also be referred to as UE context data (data).

S230, finally, the service access network device sends a UE context recovery response to the request service access network device, so as to provide the UE context data to the request service access network device.

S240, requesting the service access network device to send an RRC recovery to the terminal device.

S250, the terminal device sends an RRC recovery complete to the request service access network device to complete recovery of RRC connection.

S260, if there is downlink data in the last service access network device, in order to avoid data loss, the request service access network device may send an address indication to the last service access network device, so as to provide an address for data forwarding to the last service access network device.

S270, the service access network device is requested to send a path switch request to the AMF to perform path switch (path switch).

S280, the request service access network equipment receives the path switching request response sent by the AMF so as to complete the path switching.

S290, the request service access network device triggers the last service access network device to release the UE resource on the last service access network device.

Fig. 3 shows a schematic flow diagram of a wireless communication method 300 according to an embodiment of the application, which method 300 may be performed interactively by a terminal device, a requesting serving access network device, a last serving access network device and an AMF. The terminal device shown in fig. 3 may be a terminal device as shown in fig. 1, and the requesting serving access network device and the last serving access network device shown in fig. 3 may be access network devices as shown in fig. 1. The AMF shown in fig. 3 may be the core network device shown in fig. 1.

The procedure for the terminal device to recover the RRC connection failure is described below with reference to the method 300.

As shown in fig. 3, the method 300 may include:

s310, the terminal equipment sends RRCresumeRequest to the request service access network equipment. For example, an I-RNTI is provided in the resume request, which is the identity assigned to the terminal device by the last serving access network device.

S320, if the request service access network equipment can address the last service access network equipment according to the I-RNTI, the request service access network equipment sends a UE context recovery request to the last service access network equipment, and the UE context recovery request is used for requesting the last service access network equipment to provide UE context data.

S330, finally the service access network equipment can not recover or authenticate the UE context data.

And S340, finally, the service access network equipment indicates the recovery failure to the requested service access network equipment.

S350, the serving access network device is requested to trigger the terminal device to perform fallback, for example, a new RRC connection may be established in a manner of sending RRCsetup.

And S360, executing the RRC connection establishment process.

In the method 200 and method 300, the serving access network device finally determines success or failure of a retrieve UE context only from the UE context, without considering slice information. However, in the actual recovery process, even if the last service access network device can acquire the context, the current service access network requesting device may not support the terminal device to access the network or slice due to the slicing problem, and further the operation of acquiring the context and then releasing the context is caused, which increases the delay and signaling overhead.

In the application, slice information is considered in the process of requesting the service access network device to recover the RRC connection, and access control can be performed.

It should be understood that the slice information may be related information of a network slice (slicing), which may also be referred to as a slice for short, and for understanding the present solution, the network slice is exemplarily described below.

Based on the network slice, the method can provide lower time delay, more targeted, more flexible and higher extensible service for a plurality of services with different requirements. For example, radio Access Network (RAN) sliding may enable an application provider to participate in customizing the design, deployment, and operation of a RAN, better supporting the services of the application provider. The terminal equipment can report the slicing requirement, and the access network equipment can select proper MAF according to the slicing requirement reported by the UE after receiving the slicing requirement reported by the terminal equipment, so as to establish a service session between the UE and the network. Since the access network device can determine the slice information required by the terminal device only after receiving the message 5 (MSG 5), the slice information required by the terminal device may not be the slice requested to be supported by the serving access network device or the slice is overloaded although being the slice requested to be supported by the serving access network device. In this case, the requesting serving access network device can only send an RRC release (rrcreelease) message to the terminal device after MSG5, so that the terminal device reselects a suitable cell. Therefore, it is possible to cause other suitable terminal devices to delay access due to access of the terminal device, and it is also possible to increase a delay in provision of the slice service of the terminal device.

Fig. 4 shows a schematic flow diagram of a wireless communication method 400 according to an embodiment of the application, which method 400 may be performed by a requesting serving access network device or a last serving access network device. The requesting serving access network device and the last serving access network device shown in fig. 4 may be access network devices as shown in fig. 1.

S410, the access network equipment determines the result of recovering the context of the user equipment UE or the access control result according to the slice information.

In other words, the access network device determines an RRC reject message according to the slice information, where the RRC reject message is used to initiate the terminal device to reestablish the RRC connection.

Or, in other words, the access network device determines whether it can be allowed to access the network according to the slice information.

Or, in other words, the access network device determines the result of the request to restore the UE context according to the slice information.

The slice information is considered in the process of determining and recovering the RRC connection by the access network equipment, namely, the access control is carried out based on the slice information, and under the condition that the slice of the terminal equipment is not supported by the access network equipment, the RRC connection resource of the UE is prevented from being released after the terminal equipment is accessed into the network, so that the time delay and the signaling overhead can be reduced.

In some embodiments of the present application, the result of restoring the UE context is a restore UE context response.

In some embodiments of the present application, the resume UE context response is configured to indicate that resuming the UE context is successful, and/or the resume UE context response is configured to indicate that a terminal device may access a network or a slice, and/or the resume UE context response is configured to indicate that at least a portion of the slices of the terminal device are supported, and/or the resume UE context response is configured to indicate that at least a portion of the slices of the terminal device are not overloaded, and/or a request that a serving access network device may support at least a portion of the slices of the terminal device.

Of course, the recover UE context response may also include second indication information and/or a second cause value, and the second indication information and/or the second cause value may be used to indicate at least one of the following: the UE context restoration is successful, and/or the UE context restoration response is used for indicating that the terminal equipment can access the network or the slices, and/or the UE context restoration response is used for indicating that at least part of the slices of the terminal equipment are supported, and/or the UE context restoration response is used for indicating that at least part of the slices of the terminal equipment are not overloaded, and/or requesting that the serving access network equipment can support at least part of the slices of the terminal equipment.

It should be noted that at least some of the slices of the terminal device may be partial slices thereof, or all of the slices.

In some embodiments of the present application, the result of restoring the UE context is failure to restore the UE context.

In some embodiments of the present application, the UE context restoration failure is used to indicate a UE context restoration failure, and/or the UE context restoration failure is used to indicate that a terminal device is not accessible to a network or a slice, and/or the UE context restoration failure is used to indicate that at least part of slices of the terminal device are not supported, and/or the UE context restoration failure is used to indicate that at least part of slices of the terminal device are overloaded, and/or a request that a serving access network device not support at least part of slices of the terminal device.

It should be noted that at least some of the slices of the terminal device may be partial slices therein, or all slices.

For example, the UE context restoration failure is used to indicate that the UE context restoration fails, and/or the UE context restoration failure is used to indicate that the terminal device cannot access the network or the slice, and/or the UE context restoration failure is used to indicate that all slices of the terminal device are not supported, and/or the UE context restoration failure is used to indicate that all slices of the terminal device are overloaded, and/or the serving access network device is requested not to support all slices of the terminal device.

In some embodiments of the present application, the failure to recover the UE context includes first indication information and/or a first cause value, where the first indication information and/or the first cause value are used to indicate at least one of: the method comprises the steps of obtaining failure of non-UE context, obtaining failure of non-UE context authentication, obtaining failure of non-UE context, obtaining failure of at least part of slices of the terminal equipment, overload of at least part of the slices of the terminal equipment, requesting service access network equipment not to support at least part of the slices of the terminal equipment, RRC rejection message and information for triggering the requesting service access network equipment to send the RRC rejection message to the terminal equipment. Optionally, the RRC reject message may be an unencrypted and/or integrity protected message. Optionally, the information for triggering the request service access network device to send the RRC reject message to the terminal device may be an instruction to the request service access network device to generate the RRC reject message, or an instruction to an Anchor (Anchor) access network device to generate the RRC reject message and send the RRC reject message to the terminal device. As explained in the specification

In some embodiments of the present application, the method 400 may further comprise:

and the access network equipment acquires or sends an RRC reject message.

In some embodiments of the present application, the RRC reject message is a message generated by the last access network device, or the RRC reject message is a message requesting the serving access network device to generate the UE context recovery failure message according to at least one of the first indication information and the first cause value, where the UE context recovery failure message is sent by the last serving access network device. In some embodiments of the present application, the RRC reject message is a message generated by the last serving access network device, and the RRC reject message is encapsulated in the failure to recover the UE context. In some embodiments of the present application, the RRC reject message is sent by the requesting serving access network device to the terminal device. In some embodiments of the present application, the RRC reject message is sent by the requesting service access network device to the terminal device after the last service access network device sends to the requesting service access network device. In some embodiments of the present application, the RRC reject message includes the first indication information and/or the first cause value, and the first indication information and/or the first cause value are used to indicate at least one of: the method comprises the steps of obtaining failure of non-UE context, failure of non-UE context authentication, non-obtaining of UE context, non-support of at least part of slices in the slices of the terminal equipment, overload of at least part of the slices of the terminal equipment, non-support of at least part of the slices of the terminal equipment by a request service access network equipment, RRC reject message and information for triggering the request service access network equipment to send the RRC reject message to the terminal equipment. In some embodiments of the present application, the RRC reject message further includes an identification of slices requested to be supported by the serving access network device and/or an identification of slices that are not overloaded.

In some embodiments of the present application, the slice information comprises at least one of:

first information acquired from a terminal device;

second information obtained from an access management function, AMF;

third information obtained from the requesting service access network device; or

And finally, the fourth information stored by the service access network equipment.

In some embodiments of the application, the first information comprises information of at least one of the allowed, established, preconfigured slices requested by the terminal device.

In some embodiments of the present application, the first information is a slice identifier.

In some embodiments of the present application, the first information is information obtained by the terminal device from the terminal device through a random access channel RACH procedure, and/or the first information is information obtained by an RRC recovery request or an RRC recovery request1 from the terminal device.

In some embodiments of the present application, the second information comprises an overload start message or information related to slice overload in the overload start message.

In some embodiments of the present application, the overload initiation message may include at least one of: an overload start network slice selection assistance information NSSAI list, a slice overload response, or information indicating a reduction in slice traffic load.

In some embodiments of the present application, the third information comprises the first information and/or the second information.

In some embodiments of the present application, the third information is carried in a resume UE context request message.

In some embodiments of the present application, the fourth information is information of at least one of requested, allowed, established, preconfigured, established slices of the terminal device held by the last serving access network device.

In some embodiments of the present application, the access network device is a last serving access network device.

In some embodiments of the present application, the access network device is a request service access network device.

the requesting serving access network device determines whether to trigger a resume UE context request procedure.

In some embodiments of the present application, the identifier of the last service access network device is an identifier obtained by requesting the service access network device to resolve an identifier radio network temporary identifier I-RNTI reported by the terminal device.

The wireless communication method of the present application is described below with reference to specific flowcharts.

Fig. 5 shows a schematic flow diagram of a wireless communication method 500 according to an embodiment of the application, which method 500 may be performed interactively by a terminal device, a requesting serving access network device and finally a serving access network device. The terminal device shown in fig. 5 may be a terminal device as shown in fig. 1, and the requesting serving access network device and the last serving access network device shown in fig. 5 may be access network devices as shown in fig. 1.

As shown in fig. 5, the method 500 may include:

s510, the terminal device in the RRC deactivated state sends a Radio Resource Control (RRC) recovery request (RRCResumeRequest or RRCResumeRequest 1) to the request service access network device. Optionally, the RRC recovery request may include at least one of the following information:

a) I-RNTI, which may be assigned to the terminal device by the last serving access network device.

b) The first information. Optionally, the first information may be a slice identifier. Optionally, the first information may comprise information of requested/allowed/established/preconfigured slices of the terminal device.

S520, if the service access network equipment can be addressed to the last service access network equipment identifier according to the I-RNTI, the service access network equipment is requested to send a UE context recovery request (retrieve UE context request) to the last service access network equipment. Optionally, the UE context restoring request may include at least one of:

a) The above first information acquired from the terminal device.

b) Second information obtained from the access management function AMF. The second information may also be referred to as non-UE (non-UE), e.g., network-level, sliced information, and may also be information for a terminal device or a slice of the terminal device. The second information may be notified by the AMF to the requesting serving access network device. For example, the second information may be carried in an overload start (overload start) message, for example, the second information acquired by the service access network device may be a complete overload start message acquired by the service access network device from the AMF, or may be only at least part of information related to slice overload in the overload start message. Optionally, the overload initiation message may include at least one of: the Overload Start network Slice selection assistance information NSSAI List (Overload Start NSSAI List), the Slice Overload List (Slice Overload List), the Slice Overload Response (Slice Overload Response), or the information indicating a Reduction in the Slice Traffic Load (Slice Traffic Reduction Indication). Optionally, the second information may be obtained in advance, may also be obtained by being requested at that time, and may also be stored.

Of course, the first information may be information notified to the service access network request device by the terminal device through the RACH procedure, or may be information notified to the service access network request device by the terminal device through the RRCResumeRequest or the RRCResumeRequest 1. Similarly, the slice information may be carried in a retrieve UE context request, or may be carried in a message different from the retrieve UE context request.

S530, finally the service access network equipment receives the UE context restoring request and determines the result of restoring the UE context based on the slice information in the UE context restoring request. In the alternative,

a) Second information obtained from an access management function, AMF; the second information may also be referred to as non-UE (non-UE), e.g., network-level, sliced information, and may also be information for a terminal device or a slice of the terminal device. The second information may be notified by the AMF to the last serving access network device. For example, the second information may be carried in an overload start (overload start) message, for example, the second information acquired by the service access network device may be a complete overload start message acquired by the service access network device from the AMF, or may be only at least part of information related to slice overload in the overload start message. Optionally, the overload initiation message may include at least one of: the Overload Start network Slice selection auxiliary information NSSAI List (Overload Start NSSAI List), the Slice Overload List (Slice Overload List), the Slice Overload Response (Slice Overload Response), or the information indicating the Reduction of the Slice Traffic Load (Slice Traffic Reduction Indication). Optionally, the second information may be obtained in advance, may also be obtained by being requested at that time, and may also be stored.

b) Third information obtained from the requesting serving access network device. For example, the first information and the second information.

Optionally, the second information in a) and the second information in the third information may be the same or different.

c) Finally the fourth information stored by the serving access network device. For example, the last serving access network device holds information of at least one of the requested, allowed, established, preconfigured, once established slices of the terminal device.

S540, the last serving access network device sends a resume UE context response to the request serving access network device. For example, the last serving access network device determines whether the terminal device can access the network or at least one of the slices of the terminal device is accepted/not overloaded based on the resume UE context request, and if all or at least one of the slices of the terminal device can access the network or the terminal device is accepted/not overloaded, the last serving access network device sends a resume UE context response (resume UE context response) to the requesting serving access network device. Optionally, the role, meaning, and specifically included content of the UE context response may refer to the description in the method 400, and are not described herein again to avoid repetition.

S550, the request service access network device performs the subsequent operation, such as sending RRCResume message to the UE.

In the method 500, the serving access network device may finally determine whether the terminal device is capable of accessing the network or whether at least part of the slice of the terminal device is supported based on the slice information, and send a recover UE context response to the requesting serving access network device only when it is determined that at least part of the slice capable of accessing the network or the terminal device is supported. Based on the method, the UE context is prevented from being restored and then released under the condition that the slice of the terminal equipment is not supported, and time delay and signaling overhead can be reduced.

Fig. 6 shows a schematic flow diagram of a wireless communication method 600 according to an embodiment of the application, which method 600 may be performed interactively by a terminal device, a requesting serving access network device and finally a serving access network device. The terminal device shown in fig. 6 may be a terminal device as shown in fig. 1, and the requesting serving access network device and the last serving access network device shown in fig. 6 may be access network devices as shown in fig. 1.

As shown in fig. 6, the method 600 may include:

s610, the terminal device in the RRC deactivated state sends a Radio Resource Control (RRC) recovery request (RRCResumeRequest or RRCResumeRequest 1) to the request service access network device. Optionally, the RRC recovery request may include at least one of the following information:

a) An I-RNTI, which may be the last serving access network device assigned to the terminal device.

b) First information. Optionally, the first information may be a slice identifier. Optionally, the first information may comprise information of requested/allowed/established/preconfigured slices of the terminal device.

S620, if the request service access network equipment can address the last service access network equipment identification according to the I-RNTI, the request service access network equipment sends a UE context recovery request (retrieve UE context request) to the last service access network equipment. Optionally, the UE context restoring request may include at least one of:

a) The first information is acquired from the terminal device.

b) Second information obtained from the access management function AMF. The second information may also be referred to as non-UE (non-UE), e.g., network-level, sliced information, and may also be information for a terminal device or a slice of the terminal device. The second information may be notified by the AMF to the requesting serving access network device. For example, the second information may be carried in an overload start (overload start) message, for example, the second information acquired by the service access network device may be a complete overload start message acquired by the service access network device from the AMF, or may be only at least part of information related to slice overload in the overload start message. Optionally, the overload initiation message may include at least one of: the Overload Start network Slice selection assistance information NSSAI List (Overload Start NSSAI List), the Slice Overload List (Slice Overload List), the Slice Overload Response (Slice Overload Response), or the information indicating a Reduction in the Slice Traffic Load (Slice Traffic Reduction Indication). Optionally, the second information may be obtained in advance, may be obtained at the time of request, and may also be stored.

S630, the service access network equipment receives the UE context restoring request and determines the result of restoring the UE context based on the slice information in the UE context restoring request. In the alternative,

a) Second information obtained from the access management function AMF; the second information may also be referred to as non-UE (non-UE), e.g., network-level, sliced information, and may also be information for a terminal device or a slice of the terminal device. The second information may be notified by the AMF to the last serving access network device. For example, the second information may be carried in an overload start (overload start) message, for example, the second information acquired by the service access network device may be a complete overload start message acquired by the service access network device from the AMF, or may be only at least part of information related to slice overload in the overload start message. Optionally, the overload initiation message may include at least one of: the Overload Start network Slice selection auxiliary information NSSAI List (Overload Start NSSAI List), the Slice Overload List (Slice Overload List), the Slice Overload Response (Slice Overload Response), or the information indicating the Reduction of the Slice Traffic Load (Slice Traffic Reduction Indication). Optionally, the second information may be obtained in advance, may also be obtained by being requested at that time, and may also be stored.

S640, the last service access network device sends a failure to recover the UE context (retrieve UE context failure) to the request service access network device. For example, the last serving access network device determines whether the terminal device may access the network or whether at least one of the slices of the terminal device is accepted/not overloaded based on the request for recovering the UE context, and if at least one of the slices of the terminal device or the terminal device is not accepted/overloaded, the last serving access network device sends a failure for recovering the UE context (retrievable UE context failure) to the requesting serving access network device. Optionally, the role, meaning, and specifically included content of the UE context failure recovery may refer to the description in the method 400, and are not described herein again to avoid repetition.

S650, the requesting serving access network device performs subsequent operations, such as sending an RRC reject message to the UE. For example, the RRC reject message may carry the first indication information or the first cause value. Optionally, the RRC reject message further includes a slice identifier that requests support of the serving access network device and/or an identifier of a slice that is not overloaded.

In the method 600, the final serving access network device determines the UE context restoration result according to the slice information. And if the last service access network equipment determines that the UE slice is inaccessible or the slice overload of the terminal equipment, the last service access network equipment sends a retrieve UE context failure to the UE. Based on the method, the UE context is prevented from being restored and then released under the condition that the slice of the terminal equipment is not supported, and time delay and signaling overhead can be reduced.

Fig. 7 shows a schematic flow chart of a wireless communication method 700 according to an embodiment of the application, which method 700 may be performed interactively by a terminal device and a requesting serving access network device. The terminal device shown in fig. 7 may be a terminal device as shown in fig. 1, and the request service access network device shown in fig. 6 may be an access network device as shown in fig. 1.

As shown in fig. 7, the method 700 may include:

s710, the terminal device in the RRC deactivated state sends a Radio Resource Control (RRC) recovery request (RRCResumeRequest or RRCResumeRequest 1) to the request service access network device. Optionally, the RRC recovery request may include at least one of the following information:

S720, the requesting service access network device receives the RRC restoration request, and determines whether to send at least one of a request to restore the UE context and a result of restoring the UE context based on the slice information. Optionally, the UE context restoring request may include at least one of:

a) The above first information acquired from the terminal device.

b) Second information obtained from an access management function, AMF; the second information may also be referred to as non-UE (non-UE), e.g., network-level, sliced information, and may also be information for a terminal device or a slice of the terminal device. The second information may be notified by the AMF to the requesting serving access network device. For example, the second information may be carried in an overload start (overload start) message, for example, the second information acquired by the service access network device may be a complete overload start message acquired by the service access network device from the AMF, or may be only at least part of information related to slice overload in the overload start message. Optionally, the overload initiation message may include at least one of: the Overload Start network Slice selection assistance information NSSAI List (Overload Start NSSAI List), the Slice Overload List (Slice Overload List), the Slice Overload Response (Slice Overload Response), or the information indicating a Reduction in the Slice Traffic Load (Slice Traffic Reduction Indication). Optionally, the second information may be obtained in advance, may be obtained at the time of request, and may also be stored.

S730, if the requesting service access network equipment determines that at least one of the slices of the terminal equipment can be accessed or is not overloaded, the requesting service access network equipment sends an RRC recovery (RRCresum) message to the UE, or sends the RRCresum message to the UE after acquiring a response message for recovering the UE context; and/or, if the request service access network equipment determines that at least one of the UE slices cannot be accessed/overloaded, the request service access network equipment sends an RRCRreject message to the UE, or sends the RRCRreject message to the UE after acquiring a response/failure message for restoring the UE context; and/or, if the request service access network device determines that at least one of the slices of the terminal device cannot be accessed/overloaded, the request service access network device determines that the request for restoring the context fails, or determines that the request for restoring the context fails after obtaining a response/failure message for restoring the context of the UE.

S740, if the request service access network device determines that at least one of the UE slices can be accessed, and if the request service access network device can be addressed to the last service access network device identifier according to the I-RNTI, the request service access network device sends a retrieve UE context request to the last service access network device. And finally, the service access network equipment receives the retrieve UE context request message and determines the result of the retrieve UE context. Optionally, the service access network device receives a retrieve UE context request message, and determines a result of the retrieve UE context according to the slice information.

In method 700, a requesting serving access network device may determine whether the terminal device is capable of accessing a network or whether at least part of a slice of the terminal device is supported based on slice information. For example, an RRC reject message is further sent to the terminal device upon determining that at least part of the slice of the non-accessible network or the terminal device is not supported. Based on the method, the UE context is prevented from being restored and then released under the condition that the slice of the terminal equipment is not supported, and time delay and signaling overhead can be reduced.

In other words, the request service access network device determines whether to send RRCReject to the UE according to the slice information. For example, if the requesting serving access network device determines that the slice of the terminal device is not accessible, e.g., the slice overload of the terminal device, the requesting serving access network device sends rrcredit to the terminal device. Otherwise, requesting the service access network device to execute a subsequent normal process, namely requesting the service access network device to execute sending a retrieve UE context Request to the last service access network device and the like. Equivalently, when the requesting service access network device can obtain the slice information of the terminal device, it is determined whether to send an rrcredit to the terminal device in a non-interactive access confirmation manner. Based on the method, the UE context is prevented from being restored and then released under the condition that the slice of the terminal equipment is not supported, and time delay and signaling overhead can be reduced.

It should be understood that, in the various method embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application. For example, S730 and S740 may be executed simultaneously, S730 may be executed first and then S740 is executed, or S740 may be executed first and then S730 is executed.

The preferred embodiments of the present application have been described in detail with reference to the accompanying drawings, however, the present application is not limited to the details of the above embodiments, and various simple modifications can be made to the technical solution of the present application within the technical idea of the present application, and these simple modifications are all within the protection scope of the present application. For example, the various features described in the foregoing detailed description may be combined in any suitable manner without contradiction, and various combinations that may be possible are not described in this application in order to avoid unnecessary repetition. For example, various embodiments of the present application may be arbitrarily combined with each other, and the same shall be considered as the disclosure of the present application as long as the concept of the present application is not violated.

In addition, in the embodiment of the present application, the terms "downlink" and "uplink" are used to indicate the transmission direction of signals or data, where "downlink" is used to indicate that the transmission direction of signals or data is a first direction transmitted from a station to a user equipment of a cell, and "uplink" is used to indicate that the transmission direction of signals or data is a second direction transmitted from the user equipment of the cell to the station, for example, "downlink signal" indicates that the transmission direction of signals is the first direction. In addition, in the embodiment of the present application, the term "and/or" is only one kind of association relation describing an associated object, and means that three kinds of relations may exist. Specifically, a and/or B may represent: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter associated objects are in an "or" relationship.

Method embodiments of the present application are described in detail above with reference to fig. 1-7, and apparatus embodiments of the present application are described in detail below with reference to fig. 8-10.

Fig. 8 is a schematic block diagram of an access network apparatus 800 according to an embodiment of the present application.

As shown in fig. 8, the access network apparatus 800 may include:

a processing unit 810, configured to determine, according to the slice information, a result of restoring the context of the user equipment UE or an access control result.

In some embodiments of the present application, the failure to recover the UE context includes first indication information and/or a first cause value, where the first indication information and/or the first cause value are used to indicate at least one of: the method comprises the steps of obtaining failure of non-UE context, obtaining failure of non-UE context authentication, obtaining failure of non-UE context, obtaining failure of at least part of slices of the terminal equipment, overload of at least part of the slices of the terminal equipment, requesting service access network equipment not to support at least part of the slices of the terminal equipment, RRC rejection message and information for triggering the requesting service access network equipment to send the RRC rejection message to the terminal equipment.

In some embodiments of the present application, the access network device further includes:

and the communication unit is used for acquiring or sending the RRC reject message.

In some embodiments of the present application, the RRC reject message is a message generated by the last access network device, or the RRC reject message is a message requesting the serving access network device to generate a UE context recovery failure message, first indication information, and at least one of the first cause values, where the UE context recovery failure message, the first indication information, and the first cause values are sent by the last serving access network device.

In some embodiments of the present application, the RRC reject message is a message generated by the last serving access network device, and the RRC reject message is encapsulated in the failure to recover the UE context.

In some embodiments of the present application, the RRC reject message is a message sent by the requesting serving access network device to the last serving access network device.

In some embodiments of the present application, the RRC rejection message includes the first indication information and/or the first cause value, and the first indication information and/or the first cause value are used to indicate at least one of: the method comprises the steps of obtaining failure of non-UE context, obtaining failure of non-UE context authentication, obtaining failure of non-UE context, obtaining failure of at least part of slices of the terminal equipment, overload of at least part of the slices of the terminal equipment, requesting service access network equipment not to support at least part of the slices of the terminal equipment, RRC rejection message and information for triggering the requesting service access network equipment to send the RRC rejection message to the terminal equipment.

In some embodiments of the present application, the RRC reject message further includes an identification of slices requested to be supported by the serving access network device and/or an identification of slices not overloaded.

first information acquired from a terminal device;

second information obtained from an Access Management Function (AMF);

In some embodiments of the present application, the processing unit 810 is further configured to:

it is determined whether a resume UE context request procedure is triggered.

In some embodiments of the present application, the identifier of the last service access network device is an identifier obtained by requesting the service access network device to resolve based on an identifier radio network temporary identifier I-RNTI reported by the terminal device.

It is to be understood that apparatus embodiments and method embodiments may correspond to one another and similar descriptions may refer to method embodiments. Specifically, the access network device 800 shown in fig. 8 may correspond to a respective subject matter for performing the methods 200 to 700 of the embodiments of the present application, such as a requesting service access network device or a last service access network device. The foregoing and other operations and/or functions of each unit in the access network device 800 are respectively for implementing corresponding flows in each method in fig. 2 to fig. 7, and are not described herein again for brevity.

The communication device of the embodiments of the present application is described above in connection with the drawings from the perspective of functional modules. It should be understood that the functional modules may be implemented by hardware, by instructions in software, or by a combination of hardware and software modules.

Specifically, the steps of the method embodiments in the present application may be implemented by integrated logic circuits of hardware in a processor and/or instructions in the form of software, and the steps of the method disclosed in conjunction with the embodiments in 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.

Alternatively, the software modules may be located in random access memory, flash memory, read only memory, programmable read only memory, electrically erasable programmable memory, registers, and the like, 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 in the above method embodiments in combination with hardware thereof.

For example, the processing unit and the communication unit referred to above may be implemented by a processor and a transceiver, respectively.

Fig. 9 is a schematic structural diagram of a communication device 900 according to an embodiment of the present application.

As shown in fig. 9, the communication device 900 may include a processor 910.

From which processor 910 may invoke and execute a computer program to implement the methods in the embodiments of the present application.

With continued reference to fig. 9, the communication device 900 may also include a memory 920.

The memory 920 may be used for storing indication information, and may also be used for storing codes, instructions, and the like executed by the processor 910. From the memory 920, the processor 910 can call and run a computer program to implement the method in the embodiment of the present application. The memory 920 may be a separate device from the processor 910 or may be integrated into the processor 910.

With continued reference to fig. 9, the communication device 900 may also include a transceiver 930.

The processor 910 may control the transceiver 930 to communicate with other devices, and in particular, may transmit information or data to the other devices or receive information or data transmitted by the other devices. The transceiver 930 may include a transmitter and a receiver. The transceiver 930 may further include antennas, and the number of antennas may be one or more.

It should be understood that the various components in the communication device 900 are connected by a bus system that includes a power bus, a control bus, and a status signal bus in addition to a data bus.

It should also be understood that the communication device 900 may be a terminal device in this embodiment, and the communication device 900 may implement the corresponding flow implemented by the request service access network device in the methods in this embodiment, that is, the communication device 900 in this embodiment may correspond to the access network device 800 in this embodiment. For example, the communication device 900 may correspond to a corresponding body for performing the methods 200 to 700 according to the embodiments of the present application, and for brevity, will not be described again here.

In addition, the embodiment of the application also provides a chip.

For example, the chip may be an integrated circuit chip having signal processing capabilities and capable of implementing or executing the methods, steps and logic blocks disclosed in the embodiments of the present application. The chip may also be referred to as a system-on-chip, a system-on-chip or a system-on-chip, etc. Alternatively, the chip may be applied to various communication devices, so that the communication device mounted with the chip can execute the methods, steps and logic blocks disclosed in the embodiments of the present application.

Fig. 10 is a schematic structural diagram of a chip 1000 according to an embodiment of the present application.

As shown in fig. 10, the chip 1000 includes a processor 1010.

From which processor 1010 may invoke and execute a computer program to implement the methods of the embodiments of the present application.

With continued reference to fig. 10, the chip 1000 may further include a memory 1020.

From the memory 1020, the processor 1010 may call and run a computer program to implement the method in the embodiment of the present application. The memory 1020 may be used to store instructions and codes, instructions, etc. that may be executed by the processor 1010. The memory 1020 may be a separate device from the processor 1010 or may be integrated into the processor 1010.

With continued reference to fig. 10, the chip 1000 may also include an input interface 1030.

The processor 1010 may control the input interface 1030 to communicate with other devices or chips, and specifically may obtain information or data transmitted by the other devices or chips.

With continued reference to fig. 10, the chip 1000 may further include an output interface 1040.

The processor 1010 may control the output interface 1040 to communicate with other devices or chips, and may particularly output information or data to the other devices or chips.

It should be understood that the chip 1000 may be applied to the access network device in the embodiment of the present application, for example, the chip may implement a corresponding process implemented by the service access network device request in each method in the embodiment of the present application, or implement a corresponding process implemented by the last service access network device in each method in the embodiment of the present application, and details are not described herein for brevity.

It should also be understood that the various components in this chip 1000 are connected by a bus system that includes a power bus, a control bus, and a status signal bus in addition to a data bus.

The processors referred to above may comprise, but are not limited to:

general purpose processors, digital Signal Processors (DSPs), application Specific Integrated Circuits (ASICs), field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components, and the like.

The processor may be configured to implement or perform the methods, steps, and logic blocks disclosed in the embodiments of the present application. 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, eprom, 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 combines hardware thereof to complete the steps of the method.

The memories referred to above include, but are not limited to:

volatile memory and/or non-volatile 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. The volatile Memory may be a Random Access Memory (RAM) which serves as an external cache. 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 DRAM (SLDRAM), and Direct Rambus RAM (DR RAM).

It should be noted that the memory described herein is intended to comprise 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. The computer readable storage medium stores one or more programs, the one or more programs comprising instructions, which when executed by a portable electronic device comprising a plurality of applications, cause the portable electronic device to perform the methods of the illustrated embodiments of methods 200-700.

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

Optionally, 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.

The embodiment of the application also provides a computer program product which comprises a computer program.

Optionally, the computer program product may be applied to the network device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the network device in each method in the embodiment of the present application, which is not described herein again for brevity.

Optionally, the computer program product 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.

The embodiment of the application also provides a computer program. The computer program, when executed by a computer, enables the computer to perform the methods of the embodiments illustrated by methods 200 through 700.

Optionally, 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 the corresponding process implemented by the network device in each method in the embodiment of the present application, and for brevity, details are not described here again.

In addition, an embodiment of the present application further provides a communication system, where the communication system may include the terminal device and the network device mentioned above to form the communication system 100 shown in fig. 1, and details are not described herein for brevity. It should be noted that the term "system" and the like herein may also be referred to as "network management architecture" or "network system" and the like.

It is also to be understood that the terminology used in the embodiments of the present application and the appended claims is for the purpose of describing particular embodiments only, and is not intended to be limiting of the embodiments of the present application.

For example, as used in the examples of this application and the appended claims, the singular forms "a," "an," "the," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.

Those of skill in the art would 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 technical solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the embodiments of the present application.

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 solutions of the embodiments of the present application may be essentially implemented or make a contribution to the prior art, or may be implemented in the form of a software product stored in a storage medium and including several 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 methods described in the embodiments of the present application. And the aforementioned storage medium includes: u disk, removable hard disk, read only memory, random access memory, magnetic disk or optical disk, etc. for storing program codes.

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 division of a unit or a module or a component in the above-described device embodiments is only one logical function division, and there may be other divisions in actual implementation, for example, a plurality of units or modules or components may be combined or may be integrated into another system, or some units or modules or components may be omitted, or not executed.

Also for example, the units/modules/components described above as separate/display components may or may not be physically separate, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the units/modules/components can be selected according to actual needs to achieve the purposes of the embodiments of the present application.

Finally, it should be noted that the above 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 above description is only a specific implementation of the embodiments of the present application, but the scope of the embodiments of the present application is not limited thereto, and any person skilled in the art can easily conceive of changes or substitutions within the technical scope of the embodiments of the present application, and all the modifications and substitutions should be covered by the scope of the embodiments of the present application. Therefore, the protection scope of the embodiments of the present application shall be subject to the protection scope of the claims.

Claims

A method of wireless communication, comprising:

and the access network equipment determines the result of recovering the context of the user equipment UE or the access control result according to the slice information.
The method of claim 1, wherein the result of restoring the UE context is a restore UE context response.
The method of claim 2, wherein the resume UE context response is configured to indicate that resuming UE context is successful, and/or wherein the resume UE context response is configured to indicate that a terminal device has network or slice access, and/or wherein at least some of the slices of the terminal device are supported, and/or wherein the resume UE context response is configured to indicate that at least some of the slices of the terminal device are not overloaded, and/or wherein at least some of the slices of the terminal device are supported by a requesting serving access network device.
The method of claim 1, wherein the result of restoring the UE context is a failure to restore the UE context.
The method according to claim 4, wherein the UE context recovery failure is used to indicate a UE context recovery failure, and/or wherein the UE context recovery failure is used to indicate that a terminal device is not accessible to a network or a slice, and/or wherein the UE context recovery failure is used to indicate that at least some of the slices of the terminal device are not supported, and/or wherein the UE context recovery failure is used to indicate that at least some of the slices of the terminal device are overloaded, and/or wherein a serving access network device is requested not to support at least some of the slices of the terminal device.
The method according to claim 4 or 5, wherein the failure to recover the UE context comprises a first indication information and/or a first cause value, and wherein the first indication information and/or the first cause value is used for indicating at least one of the following: the method comprises the steps of obtaining failure of non-UE context, failure of non-UE context authentication, non-obtaining of UE context, non-support of at least part of slices in the slices of the terminal equipment, overload of at least part of the slices of the terminal equipment, non-support of at least part of the slices of the terminal equipment by a request service access network equipment, RRC reject message and information for triggering the request service access network equipment to send the RRC reject message to the terminal equipment.
The method according to any one of claims 1 to 6, further comprising:

and the access network equipment acquires or sends an RRC reject message.
The method of claim 7, wherein the RRC reject message is a message generated by a last access network device, or wherein the RRC reject message is a message requesting a serving access network device to generate the UE context recovery failure message, the first indication information, and the first cause value, which are sent by the last serving access network device.
The method of claim 7, wherein the RRC reject message is a message generated by the last serving access network device, and wherein the RRC reject message is encapsulated in the failure to recover the UE context.
The method of claim 7, wherein the RRC reject message is a message sent by the requesting serving access network device to the last serving access network device.
The method according to any of claims 7 to 10, wherein the RRC reject message comprises the first indication information and/or the first cause value, wherein the first indication information and/or the first cause value is used to indicate at least one of: the method comprises the steps of obtaining failure of non-UE context, obtaining failure of non-UE context authentication, obtaining failure of non-UE context, obtaining failure of at least part of slices of the terminal equipment, overload of at least part of the slices of the terminal equipment, requesting service access network equipment not to support at least part of the slices of the terminal equipment, RRC rejection message and information for triggering the requesting service access network equipment to send the RRC rejection message to the terminal equipment.
The method of claim 11, wherein the RRC reject message further comprises an identification of slices requested to be supported by the serving access network device and/or an identification of slices not overloaded.
The method according to any one of claims 1 to 12, wherein the slice information comprises at least one of:

first information acquired from a terminal device;

second information obtained from an access management function, AMF;

third information obtained from the requesting service access network device; or

And finally, the fourth information stored by the service access network equipment.
The method of claim 13, wherein the first information comprises information of at least one of the slices requested by the terminal device, allowed, established, and preconfigured.
The method of claim 13, wherein the first information is a slice identifier.
The method according to claim 13, wherein the first information is information obtained by the terminal device from the terminal device through a Random Access Channel (RACH) procedure, and/or wherein the first information is information obtained by an RRC recovery request or RRC recovery request1 from the terminal device.
The method of claim 13, wherein the second information comprises an overload start message or information related to slice overload in the overload start message.
The method of claim 17, wherein the overload start message comprises at least one of: an overload start network slice selection assistance information NSSAI list, a slice overload response, or information indicating a reduction in slice traffic load.
The method of claim 13, wherein the third information comprises the first information and/or the second information.
The method of claim 13, wherein the third information is carried in a resume UE context request message.
The method of claim 13, wherein the fourth information is information of at least one of requested, allowed, established, preconfigured, once established slices of the terminal device saved by the last serving access network device.
The method of any of claims 1-21, wherein the access network device is a last serving access network device.
The method of any of claims 1-21, wherein the access network device is a requesting serving access network device.
The method of claim 23, further comprising:

the requesting serving access network device determines whether to trigger a resume UE context request procedure.
The method according to any of claims 22 to 25, wherein the identifier of the last serving access network device is an identifier obtained by requesting the serving access network device to resolve based on an identifier radio network temporary identifier I-RNTI reported by the terminal device.
An access network device, comprising:

and the processing unit is used for determining a result of recovering the context of the user equipment UE or an access control result according to the slice information.
The access network device of claim 26, wherein the result of restoring the UE context is a restore UE context response.
The access network device of claim 27, wherein the resume UE context response is configured to indicate that resuming UE context is successful, and/or wherein the resume UE context response is configured to indicate that a terminal device may access a network or a slice, and/or wherein the resume UE context response is configured to indicate that at least some of the slices of the terminal device are supported, and/or wherein the resume UE context response is configured to indicate that at least some of the slices of the terminal device are not overloaded, and/or wherein a request is made for a serving access network device to support at least some of the slices of the terminal device.
The access network device of claim 26, wherein the result of restoring the UE context is a failure to restore the UE context.
The access network device of claim 29, wherein the UE context restoration failure indicates a UE context restoration failure, and/or wherein the UE context restoration failure indicates that a terminal device is not accessible to a network or a slice, and/or wherein the UE context restoration failure indicates that at least some of the slices of the terminal device are not supported, and/or wherein the UE context restoration failure indicates that at least some of the slices of the terminal device are overloaded, and/or wherein a serving access network device is requested not support at least some of the slices of the terminal device.
The access network equipment according to claim 29 or 30, wherein the failure to recover the UE context comprises a first indication information and/or a first cause value, the first indication information and/or the first cause value indicating at least one of: the method comprises the steps of obtaining failure of non-UE context, obtaining failure of non-UE context authentication, obtaining failure of non-UE context, obtaining failure of at least part of slices of the terminal equipment, overload of at least part of the slices of the terminal equipment, requesting service access network equipment not to support at least part of the slices of the terminal equipment, RRC rejection message and information for triggering the requesting service access network equipment to send the RRC rejection message to the terminal equipment.
The access network device of any one of claims 26 through 31, wherein the access network device further comprises:

a communication unit, configured to acquire or send an RRC reject message.
The access network device of claim 32, wherein the RRC reject message is a message generated by a last access network device, or wherein the RRC reject message is a message requesting a serving access network device to generate the UE context recovery failure message, the first indication information, and the first cause value, which are sent by the last serving access network device.
The access network device of claim 32, wherein the RRC reject message is a message generated by the last serving access network device, and wherein the RRC reject message is encapsulated in the failure to recover the UE context.
The access network device of claim 32, wherein the RRC reject message is a message sent by the requesting serving access network device to the last serving access network device.
An access network device according to any one of claims 32 to 35, wherein the RRC reject message comprises the first indication information and/or the first cause value, the first indication information and/or the first cause value indicating at least one of: the method comprises the steps of obtaining failure of non-UE context, failure of non-UE context authentication, non-obtaining of UE context, non-support of at least part of slices in the slices of the terminal equipment, overload of at least part of the slices of the terminal equipment, non-support of at least part of the slices of the terminal equipment by a request service access network equipment, RRC reject message and information for triggering the request service access network equipment to send the RRC reject message to the terminal equipment.
The access network device of claim 36, wherein the RRC reject message further comprises an identification of slices requested to be supported by the serving access network device and/or an identification of slices not overloaded.
The access network device of any of claims 26 to 37, wherein the slice information comprises at least one of:

first information acquired from a terminal device;

second information obtained from an Access Management Function (AMF);

third information obtained from the requesting service access network device; or

And finally, the fourth information stored by the service access network equipment.
The access network device of claim 38, wherein the first information comprises information of at least one of the terminal device requested, allowed, established, and preconfigured slices.
The access network device of claim 38, wherein the first information is a slice identifier.
The access network device of claim 38, wherein the first information is information obtained by the terminal device from the terminal device through a Random Access Channel (RACH) procedure, and/or wherein the first information is information obtained by an RRC recovery request or RRC recovery request1 from the terminal device.
The access network device of claim 38, wherein the second information comprises an overload start message or information related to slice overload in the overload start message.
The access network device of claim 42, wherein the overload start message may include at least one of: an overload start network slice selection assistance information NSSAI list, a slice overload response, or information indicating a reduction in slice traffic load.
The access network device of claim 38, wherein the third information comprises the first information and/or the second information.
The access network device of claim 38, wherein the third information is carried in a resume UE context request message.
The access network device of claim 38, wherein the fourth information is information of at least one of requested, allowed, established, preconfigured, established slices of the terminal device that was saved by the last serving access network device.
The access network device of any of claims 26-46, wherein the access network device is a last serving access network device.
An access network device according to any one of claims 26 to 46, wherein the access network device is a request service access network device.
The access network device of claim 48, wherein the processing unit is further configured to:

it is determined whether a resume UE context request procedure is triggered.
The AN equipment according to any one of claims 47 to 49, wherein the identifier of the last serving AN equipment is an identifier obtained by requesting the serving AN equipment to resolve based on an identifier radio network temporary identifier I-RNTI reported by the terminal equipment.
A network device, comprising:

a processor, a memory for storing a computer program, and a transceiver, the processor for invoking and executing the computer program stored in the memory to perform the method of any of claims 1-25.
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 25.
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 25.
A computer program product comprising computer program instructions to cause a computer to perform the method of any one of claims 1 to 25.
A computer program, characterized in that the computer program causes a computer to perform the method according to any of claims 1 to 25.