CN113891427B

CN113891427B - Communication method and device

Info

Publication number: CN113891427B
Application number: CN202010808624.1A
Authority: CN
Inventors: 朱方园; 李岩; 黄正磊
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2020-07-01
Filing date: 2020-08-12
Publication date: 2023-03-10
Anticipated expiration: 2040-08-12
Also published as: WO2022001318A1; CN113891427A

Abstract

In the technical scheme of the application, when the core network equipment determines the network slice allowing the terminal equipment to access, the core network equipment can be ensured to support the access of the core network equipment to the network slice determined by the core network equipment by considering the wireless resources supported by the terminal equipment to access and the wireless resources corresponding to the network slice deployed at the current position of the terminal equipment; in the switching scenario, when determining whether to allow the PDU session established by the terminal device to be switched to the target access network device, the target access network device considers the wireless resource supported by the terminal device for access and the wireless resource corresponding to the network slice corresponding to the PDU session to be switched to the target access network device at the current position of the terminal device, so as to ensure that the terminal device supports the network slice corresponding to the PDU session successfully switched to the target access network device at the current position. The technical scheme is beneficial to the transmission of terminal services.

Description

Communication method and device

The present application claims priority from chinese patent application having application number 202010623235.1, entitled "communication method and apparatus", filed by the chinese patent office on year 2020, month 07, 01.

Technical Field

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

Background

Fifth generation (5) ^th generation, 5G) times, hundreds of billions of internet-of-things devices access to networks, and the demands of different types of application scenarios on the networks are differentiated and sometimes even mutually conflict. Providing services for different types of application scenarios through a single network at the same time can lead to an abnormally complex network architecture, low network management efficiency and low resource utilization efficiency. The 5G network slicing technology provides mutually isolated network environments for different application scenarios in a manner of virtually simulating an independent logical network on the same network infrastructure, so that different application scenarios can customize network functions and characteristics according to respective requirements, and quality of service (QoS) requirements of different services can be practically guaranteed. The 5G network slice organically combines terminal equipment, access network resources, core network resources, a network operation and management system and the like, and provides a complete network which can be independently operated and maintained and is isolated from each other for different business scenes or business types.

In a 5G network, when a terminal device needs to use a network service, it first registers with the network. The registration process triggers the network slice selection process. In a conventional network slice selection process, a core network device selects a network slice for a terminal device according to a request of the terminal device, subscription data, local configuration information, a roaming agreement, a policy of an operator, and the like. A problem in the conventional network slice selection process is that the terminal device may not support the network slice determined in the network slice selection process, so that the terminal device cannot use the service of the network slice, and the transmission of the terminal service is affected. In some cases, the terminal device may also continuously try to establish a PDU session corresponding to a network slice that the terminal device does not support access, which causes severe power consumption of the terminal device and affects service experience of the terminal device.

Disclosure of Invention

The communication method and the communication device can ensure that the terminal equipment supports the network slice determined by the access core network equipment, and are beneficial to the transmission of terminal services.

In a first aspect, the present application provides a communication method, including: the method comprises the steps that core network equipment acquires first wireless resource information, wherein the first wireless resource information is used for indicating that terminal equipment located at a first position supports accessed wireless resources; and the core network device determines, according to the first radio resource information and second radio resource information, an identifier of a first network slice that the terminal device is allowed to access, where the second radio resource information is used to indicate a radio resource corresponding to a network slice deployed at the first location, and the terminal device supports access to the radio resource corresponding to the first network slice that is allowed to access at the first location.

Alternatively, the core network device may be a mobility and mobility management function (AMF) or a Network Slice Selection Function (NSSF).

Optionally, the core network device may further obtain an identifier of a network slice requested to be accessed by the terminal device and information of a current location where the terminal device is located (i.e., information of the first location). The information of the first location may be a Tracking Area Identity (TAI) where an access network device currently accessed by the terminal device is located.

It should be noted that the first network slice may include one or more network slices that the terminal device is allowed to access, and the network slice that the terminal device requests to access may also include one or more network slices. Optionally, the first network slice may be represented by allowed network slice selection auxiliary information (allowed NSSAI), and the network slice requested to be accessed by the terminal device may be represented by requested network slice selection auxiliary information (requested NSSAI).

It should be noted that the radio resources that the terminal device supports access may also be described as radio resource capabilities that the terminal device has. For example, the first radio resource information may be represented by a radio capability (radio capability) information element. In the above technical solution, when the core network device determines the network slice allowing the terminal device to access, the core network device selects the network slice under the wireless resource supported by the terminal device to access in consideration of the wireless resource supported by the terminal device and the wireless resource corresponding to the network slice deployed at the current position of the terminal device, so as to ensure that the terminal device supports the network slice determined by the access core network device, which is accessed by the terminal device, and to facilitate transmission of the terminal service.

With reference to the first aspect, in a possible implementation manner, the first network slice is one or more network slices requested to be accessed by the terminal device.

That is, the core network device selects a network slice to which the terminal device is allowed to access from among network slices to which the terminal device requests access.

With reference to the first aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the method further includes: and the core network equipment sends the identifier of the first network slice.

Optionally, when the core network device is an NSSF device, the core network device sends the identifier of the first network slice to the AMF, so that the AMF further sends the identifier of the first network slice to the terminal device.

Optionally, when the core network device is the AMF, the core network device sends the identifier of the first network slice to the access network device, so that the access network device further sends the identifier of the first network slice to the terminal device.

In the above technical solution, the core network device feeds back, to the terminal device, an identifier of a network slice to which the terminal device is allowed to access, so that the terminal device can know which network slice services can be used, which is beneficial to transmission of the terminal service.

With reference to the first aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the method further includes: and the core network equipment determines an identifier and first information of a second network slice which is rejected to the terminal equipment to access according to the first wireless resource information and the second wireless resource information, wherein the first information and the first information are used for indicating that the terminal equipment does not support access to wireless resources corresponding to the second network slice at the first position.

Optionally, the second network slice may include one or more network slices denying access by the terminal device.

Optionally, the second network slice is one or more of the network slices requested to be accessed by the terminal device.

Alternatively, the second network slice may be represented by rejected network slice selection assistance information (rejected NSSAI).

In the above technical solution, when determining the network slice rejecting the access of the terminal device, the core network device considers the wireless resource supported by the terminal device for access and the wireless resource corresponding to the network slice deployed at the current location of the terminal device, and if the terminal device cannot support a certain network slice deployed at the current location, determines that the certain network slice is the network slice rejecting the access of the terminal device (such as the second network slice). Therefore, the terminal equipment can be ensured to support the network slice determined by the access core network equipment, and the transmission of the terminal service is facilitated.

With reference to the first aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the method further includes: and the core network equipment sends the identification and/or the first information of the second network slice.

In the above technical solution, the core network device feeds back, to the terminal device, the identifier of the network slice to which the terminal device is denied access, so that the terminal device can know which network slice services cannot be used, thereby avoiding transmission of the network slice services and facilitating transmission of the terminal service.

With reference to the first aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the method further includes: and the core network device sends the third radio resource information, where the third radio resource information is used to indicate the radio resource corresponding to the network slice allowed to be accessed by the terminal device at the first position.

In the above technical solution, the core network device feeds back, to the terminal device, the radio resource corresponding to the first location of the network slice to which the terminal device is allowed to access, which is beneficial to subsequent operations of the terminal device, such as cell search, cell handover, and the like.

With reference to the first aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, when the core network device selects a functional network element NSSF for a network slice, the acquiring, by the core network device, first radio resource information includes: the NSSF receives a first request message from a first access and mobility management function network element, AMF, the first request message including the first radio resource information.

Optionally, the first request message further includes an identifier of a network slice requested to be accessed by the terminal device and/or information of the first location.

Alternatively, the first Request message may be a network slice selection Request message (nssf _ NSSelection _ Get Request).

With reference to the first aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, when the core network device is a first access and mobility management function network element AMF, the acquiring, by the core network device, first radio resource information includes: the first AMF sends a second request message to access network equipment, wherein the access network equipment serves the terminal equipment at the first position; the first AMF receives a second response message from the access network device, the second response message including the first radio resource information.

Alternatively, the second request message and the second response message may be N2 messages.

For example, the RADIO resource information that the terminal device supports access may be represented by a RADIO CAPABILITY (RADIO CAPABILITY) information element, the second REQUEST message may be a terminal device RADIO CAPABILITY CHECK REQUEST message (UE RADIO CAPABILITY CHECK REQUEST), and the second Response message may be a terminal device RADIO CAPABILITY CHECK Response message (UE RADIO CAPABILITY CHECK Response).

Alternatively, the first AMF may obtain the first radio resource information by using a terminal device wireless capability check request message and a terminal device wireless capability check response message.

Optionally, the first AMF may also add indication information (first indication information) in the wireless capability check request message of the terminal device, where the indication information is used to indicate that the first wireless resource information is acquired from the terminal device, so that the terminal device may only report the first wireless resource information, and does not need to report other wireless capability information, which may reduce signaling overhead.

With reference to the first aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the method further includes: and the first AMF triggers and releases a Protocol Data Unit (PDU) session corresponding to the second network slice which refuses the access of the terminal equipment.

For a mobile scenario, when the terminal device moves from a second location (source location) to a first location (target location), the terminal device initiates a registration procedure. If the terminal device has already established one or more PDU sessions at the second location, and the terminal device does not support access to the radio resources corresponding to the network slice corresponding to the established one or more PDU sessions at the first location, the first AMF triggers the release of the established one or more PDU sessions.

In the above technical solution, in a mobile scenario, the AMF determines whether to release the PDU session according to the wireless resource supported by the terminal device and the wireless resource supported by the network slice deployed at the current location of the terminal device, so as to ensure that the terminal device supports the network slice selected by the access AMF and allowing the terminal device to access, thereby facilitating service transmission.

With reference to the first aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, when a set formed by the identifier of the first network slice is an empty set or the core network device cannot determine the identifier of the first network slice, the method further includes: the first AMF sends a registration rejection message to the access network equipment; and/or the first AMF triggers a deregistration process, wherein the deregistration process is used for deregistering the terminal equipment.

In the above technical solution, in a mobile scenario, the AMF determines whether a de-registration procedure for the terminal device needs to be executed according to the wireless resource supported by the terminal device and the wireless resource supported by the network slice deployed at the current location of the terminal device, so as to de-register the terminal device from the network.

In a second aspect, the present application provides a communication method, including: a first access and mobility management function network element AMF acquires first radio resource information, wherein the first radio resource information is used for indicating that terminal equipment at a first position supports accessed radio resources; and the first AMF sends the first radio resource information to a network slice selection function network element NSSF.

Optionally, the method further comprises: the first AMF further sends, to the NSSF, information of the network slice to which the terminal device requests to access and the current location of the terminal device (i.e., information of the first location). The information of the first location may be a TAI where an access network device currently accessed by the terminal device is located.

Optionally, the network slice requested to be accessed by the terminal device may be represented by a requested NSSAI.

It should be noted that the radio resource that the terminal device supports to access may also be described as a radio resource capability that the terminal device has. For example, the first radio resource information may be represented by a radio capability (radio capability) information element.

In the above technical solution, the AMF reports the radio resource supported by the terminal device for access to the core network device, so that when the core network device determines the network slice allowing the terminal device to access, the network slice under the radio resource supported by the terminal device can be selected in consideration of the radio resource supported by the terminal device for access, thereby ensuring that the terminal device supports the network slice determined by the access to the core network device, and facilitating transmission of the terminal service.

With reference to the second aspect, in a possible implementation manner, the method further includes: the first AMF receives an identification of a first network slice allowing the terminal device to access from the NSSF, wherein the terminal device supports accessing to the wireless resource corresponding to the first network slice at the first position.

It should be noted that the first network slice may include one or more network slices allowing the terminal device to access.

Optionally, the first network slice may be represented by an allowed NSSAI.

In the above technical solution, the NSSF sends the identifier of the network slice to which the terminal device is allowed to access to the first AMF, so that the first AMF can feed back the identifier of the network slice to which the terminal device is allowed to access to the terminal device, and the terminal device can know which services of the network slice can be used, which is beneficial to transmission of the terminal service.

With reference to the second aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the first network slice is one or more network slices requested to be accessed by the terminal device.

That is, the NSSF selects a network slice to which the terminal device is allowed to access from among network slices to which the terminal device requests access.

With reference to the second aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the method further includes: and the first AMF receives an identifier of a second network slice which is rejected to be accessed by the terminal equipment and/or first information from the NSSF, wherein the first information is used for indicating that the terminal equipment does not support accessing to the wireless resources corresponding to the second network slice at the first position.

It should be noted that the second network slice may include one or more network slices that deny access to the terminal device.

Alternatively, the second network slice may be represented by a rejected NSSAI.

In the above technical solution, the NSSF sends the identifier of the network slice that rejects the access of the terminal device to the first AMF, so that the first AMF can feed back the identifier of the network slice that rejects the access of the terminal device to the terminal device, and further the terminal device can know which services of the network slice cannot be used, thereby avoiding the transmission of the services of the network slices, and facilitating the transmission of the services of the terminal device.

With reference to the second aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the method further includes: and the first AMF receives third wireless resource information from the NSSF, wherein the third wireless resource information is used for indicating wireless resources corresponding to the network slice which is allowed to be accessed by the terminal equipment at the first position.

In the above technical solution, the NSSF feeds back, to the first AMF, the radio resource corresponding to the network slice at the first location where the terminal device is allowed to access, so that the first AMF may feed back, to the terminal device, the radio resource corresponding to the network slice at the first location where the terminal device is allowed to access, which is beneficial to subsequent operations of the terminal device, such as cell search, cell handover, and the like.

With reference to the second aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the method further includes: the first AMF sends the first information and/or the third radio resource information to the access network equipment.

With reference to the second aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the acquiring, by the first AMF, first radio resource information includes: the first AMF sends a second request message to access network equipment, wherein the access network equipment serves the terminal equipment at the first position; the first AMF receives a second response message from the access network device, the second response message including the first radio resource information.

Alternatively, the first AMF may acquire the first radio resource information by using a terminal device radio capability check request message and a terminal device radio capability check response message.

In a third aspect, the present application provides a communication method, including: the method comprises the steps that access network equipment acquires first wireless resource information, wherein the first wireless resource information is used for indicating that terminal equipment located at a first position supports accessed wireless resources; the access network equipment sends the first radio resource information to a first access and mobility management function network element AMF; the access network device receives an identification of a first network slice allowing the terminal device to access from the first AMF, wherein the terminal device supports access to the wireless resource corresponding to the first network slice at the first position.

Optionally, the access network device may further send, to the first AMF, information about the network slice requested to be accessed by the terminal device and the current location of the terminal device (i.e., information about the first location). The information of the first location may be a TAI where an access network device currently accessed by the terminal device is located.

It should be noted that the first network slice may include one or more network slices allowing the terminal device to access, and the network slice the terminal device requests to access may also include one or more network slices. Optionally, the first network slice may be represented by allowed NSSAI, and the network slice requested to be accessed by the terminal device may be represented by requested NSSAI.

It should be noted that the radio resources that the terminal device supports access may also be described as radio resource capabilities that the terminal device has. For example, the first radio resource information may be represented by a radio capability (radio capability) information element.

Optionally, the first network slice is one or more of the network slices requested to be accessed by the terminal device.

In the above technical solution, the access network device reports the access-supported radio resource of the terminal device to the AMF, so that when the core network device determines the network slice allowing the terminal device to access, the network slice under the access-supported radio resource of the terminal device can be selected in consideration of the access-supported radio resource of the terminal device and the radio resource corresponding to the network slice deployed at the current location of the terminal device, thereby ensuring that the terminal device supports the access to the network slice determined by the core network device, and facilitating transmission of the terminal service.

With reference to the third aspect, in a possible implementation manner, the method further includes: and the access network equipment receives an identifier and/or first information of a second network slice rejected by the terminal equipment from the first AMF, wherein the first information is used for indicating that the terminal equipment does not support accessing to the wireless resources corresponding to the second network slice at the first position.

Alternatively, the second network slice may be represented by a rejected NSSAI.

In the above technical solution, the first AMF sends the identifier of the network slice that is rejected by the terminal device to the access network device, so that the access network device can feed back the identifier of the network slice that is rejected by the terminal device to the terminal device, and then the terminal device can know which network slice services cannot be used, thereby avoiding transmission of the network slice services, and facilitating transmission of the terminal services.

With reference to the third aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the method further includes: and the access network equipment receives third radio resource information from the first AMF, wherein the third radio resource information is used for indicating radio resources corresponding to the network slice which allows the terminal equipment to access in the first position.

In the above technical solution, the first AMF feeds back, to the access network device, the radio resource corresponding to the first location of the network slice to which the terminal device is allowed to access, so that the access network device can feed back, to the terminal device, the radio resource corresponding to the first location of the network slice to which the terminal device is allowed to access, which is beneficial to subsequent operations of the terminal device, such as cell search, cell handover, and the like.

With reference to the third aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the method further includes: and the access network equipment sends the first information and/or the third wireless resource information to the terminal equipment.

With reference to the third aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the obtaining, by the access network device, first radio resource information includes: the access network equipment sends a third request message to the terminal equipment; the access network device receives a third response message from the terminal device, wherein the third response message comprises the first radio resource information.

Alternatively, the third request message and the third response message may be Radio Resource Control (RRC) messages.

For example, the radio resource Information that the terminal device supports access may be represented by a radio Capability (radio Capability) Information element, the third request message may be a terminal device Capability query message (UE Capability query), and the third response message may be a terminal device Capability Information message (UE Capability Information).

Optionally, the access network device may obtain the first radio resource information by using a terminal device capability query message.

Optionally, when the access network device receives, from the first AMF, indication information for indicating to acquire the first radio resource information to the terminal device, the access network device may also add, in the terminal device capability query message, the indication information for indicating to acquire the first radio resource information to the terminal device. Therefore, the terminal equipment can only report the first radio resource information without reporting other radio capability information, and the signaling overhead can be reduced.

In a fourth aspect, the present application provides a method of communication, the method comprising: a terminal device located at a first position sends first wireless resource information to an access network device, wherein the first wireless resource information is used for indicating that the terminal device supports accessed wireless resources; and the terminal equipment receives an identification of a first network slice allowing the terminal equipment to access from the access network equipment, wherein the terminal equipment supports accessing to the wireless resource corresponding to the first network slice at the first position.

Optionally, the terminal device may further send, to the access network device, information of the network slice requested to be accessed by the terminal device and the current location where the terminal device is located (i.e., information of the first location). The information of the first location may be a TAI where an access network device currently accessed by the terminal device is located.

In the above technical solution, the terminal device reports the wireless resource supported by the terminal device for access, so that when the core network device determines the network slice allowing the terminal device to access, the core network device may select the network slice under the wireless resource supported by the terminal device for access in consideration of the wireless resource supported by the terminal device for access and the wireless resource corresponding to the network slice deployed at the current position of the terminal device, thereby ensuring that the terminal device supports the network slice determined by the access core network device, and facilitating transmission of the terminal service.

With reference to the fourth aspect, in a possible implementation manner, the method further includes: and the terminal equipment receives an identifier and/or first information of a second network slice refusing the access of the terminal equipment from the access network equipment, wherein the first information is used for indicating that the terminal equipment does not support the access of wireless resources corresponding to the second network slice at the first position.

Optionally, the second network slice may include one or more network slices that deny access by the terminal device.

Alternatively, the second network slice may be represented by a rejected NSSAI.

In the technical scheme, the terminal equipment acquires the identifier of the network slice which is refused to be accessed by the terminal equipment, so that the terminal equipment can know which network slice services cannot be used, thereby avoiding the transmission of the network slice services and being beneficial to the transmission of the terminal services.

With reference to the fourth aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the method further includes: and the terminal equipment receives third wireless resource information from the access network equipment, wherein the third wireless resource information is used for indicating wireless resources corresponding to the network slice which is allowed to be accessed by the terminal equipment at the first position.

In the above technical solution, the terminal device obtains the radio resource corresponding to the first location of the network slice to which the terminal device is allowed to access, which is beneficial for subsequent operations of the terminal device, such as cell search, cell handover, and the like.

With reference to the fourth aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the sending, by the terminal device located at the first location, the first radio resource information to the access network device includes: the terminal equipment receives a third request message from the access network equipment; and the terminal equipment sends a third response message to the access network equipment, wherein the third response message comprises the first radio resource information.

Alternatively, the third request message and the third response message may be RRC messages.

Alternatively, the terminal device capability query message may be a terminal device capability query message.

Optionally, the terminal device capability query message may include indication information, where the indication information is used to indicate that the first radio resource information is acquired from the terminal device. Therefore, the terminal equipment can only report the first radio resource information without reporting other radio capability information, and the signaling overhead can be reduced.

In a fifth aspect, the present application provides a communication method, including: a second access network device receives a first message from a first access network device, the second access network device being located at a first position, the first message being used to request a Protocol Data Unit (PDU) session established by a terminal device to be switched to the second access network device, the first message including first radio resource information, the first radio resource information being used to indicate that the terminal device supports accessed radio resources; and the second access network equipment determines whether to allow the PDU session established by the terminal equipment to be switched to the second access network equipment according to the first radio resource information and the radio resource corresponding to the network slice corresponding to the PDU session established by the terminal equipment at the first position.

In the above technical solution, the second access network device determines whether to allow the PDU session established by the terminal device to be switched to the second access network device according to the wireless resource supported by the terminal device for access and the wireless resource corresponding to the network slice corresponding to the established PDU session at the current location of the terminal, so as to ensure that the terminal device supports the network slice corresponding to the PDU session successfully switched to the second access network device at the current location, and facilitate transmission of the terminal service.

With reference to the fifth aspect, in a possible implementation manner, the method further includes that the second access network device sends a second message to the core network device, where the second message includes an identifier of a first PDU session and/or second information, the first PDU session is a PDU session that is rejected to be switched to the second access network device, the first PDU session belongs to a PDU session that has been established by the terminal device, and the second information is used to indicate that the terminal device does not support accessing to a radio resource corresponding to a network slice corresponding to the first PDU session at the first location.

With reference to the fifth aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the method further includes: and the second access network equipment sends a third message to the core network equipment, wherein the third message comprises an identifier of a second PDU session, the second PDU session is a PDU session which is allowed to be switched to the second access network equipment, the second PDU session belongs to the PDU session established by the terminal equipment, and the terminal equipment supports accessing to the wireless resource corresponding to the network slice corresponding to the second PDU session and corresponding to the first position.

In a sixth aspect, the present application provides a communication method, including: the method comprises the steps that first access network equipment sends a first message to second access network equipment, the second access network equipment is located at a first position, the first message is used for requesting to switch a Protocol Data Unit (PDU) session established by terminal equipment to the second access network equipment, the first message comprises first radio resource information, and the first radio resource information is used for indicating that the terminal equipment supports accessed radio resources.

In the above technical solution, the first access network device sends, to the second access network device, information for indicating that the terminal device supports the accessed radio resource, so that when determining whether to allow the PDU session established by the terminal device to be switched to the second access network device, the second access network device may consider the radio resource supported by the terminal device for access, and may ensure that the terminal device supports, at the current location, a network slice corresponding to the PDU session successfully switched to the second access network device, thereby facilitating transmission of a terminal service.

In a seventh aspect, the present application provides a communication method, including: an access and mobility management function network element AMF receives an identifier and/or second information of a first PDU session from a second access network device, the second access network device is located at a first position, the first PDU session is a PDU session refusing to be switched to the second access network device, the first PDU session belongs to the PDU session established by the terminal device, and the second information is used for indicating that the terminal device does not support accessing wireless resources corresponding to a network slice corresponding to the second PDU session at the first position; and the AMF carries out the path switching of the PDU conversation according to the identification of the first PDU conversation and/or the second information.

In an eighth aspect, the present application provides a communication method, including: the method comprises the steps that access network equipment acquires first wireless resource information, second wireless resource information and an identifier of a first network slice, wherein the first wireless resource information is used for indicating that terminal equipment located at a first position supports accessed wireless resources, the second wireless resource information is used for indicating wireless resources corresponding to at least one network slice at the first position, and the at least one network slice comprises the first network slice; the access network device determines an identifier of a second network slice according to the first radio resource information, the second radio resource information and the identifier of the first network slice, wherein the terminal device supports access to radio resources corresponding to the second network slice at the first position; and the access network equipment sends the identifier of the second network slice to a first access and mobility management network element.

Optionally, the information of the first location may be a TAI in which an access network device currently accessed by the terminal device is located.

Alternatively, the first network slice may be a network slice to which the terminal device requests access.

Alternatively, the first network slice may be a network slice received by the access network device from the first access and mobility management network element that is allowed to be accessed by the terminal device.

Optionally, the first network slice may be another network slice received by the access network device from the first access and mobility management network element, which is not limited in this embodiment of the present application. It should be noted that the first network slice may include one or more network slices, and the second network slice may also include one or more network slices.

Alternatively, the second network slice may be represented by supported network slice selection assistance information (supported nsai), the network slice requested to be accessed by the terminal device may be represented by requested network slice selection assistance information (requested nsai), and the network slice allowed to be accessed by the terminal device may be represented by allowed network slice selection assistance information (allowed nsai).

It should be noted that the wireless resources supported by the terminal device for access may also be described as the wireless capability possessed by the terminal device. For example, the first radio resource information may be represented by a radio capability (radio capability) information element.

In consideration that the access and mobility management network element may not be aware of the wireless capability of the terminal device in the registration procedure, in this embodiment of the present application, the access and mobility management network element may send a requested NSSAI or an allowed NSSAI to the access network device, so that the access network device may determine, according to the wireless capability of the terminal device, whether to support a wireless resource corresponding to each S-NSSAI included in the accessed requested NSSAI or the allowed NSSAI, and may ensure that the terminal device supports access and a network slice determined by the mobility management network element.

Optionally, the second radio resource information includes information of radio resources corresponding to the network slice in the requested NSSAI at the first position.

Optionally, the second radio resource information includes information of radio resources corresponding to the network slice deployed at the first location.

With reference to the eighth aspect, in a possible implementation manner, the identifier of the first network slice includes an identifier of a network slice requested to be accessed by the terminal device.

With reference to the eighth aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the acquiring, by the access network device, an identifier of the first network slice includes: and the access network equipment acquires the identifier of the first network slice from the first access and mobility management network element or the terminal equipment.

With reference to the eighth aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the acquiring, by the access network device, second radio resource information includes: and the access network equipment acquires the second radio resource information from the first access and mobility management network element, the access network equipment or other access network equipment.

With reference to the eighth aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the method further includes: and the access network equipment sends third indication information to the first access and mobility management network element, where the third indication information is used to indicate whether the terminal equipment supports simultaneous access to part or all of the second network slices.

By the technical scheme, the access network equipment can indicate the terminal equipment to support the network slice accessed simultaneously to the first access and mobility management network element, which is beneficial to simplifying the process that the first access and mobility management network element determines the identifier of the network slice allowed to be accessed by the terminal equipment.

With reference to the eighth aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the method further includes: and the access network equipment sends an identifier of a third network slice to the first access and mobility management network element, wherein the terminal equipment does not support the access of the wireless resource corresponding to the third network slice at the first position.

It should be noted that the third network slice may include one or more network slices. Alternatively, the third network slice may be represented by non-supported network slice selection assistance information (non-supported nsai).

With reference to the eighth aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the method further includes: and the access network equipment sends fourth indication information and a registration request message received from the terminal equipment to the first access and mobility management network element, wherein the fourth indication information is used for indicating the first access and mobility management network element to determine the identifier of the network slice allowing the terminal equipment to access according to the identifier of the first network slice.

That is to say, after receiving the registration request message sent by the terminal device, the access network device may first determine the network slice that the terminal device supports access, instead of forwarding the registration request message to the first access and mobility management network element, and then send the identifier of the network slice that the terminal device supports access and the registration request message to the first access and mobility management network element, and simultaneously instruct the first access and mobility management network element to determine the identifier of the network slice that the terminal device is allowed to access according to the identifier of the network slice that the terminal device supports access, so as to ensure that the terminal device supports access and the mobility management network element to determine the network slice.

In a ninth aspect, the present application provides a method of communication, the method comprising: a first access and mobility management network element sends an identifier of a first network slice to access network equipment located at a first position; the first access and mobility management network element receives, from the access network device, an identifier of a second network slice and third indication information, where the terminal device supports access to a radio resource corresponding to the second network slice at the first position, and the third indication information is used to indicate whether the terminal device supports simultaneous access to part or all of the second network slices; the first access and mobility management network element determines an identifier of a network slice allowing the terminal device to access according to the second network slice and the third indication information; and the first access and mobility management network element sends the identifier of the network slice allowing the terminal equipment to access to the terminal equipment.

It should be noted that the second network slice may include one or more network slices, and the second network slice may also include one or more network slices.

Optionally, the second network slice may be represented by supported network slice selection auxiliary information (supported nsai), the network slice requested to be accessed by the terminal device may be represented by requested network slice selection auxiliary information (requested nsai), and the network slice allowed to be accessed by the terminal device may be represented by allowed network slice selection auxiliary information (allowed nsai).

With reference to the ninth aspect, in a possible implementation manner, the identifier of the first network slice includes an identifier of a network slice requested to be accessed by the terminal device.

With reference to the ninth aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the method further includes: and the first access and mobility management network element sends second radio resource information to the access network device, where the second radio resource information is used to indicate radio resources corresponding to at least one network slice at the first position, and the at least one network slice includes the first network slice.

Optionally, the second radio resource information includes information of radio resources corresponding to the network slice in the requested NSSAI at the first location.

With reference to the ninth aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the method further includes: and the first access and mobility management network element receives an identifier of a third network slice from the access network device, wherein the terminal device does not support the radio resource corresponding to the third network slice accessed at the first position.

With reference to the ninth aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the method further includes: and the first access and mobility management network element receives fourth indication information and a registration request message sent by the access network device, where the fourth indication information is used to indicate, to the first access and mobility management network element, an identifier of a network slice to which the terminal device is allowed to access according to the identifier of the second network slice.

That is to say, after receiving the registration request message sent by the terminal device, the access network device may first determine the network slice that the terminal device supports access, and then send the identifier of the network slice that the terminal device supports access and the registration request message to the first access and mobility management network element, and simultaneously instruct the first access and mobility management network element to determine the identifier of the network slice that the terminal device is allowed to access according to the identifier of the network slice that the terminal device supports access, so as to ensure that the terminal device supports access and the mobility management network element to determine the network slice.

With reference to the ninth aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the method further includes: and the first access and mobility management network element determines the network slice which rejects the access of the terminal equipment.

It should be noted that the network slice that is denied the access of the terminal device may include one or more network slices. Optionally, the network slice rejected for the terminal device to access may be represented by rejected network slice selection assistance information (rejected nsai).

With reference to the ninth aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the method further includes: and the first access and mobility management network element releases a Protocol Data Unit (PDU) session corresponding to the network slice refusing the access of the terminal equipment.

In a tenth aspect, the present application provides a method of communication, the method comprising: a terminal device at a first position receives identification of a network slice deployed at the first position and information of radio resources corresponding to the network slice at the first position from an access network device; the terminal equipment determines the identifier of a first network slice which is requested to be accessed by the terminal equipment according to the identifier of the network slice and the information of the wireless resource corresponding to the network slice, and the terminal equipment supports accessing the wireless resource corresponding to the first network slice at the first position; and the terminal equipment sends a registration request message to the access network equipment, wherein the registration request message comprises the identifier of the first network slice.

In the above technical solution, the access network device sends, to the terminal device, information of radio resources corresponding to a network slice deployed at a location where the access network device is located, so that the terminal device can construct a requested NSSAI according to its air interface radio capability, thereby ensuring that radio resources corresponding to a network slice requested to be accessed by the terminal device are all supported by the air interface capability of the terminal device.

With reference to the tenth aspect, in a possible implementation manner, the receiving, by the terminal device, from an access network device, an identifier of a network slice deployed at the first location and information of radio resources corresponding to the network slice at the first location includes: and the terminal equipment receives the identification of the network slice deployed at the first position and the information of the wireless resource corresponding to the network slice at the first position from access network equipment through a broadcast message.

In an eleventh aspect, the present application provides a method of communication, the method comprising: the method comprises the steps that access network equipment sends an identifier of a network slice deployed at a first position and information of radio resources corresponding to the network slice at the first position to terminal equipment at the first position; and the access network equipment receives a registration request message from the terminal equipment, wherein the registration request message comprises an identifier of a first network slice, and the terminal equipment supports access to a wireless resource corresponding to the first network slice at the first position.

With reference to the eleventh aspect, in a possible implementation manner, the sending, by the access network device, to a terminal device at a first location, an identifier of a network slice deployed at the first location and information of radio resources corresponding to the network slice at the first location includes: and the access network equipment sends the identifier of the network slice deployed at the first position and the information of the wireless resource corresponding to the network slice at the first position to the terminal equipment through a broadcast message.

With reference to any one of the foregoing aspects or any one of the foregoing possible implementation manners, in another possible implementation manner, the radio resource includes a frequency point and/or a frequency band.

In a twelfth aspect, the present application provides a communications apparatus, comprising:

A transceiver unit, configured to acquire first radio resource information, where the first radio resource information is used to indicate that a terminal device located at a first location supports an accessed radio resource;

a processing unit, configured to determine, according to the first radio resource information and second radio resource information, an identifier of a first network slice to which the terminal device is allowed to access, where the second radio resource information is used to indicate a radio resource corresponding to a network slice deployed at the first location, and the terminal device supports accessing the radio resource corresponding to the first network slice at the first location.

Alternatively, the communication device may be an AMF or an NSSF.

Optionally, the communication apparatus may further obtain an identifier of a network slice requested to be accessed by the terminal device and information of a current location where the terminal device is located (i.e., information of the first location). The information of the first location may be a TAI where an access network device currently accessed by the terminal device is located.

It should be noted that the first network slice may include one or more network slices allowing the terminal device to access, and the network slice the terminal device requests to access may also include one or more network slices. Optionally, the first network slice allowed to be accessed by the terminal device may be represented by allowed NSSAI, and the network slice requested to be accessed by the terminal device may be represented by requested NSSAI.

In the above technical solution, when determining a network slice allowing the terminal device to access, the communication device selects a network slice under the wireless resource supported by the terminal device for access in consideration of the wireless resource supported by the terminal device and the wireless resource corresponding to the network slice deployed at the current location of the terminal device, thereby ensuring that the terminal device supports the network slice determined by the access communication device, and facilitating transmission of a terminal service.

With reference to the twelfth aspect, in a possible implementation manner, the first network slice is one or more of network slices requested to be accessed by the terminal device.

That is, the communication apparatus selects a network slice to which the terminal device is permitted to access, from among network slices to which the terminal device requests access.

With reference to the twelfth aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the transceiver unit is further configured to send an identifier of the first network slice.

Optionally, when the communication device is NSSF, the communication device sends the identifier of the first network slice to the AMF, so that the AMF further sends the identifier of the first network slice to the terminal device.

Optionally, when the communication device is an AMF, the communication device sends the identifier of the first network slice to the access network device, so that the access network device further sends the identifier of the first network slice to the terminal device.

In the above technical solution, the communication device feeds back, to the terminal device, the identifier of the network slice to which the terminal device is allowed to access, so that the terminal device can know which network slice services can be used, which is helpful for transmission of the terminal service.

With reference to the twelfth aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the processing unit is further configured to determine, according to the first radio resource information and the second radio resource information, an identifier and first information of a second network slice that the terminal device is denied access to, where the first information is used to indicate that the terminal device does not support accessing to a radio resource corresponding to the second network slice at the first location.

Optionally, the second network slice may be represented by a rejected NSSAI.

In the above technical solution, when determining the network slice rejecting the access of the terminal device, the communication apparatus considers a radio resource supported by the terminal device for access and a radio resource corresponding to the network slice deployed at the current location of the terminal device, and if the terminal device cannot support a certain network slice deployed at the current location, determines the certain network slice as the network slice rejecting the access of the terminal device (such as the second network slice). Therefore, the terminal equipment can be ensured to support the network slice determined by the access communication device, and the transmission of the terminal service is facilitated.

With reference to the twelfth aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the transceiver unit is further configured to send an identifier of the second network slice and/or the first information.

In the above technical solution, the communication device feeds back, to the terminal device, the identifier of the network slice to which the terminal device is denied access, so that the terminal device can know which network slice services cannot be used, thereby avoiding transmission of the network slice services and facilitating transmission of the terminal service.

With reference to the twelfth aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the transceiver unit is further configured to send the third radio resource information, where the third radio resource information is used to indicate a radio resource corresponding to the network slice allowed to be accessed by the terminal device at the first position.

In the above technical solution, the communication device feeds back, to the terminal device, the radio resource corresponding to the network slice at the first location, to which the terminal device is allowed to access, which is beneficial to subsequent operations of the terminal device, such as cell search, cell handover, and the like.

With reference to the twelfth aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, when the communication device is a network slice selection function network element NSSF, the transceiver unit is specifically configured to receive a first request message from a first access and mobility management function network element AMF, where the first request message includes the first radio resource information.

With reference to the twelfth aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, when the communication device is a first access and mobility management function network element AMF, the transceiver unit is specifically configured to send a second request message to an access network device, where the access network device is an access network device serving the terminal device at the first location; the first AMF receives a second response message from the access network device, the second response message including the first radio resource information.

Optionally, the first AMF may also add indication information (first indication information) in the wireless capability check request message of the terminal device, where the indication information is used to indicate that the first wireless resource information is obtained from the terminal device, so that the terminal device may only report the first wireless resource information without reporting information of other wireless capabilities, and signaling overhead may be reduced.

With reference to the twelfth aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the processing unit is further configured to trigger release of a protocol data unit, PDU, session corresponding to the second network slice.

For a mobile scene, when the terminal device moves from a second position (source position) to a first position (target position), the terminal device initiates a registration process. If the terminal device has established one or more PDU sessions at the second location and the terminal device does not support access to radio resources corresponding to the network slice corresponding to the established one or more PDU sessions at the first location, the communication device triggers release of the established one or more PDU sessions.

In the above technical solution, in a mobile scenario, the communication device determines whether to release the PDU session according to the wireless resource supported by the terminal device and the wireless resource supported by the network slice deployed at the current location of the terminal device, which is helpful for transmission of the terminal service.

With reference to the twelfth aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, when a set formed by the identifier of the first network slice is an empty set or the core network device cannot determine the identifier of the first network slice, the transceiver unit is further configured to send a registration rejection message to the access network device; and/or the processing unit is further configured to trigger a deregistration process, where the deregistration process is used to deregister the terminal device.

In the above technical solution, in a mobile scenario, the communication device determines whether a de-registration procedure for the terminal device needs to be executed according to the wireless resource supported by the terminal device and the wireless resource supported by the network slice deployed at the current location of the terminal device, so as to de-register the terminal device from the network.

In a thirteenth aspect, the present application provides a communication apparatus, comprising:

a receiving and sending unit, configured to obtain first radio resource information, where the first radio resource information is used to indicate that a terminal device located at a first location supports an accessed radio resource;

the transceiver unit is further configured to send the first radio resource information to a network slice selection function network element NSSF.

Optionally, the communication device is an AMF.

Optionally, the transceiver unit is further configured to send, to the NSSF, the network slice requested to be accessed by the terminal device and information of a current location where the terminal device is located (i.e., information of the first location). The information of the first location may be a TAI where an access network device currently accessed by the terminal device is located.

In the above technical solution, the communication device reports the radio resource supported by the terminal device for access to the NSSF, so that when the NSSF determines the network slice allowing the terminal device to access, the network slice under the radio resource supported by the terminal device can be selected in consideration of the radio resource supported by the terminal device for access, thereby ensuring that the terminal device supports access to the network slice determined by the NSSF, and facilitating transmission of a terminal service.

With reference to the thirteenth aspect, in a possible implementation manner, the transceiver unit is further configured to receive, from the NSSF, an identifier of a first network slice that the terminal device is allowed to access, where the terminal device supports accessing to a radio resource corresponding to the first network slice at the first location.

Optionally, the first network slice may be represented by an allowed NSSAI.

In the above technical solution, the NSSF sends the identifier of the network slice to which the terminal device is allowed to access to the communication device, so that the communication device can feed back the identifier of the network slice to which the terminal device is allowed to access to the terminal device, and the terminal device can know which network slice services can be used, which is beneficial to transmission of the terminal service.

With reference to the thirteenth aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the first network slice is one or more network slices requested to be accessed by the terminal device.

With reference to the thirteenth aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the transceiver unit is further configured to receive, from the NSSF, an identifier of a second network slice that the terminal device is denied access to, and/or first information, where the first information is used to indicate that the terminal device does not support accessing to a radio resource corresponding to the second network slice at the first location.

Alternatively, the second network slice may be represented by a rejected NSSAI.

In the above technical solution, the NSSF sends the identifier of the network slice that rejects the access of the terminal device to the communication device, so that the communication device can feed back the identifier of the network slice that rejects the access of the terminal device to the terminal device, and further the terminal device can know which network slice services cannot be used, thereby avoiding the transmission of the network slice services and facilitating the transmission of the terminal services.

With reference to the thirteenth aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the transceiver unit is further configured to receive third radio resource information from the NSSF, where the third radio resource information is used to indicate a radio resource corresponding to the network slice allowed to be accessed by the terminal device at the first position.

In the above technical solution, the NSSF feeds back, to the communication device, the radio resource corresponding to the network slice at the first location where the terminal device is allowed to access, so that the communication device can feed back, to the terminal device, the radio resource corresponding to the network slice at the first location where the terminal device is allowed to access, which is beneficial to subsequent operations of the terminal device, such as cell search, cell handover, and the like.

With reference to the thirteenth aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the transceiver unit is further configured to send the first information and/or the third radio resource information to the access network device.

With reference to the thirteenth aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the transceiver unit is specifically configured to send a second request message to an access network device, where the access network device is an access network device that serves the terminal device at the first location; receiving a second response message from the access network device, the second response message including the first radio resource information.

In a fourteenth aspect, the present application provides a communications apparatus, comprising:

the transceiver unit is further configured to send the first radio resource information to a first access and mobility management function network element AMF;

the transceiver unit is further configured to receive, from the first AMF, an identifier of a first network slice allowing the terminal device to access, where the terminal device supports accessing to a radio resource corresponding to the first network slice at the first location.

Optionally, the communication device is an access network device.

Optionally, the transceiver unit is further configured to send, to the first AMF, information about a network slice requested to be accessed by the terminal device and a current location where the terminal device is located (i.e., information about the first location). The information of the first location may be a TAI where an access network device currently accessed by the terminal device is located.

It should be noted that the first network slice may include one or more network slices allowing the terminal device to access, and the network slice the terminal device requests to access may also include one or more network slices.

Alternatively, the first network slice may be represented by an allowed NSSAI, and the network slice requested to be accessed by the terminal device may be represented by a requested NSSAI. It should be noted that the radio resources that the terminal device supports access may also be described as radio resource capabilities that the terminal device has. For example, the first radio resource information may be represented by a radio capability (radio capability) information element.

In the above technical solution, the communication device reports the access-supported radio resource of the terminal device to the AMF, so that when the core network device determines the network slice allowing the terminal device to access, the core network device may select the network slice under the access-supported radio resource of the terminal device in consideration of the access-supported radio resource of the terminal device and the radio resource corresponding to the network slice deployed at the current location of the terminal device, thereby ensuring that the terminal device supports the network slice determined by the access-supported core network device, and facilitating transmission of the terminal service.

With reference to the fourteenth aspect, in a possible implementation manner, the transceiver unit is further configured to receive, from the first AMF, an identifier of a second network slice that rejects access by the terminal device and/or first information, where the first information is used to indicate that the terminal device does not support access to a radio resource corresponding to the second network slice at the first location.

Optionally, the second network slice may be represented by a rejected NSSAI.

In the above technical solution, the first AMF sends the identifier of the network slice that is rejected by the terminal device to the communication device, so that the communication device can feed back the identifier of the network slice that is rejected by the terminal device to the terminal device, and further the terminal device can know which network slice services cannot be used, thereby avoiding transmission of the network slice services, and facilitating transmission of the terminal services.

With reference to the fourteenth aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the transceiver unit is further configured to receive third radio resource information from the first AMF, where the third radio resource information is used to indicate a radio resource corresponding to the network slice allowed to be accessed by the terminal device at the first position.

In the above technical solution, the first AMF feeds back, to the communication device, the radio resource corresponding to the first location of the network slice to which the terminal device is allowed to access, so that the communication device can feed back, to the terminal device, the radio resource corresponding to the first location of the network slice to which the terminal device is allowed to access, which is beneficial to subsequent operations of the terminal device, such as cell search, cell handover, and the like.

With reference to the fourteenth aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the transceiver unit is further configured to send the first information and/or the third radio resource information to the terminal device.

With reference to the fourteenth aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the transceiver unit is specifically configured to send a third request message to the terminal device; receiving a third response message from the terminal device, the third response message including the first radio resource information.

Alternatively, when the communication apparatus receives, from the first AMF, the indication information for indicating acquisition of the first radio resource information to the terminal device, the communication apparatus may add, to the terminal device capability query message, the indication information for indicating acquisition of the first radio resource information to the terminal device. Therefore, the terminal equipment can only report the first radio resource information without reporting other radio capability information, and the signaling overhead can be reduced.

In a fifteenth aspect, the present application provides a communication device, the communication device being located at a first location, the device comprising:

a transceiving unit, configured to send first radio resource information to an access network device, where the first radio resource information is used to indicate that the communication apparatus supports an accessed radio resource;

the transceiver unit is further configured to receive, from the access network device, an identification of a first network slice that the communication apparatus is allowed to access, where the communication apparatus supports access to radio resources corresponding to the first network slice at the first location.

Optionally, the communication device is a terminal device.

Optionally, the transceiving unit is further configured to send, to the access network device, the network slice requested to be accessed by the communication device and information of a location where the communication device is currently located (i.e., information of the first location). The information of the first location may be a TAI where an access network device currently accessed by the communication apparatus is located.

It should be noted that the first network slice may include one or more network slices allowing the terminal device to access, and the network slice the terminal device requests to access may also include one or more network slices. Alternatively, the first network slice may be represented by an allowed NSSAI, and the network slice requested to be accessed by the communication apparatus may be represented by a requested NSSAI.

It should be noted that the radio resources that the communication device supports access may also be described as radio resource capabilities that the communication device has. For example, the first radio resource information may be represented by a radio capability (radio capability) information element.

Optionally, the first network slice is one or more of the network slices to which the communication device requests access.

In the above technical solution, the communication device reports the radio resource supported by the communication device for access, so that when the core network device determines the network slice allowing the communication device to access, the radio resource supported by the communication device for access and the radio resource corresponding to the network slice deployed at the current location of the communication device may be considered, and the network slice under the radio resource supported by the communication device for access is selected, thereby ensuring that the communication device supports the network slice determined by the access core network device, and facilitating transmission of a terminal service.

With reference to the fifteenth aspect, in a possible implementation manner, the transceiver unit is further configured to receive, from the access network device, an identifier of a second network slice that the communication apparatus is denied access to, and/or first information, where the first information is used to indicate that the communication apparatus does not support accessing to a radio resource corresponding to the second network slice at the first location.

Optionally, the second network slice is one or more of the network slices requested to be accessed by the communication device.

Alternatively, the second network slice may be represented by a rejected NSSAI.

In the above technical solution, the communication device obtains the identifier of the network slice that the communication device is denied access to, so that the communication device can know which network slice services cannot be used, thereby avoiding transmission of the network slice services and facilitating transmission of the terminal services.

With reference to the fifteenth aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the method further includes: the communication device receives third wireless resource information from the access network equipment, wherein the third wireless resource information is used for indicating wireless resources corresponding to the network slice which is allowed to be accessed by the communication device at the first position.

In the above technical solution, the communication device obtains the radio resource corresponding to the network slice allowed to be accessed by the communication device at the first position, which is beneficial to subsequent operations of the communication device, such as cell search, cell handover, and the like.

With reference to the fifteenth aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the transceiver unit is specifically configured to receive a third request message from the access network device; sending a third response message to the access network device, the third response message including the first radio resource information.

For example, the radio resource Information that the communication device supports access may be represented by a radio Capability (radio Capability) Information element, the third request message may be a communication device Capability query message (UE Capability query), and the third response message may be a communication device Capability Information message (UE Capability Information).

Alternatively, the communication device capability query message may be a communication device capability query message.

Optionally, the communication apparatus capability query message may include indication information indicating acquisition of the first radio resource information to the communication apparatus. Therefore, the communication device can only report the first radio resource information without reporting other radio capability information, and the signaling overhead can be reduced.

In a sixteenth aspect, the present application provides a communication apparatus, comprising:

a transceiving unit, configured to receive a first message from a first access network device, where the communication apparatus is located at a first location, the first message is used to request to switch an established protocol data unit, PDU, session of a terminal device to the communication apparatus, and the first message includes first radio resource information, where the first radio resource information is used to indicate that the terminal device supports accessed radio resources;

and the processing unit is used for determining whether to allow the PDU session established by the terminal equipment to be switched to the communication device according to the first radio resource information and the radio resource corresponding to the network slice corresponding to the PDU session established by the terminal equipment at the first position.

Optionally, the communication device is an access network device.

In the above technical solution, the communication device determines whether to allow the PDU session established by the terminal device to be switched to the communication device according to the wireless resource supported by the terminal device for access and the wireless resource corresponding to the network slice corresponding to the established PDU session at the current location of the terminal, so as to ensure that the terminal device supports the network slice corresponding to the PDU session successfully switched to the communication device at the current location, which is beneficial to the transmission of the terminal service.

With reference to the sixteenth aspect, in a possible implementation manner, the transceiver unit is further configured to send a second message to a core network device, where the second message includes an identifier of a first PDU session and/or second information, the first PDU session is a PDU session that is rejected to be switched to the communication apparatus, the first PDU session belongs to a PDU session already established by the terminal device, and the second information is used to indicate that the terminal device does not support accessing to a radio resource corresponding to a network slice corresponding to the first PDU session at the first location.

With reference to the sixteenth aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the transceiver unit is further configured to send a third message to a core network device, where the third message includes an identifier of a second PDU session, the second PDU session is a PDU session that is allowed to be switched to the communication apparatus, the second PDU session belongs to a PDU session that has been established by the terminal device, and the terminal device supports accessing to a radio resource corresponding to a network slice corresponding to the second PDU session at the first location.

In a seventeenth aspect, the present application provides a communication apparatus, comprising:

A transceiving unit, configured to send a first message to a second access network device, where the second access network device is located at a first location, the first message is used to request to switch a protocol data unit PDU session established by a terminal device to the second access network device, and the first message includes first radio resource information, where the first radio resource information is used to indicate that the terminal device supports an accessed radio resource.

Optionally, the communication device is an access network device.

In the above technical solution, the communication device sends, to the second access network device, information for indicating that the terminal device supports the accessed wireless resource, so that the second access network device may consider the wireless resource that the terminal device supports to access when determining whether to allow the PDU session that the terminal device has established to be switched to the second access network device, and may ensure that the terminal device supports, at the current location, a network slice corresponding to the PDU session that is successfully switched to the second access network device, which is helpful for transmission of a terminal service.

In an eighteenth aspect, the present application provides a communication device, comprising:

a transceiver unit, configured to receive, from a second access network device, an identifier and/or second information of a first PDU session, where the second access network device is located at a first location, the first PDU session is a PDU session that is rejected to be switched to the second access network device, the first PDU session belongs to a PDU session already established by the terminal device, and the second information is used to indicate that the terminal device does not support accessing to a radio resource corresponding to a network slice corresponding to the second PDU session at the first location;

And the processing unit is used for switching the path of the PDU session according to the identifier of the first PDU session and/or the second information.

Optionally, the communication device is an AMF.

In a nineteenth aspect, the present application provides a communication apparatus, the apparatus comprising:

a transceiving unit, configured to acquire first radio resource information, second radio resource information, and an identifier of a first network slice, where the first radio resource information is used to indicate that a terminal device located at a first location supports access to radio resources, the second radio resource information is used to indicate radio resources corresponding to at least one network slice at the first location, and the at least one network slice includes the first network slice;

a processing unit, configured to determine an identifier of a second network slice according to the first radio resource information, the second radio resource information, and the identifier of the first network slice, where the terminal device supports accessing to a radio resource corresponding to the second network slice at the first location;

the transceiver unit is further configured to send the identifier of the second network slice to the first access and mobility management network element.

Optionally, the communication device is an access network device or a module or unit in the access network device.

Optionally, the information of the first location may be a TAI where an access network device currently accessed by the terminal device is located.

It should be noted that the first network slice may include one or more network slices, and the second network slice may also include one or more network slices.

In consideration that the access and mobility management network element may not be aware of the wireless capability of the terminal device in the registration procedure, in this embodiment of the present application, the access and mobility management network element may send a requested NSSAI or an allowed NSSAI to the communication device, so that the communication device may determine, according to the wireless capability of the terminal device, whether to support a wireless resource corresponding to each S-NSSAI included in the access requested NSSAI or the allowed NSSAI, and may ensure that the terminal device supports the network slice determined for the access and mobility management network element.

With reference to the nineteenth aspect, in a possible implementation manner, the identifier of the first network slice includes an identifier of a network slice requested to be accessed by the terminal device.

With reference to the nineteenth aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the transceiver unit is specifically configured to acquire the identifier of the first network slice from the first access and mobility management network element or the terminal device.

With reference to the nineteenth aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the transceiver unit is specifically configured to acquire the second radio resource information from the first access and mobility management network element, the communication device, or other access network equipment.

With reference to the nineteenth aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the transceiver unit is further configured to send third indication information to the first access and mobility management network element, where the third indication information is used to indicate whether the terminal device supports simultaneous access to part or all of the second network slices.

By the technical scheme, the communication device can indicate the terminal equipment to support the network slice accessed simultaneously to the first access and mobility management network element, which is helpful for simplifying the process that the first access and mobility management network element determines the identifier of the network slice allowed to be accessed by the terminal equipment.

With reference to the nineteenth aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the transceiver unit is further configured to send an identifier of a third network slice to the first access and mobility management network element, where the terminal device does not support accessing, at the first location, a radio resource corresponding to the third network slice.

It should be noted that the third network slice may include one or more network slices. Alternatively, the third network slice may be represented by non-supported network slice selection assistance information (non-supported NSSAI).

With reference to the nineteenth aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the transceiver unit is further configured to send fourth indication information and a registration request message received from the terminal device to the first access and mobility management network element, where the fourth indication information is used to indicate, to the first access and mobility management network element, an identifier of a network slice that the terminal device is allowed to access, where the identifier of the first network slice is determined according to the identifier of the network slice.

That is to say, after receiving the registration request message sent by the terminal device, the communication device may first determine the network slice that the terminal device supports access, and then send the identifier of the network slice that the terminal device supports access and the registration request message to the first access and mobility management network element, and simultaneously instruct the first access and mobility management network element to determine the identifier of the network slice that the terminal device is allowed to access according to the identifier of the network slice that the terminal device supports access, so as to ensure that the terminal device supports access to the network slice that the first access and mobility management network element determines for the terminal device.

In a twentieth aspect, the present application provides a communication apparatus, comprising:

a transceiving unit, configured to send an identifier of a first network slice to an access network device located at a first location;

the transceiver unit is further configured to receive, from the access network device, an identifier of a second network slice and third indication information, where the terminal device supports accessing to a radio resource corresponding to the second network slice at the first location, and the third indication information is used to indicate whether the terminal device supports accessing to part or all of the second network slices simultaneously;

A processing unit, configured to determine, according to the second network slice and the third indication information, an identifier of a network slice to which the terminal device is allowed to access;

the transceiver unit is further configured to send, to the terminal device, an identifier of the network slice that the terminal device is allowed to access.

Alternatively, the communication device may be an AMF.

By the technical scheme, the access network equipment can indicate the terminal equipment to support the network slices accessed simultaneously to the communication device, which is beneficial to simplifying the process that the communication device determines the identifier of the network slice allowed to be accessed by the terminal equipment.

With reference to the twentieth aspect, in a possible implementation manner, the identifier of the first network slice includes an identifier of a network slice requested to be accessed by the terminal device.

With reference to the twentieth aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the transceiver unit is further configured to send second radio resource information to the access network device, where the second radio resource information is used to indicate radio resources corresponding to at least one network slice at the first position, and the at least one network slice includes the first network slice.

With reference to the twentieth aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the transceiver unit is further configured to receive, from the access network device, an identifier of a third network slice, where the terminal device does not support a radio resource corresponding to the third network slice accessed at the first location.

With reference to the twentieth aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the transceiver unit is further configured to receive fourth indication information and a registration request message from the access network device, where the fourth indication information is used to indicate, to the first access and mobility management network element, an identifier of a network slice that the terminal device is allowed to access according to the identifier of the second network slice.

That is to say, after receiving the registration request message sent by the terminal device, the access network device may first determine the network slice that the terminal device supports access, but first determine the identifier of the network slice that the terminal device supports access and the registration request message, and then instruct the communication device to determine the identifier of the network slice that the terminal device is allowed to access according to the identifier of the network slice that the terminal device supports access, so as to ensure that the terminal device supports access to the network slice determined by the communication device.

With reference to the twentieth aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the processing unit is further configured to determine a network slice to which the terminal device is denied access.

It should be noted that the network slice denying the terminal device access may include one or more network slices. Optionally, the network slice rejected by the terminal device may be represented by rejected network slice selection assistance information (rejected NSSAI).

With reference to the twentieth aspect or any one of the foregoing possible implementation manners, in another possible implementation manner, the processing unit is further configured to release, by the first access and mobility management network element, a protocol data unit PDU session corresponding to the network slice to which the terminal device is denied access.

In a twenty-first aspect, the present application provides a communication apparatus, comprising:

a transceiving unit, configured to receive, from an access network device, an identifier of a network slice deployed in a first location, and information of radio resources corresponding to the network slice in the first location, where the apparatus is located;

A processing unit, configured to determine, according to the identifier of the network slice and information of the radio resource corresponding to the network slice, an identifier of a first network slice to which the terminal device requests to access, where the terminal device supports accessing the radio resource corresponding to the first network slice at the first location;

the transceiver unit is further configured to send a registration request message to the access network device, where the registration request message includes an identifier of the first network slice.

Alternatively, the communication device may be a terminal device or a module or unit in the terminal device.

In the above technical solution, the access network device sends information of radio resources corresponding to the network slice deployed at the location of the access network device to the communication apparatus, so that the communication apparatus can construct a requested NSSAI according to its air interface radio capability, thereby ensuring that the radio resources corresponding to the network slice requested to be accessed by the communication apparatus are all supported by the air interface capability of the communication apparatus.

With reference to the twenty-first aspect, in a possible implementation manner, the transceiver unit is specifically configured to receive, through a broadcast message, an identifier of a network slice deployed at the first location and information of a radio resource corresponding to the network slice at the first location from an access network device.

In a twenty-second aspect, the present application provides a communication apparatus, comprising:

a transceiving unit, configured to send, to a terminal device at a first location, an identifier of a network slice deployed at the first location and information of a radio resource corresponding to the network slice at the first location;

the transceiver unit is further configured to receive a registration request message from the terminal device, where the registration request message includes an identifier of a first network slice, and the terminal device supports access to a radio resource corresponding to the first network slice at the first location.

Alternatively, the communication device may be an access network device or a module or unit in the access network device.

In the above technical solution, the communication device sends information of the wireless resources corresponding to the network slice deployed at the location of the communication device to the terminal device, so that the terminal device can construct a requested NSSAI according to its air interface wireless capability, thereby ensuring that the wireless resources corresponding to the network slice requested to be accessed by the terminal device are all supported by the air interface capability of the terminal device.

With reference to the twenty-second aspect, in a possible implementation manner, the transceiver unit is specifically configured to send, to the terminal device through a broadcast message, an identifier of a network slice deployed at the first location and information of a radio resource corresponding to the network slice at the first location.

In a twenty-third aspect, the present application provides a communication device, which includes a processor connected to a memory, and configured to read and execute a software program stored in the memory to implement the method according to any one of the above aspects or any one of the above implementation manners.

In one possible implementation, the communication device further includes a transceiver.

In a possible implementation manner, when the communication apparatus is used to implement the method of the first aspect or any implementation manner of the first aspect, the communication apparatus is a core network device or a chip that can be applied to the core network device.

Alternatively, the core network device may be an AMF or an NSSF.

In a possible implementation manner, when the communication device is used to implement the method according to the second aspect or any implementation manner of the second aspect, the communication device is an AMF or a chip that can be applied to the AMF.

In a possible implementation manner, when the communication apparatus is used to implement the method in any one of the third aspect or the implementation manner of the third aspect, the communication apparatus is an access network device or a chip that can be applied to the access network device.

In a possible implementation manner, when the communication apparatus is used to implement the method according to any one of the implementation manners of the fourth aspect or the fourth aspect, the communication apparatus is a terminal device or a chip that can be applied to the terminal device.

In a possible implementation manner, when the communication apparatus is used to implement the method described in any one implementation manner of the fifth aspect or the fifth aspect, the communication apparatus is an access network device or a chip that can be applied to the access network device.

In a possible implementation manner, when the communication apparatus is used to implement the method described in any one implementation manner of the sixth aspect or the sixth aspect, the communication apparatus is an access network device or a chip that can be applied to the access network device.

In a possible implementation manner, when the communication device is used to implement the method in any one of the implementation manners of the seventh aspect or the seventh aspect, the communication device is an AMF or a chip that can be applied to the AMF.

In a possible implementation manner, when the communication apparatus is used to implement the method of any one implementation manner of the above-mentioned eighth aspect or eighth aspect, the communication apparatus is a terminal device or a chip that can be applied to the terminal device.

In a possible implementation manner, when the communication apparatus is used to implement the method described in any one of the implementations of the ninth aspect or the ninth aspect, the communication apparatus is an access network device or a chip that can be applied to the access network device.

In a possible implementation manner, when the communication apparatus is used to implement the method according to any one of the above-mentioned tenth aspect or the tenth aspect, the communication apparatus is a terminal device or a chip that can be applied to the terminal device.

In a possible implementation manner, when the communication apparatus is used to implement the method according to any one of the above-mentioned eleventh aspect or eleventh aspect, the communication apparatus is an access network device or a chip that can be applied to the access network device.

In a twenty-fourth aspect, the present application provides a computer program product comprising computer instructions that, when executed, cause the method in any one of the previous aspects or any one of the possible implementations to be performed.

In a twenty-fifth aspect, the present application provides a computer-readable storage medium storing computer instructions that, when executed, cause a method of any one of the foregoing aspects or any one of the possible implementations to be performed.

In a twenty-sixth aspect, the present application provides a communication system comprising any one of the communication devices of any one of the above aspects or any one of the possible implementations.

Drawings

Fig. 1 is a schematic architecture diagram of a communication system to which the present application may be applied.

Fig. 2 is another schematic architecture diagram of a communication system to which the present application may be applied.

Fig. 3 is a schematic flow chart of a communication method provided in the present application.

Fig. 4 is another schematic flow chart of a communication method provided herein.

Fig. 5 is another schematic flow chart of a communication method provided herein.

Fig. 6 is another schematic flow chart of a communication method provided herein.

Fig. 7 is another schematic flow chart of a communication method provided herein.

Fig. 8 is another schematic flow chart of a communication method provided herein.

Fig. 9 is a schematic diagram of a method for configuring second radio resource information provided in the present application.

Fig. 10 is a diagram illustrating another method for configuring second radio resource information provided herein.

Fig. 11 is another schematic flow chart of a communication method provided herein.

Fig. 12 is another schematic flow chart of a communication method provided herein.

Fig. 13 is a schematic structural diagram of a communication device provided in the present application.

Fig. 14 is another schematic structural diagram of the communication device provided in the present application.

Detailed Description

The technical solution in the present application will be described below with reference to the accompanying drawings.

The technical scheme of the embodiment of the application can be applied to various communication systems, for example: a 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, a 5G communication system or a New Radio (NR) communication system, or a future communication system, etc.

Fig. 1 is a schematic architecture diagram of a communication system to which the present application may be applied. Taking 5G network architecture as an example, the network architecture includes: a User Equipment (UE) 101, a Radio Access Network (RAN) 102, a User Plane Function (UPF) network element 103, a Data Network (DN) network element 104, an authentication server function (AUSF) network element 105, a Unified Data Repository (UDR) 113, an AMF network element 106, a Session Management Function (SMF) network element 107, an NSSF network element 112, a network open function (PCF) network element 108, a network function library (network) function (NRF) network element 109, a Policy Control Function (PCF) network element 110, a Unified Data Management (UDM) network element 111, and an Application Function (AF) network element 114. User equipment 101, radio access network equipment 102, UPF network element 103, DN network element 104, AUSF network element 105, AMF network element 106, SMF network element 107, NEF network element 108, NRF network element 109, PCF network element 110, UDM network element 111, NSSF network element 112, UDR network element 113, and AF network element 114 are hereinafter referred to simply as UE101, RAN102, UPF103, DN104, AUSF105, AMF106, SMF107, NEF108, NRF109, PCF110, UDM111, NSSF112, UDR113, and AF114, respectively.

The UE101 mainly accesses the 5G network through a wireless air interface and obtains services, and the UE101 interacts with the RAN102 through the air interface and interacts with the AMF106 of the core network through non-access stratum signaling (NAS).

The RAN102 is responsible for air interface resource scheduling and air interface connection management for the UE101 accessing the network.

The UPF103 is responsible for forwarding and receiving user data in the terminal. For example, UPF103 may receive user data from DN104 and transmit to UE101 through RAN102, and may also receive user data from UE101 through RAN102 and forward to DN104. The transmission resources and scheduling functions in the UPF103 that serve the UE101 are managed and controlled by the SMF 107.

The AUSF105 belongs to a core network control plane network element, and is mainly responsible for authentication and authorization of a user to ensure that the user is a legal user.

The AMF106 belongs to a core network and is responsible for mobility management of a user, including mobility state management, user temporary identity allocation, authentication and authorization of the user, and the AMF106 may also provide a storage resource of a control plane for a session in the UE101 under the condition of providing a service for the session, so as to store a session identifier, an identifier of the SMF107 associated with the session identifier, and the like.

The SMF107 is responsible for user plane network element selection, user plane network element redirection, internet Protocol (IP) address allocation, bearer establishment, modification and release, and QoS control.

NEF108 belongs to a core network control plane network element, and is responsible for opening mobile network capabilities to the outside, and opening network capabilities and services to the outside. NEF uses the standardized interface of UDR113 to store/retrieve structured data. The exchange information of the AF114 is translated with the exchange information of the internal network functions.

NRF109 belongs to a core network control plane network element, and is responsible for dynamic registration of service capabilities of network functions and network function discovery.

The PCF110 includes a policy control decision and a function based on flow charging control, including a user subscription data management function, a policy control function, a charging policy control function, qoS control, and the like, and mainly supports providing a unified policy framework to control network behaviors, providing policy rules to a control layer network function, and being responsible for acquiring user subscription information related to the policy decision.

The UDM111 belongs to a core network control plane network element, a home subscriber server, a unified data management network element, and is responsible for managing subscription data and notifying a corresponding network element when the subscription data is modified.

The NSSF112 is used to complete the network slice selection function for the UE 101.

The UDR113 is responsible for storing and retrieving subscription data, policy data, public architecture data, and the like; for UDM111, PCF110 and NEF to obtain relevant data; the UDR113 has to have different data access authentication mechanisms for different types of data, such as subscription data and policy data, to ensure the security of data access; the UDR is able to return a failure response carrying a suitable cause value for an illegal servicing operation or data access request.

The AF114 is responsible for providing some application layer services to the UE101, and the AF114 has requirements on quality of service QoS (policy) and charging policy (charging) and needs to inform the network when providing services to the UE 101. Meanwhile, the AF114 also needs application-related information fed back by the core network.

In the network architecture, nausf is a service-based interface presented by AUSF105, namf is a service-based interface presented by AMF106, nsmf is a service-based interface presented by SMF107, nnef is a service-based interface presented by NEF108, nrrf is a service-based interface presented by NRF109, npcf is a service-based interface presented by PCF110, nudm is a service-based interface presented by UDM111, NSSF is a service-based interface presented by NSSF112, nudr is a service-based interface presented by UDR113, and Naf is a service-based interface presented by AF 114. N1 is an interface between the UE101 and the AMF106, and N2 is an interface between the RAN102 and the AMF106, and is used for sending NAS messages, and the like; n3 is an interface between RAN102 and UPF103, and is used to transmit user plane data and the like; n4 is an interface between the SMF107 and the UPF103, and is used to transmit information such as tunnel identifier information, data cache indicator information, and downlink data notification message of the N3 connection; the N6 interface is an interface between the UPF103 and the DN104, and is used for transmitting user plane data and the like.

The UE101 in fig. 1 may be a terminal device, an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent, a user equipment, a handheld terminal, a laptop computer, a cellular phone, a smart phone, a tablet computer, a handheld device, an Augmented Reality (AR) device, a Virtual Reality (VR) device, a machine type communication terminal, or other device that can access a network. The terminal may also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with a wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal in a 5G network or a terminal device in a Public Land Mobile Network (PLMN) for future evolution, and the like, which is not limited in this embodiment of the present application. In addition, in the car networking communication, a communication terminal uploaded by a vehicle is a user equipment, and a Road Side Unit (RSU) can also be used as a user equipment. The communication terminal uploaded by the unmanned aerial vehicle can be regarded as user equipment. For convenience of description, hereinafter, collectively referred to as terminal devices.

The RAN102 in fig. 1 may be a device for communicating with user equipment, and is mainly responsible for functions of radio resource management, quality of service management, data compression, and encryption on the air interface side. The access network device may be a Transmission Reception Point (TRP), an evolved Node B (eNB or eNodeB) in an LTE system, a home base station (e.g., home evolved Node B, home Node B, HNB), a baseband unit (BBU), a radio controller in a Cloud Radio Access Network (CRAN) scenario, or the access network device may be a relay station, an access point, a vehicle-mounted device, a wearable device, an access network element in a 5G network or an access network device in a future evolved public mobile network (PLMN) network, or the access network device may be an Access Point (AP) in a WLAN, or a gNB in a new radio system (NR) system, which is not limited in this embodiment. In one network configuration, the access network device may comprise a Centralized Unit (CU) node, or a Distributed Unit (DU) node, or an access network device comprising a CU node and a DU node, or an access network device comprising a control plane CU node (CU-CP node) and a user plane CU node (CU-UP node) and a DU node. For convenience of description, hereinafter referred to collectively as access network devices.

Fig. 2 is another schematic architecture diagram of a communication system to which the present application may be applied. Fig. 2 is a schematic diagram of a 5G network architecture based on a point-to-point interface, where introduction of functions of each network element may refer to introduction of functions of a corresponding network element in fig. 1, and details are not described herein again. The main difference between fig. 2 and fig. 1 is that the interfaces between the various network elements in fig. 2 are point-to-point interfaces, rather than serviced interfaces.

It should be understood that the naming of each network element shown in fig. 1 and 2 is only one name, and the name does not limit the functionality of the network element itself. In different networks, the network elements may also be given other names, and this embodiment of the present application is not limited to this specific name. For example, in a 6G network, some or all of the above network elements may use the terminology in 5G, or may use other nomenclature, and so on, which are described herein in a unified manner and will not be described again below. Similarly, the interfaces between the network elements shown in fig. 1 and fig. 2 are only an example, and in a 5G network and other networks in the future, the interfaces between the network elements may not be the interfaces shown in the figures, which is not limited in this application. It should also be understood that the embodiments of the present application are not limited to the system architectures shown in fig. 1 and 2. For example, a communication system to which the present application may be applied may comprise more or fewer network elements or devices. The devices or network elements in fig. 1 and 2 may be hardware, or may be functionally divided software, or a combination of the two. The devices or network elements in fig. 1 and 2 may communicate with each other via other devices or network elements.

In 5G communication systems, network slices are introduced. The network slice is based on a logic concept, and is used for recombining resources, so that a plurality of logic subnets with different characteristics and isolated from each other can be virtually simulated on the same set of physical facilities to provide services for users in a targeted manner. Different logical subnets are identified and distinguished by a single network slice selection assistance information (S-NSSAI). The S-NSSAI may include a network slice/service type (SST) and a Slice Differentiation (SD), with SD being optional. Where SST is used to point to network slice specific features and traffic types, SD, in addition to SST, can further distinguish between multiple network slices that satisfy the same SST. The third generation partnership project (3 gpp) emphasizes that network slices do not affect each other, e.g. a large amount of bursty meter reading traffic should not affect normal mobile broadband traffic. In order to meet the diversity requirement and the isolation among network slices, relatively independent management and operation and maintenance among services are required, and customized service functions and analysis capability are provided. Instances of different types of services are deployed on different network slices, and different instances of the same service type may also be deployed on different network slices.

When a terminal device needs to use a network service, it first registers with the network. If the core network deploys the network slice, a network slice selection process is triggered in the registration process. In a conventional network slice selection process, a core network device selects a network slice (allowed NSSAI) to which a terminal device is allowed to access according to subscription data of the terminal device, local configuration information, a roaming agreement, a policy of an operator, and the like.

For a network slice:

1) In consideration of different performance requirements of various network slices, the radio resources (e.g., frequency points or frequency bands) corresponding to different network slices may be different. For example, as shown in table 1, the network slices S-NSSAI-1, S-NSSAI-2, and S-NSSAI-3 correspond to frequency points or frequency bands, respectively.

TABLE 1

Identification of network slices	Wireless resource corresponding to the deployment position of the network slice
		S-NSSAI-1	The frequency point is 2.6GHz; or a frequency band of n1
S-NSSAI-2	The frequency points are 2.6GHz and 4.9GHz; or frequency bands n77 and n38
		S-NSSAI-3	The frequency point is 4.9GHz; or in a frequency band n38

Wherein, n1, n77 and n38 in table 1 represent numbers corresponding to frequency bands, and the description of the numbers corresponding to the frequency bands is shown in table 2 according to the definition of the 3gpp TS 38.101 protocol.

TABLE 2

2) The wireless resources deployed in different areas may be different for the same network slice. For example, as shown in table 3, the frequency points of the network slice S-NSSAI-1 deployed in the regions corresponding to TAI-1 and TAI-2 are the same and are both F1; the frequency points of S-NSSAI-2 deployed in the areas corresponding to TAI-1 and TAI-2 are different, wherein the frequency point deployed in the area corresponding to TAI-1 is F2, and the frequency points deployed in the area corresponding to TAI-2 are all F3; the frequency points of S-NSSAI-3 deployed in all corresponding areas (TAI-1, TAI-2 \8230; TAI-10) are the same and are F3.

TABLE 3

For a terminal device: different terminal devices may support different access wireless resources (which may also be referred to as: different terminal devices may have different wireless resource capabilities), for example, a private network terminal device, the terminal device in this type has limited capabilities, and only part of frequency points or frequency bands can be accessed.

In view of the above characteristics of network slice deployment radio resources and the characteristics of the terminal device itself, since the core network device does not consider the radio resources supported by the terminal device and the radio resources supported by the slice deployed at the current location of the terminal in the conventional network slice selection process, one problem in the conventional network slice selection process is that the terminal device may not support the network slice selected by the access core network device, which is not beneficial to service transmission. It can also be understood that, in the conventional network slice selection process, the radio resource corresponding to the network slice determined by the core network device for the terminal device may be different from the radio resource supported by the terminal device, and since the terminal device itself cannot access the radio resource corresponding to the network slice selected by the core network device, the terminal device cannot access the network slice.

For example, in combination with table 3, it is assumed that the frequency points supported by the terminal device for access are F1 and F2, the subscribed network slices are S-NSSAI-1, S-NSSAI-2, and S-NSSAI-3, the terminal device is currently located in the area corresponding to TAI-1, the frequency bands corresponding to the deployed network slices S-NSSAI-1, S-NSSAI-2, and S-NSSAI-3 in the area are F1, the frequency band corresponding to S-NSSAI-2 is F2, and the frequency band corresponding to S-NSSAI-3 is F3. When the terminal equipment simultaneously requests to access network slices S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3 through F1, according to the traditional network slice selection process, the core network allows the terminal equipment to access network slices S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3, namely allowed NSSAI is S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3. However, since S-NSSAI-3 can only be accessed through F3, and the terminal device does not support accessing to the frequency band F3 corresponding to S-NSSAI-3, even if the allowed NSSAI includes S-NSSAI-3, the terminal device cannot initiate a PDU session corresponding to S-NSSAI-3, so that the terminal device cannot use the service of S-NSSAI-3, and even the terminal device may continuously try to establish the PDU session corresponding to S-NSSAI-3, which causes severe power consumption of the terminal device and affects service experience of the terminal.

In order to solve the above problems, the present application provides a communication method and apparatus, when determining a network slice allowing a terminal device to access, a core network device considers a wireless resource supported by the terminal device for access and a wireless resource corresponding to the network slice deployed at a current location of the terminal device, so as to ensure that the terminal device supports a network slice allowing the terminal device to access, which is selected by the access core network device, and thus, the transmission of a service is facilitated.

The core network device may be an AMF. For example, the AMF serving the terminal device may determine the network slice allowed to be accessed by the terminal device according to the wireless resources supported by the terminal device for access and the wireless resources corresponding to the network slice deployed at the current location of the terminal device.

Alternatively, the core network device may also be an NSSF. For example, the NSSF may determine the network slice to which the terminal device is allowed to access according to the radio resource supported by the terminal device for access and the radio resource corresponding to the network slice deployed at the current location of the terminal device.

The communication method provided by the present application may be applied to various registration scenarios, which is not specifically limited. For example, the terminal device is initially registered with the network. For another example, when the terminal device moves out of the area of the original registration, mobility registration update is performed. For another example, the terminal device performs periodic registration update and the like.

The following describes a communication method provided by the present application with reference to the drawings.

1) Determination of network slices to allow terminal device access by NSSF

Fig. 3 is a schematic flow chart of a communication method provided in an embodiment of the present application. The method shown in fig. 3 may be performed by the end device, the access network device, the AMF, and the NSSF, or may be performed by a module or unit (e.g., a circuit, a chip, or a System On Chip (SOC)) in the end device, the access network device, the AMF, and the NSSF. In fig. 3, the technical solution of the embodiment of the present application is described by taking an execution subject as a terminal device, an access network device, an AMF, and an NSSF as an example. The method illustrated in FIG. 3 may include at least some of the following.

In step 301, a terminal device at a first location initiates a registration procedure. Specifically, the terminal device sends a registration request message to the first AMF. Accordingly, the first AMF receives a registration request message from the terminal device.

Optionally, the registration request message may include an identification of the network slice to which the terminal device requests access. Optionally, when the terminal device needs to access a certain network slice or certain network slices, the registration request message includes the network slice (requested NSSAI) that the terminal device requests to access. The network slice requested to be accessed by the terminal device may be one or more network slices, and it is understood that the requested NSSAI may include one S-NSSAI or a plurality of S-NSSAIs. Illustratively, a requested NSSAI comprises S-NSSAI-1, S-NSSAI-2, and S-NSSAI-3.

The method for sending the registration request message to the first AMF by the terminal equipment is that the terminal equipment sends the registration request message to the access network equipment which is currently accessed by the terminal equipment through RRC signaling, the access network equipment sends an N2 message to the first AMF, and the N2 message carries the registration request message and the information of the first position.

Optionally, the information of the first location may be a TAI corresponding to a Tracking Area (TA) in which an access network device currently accessed by the terminal device is located. Such as TAI-1.

Alternatively, the first AMF may be an initial AMF (initial AMF) when the terminal device initially registers to the network. At this time, the first AMF may or may not have the capability of serving the network slice requested by the terminal device, and the embodiment of the present application is not limited thereto.

Alternatively, when the terminal device performs mobility registration update or periodic registration update, the first AMF may be an AMF (serving AMF) currently serving the terminal device.

The embodiment of the present application does not specifically limit the manner in which the terminal device sends the registration request message to the first AMF.

In one implementation, as shown in fig. 3, the terminal device may send a registration request message to the first AMF through the access network device, and the first AMF may receive the registration request message from the terminal device from the access network device. Specifically, the terminal device may send the registration request message to the access network device, and after receiving the registration request message from the terminal device, the access network device selects the first AMF for the terminal device according to the identifier of the network slice requested to be accessed by the terminal device, which is carried in the registration request message, and sends the registration request message from the terminal device to the selected first AMF.

In step 302, the first AMF sends, after receiving the registration request message from the terminal device, the first radio resource information, an identifier (requested NSSAI) of a network slice requested to be accessed by the terminal device, and information of the first location to the NSSF.

The first radio resource information is used to indicate the radio resource that the terminal device supports access, or the first radio resource information is used to indicate the radio resource capability that the terminal device has, for example, the first radio resource information may be represented by a radio capability (radio capability) information element. Optionally, the wireless resource in the embodiment of the present application may be one or more of a frequency point, a frequency, or a frequency band, which is not limited in the embodiment of the present application. For example, the first radio resource information may indicate one or more frequency points that the terminal device supports access, and/or one or more frequency bands that the terminal device supports access.

In addition, in step 302, the first AMF may also send network slice information (subscribed NSSAI) signed by the terminal device to the NSSF.

Accordingly, the NSSF receives the first radio resource information from the first AMF, the requested NSSAI, and the information of the first location.

In some embodiments, when the first AMF does not have the capability to serve the network slice requested by the terminal device, the first AMF sends first radio resource information to the NSSF requesting the NSSF to determine a network slice (allowed NSSAI) to which the terminal device is allowed to access.

In some embodiments, when the first AMF receives a registration request message from a terminal device, the first AMF may determine whether first radio resource information corresponding to the terminal device is stored. When the first AMF stores the first radio resource information corresponding to the terminal device, the first AMF may directly read the first radio resource information and transmit the first radio resource information to the NSSF. When the first AMF does not store the first radio resource information corresponding to the terminal device, steps 303-306 may be performed so that the first AMF acquires the first radio resource information from the terminal device.

In step 303, the first AMF sends a second request message to the access network device. The second request message is used for acquiring the first radio resource information.

Accordingly, the access network equipment receives the second request message sent by the first AMF.

Optionally, the second request message may be an N2 message.

For example, the RADIO resource information that the terminal device supports access may be represented by RADIO CAPABILITY (RADIO CAPABILITY) information element, and the second REQUEST message may be a terminal device RADIO CAPABILITY CHECK REQUEST message (UE RADIO CAPABILITY CHECK REQUEST).

Alternatively, the first AMF may acquire the first radio resource information by using a terminal device radio capability check request message.

In step 304, the access network device sends a third request message to the terminal device after receiving the second request message. The third request message is used for acquiring the first radio resource information.

Correspondingly, the terminal device receives the third request message sent by the access network device.

Alternatively, the third request message may be an RRC message.

For example, the radio resource information that the terminal device supports access may be represented by a radio Capability (radio Capability) information element, and the third request message may be a terminal device Capability query message (UE Capability query).

Also, optionally, the access network device may obtain the first radio resource information by using a terminal device capability query message. Optionally, when the access network device receives, from the first AMF, indication information for indicating to acquire the first radio resource information to the terminal device, the access network device may also add, in the terminal device capability query message, indication information (second indication information) for indicating to acquire the first radio resource information to the terminal device, so that the terminal device may report only the first radio resource information without reporting other radio capability information, and signaling overhead may be reduced.

In step 305, the terminal device sends a third response message to the access network device. The third response message is a response message of the third request message. The third response message includes the first radio resource information. Correspondingly, the access network equipment receives the third response message sent by the terminal equipment.

Alternatively, the third response message may be an RRC message.

For example, the radio resource Information that the terminal device supports access may be represented by a radio Capability (radio Capability) Information element, and the third response message may be a terminal device Capability Information message (UE Capability Information).

For example, the radio capability indicates that the frequency point information supported by the terminal device is F1 and F2.

Optionally, when the access network device may use the terminal device capability query message, the terminal device capability information message includes information about other terminal device capabilities. Alternatively, when indication information for indicating acquisition of the first radio resource information to the terminal device is included in the terminal device capability query message, the terminal device capability information message may include only the first radio resource information.

In step 306, the access network device sends a second response message to the first AMF. The second response message is a response message to the second request message. The second response message includes the first radio resource information. Correspondingly, the access network equipment receives the second response message sent by the terminal equipment.

Optionally, the second response message may be an N2 message.

For example, the RADIO resource information that the terminal device supports access may be represented by a RADIO CAPABILITY (RADIO CAPABILITY) information element, and the second Response message may be a terminal device RADIO CAPABILITY CHECK Response message (UE RADIO CAPABILITY CHECK Response).

Alternatively, when the access network device may utilize the terminal device wireless capability check request message, the terminal device wireless capability check response message may include information about other terminal device capabilities. Alternatively, when indication information for indicating acquisition of the first radio resource information to the terminal device is included in the terminal device radio capability check request message, the terminal device radio capability check response message may include only the first radio resource information.

Optionally, after receiving the first radio resource information from the access network device, the first AMF stores the first radio resource information locally.

In step 307, the NSSF determines a network slice (allowed NSSAI) to which the terminal device is allowed to access, based on the first radio resource information and the second radio resource information.

In a possible implementation, the NSSF determines, according to the first location, second radio resource information, where the second radio resource information is used to indicate radio resources corresponding to the network slice deployed at the first location (i.e., the location where the terminal device is currently located). It should be noted that the network slice deployed in the first location may include one S-NSSAI or multiple S-NSSAIs in a requested NSSAI, and the embodiment of the present application is not limited thereto. Further, the NSSF determines a network slice (allowed NSSAI) to which the terminal device is allowed to access according to the first radio resource information, the requested NSSAI, and the second radio resource information. The terminal device supports accessing the wireless resource corresponding to the network slice which allows the terminal device to access in the first position.

The set formed by the identifier of the network slice allowed to be accessed by the terminal device may be a non-null value or a null value, which is not limited in this embodiment.

a. When the set of identities of the network slices to which the terminal device is allowed to access is a non-null value, the implementation is as follows:

alternatively, the network slice to which the terminal device is allowed to access may be one or more of the network slices to which the terminal device requests access. That is, the NSSF selects a network slice to which the terminal device is allowed to access, from among network slices to which the terminal device requests access. Or, the terminal device supports accessing to the radio resources corresponding to the first location of the one or more network slices requested to be accessed by the terminal device.

Optionally, when the terminal device does not support the radio resource corresponding to the first location of any network slice requested to be accessed by the access terminal device, if the terminal device supports access to the radio resource corresponding to the first location of one or more network slices in the subscribed NSSAIs, the NSSF may use one or more of the subscribed NSSAIs as the network slice allowed to be accessed by the terminal device.

b. When the set of identifiers of the network slices allowed to be accessed by the terminal device is null, the following is implemented:

Alternatively, if the NSSF cannot determine the identifier of the network slice allowed to be accessed by the terminal device according to the first radio resource information, the requested NSSAI, and the second radio resource information, the NSSF may determine that the set of identifiers of the network slices allowed to be accessed by the terminal device is null. For example, if the terminal device does not support the radio resource corresponding to any one of the requested NSSAIs at the first location, it may be determined that the set formed by the identifiers of the network slices to which the terminal device is allowed to access is null.

Or, when the terminal device does not support the radio resource corresponding to the requested nsai or the subscribed nsai at the first location, it may be determined that the set formed by the identifier of the network slice to which the terminal device is allowed to access is a null value.

In some embodiments, the NSSF may further perform step 318, that is, the NSSF may further determine a network slice (rejected NSSAI) rejecting access by the terminal device according to the first radio resource information, the requested NSSAI, and the second radio resource information. Further optionally, the NSSF may determine the first information. Wherein the first information indicates a reject cause value for rejecting access by the terminal device. For example, the reject cause value may indicate that the terminal device does not support access to radio resources corresponding to the network slice identified by the rejected NSSAI.

For the foregoing example, the requested NSSAI includes S-NSSAI-1, S-NSSAI-2, and S-NSSAI-3, the first location is TAI-1, the first radio resource information is F1 and F2, and the NSSF determines, according to TAI-1, the second radio resource information corresponding to the network slice deployed in TAI-1 as shown in table 4 below:

TABLE 4

The network slices deployed at TAI-1 include S-NSSAI-1, S-NSSAI-2, S-NSSAI-3, S-NSSAI-4, S-NSSAI-5, and S-NSSAI-6. Further, the NSSF determines the allowed NSSAI as S-NSSAI-1 and S-NSSAI-2 according to the first wireless resource information (F1 and F2), the requested NSSAI and the second wireless resource information. Since the terminal device does not support the access F3, the rejected NSSAI is S-NSSAI-3, and the reject cause value may be indication information indicating that the terminal device does not support the access to the radio resource corresponding to S-NSSAI-3.

In another possible implementation manner, the NSSF determines, according to the first location and the requested NSSAI, radio resource information indicating that the requested NSSAI corresponds to the first location. Further, the NSSF determines a network slice (allowed NSSAI) to which the terminal device is allowed to access according to the first radio resource information and the radio resource information corresponding to the first location and indicating the requested NSSAI. The terminal equipment supports accessing the wireless resources corresponding to the network slice which is allowed to be accessed by the terminal equipment at the first position.

The set formed by the identifier of the network slice allowed to be accessed by the terminal device may be a non-null value or a null value, which is not limited in this embodiment. For specific description, reference may be made to the above description, and details are not repeated herein.

Similarly, the NSSF may also perform step 318, and for a detailed description, reference may be made to the description about step 318 above, which is not described herein again.

For the foregoing example, the requested NSSAI includes S-NSSAI-1, S-NSSAI-2 and S-NSSAI-3, the first location is TAI-1, the first radio resource information is F1 and F2, and the NSSF determines the radio resource information corresponding to the requested NSSAI at TAI-1 according to TAI-1 as shown in table 5 below:

TABLE 5

Further, the NSSF determines the allowed NSSAI to be S-NSSAI-1 and S-NSSAI-2 according to the first radio resource information (F1 and F2) and the radio resource information corresponding to the requested NSSAI in TAI-1. Since the terminal device does not support the access F3, the rejected NSSAI is S-NSSAI-3, and the reject cause value may be indication information indicating that the terminal device does not support the access to the radio resource corresponding to S-NSSAI-3.

In the embodiment of the present application, when determining the network slice allowing the terminal device to access, the NSSF considers the wireless resource supported by the terminal device to access and the wireless resource corresponding to the network slice deployed at the current location of the terminal device at the location, so that the embodiment of the present application can ensure that the terminal device supports accessing the wireless resource corresponding to the network slice allowing the terminal device to access, that is, the terminal device can ensure that the terminal device can access the network slice allowing the terminal device to access.

In this embodiment of the present application, the second radio resource information may be configured in the NSSF in advance, or may be obtained from another network element, which is not limited in this embodiment of the present application.

In some embodiments, after step 307, the NSSF may also send the terminal device an identification of the determined network slice to which the terminal device is allowed to access.

In step 308, the NSSF sends the first AMF an identifier of the network slice allowed to be accessed by the terminal device, and accordingly, the first AMF receives the identifier of the network slice allowed to be accessed by the terminal device sent by the NSSF.

a. When the set of identities of the network slices that the terminal device is allowed to access in step 308 is a non-null value, the following steps are described as follows:

optionally, when the first AMF does not have the capability of serving the terminal device (for example, the first AMF does not support the network slice allowing the terminal device to access), as shown in fig. 3, the first AMF may further perform step 309, that is, an AMF redirection procedure, to switch the terminal device to a second AMF having the capability of serving the terminal device, and send the received identifier of the network slice allowing the terminal device to access to the second AMF. The second AMF performs step 310 to send the network slice to which the terminal device is allowed to access to the access network device. Further, in step 311, the access network device sends the terminal device an identifier of the network slice allowed to be accessed by the terminal device, and accordingly, the terminal device receives the identifier of the network slice allowed to be accessed by the terminal device sent by the access network device.

Optionally, when the first AMF is capable of serving the terminal device (e.g., the first AMF supports a network slice allowing the terminal device to access), an identification of the network slice allowing the terminal device to access may be fed back to the terminal device by the first AMF. The method for the first AMF to send the identifier of the network slice allowed to be accessed by the terminal device to the terminal device is the same as that of the second AMF (not shown in fig. 3), and details are not repeated here.

Optionally, the second AMF or the first AMF may send, to the access network device, an identifier of a network slice to which the terminal device is allowed to access through a registration accept message; the access network device may send the terminal device an identification of the network slice to which the terminal device is allowed to access via a registration accept message.

In some embodiments, in case the NSSF determines a rejected network slice (rejected NSSAI) for the terminal device to access and the first information, the NSSF may further feed back to the terminal device the identity of the network slice for which the terminal device is rejected and/or the first information, i.e., perform steps 312, 313 and 314. The first information is used for indicating a reason value for rejecting the access of the terminal equipment. The first information indicates that the terminal equipment does not support the wireless resource corresponding to the network slice accessed by the access refusal terminal equipment at the first position. The specific implementation manner is similar to the manner of feeding back the identifier of the network slice to which the terminal device is allowed to access, and is not described herein again.

Optionally, the network slice to which the terminal device is denied access is one or more of the network slices to which the terminal device requests access.

In some embodiments, the NSSF may also feed back the third radio resource information to the terminal device, i.e. perform steps 315, 316 and 317. And the third radio resource information is used for indicating the radio resource corresponding to the network slice which is allowed to be accessed by the terminal equipment at the first position. For example, the third radio resource information includes F1 corresponding to S-NSSAI-1 and F2 corresponding to S-NSSAI-2. The specific implementation manner is similar to the manner of feeding back the identifier of the network slice to which the terminal device is allowed to access, and is not described herein again.

It should be noted that, in step 308, step 312 and step 315, the NSSF may send the identifier of the network slice allowed to be accessed by the terminal device, the identifier of the network slice denied to be accessed by the terminal device, and/or the first information and the third radio resource information to the first AMF in the same message or in multiple messages, which is not limited in the embodiment of the present application. Likewise, in step 310, step 313 and step 316, the second AMF may send the identifier of the network slice allowed to be accessed by the terminal device, the identifier of the network slice denied to be accessed by the terminal device, and/or the first information and the third radio resource information in the same message or in multiple messages to the terminal device through the access network device, which is not limited in the embodiment of the present application. Similarly, in step 311, step 314, and step 317, the access network device may send the identifier of the network slice allowed to be accessed by the terminal device, the identifier of the network slice refusing to be accessed by the terminal device, and/or the first information and the third radio resource information to the terminal device in the same message or in multiple messages, which is not limited in the embodiment of the present application.

In some embodiments, if the radio resource currently accessed by the terminal device is not consistent with the radio resource supported by the network slice allowing the terminal device to access, the core network device may trigger the access network device to adjust the terminal device to the suitable radio resource through a RAT/frequency selection priority (RFSP) index (index).

In the embodiment of the present application, the network slice identifier may be an S-NSSAI or other identifier that can uniquely identify one network slice. The location (for example, the location of the terminal device and the location of the access network device, etc.) referred to in the embodiments of the present application may be a TA or other information that may characterize the location, where the TA may be represented by a TAI.

b. When the set formed by the identifiers of the network slices that the terminal device is allowed to access in step 308 is a null value, the first AMF sends a registration rejection message to the terminal device, and rejects the terminal device to register in the network this time.

2) Determining, by AMF, network slices to allow terminal device access

When the first AMF is capable of serving the terminal device (e.g., the first AMF supports the network slice requested to be accessed by the terminal device, or it is understood that the network slice supported by the first AMF includes the network slice requested to be accessed by the terminal device), the network slice allowed to be accessed by the terminal device may also be determined by the first AMF. Fig. 4 is another schematic flow chart of a communication method provided in an embodiment of the present application. The method illustrated in fig. 4 may be performed by the end device, the access network device, and the AMF, or may be performed by a module or element (e.g., a circuit, a chip, or an SOC) in the end device, the access network device, and the AMF. In fig. 4, the implementation subject is taken as a terminal device, an access network device, and an AMF as examples to describe the technical solution of the embodiment of the present application. The method illustrated in fig. 4 may include at least some of the following.

In step 401, a terminal device at a first location initiates a registration procedure. Step 401 is similar to step 301 in fig. 3, and reference may be made to the description of step 301, which is not described herein again.

In step 402, if the first AMF has the capability of serving the terminal device, after receiving the registration request message from the terminal device, the first AMF may determine a network slice to which the terminal device is allowed to access according to the first radio resource information and the second radio resource information. Step 402 is similar to step 307 in fig. 3, and reference may be made to the description of step 307, which is not described herein again.

In some embodiments, when the first AMF receives the registration request message from the terminal device, the first AMF may determine whether first radio resource information corresponding to the terminal device is stored. When the first AMF stores the first radio resource information corresponding to the terminal device, the first AMF may directly read the first radio resource information. When the first AMF does not store the first radio resource information corresponding to the terminal device, steps 403-406 may be performed so that the first AMF acquires the first radio resource information from the terminal device. Steps 403-406 are similar to steps 303-306 in fig. 3, and reference may be made to the description of steps 303-306, which are not repeated herein.

Optionally, after receiving the first radio resource information from the access network device, the first AMF stores the first radio resource information locally. For example, the first AMF saves the first radio resource information in the context of the terminal device.

In some embodiments, the first AMF may obtain the second radio resource information from the access network device. Alternatively, the access network device may send, to the first AMF, the network slices deployed at the locations where the access network device is located and the radio resources supported by the network slices deployed at the locations in step 407. It should be noted that the access network device in step 407 is any access network device within the first AMF service area, including the access network device currently accessed by the terminal device.

For example, the first AMF may acquire the second radio resource information reported by the access network device in the N2 connection establishment procedure. For example, the fourth REQUEST message is an N2 connection establishment REQUEST message (N2 SETUP REQUEST), that is, the access network device may carry, in the N2 connection establishment REQUEST message, an identifier of a network slice corresponding to the location deployment of the access network device and second radio resource information corresponding to the current location of the network slice.

Optionally, after receiving the second radio resource information from the access network device, the first AMF stores the second radio resource information locally.

Optionally, in step 408, after receiving the fourth request message sent by the access network device, the first AMF may send a fourth response message to the access network device, where the fourth response message is a response message of the fourth request message.

Alternatively, the fourth RESPONSE message may be an N2 connection SETUP RESPONSE message (N2 SETUP RESPONSE).

In some embodiments, after step 402, the first AMF may further send the determined identity of the network slice allowed for access by the terminal device to the terminal device if the set of identities of the network slices allowed for access by the terminal device is a non-null value.

Optionally, sending the determined identity of the network slice to which the terminal device is allowed to access to the terminal device may be implemented by steps 409-410. In step 409, the first AMF sends the identifier of the network slice allowed to be accessed by the terminal device to the access network device, and accordingly, the access network device receives the identifier of the network slice allowed to be accessed by the terminal device sent by the first AMF. In step 410, the access network device sends the terminal device an identifier of the network slice allowing the terminal device to access, and accordingly, the terminal device receives the identifier of the network slice allowing the terminal device to access, which is sent by the access network device.

Optionally, the first AMF may send, to the access network device, an identifier of a network slice to which the terminal device is allowed to access, through the registration accept message; the access network device may send the terminal device an identification of the network slice to which the terminal device is allowed to access via a registration accept message.

Optionally, steps 415, 411, and 412 may also be performed, that is, the first AMF determines a network slice (rejected nsai) rejecting the terminal device to access according to the first radio resource information and the second radio resource information; optionally, the first AMF may also determine the first information; and the first AMF feeds back the identification and/or the first information of the network slice which is rejected to the terminal equipment. The first information is used for indicating a reason value for rejecting the access of the terminal equipment. The first information indicates that the terminal equipment does not support the wireless resource corresponding to the network slice accessed by the access refusal terminal equipment at the first position. The specific implementation manner is similar to the manner of feeding back the identifier of the network slice to which the terminal device is allowed to access, and details are not repeated here.

Optionally, steps 413-414 may also be performed, i.e. the first AMF may also feed back the third radio resource information to the terminal device. And the third radio resource information is used for indicating the radio resource corresponding to the network slice which is allowed to be accessed by the terminal equipment at the first position. For example, the third radio resource information includes F1 corresponding to S-NSSAI-1 and F2 corresponding to S-NSSAI-2. The specific implementation manner is similar to the manner of feeding back the identifier of the network slice to which the terminal device is allowed to access, and details are not repeated here.

It should be noted that, in step 409, step 411, and step 413, the first AMF may send, to the terminal device through the access network device, an identifier of a network slice that the terminal device is allowed to access, an identifier of a network slice that the terminal device is denied to access, and/or the first information and the third radio resource information in the same message or in multiple messages, which is not limited in this embodiment of the application. Similarly, in step 410, step 412 and step 414, the access network device may send, to the terminal device, the identifier of the network slice allowing the terminal device to access, the identifier of the network slice denying the terminal device to access, and/or the first information and the third radio resource information in the same message or in multiple messages, which is not limited in the embodiment of the present application

In some embodiments, if the radio resource currently accessed by the terminal device is not consistent with the radio resource supported by the network slice allowing the terminal device to access, the core network device may trigger the access network device to adjust the terminal device to the suitable radio resource through the RAT/frequency selection priority index, and the specific implementation may refer to an existing implementation.

In some embodiments, after step 402, if the set of identifiers of the network slices allowed to be accessed by the terminal device is null, the first AMF sends a registration rejection message to the terminal device, and rejects the terminal device to register in the network this time.

The following describes aspects of embodiments of the present application with reference to specific examples.

Assuming that the current position of the terminal device is TAI-1, the network slice requested to be accessed by the terminal device includes S-NSSAI-1, S-NSSAI-2, and S-NSSAI-3, where the terminal device supports access frequency points F1 and F2, and the frequency points deployed at the current position of the network slice requested to be accessed by the terminal device are shown in table 6.

TABLE 6

At this time, the first AMF may determine that the network slices to which the terminal device is allowed to access are S-NSSAI-1 and S-NSSAI-2. The first AMF returns an identification of a network slice which allows the terminal device to access, an identification of a network slice which rejects the terminal device to access (rejected NSSAI) and first information. For the example, the first AMF returns an allowed NSSAI including S-NSSAI-1 and S-NSSAI-2, the rejected NSSAI including S-NSSAI-3, and the reject cause value is that the frequency point corresponding to S-NSSAI-3 is not supported.

3)

The communication method provided by the application is also suitable for mobile scenes. In a mobile scenario, the terminal device may perform a registration update procedure. The following describes an application of the communication method provided in the present application in a mobile scenario with reference to fig. 5.

Fig. 5 is another schematic flow chart of a communication method provided herein. The method shown in fig. 5 may be performed by the terminal device, the access network device, the AMF, and the SMF, or may be performed by a module or unit (e.g., a circuit, a chip, or an SOC) in the terminal device, the access network device, the AMF, and the SMF. In fig. 5, the technical solution of the embodiment of the present application is described by taking an execution subject as a terminal device, an access network device, an AMF, and an SMF as an example. The method illustrated in fig. 5 may include at least some of the following.

In step 501, when the terminal device moves from the second location (source location) to the first location (target location), the terminal device initiates a registration process. Step 501 is similar to step 301 in fig. 3, and reference may be made to the description of step 301, which is not repeated herein.

In step 502, after receiving the registration request message from the terminal device, the first AMF may determine a network slice (allowed NSSAI) to which the terminal device is allowed to access according to the stored first radio resource information and second radio resource information. Step 502 is similar to step 307 in fig. 3, and reference may be made to the description of step 307, which is not described herein again.

Optionally, the first AMF may further perform step 513, that is, the first AMF determines a rejected network slice (rejected NSSAI) to which the terminal device is rejected, according to the stored first radio resource information and second radio resource information. Optionally, the first AMF may also determine the first information. Wherein the first information indicates a reject cause value for rejecting access by the terminal device. For example, the reject cause value may be indication information indicating that the terminal device does not support access to radio resources corresponding to the network slice identified by the rejected NSSAI. Step 513 is similar to step 318 in fig. 3, and reference may be made to the description of step 318, which is not repeated herein.

In some embodiments, when the terminal device has established one or more PDU sessions at the second location, the first AMF further performs step 503, namely triggering release of the established one or more PDU sessions, if the terminal device does not support access to the radio resources corresponding to the network slice corresponding to the established one or more PDU sessions at the first location.

For example, the terminal device has normally accessed S-NSSAI-3 at the second location and initiated a PDU session of S-NSSAI-3, after the terminal device moves to the first location, a registration procedure is initiated, and the first AMF determines, according to first radio resource information included in a context of the terminal device stored locally, that the terminal device does not support a radio resource corresponding to the first location of the access network slice S-NSSAI-3, and then the first AMF may determine, according to the context, an SMF corresponding to the PDU session of S-NSSAI-3, and send a PDU session context release message (Nsmf _ PDU _ release _ PDU context) to the SMF, to trigger release of the PDU session corresponding to S-NSSAI-3.

For a mobile scenario, the first AMF determines that the network slice allowed for access by the terminal device may be a network slice updated to allow access by the terminal device. Optionally, while updating the network slice allowing the terminal device to access, the first AMF may further determine the network slice rejecting the terminal device to access and first information, where the first information is used to indicate that the terminal device does not support accessing the radio resource corresponding to the network slice rejecting the terminal device to access at the first location. Specifically, the first AMF places an identifier of a network slice corresponding to the released PDU session in a rejected NSSAI, and generates first information.

For example, the allowed NSSAIs stored in the first AMF are S-NSSAI-1, S-NSSAI-2, and S-NSSAI-3, and when the terminal device moves from the second location to the first location, and the first AMF determines that the terminal device does not support the wireless resource corresponding to the access network slice S-NSSAI-3 at the first location through a registration procedure, the first AMF deletes the S-NSSAI-3 from the allowed NSSAI to obtain an updated allowed NSSAI, where the updated allowed NSSAI includes S-NSSAI-1 and S-NSSAI-2. Meanwhile, the first AMF puts the terminal equipment which does not support the access network slice S-NSSAI-3 into the rejected NSSAI and generates first information, wherein the first information is used for indicating that the terminal equipment does not support the wireless resource corresponding to the access network slice S-NSSAI-3.

The updated network slice allowing the terminal device to access may have the following two situations:

in case one, a set formed by identifiers of network slices allowing terminal equipment to access is a non-null value;

in case two, the set of identifiers of network slices to which the terminal device is allowed to access is null.

For case one, the first AMF may perform steps 504 to 509, that is, the first AMF sends at least one of the updated identifier of the network slice allowing the terminal device to access, the identifier of the network slice denying the terminal device to access, and the first information to the terminal device. Steps 504-509 are similar to steps 409-414 in fig. 4, and the description of steps 409-414 may be referred to, and are not repeated herein.

For case two, the first AMF may perform steps 510-512, i.e., the first AMF sends a registration reject message (registration reject) to the terminal device and initiates a de-registration procedure for the terminal device. The first AMF may not perform step 512 when the terminal device fails to register upon initial registration.

The following describes the technical solution of the present embodiment with reference to a specific example.

Example 1

The terminal device moves from the area corresponding to the TAI-1 to the area corresponding to the TAI-2, the current position of the terminal device is in the TAI-2, and the first AMF judges whether the terminal device supports the frequency point corresponding to the S-NSSAI corresponding to the established PDU session in the current position or not according to the frequency point supported by the terminal device to be accessed and the current position (namely, the TAI-2) of the terminal device. If not, the first AMF deletes the corresponding network slice identifier from the allowed NSSAI and triggers PDU session release.

For example, the current location of the terminal device is in TAI-2, the allowed NSSAI in the context stored in the first AMF includes S-NSSAI-1 and S-NSSAI-2, the frequency points supported by the terminal device for access are F1 and F2, and the network slice requested by the terminal device for access includes S-NSSAI-1 and S-NSSAI-2. In conjunction with Table 3 above, the frequency points deployed at each network slice at the current location TAI-2 are shown in Table 7.

TABLE 7

The frequency point deployed by the S-NSSAI-2 in the area corresponding to the TAI-2 is F3, the terminal device does not support the access frequency point F3, at the moment, the first AMF deletes the S-NSSAI-2 from the allowed NSSAI, the updated allowed NSSAI comprises S-NSSAI-1, the first AMF determines that the rejected NSSAI comprises S-NSSAI-2, and the rejection reason value is that the frequency point corresponding to the S-NSSAI-2 is not supported. For the example, the first AMF returns an allowed NSSAI including S-NSSAI-1, a rejected NSSAI including S-NSSAI-2, and the reject cause value is the frequency point corresponding to the non-supported S-NSSAI-2. In addition, if the terminal equipment establishes the PDU session corresponding to the S-NSSAI-2, the first AMF triggers and releases the PDU session corresponding to the S-NSSAI-2.

Example 2

The terminal device moves from the area corresponding to the TAI-1 to the area corresponding to the TAI-2, the current position of the terminal device is in the TAI-2, and the first AMF judges whether the network slice allowing the terminal device to access needs to be updated or not according to the frequency point supported by the terminal device to access and the current position (namely the TAI-2) of the terminal device.

For example, the current location of the terminal device is in TAI-2, the allowed NSSAI in the context stored in the first AMF includes S-NSSAI-2, the frequency points supported by the terminal device for access are F1 and F2, and the network slice requested by the terminal device for access includes S-NSSAI-2. In conjunction with Table 3 above, the frequency points deployed by network slice S-NSSAI-2 at the current location TAI-2 are shown in Table 8.

TABLE 8

The frequency point deployed by the S-NSSAI-2 in the area corresponding to the TAI-2 is F3, the terminal device does not support the access frequency point F3, at the moment, the first AMF deletes the S-NSSAI-2 from the allowed NSSAI, the updated allowed NSSAI is a null value, the first AMF determines that the rejected NSSAI comprises the S-NSSAI-2, and the rejection reason value is the frequency point which does not support the S-NSSAI-2. For the example, the first AMF sends a registration rejection message to the terminal device through the access network device, and initiates a de-registration process for the terminal device to de-register the terminal device from the network.

In the above embodiment, in a mobile scenario, the AMF determines, according to the wireless resource supported by the terminal device and the wireless resource supported by the network slice deployed at the current location of the terminal device, whether to release a PDU session or to register the UE, which may ensure that the terminal device supports accessing the network slice selected by the AMF and allowing the terminal device to access, and facilitate service transmission.

4)

For the terminal device in the connected state, when the terminal device moves from the second location to the first location, that is, the terminal device is switched from the source access network device to the target access network device, the target access network device needs to determine whether to allow the PDU session established by the terminal device to be switched to the target access network device.

The following describes an application of the communication method provided in the present application in a handover scenario with reference to fig. 6 and fig. 7.

Fig. 6 is another schematic flow chart of a communication method provided herein. The method shown in fig. 6 may be performed by the terminal device, the access network device, the AMF, the SMF, and the UPF, or may be performed by a module or unit (e.g., a circuit, a chip, or an SOC) in the terminal device, the access network device, the AMF, the SMF, and the UPF. In fig. 6, the technical solution of the embodiment of the present application is described by taking an execution subject as a terminal device, an access network device, an AMF, an SMF, and a UPF as an example. The method illustrated in FIG. 6 may include at least some of the following.

The first access network device in fig. 6 corresponds to the source access network device (i.e., the access network device located at the second location) and the second access network device corresponds to the target access network device (i.e., the access network device located at the first location). Fig. 6 exemplifies the access network device triggering the handover of the Xn interface.

In step 601, the terminal device moves from the second location to the first location, and triggers a handover procedure of the Xn interface.

In a possible implementation manner, when the terminal device is in a connected state, the terminal device performs related measurement according to a measurement configuration message issued by the first access network device to obtain a measurement report; the terminal device then sends the measurement report to the source access network device. The measurement report includes a candidate access network device information list (e.g., a list of candidate Target IDs) and a result of a measurement indicator between each candidate access network device and the terminal device. And the first access network equipment selects the second access network equipment from the candidate access network equipment according to the measurement report reported by the terminal equipment. Further, the first access network device determines whether an Xn interface exists between the first access network device and the second access network device, and if so, triggers a switching procedure of the Xn interface (that is, an Xn based switching procedure).

Optionally, the measurement indicator includes at least one of a Received Signal Strength Indicator (RSSI), a Reference Signal Received Power (RSRP), a Reference Signal Received Quality (RSRQ), and the like, which are obtained by the terminal device.

In some embodiments, prior to step 601, the terminal device may initiate a PDU session setup procedure to establish one or more PDU sessions for transporting traffic. In particular, steps 604-607 may be performed.

In step 604, the terminal device sends a PDU session setup request message to the first AMF. Accordingly, the first AMF receives a PDU session setup request message from the terminal device.

Optionally, the PDU session setup request message may include parameters such as a PDU session identifier, S-NSSAI, and Data Network Name (DNN).

In step 605, the core network device performs a PDU session establishment procedure.

Specifically, the first AMF determines a network slice instance according to the received S-NSSAI; further, the first AMF selects an SMF based on the S-NSSAI, the network slice instance, and the DNN; the first AMF sends the identification of the first AMF, the identification of the terminal equipment (for example, the permanent identification of the terminal equipment), the position information of the terminal equipment, the PDU session identification, the S-NSSAI, the DNN and other parameters to the selected SMF; the SMF selects an anchor UPF for the PDU session based on parameters such as S-NSSAI, network slice instance, and DNN. In step 606, the first AMF sends an N2 PDU session setup request message (N2 PDU session request) to the first access network device. Accordingly, the first access network device receives a N2 PDU session setup request message from the first AMF. Wherein, the N2 PDU session setup request message includes N2 SM information and a PDU session setup accept message. The N2 SM information may include a PDU session ID and a corresponding or associated S-NSSAI for the PDU session.

The first access network device may maintain a PDU session ID and a corresponding or associated S-NSSAI for the PDU session.

In step 607, the first access network device sends a PDU session setup accept message to the terminal device. Correspondingly, the terminal equipment receives the PDU session establishment receiving message sent by the first access network equipment, and the establishment of the PDU session is completed.

More specific PDU session establishment procedures can refer to the PDU session establishment procedures in the prior art, and are not described in detail herein.

In step 602, a first access network device sends a first message to a second access network device. Accordingly, the second access network device receives the first message from the first access network device. The first message is used for requesting to switch the PDU session established by the terminal equipment to the second access network equipment. The first message includes first radio resource information indicating radio resources for which the terminal device supports access.

Optionally, the first message is a handover request message (handover request).

Optionally, the first message further includes the target cell ID and information of the PDU session that the terminal device has established, and the like. The information of the established PDU sessions includes a network slice corresponding to each established PDU session and Qos configuration (Qos) information corresponding to each established PDU session.

In step 603, the second access network device performs admission control (admission control). Specifically, the second access network device determines whether to allow the established PDU session to be switched to the second access network device according to the first radio resource information and the radio resource corresponding to the network slice corresponding to the established PDU session at the first location.

In a possible implementation manner, if the terminal device does not support the radio resource corresponding to the network slice corresponding to a certain established PDU session at the first location, the second access network device refuses to switch the PDU session to the second access network device; if the terminal device supports the radio resource corresponding to the network slice corresponding to a certain established PDU session at the first position, the second access network device allows the PDU session to be switched to the second access network device. It will be appreciated that the second access network device determining whether to allow handover of the PDU session to the second access network device may also take into account other factors, such as requirements for corresponding admission factors.

Optionally, after determining whether to allow handover of the established PDU session to the second access network device, the second access network device may further perform step 608. I.e. the second access network device may also send a second message to the first AMF. Accordingly, the first AMF receives a second message sent by the second access network device. Wherein the second message comprises an identification of the PDU session rejecting the handover to the second access network device and/or second information. The second information is used for indicating that the terminal equipment does not support accessing the wireless resource corresponding to the network slice corresponding to the PDU session refused to be switched to the second access network equipment at the first position.

Alternatively, the second message may be a path switch request message (N2 path switch request).

Optionally, after determining whether to allow handover of the established PDU session to the second access network device, the second access network device may further perform step 609. I.e. the second access network device may also send a third message to the first AMF. Accordingly, the first AMF receives a third message sent by the second access network device. Wherein the third message includes an identification of a PDU session that allows handover to the second access network device.

Alternatively, the third message may be a path switch request message.

In step 610, the core network device performs path switching of the PDU session according to the identifier of the PDU session allowed to be switched to the second access network device and/or the identifier of the PDU session rejected to be switched to the second access network device. Specifically, the first AMF sends a PDU session update request message (Nsmf _ PDU _ update smcontext request) to the SMF, and accordingly, the SMF receives the PDU session update request message sent by the first AMF. Wherein the PDU session update request message includes an identification of a PDU session to allow handover to the second access network device and/or an identification of a PDU session to deny handover to the second access network device. The SMF initiates a PDU session modification flow to the UPF. Then, the SMF sends a PDU session update response message (Nsmf _ PDUSESION _ UpdateSMContext response) to the first AMF, and the PDU session update process is completed.

In step 611, the first AMF sends a path switch request response message (N2 path switch request ACK) message to the second access network device, and completes the path switch procedure of the PDU session.

Optionally, in step 612, the SMF initiates a PDU session release procedure for the PDU session that cannot be successfully handed over to the second access network device.

Optionally, after step 612, the terminal device may further initiate a mobility registration update procedure, in this process, the first AMF determines a network slice allowing the terminal device to access, and meanwhile, the first AMF places an identifier of a network slice corresponding to the released PDU session in a rejected NSSAI, and generates first information, where the first information is used to indicate that the terminal device does not support accessing a radio resource corresponding to the network slice that is denied for the terminal device to access, at the first location.

Fig. 7 is another schematic flow chart of a communication method provided herein. The method shown in fig. 7 is similar to the method shown in fig. 6, except that the access network device triggers a handover of the N2 interface instead of the Xn interface.

In step 701, the terminal device moves from the second location to the first location, and triggers a handover procedure of the N2 interface.

In a possible implementation manner, when the terminal device is in a connected state, the terminal device performs related measurement according to a measurement configuration message issued by the first access network device to obtain a measurement report; the terminal device then sends the measurement report to the source access network device. The measurement report includes a candidate access network device information list (e.g., a list of candidate Target IDs) and a result of a measurement indicator between each candidate access network device and the terminal device. And the first access network equipment selects the second access network equipment from the candidate access network equipment according to the measurement report reported by the terminal equipment. Further, the first access network device determines whether an Xn interface exists between the first access network device and the second access network device, and if not, triggers a switching process of the N2 interface.

Optionally, the measurement indicator includes at least one of RSSI, RSRP, RSRQ, and the like obtained by the terminal device.

In some embodiments, prior to step 701, the terminal device may initiate a PDU session setup procedure to establish one or more PDU sessions for transporting traffic. In particular, steps 704-707 may be performed. Steps 704-707 are similar to steps 604-607 in FIG. 6, and reference can be made to the description of steps 604-607, which are not repeated herein.

In step 702, a first access network device sends a first message to a second access network device. Accordingly, the second access network device receives the first message from the first access network device. The first message is used for requesting to switch the PDU session established by the terminal equipment to the second access network equipment. The first message includes first radio resource information indicating radio resources for which the terminal device supports access.

Since there is no Xn interface between the first access network device and the second access network device, as shown in fig. 7, the first access network device sends the first information to the second access network device through the first AMF and the second AMF.

Specifically, in step 702-1, the first access network device sends a first message to the first AMF. Accordingly, the first AMF receives a first message from the first access network device. The first message includes the first radio resource information, the target cell ID, and information of the PDU session established by the terminal device. The information of the established PDU sessions includes a network slice corresponding to each established PDU session and Qos configuration (Qos profile (s)) information corresponding to each established PDU session. Optionally, the first message is a handover request message. In step 702-2, the first AMF selects a second AMF based on the target cell ID. In step 702-3, the first AMF transfers the context of the terminal device to the second AMF, wherein the context of the terminal device includes the first radio resource information, the target cell ID, and the information of the PDU session established by the terminal device. In step 702-4, the second AMF selects a second access network device and sends a first message to the second access network device.

Step 703 is similar to step 603, and reference may be made to the description of step 603, which is not described herein again.

Steps 708-712 are similar to steps 608-612 and reference may be made to the description of steps 608-612. In contrast, the second access network device performs the relevant procedure of path switching.

Optionally, after step 712, the terminal device may further initiate a mobility registration update procedure, in which the first AMF determines a network slice allowing the terminal device to access, and meanwhile, the first AMF places an identifier of a network slice corresponding to the released PDU session in a rejected NSSAI, and generates first information, where the first information is used to indicate that the terminal device does not support accessing a radio resource corresponding to the network slice that is denied the terminal device to access in the first location.

In the methods shown in fig. 6 and 7, in a handover scenario, the AMF determines whether to allow the PDU session established by the terminal device to be handed over to the second access network device according to the radio resource supported by the terminal device for access and the radio resource corresponding to the network slice corresponding to the established PDU session at the current location of the terminal, so that it can be ensured that the terminal device supports the network slice selected by the access AMF and allowing the terminal device to access, and service transmission is facilitated.

5)

Fig. 8 is another schematic flowchart of a communication method provided in an embodiment of the present application. The method shown in fig. 8 may be performed by the terminal device, the access network device, the AMF, and the SMF, or may be performed by a module or unit (e.g., a circuit, a chip, or an SOC, etc.) in the terminal device, the access network device, the AMF, and the SMF. In fig. 8, the technical solution of the embodiment of the present application is described by taking an execution subject as a terminal device, an access network device, an AMF, and an SMF as an example. The method illustrated in FIG. 8 may include at least some of the following.

In step 801, a terminal device at a first location initiates a registration procedure. Specifically, the terminal device sends a registration request message to the access network device. Accordingly, the access network device receives the registration request message from the terminal device.

Optionally, the registration request message may include an identification of the network slice that the terminal device requests access to. Optionally, when the terminal device needs to access a certain network slice or certain network slices, the registration request message includes a requested NSSAI (requested NSSAI) that the terminal device requests to access. The network slice requested to be accessed by the terminal device may be one or more network slices, and it may be understood that the requested NSSAI may include one S-NSSAI or multiple S-NSSAIs.

Illustratively, the network slice to which the terminal device requests access may be shown in table 9.

TABLE 9

Requested NSSAI
	S-NSSAI-1
S-NSSAI-2
	S-NSSAI-3

Optionally, the terminal device sends an RRC signaling to the access network device, where the RRC signaling carries the registration request message.

The information of the first location may be a TAI corresponding to a Tracking Area (TA) in which an access network device currently accessed by the terminal device is located. Such as TAI-1.

In step 802, the access network device sends the received registration request message and information of the first location to the first AMF. Accordingly, the first AMF receives the registration request message sent by the access network device.

Optionally, after receiving the registration request message from the terminal device, the access network device selects a first AMF for the terminal device according to the identifier of the network slice requested to be accessed by the terminal device, which is carried in the registration request message, and sends the registration request message from the terminal device to the selected first AMF. In step 803, the first AMF sends a second request message to the access network device. Accordingly, the access network equipment receives the second request message sent by the first AMF.

Specifically, the first AMF determines the first network slice based on the identifier of the network slice requested to be accessed by the terminal device and the subscription information of the terminal device.

Optionally, if the first AMF does not determine whether the terminal device supports the radio resource corresponding to the first network slice at the first location, the first AMF sends an N2 message to the access network device, where the N2 message carries a second request message, and the second request message carries an identifier of the first network slice.

The first AMF may also decide whether to send the N2 message to the access network device based on other determination conditions, for example, before the registration procedure, the access network device sends indication information to the first AMF, and the first AMF decides to send the N2 message to the access network device based on the indication information.

The identifier of the first network slice may be an identifier of a network slice requested to be accessed by the terminal device, or an identifier of a network slice allowed to be accessed by the terminal device, or an identifier of another network slice determined by the first AMF, which is not limited in the embodiment of the present application. The first network slice may be understood as a network slice to be determined, or as a network slice to be checked whether to match the air interface capability of the terminal device.

The identifier of the network slice allowed to be accessed by the terminal device may be determined by the first AMF according to the identifier of the network slice requested to be accessed by the terminal device and subscription information of the terminal device. It can be understood that, since the first AMF does not determine whether the terminal device supports the radio resource corresponding to the first network slice at the first position, and the network slice that the terminal device is allowed to access and is determined by the first AMF in this step only considers factors such as an identifier of the network slice that the terminal device requests to access and subscription information of the terminal device, the terminal device may not support the network slice that the terminal device is allowed to access and is determined in this step.

Optionally, the second request message may further include second radio resource information, where the second radio resource information is used to indicate radio resources corresponding to the at least one network slice at the first location, and the at least one network slice includes a network slice requested to be accessed by the terminal device.

Optionally, the second radio resource information may include information of radio resources corresponding to the network slice deployed at the first location. That is, the first AMF may provide information of radio resources corresponding to the network slice deployed at the first location to the access network device.

Optionally, the second radio resource information may include information of radio resources corresponding to the first network slice at the first position. That is, the first AMF may provide information of only radio resources corresponding to a portion of the network slices deployed at the first location to the access network device. For example, the first AMF may provide, to the access network device, information of radio resources corresponding to a portion of the network slices deployed at the first location according to the network slice requested to be accessed by the terminal device, where the portion of the network slices includes at least one network slice of the network slices requested to be accessed by the terminal device. Alternatively, the first AMF may provide, to the access network device, information of radio resources corresponding to a portion of the network slices deployed at the first location according to the network slices to which the terminal device is allowed to access, where the portion of the network slices includes at least one of the network slices to which the terminal device is allowed to access.

For example, after receiving the registration request message sent by the access network device, the first AMF may determine, according to the information of the radio resource corresponding to the network slice deployed at the first location and the identifier of the first network slice, the information of the radio resource corresponding to the first network slice at the first location.

Illustratively, taking the first network slice as the identifier of the network slice requested to be accessed by the terminal device, the first AMF may determine the radio resource information shown in table 11 according to the requested NSSAI shown in table 9 and the information of the radio resource corresponding to the network slice deployed at the first location shown in table 10, where the requested NSSAI does not include S-NSSAI-4, and therefore the radio resource information corresponding to S-NSSAI-4 may not be sent to the access network device.

TABLE 10

TABLE 11

In some implementations, the second REQUEST message may be a UE RADIO CAPABILITY CHECK REQUEST message.

In some implementations, if a radio capability ID (UE radio capability ID) of the terminal device is stored in the first AMF, the second request message may further include the UE radio capability ID.

Alternatively, information of radio resources corresponding to the network slice deployed at the first location may be preconfigured in the first AMF.

Optionally, if the access network device stores information of the radio resource corresponding to the network slice deployed at the first location, the first AMF does not need to send the second radio resource information to the access network device.

There are many ways to configure the information of the radio resource corresponding to the network slice deployed in the first location for the access network device, and this embodiment of the present application is not particularly limited.

In the method 1, information of radio resources corresponding to a network slice deployed at a first position is preconfigured in the access network device.

According to the foregoing description, the information of the first location may be a TAI corresponding to a tracking area where an access network device currently accessed by the terminal device is located. Therefore, the method 1 may be understood as that the access network device pre-configures information of radio resources corresponding to a network slice of the TAI deployment where the access network device is located.

In the method 2, the access network device acquires the information of the radio resource corresponding to the network slice deployed at the first location from the second request message sent by the first AMF.

As described above, since the first AMF may obtain the information of the first location (i.e., the TAI corresponding to the tracking area where the access network device is located) from the access network device in step 801, the first AMF may send the information of the radio resource corresponding to the network slice deployed in the first location to the access network device through the second request message. The first AMF may pre-configure information of radio resources corresponding to the network slice deployed at the first location, or obtain information of radio resources corresponding to the network slice deployed at the first location from another network element, which is not limited in this embodiment of the present application.

In the method 3, the access network device may request, from the first AMF, information of radio resources corresponding to the network slice deployed at the first location in the N2 connection establishment procedure. Specifically, the access network device may send an N2 connection request message to the first AMF, where the message includes an identification of the network slice deployed at the first location, which may optionally be represented by an identification TAI of a tracking area in which the access network device is located; after receiving the N2 connection request message, the first AMF carries information of radio resources corresponding to the network slice deployed at the first location in an N2 connection response message sent to the access network device.

By the method 3, the access network device may obtain the information of the radio resource corresponding to the network slice deployed at the first location before the terminal device is registered, and the information of the radio resource corresponding to the network slice deployed at the first location may be stored on the access network device. When the terminal device registers from the access network device located at the first location, the access network device may directly read information of the radio resource corresponding to the network slice deployed at the first location from the locally stored context information.

And 4, the access network equipment and other access network equipment interactively support each other through the identification of the network slice and the wireless resource information corresponding to the network slice. For convenience of description, the access network device is referred to as a first access network device, and the other access network devices are referred to as second access network devices.

1) If an Xn interface exists between the first access network equipment and the second access network equipment

The first access network device may interact with the second access network device in an Xn interface establishment procedure, the identifier of each supported network slice and the radio resource information corresponding to the network slice.

For example, as shown in fig. 9, the first access network device sends an Xn SETUP REQUEST message (Xn SETUP REQUEST) message to the second access network device, where the Xn SETUP REQUEST message carries an identifier of a network slice supported by the first access network device and radio resource information corresponding to the network slice in the first access network device. The second access network device stores the identifier of the network slice supported by the first access network device and the radio resource information corresponding to the network slice in the first access network device. The second access network device sends an Xn SETUP RESPONSE message (Xn SETUP RESPONSE) to the first access network device, where the Xn SETUP RESPONSE message carries an identifier of a network slice supported by the second access network device and radio resource information of the network slice corresponding to the second access network device, and then the first access network device stores the identifier of the network slice supported by the second access network device and the radio resource information of the network slice corresponding to the second access network device.

Optionally, the cell where the second access network device is located and the cell where the first access network device is located may be in a neighboring cell relationship.

2) If the Xn interface does not exist between the first access network equipment and the second access network equipment

The first access network device and the second access network device may obtain, through an inter NG-RAN Configuration Transfer procedure, an identifier of a network slice supported by each of the first access network device and the second access network device and radio resource information corresponding to the network slice.

The AMF network element connected to the first access network device is a first AMF network element, the AMF network element connected to the second access network device is a second AMF network element, and the first AMF network element and the second AMF network element may be the same or different, which is not limited in this embodiment of the present application.

For example, as shown in fig. 10, by taking an example that the first AMF network element is different from the second AMF network element, the first access network device sends a Configuration Transfer message (Configuration Transfer message) to the first AMF network element, where the message includes an identifier of the first access network device, an identifier of a network slice supported by the first access network device, radio resource information corresponding to the network slice in the first access network device, and an identifier of the second access network device. The first AMF network element and the first access network device have an N2 interface connection, the identifier of the first access network device may be an address of the first access network device, and the identifier of the second access network device may be an address of the second access network device.

And the first AMF network element determines a second AMF network element according to the identifier of the second access network equipment, and sends the configuration transmission message from the first access network equipment to the second AMF network element, wherein the second AMF network element is in N2 interface connection with the second access network equipment, and the first AMF network element is in N14 interface connection with the second AMF network element.

And the second AMF network element determines second access network equipment according to the identifier of the second access network equipment and sends the configuration transmission message from the first access network equipment to the second access network equipment.

And the second access network equipment acquires the identifier of the network slice supported by the first access network equipment and the radio resource information corresponding to the network slice in the first access network equipment.

Similarly, the second access network device may send, by using the same method, the identifier of the network slice supported by the second access network device and the radio resource information of the network slice corresponding to the second access network device to the first access network device through the second AMF network element and the first AMF network element, and thus, the first access network device obtains the identifier of the network slice supported by the second access network device and the radio resource information of the network slice corresponding to the second access network device.

Referring back to fig. 8, in step 804, the access network device determines an identifier (supported nsai) of a network slice that the terminal device supports access according to the first radio resource information, the second radio resource information, and the identifier of the first network slice. The identifier of the network slice which the terminal device supports access is used for indicating that the terminal device in the first network slice supports S-NSSAI of air interface access. It is to be understood that the first network slice comprises a network slice in which the terminal device supports access, or that the network slice in which the terminal device supports access is part or all of the first network slice.

The first radio resource information is used to indicate a radio resource that the terminal device supports access, or the first radio resource information is used to indicate radio capability information that the terminal device has, for example, the first radio resource information may be represented by a radio capability (radio capability) information element.

Optionally, the radio resource in this embodiment may be one or more of a frequency point, a frequency, or a frequency band, and this embodiment is not limited in this application. For example, the first radio resource information may indicate one or more frequency points that the terminal device supports access, and/or one or more frequency bands that the terminal device supports access.

There are many ways for the access network device to obtain the first radio resource information, and this embodiment of the present application is not limited in particular.

In some implementations, if the access network device stores the first radio resource information, the access network device may locally read the first radio resource information.

For example, the access network device reads the first radio resource information according to the identifier of the terminal device.

For another example, if the access network device stores the mapping relationship between the radio capability ID of the UE and the radio capability information of the terminal device, the access network device may read the first radio resource information according to the radio capability ID of the UE, where the radio capability ID of the UE may be from the first AMF.

In other implementations, the access network device may obtain the first radio resource information from the terminal device if the access network device does not have the first radio resource information. Specifically, as shown in steps 805 and 806.

In step 805, the access network device sends a third request message to the terminal device, and accordingly, the terminal device receives the third request message sent by the access network device.

Alternatively, the third request message may be an RRC message.

Optionally, the access network device may also add indication information (second indication information) in the capability query message of the terminal device, where the indication information is used to indicate that the first radio resource information is obtained from the terminal device, so that the terminal device may only report the first radio resource information without reporting other radio capability information, and signaling overhead may be reduced.

In step 806, the terminal device sends a third response message to the access network device. The third response message is a response message of the third request message. The third response message includes the first radio resource information. Correspondingly, the access network equipment receives the third response message sent by the terminal equipment.

Alternatively, the third response message may be an RRC message.

For example, the radio capability indicates that the terminal device supports operating band-1 and operating band-2.

Alternatively, when indication information for indicating acquisition of the first radio resource information to the terminal device is included in the terminal device capability query message, the terminal device capability information message may include only the first radio resource information.

Optionally, in some embodiments, the access network device may further determine, according to the first radio resource information, the second radio resource information, and the identifier of the first network slice, that the terminal device does not support an identifier of a network slice (non-supported NSSAI) for access. The identifier (non-supported NSSAI) of the network slice that the terminal device does not support access is used to indicate that the terminal device does not support S-NSSAI of air interface access in the first network slice. It may be understood that the first network slice comprises a network slice where the terminal device does not support access, or that the network slice where the terminal device does not support access is part or all of the first network slice.

Optionally, in some embodiments, when the supported NSSAI includes multiple network slices and the radio resource information corresponding to the multiple network slices included in the supported NSSAI is different, the access network device may further determine whether the terminal device supports simultaneous access to multiple network slices in the supported NSSAI. The terminal device may simultaneously access the multiple network slices in the supported NSSAI, which may be understood as that the terminal device may simultaneously access the multiple network slices in the supported NSSAI through multiple radio resources, or that the terminal device may simultaneously establish multiple PDU sessions associated with the multiple network slices in the supported NSSAI through multiple radio resources.

For example, the access network device may determine, according to the terminal wireless capability information, that the terminal device has a Dual Connectivity (DC) capability and the terminal device supports accessing to a wireless resource corresponding to each S-NSSAI in the supported NSSAI, and then the access network device may determine which S-NSSAIs in the supported NSSAIs the terminal device may simultaneously access through the DC.

For another example, when the supported NSSAI includes 2 network slices, and the radio resource information corresponding to the 2 network slices is the operating band-1 and the operating band-2. The access network device may determine that the terminal device may simultaneously access the operating band-1 and the operating band-2 through the DC, and then the access network device may determine that the terminal device may simultaneously access the supported NSSAI through the DC.

In step 807, the access network device sends a second response message to the first AMF. Accordingly, the first AMF receives the second response message sent by the access network equipment. The second response message is a response message of the second request message. The second response message includes an identifier (supported nsai) of the network slice that the terminal device supports access. Alternatively, the second response message may be an N2 message. For example, the second Response message may be a terminal device RADIO CAPABILITY CHECK Response message (UE RADIO CAPABILITY CHECK Response).

Optionally, the second response message may further include an identifier (non-supported nsai) of a network slice that the terminal device does not support access.

Optionally, the identifier of the network slice that the terminal device does not support access may also be sent to the first AMF (Rejected NSSAI) as the network slice that the terminal device rejects access to, which is not limited in this application.

Optionally, the second response message may further carry third indication information, where the third indication information is used to indicate whether the terminal device supports simultaneous access to some or all network slices in the supported NSSAI.

It should be noted that, in the embodiment of the present application, the meaning used for indicating whether the terminal device supports simultaneous access to some or all network slices in the supported NSSAI is the same as the meaning used for indicating which S-NSSAIs the terminal device can access simultaneously. It is to be understood that the third indication information may be used to indicate whether the terminal device supports simultaneous access to some or all network slices in the supported NSSAI, and may also be used to indicate which S-NSSAIs the terminal device may simultaneously access.

Optionally, when the supported NSSAI includes a plurality of network slices, and the radio resource information corresponding to the plurality of network slices included in the supported NSSAI is different, the second response message may carry the third indication information.

As one implementation, in step 807, the access network device sends a second response message to the first AMF. The second response message may include only the third indication information indicating which S-NSSAIs the terminal device may access simultaneously.

In step 808, the first AMF determines a network slice (allowed NSSAI) that the terminal device is allowed to access. The allowed NSSAI determined in this step is not only a network slice allowing the terminal device to access, but also the terminal device can support access of the allowed NSSAI. For example, the first AMF determines an allowed NSSAI according to the supported NSSAI and subscription information of the terminal device.

For example, with reference to table 9, table 10, and table 11, assuming that the terminal device supports access to operating band-1, the supported NSSAI includes S-NSSAI-1 and S-NSSAI-2, and if it is determined that the terminal device has subscribed to S-NSSAI-1 and S-NSSAI-2 according to the subscription information of the terminal device, the first AMF determines that the allowed NSSAI includes S-NSSAI-1 and S-NSSAI-2.

Optionally, if the first AMF receives the third indication information from the access network device, the first AMF may determine an allowed NSSAI according to an identifier of a network slice (supported NSSAI) that the terminal device supports access and the third indication information. For example, the first AMF determines whether the terminal device supports simultaneous access to supported NSSAI according to the third indication information, and further determines allowed NSSAI, where at this time, the terminal device supports simultaneous access to all network slices in allowed NSSAI.

Optionally, if the first AMF receives only the third indication information from the access network device, the first AMF may determine an allowed NSSAI according to the third indication information. For example, the first AMF determines which S-NSSAIs the terminal device can simultaneously access according to the third indication information, and further determines which S-NSSAIs can be used as allowed NSSAIs.

It can be understood that the terminal device may access not only the radio resource corresponding to the network slice in the allowed NSSAI, but also simultaneously access all the network slices in the allowed NSSAI.

Optionally, the first AMF may also determine a network slice (rejected nsai) to which the terminal device is denied access.

For example, the first AMF determines a network slice (rejected NSSAI) that the terminal device is denied access to according to the identifier of the network slice that the terminal device supports access to. If the first AMF does not receive an identifier (non-supported nsai) of a network slice that the terminal device does not support access from the access network device or does not receive a network slice (Rejected nsai) that the terminal device rejects access from the access network device, the first AMF may determine the Rejected nsai according to the requested nsai and the allowed nsai, that is, may determine that the S-nsai included in the requested nsai and not included in the allowed nsai is the Rejected nsai.

For another example, if the first AMF receives an identifier (non-supported nsai) of a network slice that the terminal device does not support access from the access network device or does not receive a network slice (Rejected nsai) that the terminal device rejects access from the access network device, the first AMF may first check whether the terminal device signs a network slice that the terminal device supports access according to subscription information of the terminal device, and further, the first AMF determines a network slice (Rejected nsai) that the terminal device rejects access according to a network slice that the terminal device does not support access. The network slice determined by the AMF and refusing the access of the terminal equipment not only contains the network slice which is not signed by the terminal equipment in the supported NSSAI, but also contains the network slice which does not support the access of the terminal equipment.

Optionally, if the rejected NSSAI includes an S-NSSAI for which the terminal device currently has established a PDU session association, the first AMF may trigger the PDU session release.

Optionally, in step 811, the first AMF sends a registration accept message to the access network device and the terminal device, wherein the registration accept message may include an identification of a network slice to which the terminal device is allowed to access. Optionally, the registration accept message may include an identification of the network slice to which the terminal device is denied access. Wherein, the identifier of the network slice allowed to be accessed by the terminal device is determined by the first AMF according to the identifier of the network slice supported by the terminal device (supported NSSAI) in step 808.

Considering that the AMF may not sense the wireless capability of the terminal device in the registration process, in this embodiment of the application, the AMF may send the first network slice to the access network device, so that the access network device may determine, according to the wireless capability of the terminal device, whether to support access to a wireless resource corresponding to each S-NSSAI included in the first network slice, and send a supported NSSAI to the AMF, which may ensure that the terminal device supports access to a network slice determined by the AMF, and is beneficial to transmission of a service of the terminal device.

6)

If the access network device locally configures information of the radio resource corresponding to the network slice deployed at the location (i.e., the first location) where the access network device is located, the radio capability information of the terminal device may also be considered in the terminal device registration process through the process shown in fig. 11. Therein, information of radio resources corresponding to a network slice deployed in the first location may be configured for the access network device by referring to methods 1 to 4 in fig. 8.

Fig. 11 is another schematic flow chart of a communication method provided in an embodiment of the present application. The method shown in fig. 11 may be performed by the terminal device, the access network device, the AMF, and the SMF, or may be performed by a module or unit (e.g., a circuit, a chip, or an SOC, etc.) in the terminal device, the access network device, the AMF, and the SMF. In fig. 11, the technical solution of the embodiment of the present application is described by taking an execution subject as a terminal device, an access network device, an AMF, and an SMF as an example. The method illustrated in FIG. 11 may include at least some of the following.

In step 1101, a terminal device at a first location initiates a registration procedure. Specifically, the terminal device sends a registration request message to the access network device. Accordingly, the access network device receives the registration request message from the terminal device. Step 1101 is the same as step 801, and reference may be made to the description related to step 801, which is not described herein again.

In step 1102, since the access network device locally configures information (i.e., second radio resource information) of radio resources corresponding to the network slice deployed at the first location, the access network device may determine, directly according to the first radio resource information, the second radio resource information, and the identifier of the first network slice, an identifier (supported nsai) of the network slice that the terminal device supports accessing. The identifier of the network slice which the terminal equipment supports to access is used for indicating that the terminal equipment in the first network slice supports the S-NSSAI of the air interface access. Wherein the identification of the first network slice is the identification of the network slice that the terminal device requests to access provided in step 1101.

It is to be understood that a Requested NSSAI (i.e. the first network slice) includes a network slice for which the terminal device supports access, or that a network slice for which the terminal device supports access is part or all of a Requested NSSAI.

Optionally, the wireless resource in the embodiment of the present application may be one or more of a frequency point, a frequency, or a frequency band, which is not limited in the embodiment of the present application. For example, the first radio resource information may indicate one or more frequency points supported by the terminal device for access, and/or one or more frequency bands supported by the terminal device for access.

The manner of acquiring the first radio resource information by the access network device may refer to the related content in fig. 8, which is not described herein again.

Optionally, in some embodiments, the access network device may further determine, according to the first radio resource information, the second radio resource information, and an identifier of a network slice requested to be accessed by the terminal device, that the terminal device does not support an identifier of a network slice (non-supported nsai) that is accessed. The non-supported nsai (non-supported nsai) of the network slice that the terminal device does not support access is used to indicate that the terminal device inside the Requested nsai (i.e. the first network slice) does not support S-nsai of air interface access. It is understood that a Requested NSSAI includes a network slice where the terminal device does not support access, or that a network slice where the terminal device does not support access is part or all of a Requested NSSAI.

Optionally, in some embodiments, when the supported NSSAI includes multiple network slices and the radio resource information corresponding to the multiple network slices included in the supported NSSAI is different, the access network device may further determine whether the terminal device supports simultaneous access to the multiple network slices of the supported NSSAI. The terminal device simultaneously accesses the multiple network slices in the supported NSSAI, which may be understood as that the terminal device may simultaneously access the multiple network slices in the supported NSSAI through multiple radio resources, or that the terminal device may simultaneously establish multiple PDU sessions associated with the multiple network slices in the supported NSSAI through multiple radio resources.

In step 1105, the access network device sends a fourth message to the first AMF. Accordingly, the first AMF receives the fourth message sent by the access network equipment. The fourth message includes an identifier (supported NSSAI) of a network slice that the terminal device supports access, fourth indication information, and a registration request message received from the terminal device.

The fourth indication information is used for indicating that the first AMF determines a network slice (allowed NSSAI) allowing the terminal device to access according to an identifier (supported NSSAI) of a network slice which the terminal device supports access. It is understood that the supported NSSAI has a higher priority than the requested NSSAI, i.e., the first AMF ignores the requested NSSAI included in the registration request message and determines the allowed NSSAI with reference to the supported NSSAI.

In this embodiment, the access network device may select the first AMF according to the determined identifier of the network slice that the terminal device supports access.

Optionally, the fourth message may be an N2 message.

Optionally, the fourth message may further include an identifier (non-supported NSSAI) of a network slice that the terminal device does not support access.

Optionally, the fourth message may further carry third indication information, where the third indication information is used to indicate whether the terminal device supports simultaneous access to part or all of the network slices in the supported NSSAI.

Optionally, when the supported NSSAI includes multiple network slices and radio resource information corresponding to the multiple network slices included in the supported NSSAI is different, the fourth message may carry the third indication information.

In step 1106, the first AMF determines a network slice (allowed nsai) to which the terminal device is allowed to access according to an identifier (supported nsai) of the network slice to which the terminal device supports access. The allowed NSSAI is not only a network slice that the terminal device is allowed to access, but also the terminal device can support access to the allowed NSSAI.

For example, the first AMF determines an allowed NSSAI according to the supported NSSAI and the subscription information of the terminal equipment. For example, with reference to table 9 and table 10, assuming that the terminal device supports the access operating band-1, the supported NSSAI includes S-NSSAI-1 and S-NSSAI-2, and if it is determined that the terminal device subscribes to S-NSSAI-1 and S-NSSAI-2 according to the subscription information of the terminal device, the first AMF determines that the allowed NSSAI includes S-NSSAI-1 and S-NSSAI-2.

Optionally, if the first AMF receives the third indication information from the access network device, the first AMF may determine an allowed NSSAI according to an identifier of a network slice (supported NSSAI) that the terminal device supports access and the third indication information. For example, the first AMF determines whether the terminal device supports simultaneous access to the supported NSSAI according to the third indication information, and further determines an allowed NSSAI, where the terminal device supports simultaneous access to the allowed NSSAI.

Optionally, the first AMF may also determine a network slice (rejected NSSAI) to which the terminal device is denied access.

For another example, if the first AMF receives an identifier (non-supported nsai) of a network slice that the terminal device does not support access from the access network device or does not receive a network slice (Rejected nsai) that the terminal device rejects access from the access network device, the first AMF may first check whether the terminal device signs a network slice that the terminal device supports access according to subscription information of the terminal device, and further, the first AMF determines a network slice (Rejected nsai) that the terminal device rejects access according to a network slice that the terminal device does not support access. The network slice determined by the AMF and refusing the access of the terminal equipment not only contains the network slice which is not signed by the terminal equipment in the supported NSSAI, but also contains the network slice which does not support the access of the terminal equipment. Optionally, if the rejected NSSAI includes an S-NSSAI for which the terminal device currently has established a PDU session association, the first AMF may trigger the PDU session release.

Optionally, in step 811, the first AMF sends a registration accept message to the access network device and the terminal device, where the registration accept message may include an identification of a network slice that the terminal device is allowed to access. Optionally, the registration acceptance message may include an identification of the network slice to which the terminal device is denied access.

In the embodiment of the application, after receiving a registration request message sent by a terminal device, an access network device may first determine a network slice that the terminal device supports access, but first determine an identifier of the network slice that the terminal device supports access and the registration request message, and then send the determined identifier of the network slice that the terminal device supports access and the registration request message to the AMF, and simultaneously instruct the AMF to determine an identifier of a network slice that the terminal device is allowed to access according to the identifier of the network slice that the terminal device supports access, thereby ensuring that the terminal device supports access to the network slice determined by the AMF, and facilitating transmission of a service of the terminal device.

The application provides a communication method, in which an access network device acquires first radio resource information, second radio resource information and an identifier of a first network slice, wherein the first radio resource information is used for indicating that a terminal device located at a first position supports access to radio resources, the second radio resource information is used for indicating radio resources corresponding to at least one network slice at the first position, and the at least one network slice includes the first network slice.

In an implementation manner, the access network device obtains, from the first access and mobility management network element or the terminal device, an identifier of a network slice that the terminal device requests to access, and the specific description may refer to steps 801 to 803 or step 1101.

In an implementation manner, the access network device obtains the second radio resource information from the first access and mobility management network element, the access network device, or another access network device, and the specific description may refer to step 803 or the description in fig. 9 and fig. 10.

In this method, the access network device determines, according to the first radio resource information, the second radio resource information, and the identifier of the first network slice, an identifier of a second network slice, where the terminal device supports accessing to the radio resource corresponding to the second network slice at the first position, and the specific description may refer to step 804 or step 1102.

In the method, the access network device sends an identifier of the second network slice to a first access and mobility management network element. In some implementations, the access network device sends third indication information to the first access and mobility management network element, where the third indication information is used to indicate whether the terminal device supports simultaneous access to part or all of the second network slices. In some implementations, the access network device sends an identifier of a third network slice to the first access and mobility management network element, where the terminal device does not support accessing a radio resource corresponding to the third network slice at the first location. The detailed description may refer to step 807 or step 1105.

In the method, a first access and mobility management network element sends an identification of a first network slice to an access network device located at a first location. In some implementations, the first access and mobility management element sends, to the access network device, second radio resource information indicating radio resources corresponding to at least one network slice at the first location, where the at least one network slice includes the first network slice. The detailed description may refer to step 803.

In the method, the first access and mobility management network element receives, from the access network device, an identifier of a second network slice and third indication information, where the terminal device supports accessing to a radio resource corresponding to the second network slice at the first location, and the third indication information is used to indicate whether the terminal device supports accessing to part or all of the second network slices simultaneously. In some implementations, the first access and mobility management element receives fourth indication information and a registration request message sent by the access network device, where the fourth indication information is used to indicate, to the first access and mobility management element, an identifier of a network slice to which the terminal device is allowed to access according to the identifier of the second network slice. The specific description may refer to the description of step 807 or step 1105.

In this method, the first access and mobility management network element determines, according to the second network slice and the third indication information, an identifier of a network slice that the terminal device is allowed to access, and a specific description may refer to the description in step 808 or step 1106.

Optionally, the first access and mobility management network element determines a network slice to which the terminal device is denied access, and the specific description may refer to the description in step 809 or step 1107.

In this method, the first access and mobility management network element sends, to the terminal device, an identifier of the network slice that the terminal device is allowed to access, and a specific description may refer to the description in step 811 or step 1109.

7)

If the access network device locally configures information of radio resources corresponding to the network slice deployed at the location where the access network device is located (i.e., the first location), the radio capability information of the terminal device may also be considered in the terminal device registration process through the process shown in fig. 12. Therein, the information of the radio resources corresponding to the network slice deployed in the first location may be configured for the access network device by referring to methods 1, 3, and 4 in fig. 8.

Fig. 12 is another schematic flowchart of a communication method provided in an embodiment of the present application. The method illustrated in fig. 12 may be performed by the end device, the access network device, and the AMF, and may also be performed by a module or unit (e.g., a circuit, a chip, or an SOC, etc.) in the end device, the access network device, and the AMF. In fig. 11, the technical solution of the embodiment of the present application is described by taking an execution subject as a terminal device, an access network device, and an AMF as an example. The method illustrated in FIG. 12 may include at least some of the following.

In step 1201, the access network device sends, to the terminal device, an identifier of the network slice deployed at the first location and information of a radio resource corresponding to the network slice deployed at the first location. Correspondingly, the terminal device receives the identifier of the network slice deployed at the first position and the information of the radio resource corresponding to the network slice deployed at the first position, which are sent by the access network device.

Optionally, the access network device sends, to the terminal device through a broadcast message, an identifier of the network slice deployed in the first location and information of a radio resource corresponding to the network slice deployed in the first location.

Alternatively, the broadcast message may be an RRC message.

In step 1202, the terminal device determines, according to the first radio resource information and the information of the radio resource corresponding to the network slice deployed at the first location, an identifier of the network slice to which the terminal device requests to access.

For example, when determining the network slice to which the terminal device requests to access, the terminal device may consider the network resource (i.e., the first radio resource information) that supports access, and may also consider information of the radio resource corresponding to the network slice deployed at the first location (e.g., the current location of the terminal device). If the terminal device does not support the network resource accessed to a certain network slice, or if the wireless resource corresponding to the network slice at the current position is inconsistent with the network resource supported by the terminal device, the terminal device does not use the network slice as the network slice requested to be accessed by the terminal device. In other words, the network slice to which the terminal device requests access does not include the network slice.

And the terminal equipment supports accessing the wireless resources corresponding to the network slice requested to be accessed at the first position.

The first radio resource information is used for indicating the radio resource which the terminal device supports to access, or the first radio resource information is used for indicating the radio capability information which the terminal device has.

Optionally, the radio resource in this embodiment may be one or more of a frequency point, a frequency, or a frequency band, and this embodiment is not limited in this application. For example, the first radio resource information may indicate one or more frequency points supported by the terminal device for access, and/or one or more frequency bands supported by the terminal device for access.

In step 1203, the terminal device normally initiates a registration request procedure by sending a registration request message to the access network device, and registers in the network. The registration request message includes the identifier of the network slice requested to be accessed by the terminal device determined by the method.

In this embodiment of the present application, the access network device sends, to the terminal device, information of a radio resource corresponding to a network slice deployed at a location where the access network device is located, so that the terminal device can construct a requested NSSAI according to an air interface radio capability of the terminal device, thereby ensuring that radio resources corresponding to a network slice requested to be accessed by the terminal device are all supported by the air interface capability of the terminal device.

The above embodiments may be implemented individually or in combination as appropriate.

It should be further noted that the identifier of the network slice in the above embodiments may be S-NSSAI or other identifiers that can uniquely identify one network slice. The location (for example, the location of the terminal device and the location of the access network device, etc.) referred to in the embodiments of the present application may be a TA or other information that may characterize the location, where the TA may be represented by a TAI.

It is understood that, in order to implement the functions of the above embodiments, the communication device includes a corresponding hardware structure and/or software modules for performing the respective functions. Those of skill in the art will readily appreciate that the various illustrative elements and method steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is performed as hardware or computer software driven hardware depends on the particular application scenario and design constraints imposed on the solution.

Fig. 13 to 14 are schematic structural diagrams of possible apparatuses provided in the embodiments of the present application.

The apparatuses may be configured to implement the functions of the terminal device, the access network device, the AMF, or the NSSF in the foregoing method embodiment, and therefore, the advantageous effects of the foregoing method embodiment can also be achieved. In the embodiment of the present application, the communication device may be an end device, an access network device, an AMF, or an NSSF, and may also be a module (e.g., a chip) applied to the end device, the access network device, the AMF, or the NSSF.

As shown in fig. 13, the apparatus 800 includes a processing unit 810 and a transceiving unit 820. The apparatus 800 is configured to implement the functions of the terminal device, the access network device, the AMF, or the NSSF in any of the method embodiments shown in fig. 3 to fig. 7.

When the apparatus 800 is used to implement the functions of the terminal device in the method embodiment shown in fig. 3: the transceiving unit 820 may perform steps 301, 304, 305, 311, 314 and 317 as shown in the method side embodiment. When the apparatus 800 is used to implement the functions of the access network device in the method embodiment shown in fig. 3: the transceiving unit 820 may perform steps 301, 303, 306, 310, 313 and 316 as shown in the method side embodiment. When the apparatus 800 is used to implement the functionality of the first AMF in the method embodiment shown in fig. 3: the processing unit 810 may perform step 309 as shown in the method-side embodiment, and the transceiving unit 820 may perform steps 301 to 303, 306, 308, 312, 315, 310, 313 and 316 as shown in the method-side embodiment. When the apparatus 800 is used to implement the functionality of the second AMF in the method embodiment shown in fig. 3: the processing unit 810 may perform step 309 shown in the method-side embodiment, and the transceiving unit 820 may perform steps 310, 313, 4, and 316 shown in the method-side embodiment. When the apparatus 800 is used to implement the functionality of NSSF in the method embodiment shown in fig. 3: the processing unit 810 may perform steps 307 and 318 shown in the method side embodiment, and the transceiving unit 820 may perform steps 302, 308, 312 and 315 shown in the method side embodiment.

When the apparatus 800 is used to implement the functions of the terminal device in the method embodiment shown in fig. 4: the transceiving unit 820 may perform steps 401, 404, 405, 410, 412 and 414 as shown in the method side embodiments. When the apparatus 800 is used to implement the functions of the access network device in the method embodiment shown in fig. 4: the transceiving unit 820 may perform steps 401 and 403-412 as shown in the method side embodiment. When the apparatus 800 is used to implement the functionality of the first AMF in the method embodiment shown in fig. 4: the processing unit 810 may perform steps 402 and 415 shown in the method-side embodiment, and the transceiving unit 820 may perform steps 403, 406, 407, 408, 409, 411, and 413 shown in the method-side embodiment.

When the apparatus 800 is used to implement the functions of the terminal device in the method embodiment shown in fig. 5: the processing unit 810 may perform step 512 shown in the method-side embodiment, and the transceiving unit 820 may perform steps 501, 505, 507, 509, and 511 shown in the method-side embodiment. When the apparatus 800 is used to implement the functions of the access network device in the method embodiment shown in fig. 5: the processing unit 810 may perform step 512 shown in the method-side embodiment, and the transceiving unit 820 may perform steps 501 and 504-511 shown in the method-side embodiment. When the apparatus 800 is used to implement the functionality of the first AMF in the method embodiment shown in fig. 5: the processing unit 810 may perform steps 502, 503 and 513 shown in the method side embodiment, and the transceiving unit 820 may perform steps 501, 504, 506, 508 and 510 shown in the method side embodiment. When the apparatus 800 is used to implement the functionality of the SMF in the method embodiment shown in fig. 5: processing unit 810 may perform steps 503 and 512 shown in the method side embodiment.

When the apparatus 800 is used to implement the functions of the terminal device in the method embodiment shown in fig. 6: the processing unit 810 may perform steps 601 and 612 shown in the method side embodiment, and the transceiving unit 820 may perform steps 604 and 607 shown in the method side embodiment. When the apparatus 800 is used to implement the function of the first access network device in the method embodiment shown in fig. 6: the processing unit 810 may perform steps 601 and 612 shown in the method-side embodiment, and the transceiving unit 820 may perform steps 604, 606, 607, and 602 shown in the method-side embodiment. When the apparatus 800 is used to implement the function of the second access network device in the method embodiment shown in fig. 6: the processing unit 810 may perform steps 603 and 612 shown in the method-side embodiment, and the transceiver 820 may perform steps 602, 608, 609, and 611 shown in the method-side embodiment. When the apparatus 800 is used to implement the functionality of the first AMF in the method embodiment shown in fig. 6: the processing unit 810 may perform step 612 shown in the method-side embodiment, and the transceiver 820 may perform steps 604-606 and 608-611 shown in the method-side embodiment. When the apparatus 800 is used to implement the functionality of the SMF in the method embodiment shown in fig. 6: the processing unit 810 may perform step 612 shown in the method-side embodiment, and the transceiving unit 820 may perform steps 605 and 610 shown in the method-side embodiment. When the apparatus 800 is used to implement the functions of UPF in the method embodiment shown in fig. 6: the processing unit 810 may perform step 612 shown in the method-side embodiment, and the transceiving unit 820 may perform steps 605 and 610 shown in the method-side embodiment.

When the apparatus 800 is used to implement the functions of the terminal device in the method embodiment shown in fig. 7: the processing unit 810 may perform steps 701 and 712 shown in the method side embodiment, and the transceiving unit 820 may perform steps 704 and 707 shown in the method side embodiment. When the apparatus 800 is used to implement the function of the first access network device in the method embodiment shown in fig. 7: the processing unit 810 may perform steps 701 and 712 shown in the method side embodiment, and the transceiving unit 820 may perform steps 704, 706, 707, and 702-1 shown in the method side embodiment. When the apparatus 800 is used to implement the function of the second access network device in the method embodiment shown in fig. 7: the processing unit 810 may perform steps 703 and 712 shown in the method side embodiment, and the transceiving unit 820 may perform steps 702-4, 708, 709, and 711 shown in the method side embodiment. When the apparatus 800 is used to implement the functionality of the first AMF in the method embodiment shown in fig. 7: the processing unit 810 may perform steps 702-2 and 712 shown in the method side embodiment and the transceiving unit 820 may perform steps 704, 705, 706, 702-1 and 702-3 shown in the method side embodiment. When the apparatus 800 is used to implement the functionality of the second AMF in the method embodiment shown in fig. 7: the processing unit 810 may perform step 712 shown in the method side embodiment and the transceiving unit 820 may perform steps 702-3, 702-4 and 708-711 shown in the method side embodiment. When the apparatus 800 is used to implement the functionality of the SMF in the method embodiment shown in fig. 7: the processing unit 810 may perform step 712 shown in the method-side embodiment, and the transceiving unit 820 may perform steps 705 and 710 shown in the method-side embodiment. When the apparatus 800 is used to implement the functions of the UPF in the method embodiment shown in fig. 7: the processing unit 810 may perform step 612 shown in the method-side embodiment, and the transceiving unit 820 may perform steps 705 and 710 shown in the method-side embodiment.

When the apparatus 800 is used to implement the functions of the terminal device in the method embodiment shown in fig. 8: the transceiving unit 820 may perform steps 801, 805, 806 and 811 as shown in the method side embodiment. When the apparatus 800 is used to implement the functions of the access network device in the method embodiment shown in fig. 8: the processing unit 810 may perform step 804 shown in the method side embodiment, and the transceiving unit 820 may perform steps 801, 802, 803, 805, 806, 807 and 811 shown in the method side embodiment. When the apparatus 800 is used to implement the functionality of the first AMF in the method embodiment shown in fig. 8: the processing unit 810 may perform steps 808-810 shown in the method side embodiment and the transceiving unit 820 may perform steps 802, 803, 807 and 811 shown in the method side embodiment. When the apparatus 800 is used to implement the functionality of the SMF in the method embodiment shown in fig. 8: processing unit 810 may perform step 810 as shown in the method-side embodiment.

When the apparatus 800 is used to implement the functions of the terminal device in the method embodiment shown in fig. 11: the transceiving unit 820 may perform steps 1101, 1103, 1104 and 1109 shown in the method side embodiment. When the apparatus 800 is used to implement the functions of the access network device in the method embodiment shown in fig. 11: the processing unit 810 may perform step 1102 shown in the method side embodiment, and the transceiving unit 820 may perform steps 1101, 1103-1105 and 1109 shown in the method side embodiment. When the apparatus 800 is used to implement the functionality of the first AMF in the method embodiment shown in fig. 11: the processing unit 810 may perform steps 1106 to 1108 shown in the method side embodiment, and the transceiving unit 820 may perform steps 1105 and 1109 shown in the method side embodiment. When the apparatus 800 is used to implement the functionality of the SMF in the method embodiment shown in fig. 11: processing unit 810 may perform step 1108 shown in the method-side embodiments.

When the apparatus 800 is used to implement the functions of the terminal device in the method embodiment shown in fig. 12: the transceiving unit 820 may perform steps 1201 and 1203 as shown in the method side embodiment. When the apparatus 800 is used to implement the functions of the access network device in the method embodiment shown in fig. 12: the transceiving unit 820 may perform steps 1201 and 1203 as shown in the method side embodiment. When the apparatus 800 is used to implement the functionality of the first AMF in the method embodiment shown in fig. 12: the transceiving unit 820 may perform step 1203 as shown in the method side embodiment.

More detailed descriptions about the processing unit 810 and the transceiver 820 can be directly obtained by referring to the related descriptions in the method embodiments shown in fig. 3-12, which are not repeated herein.

As shown in fig. 14, the apparatus 900 includes a processor 910 and an interface circuit 920. The processor 910 and the interface circuit 920 are coupled to each other. It is understood that the interface circuit 920 may be a transceiver or an input-output interface. Optionally, the apparatus 900 may further include a memory 930 for storing instructions to be executed by the processor 910 or for storing input data required by the processor 910 to execute the instructions or for storing data generated by the processor 910 after executing the instructions.

When the apparatus 900 is configured to implement the methods shown in fig. 3-12, the processor 910 is configured to perform the functions of the processing unit 910, and the interface circuit 920 is configured to perform the functions of the transceiver 920.

When the device is a chip applied to a terminal device, the terminal device chip implements the functions of the terminal device in the method embodiment. The terminal device chip receives information from other modules (such as a radio frequency module or an antenna) in the terminal device, and the information is sent to the terminal device by the other devices; or, the terminal device chip sends information to other modules (such as a radio frequency module or an antenna) in the terminal device, where the information is sent by the terminal device to other devices.

When the device is a chip applied to the access network equipment, the access network equipment chip realizes the functions of the access network equipment in the embodiment of the method. The access network device chip receives information from other modules (such as a radio frequency module or an antenna) in the access network device, and the information is sent to the access network device by the other devices; alternatively, the access network device chip sends information to other modules (such as a radio frequency module or an antenna) in the access network device, where the information is sent by the access network device to other devices.

When the device is a chip applied to the AMF, the AMF chip implements the functions of the AMF in the above method embodiments. The AMF chip receives information from other modules (such as radio frequency modules or antennas) in the AMF, and the information is sent to the AMF by other devices; alternatively, the AMF chip may send information to other modules (e.g., radio frequency modules or antennas) in the AMF, which the AMF sends to other devices.

When the device is a chip applied to NSSF, the NSSF chip implements the function of NSSF in the above method embodiments. The NSSF chip receives information from other modules (such as a radio frequency module or an antenna) in the NSSF, and the information is sent to the NSSF by other equipment; alternatively, the NSSF chip sends information to other modules (such as a radio frequency module or an antenna) in the NSSF, and the information is sent by the NSSF to other devices.

It is understood that the Processor in the embodiments of the present Application may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, a transistor logic device, a hardware component, or any combination thereof. The general purpose processor may be a microprocessor, but may be any conventional processor.

The method steps in the embodiments of the present application may be implemented by hardware, or may be implemented by software instructions executed by a processor. The software instructions may be comprised of corresponding software modules that may be stored in Random Access Memory (RAM), flash Memory, read-Only Memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically Erasable PROM (EEPROM), registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be integral to the processor. The processor and the storage medium may reside in an ASIC. In addition, the ASIC may reside in a terminal device, an access network device, an AMF, or an NSSF. Of course, the processor and the storage medium may reside as discrete components in the terminal device, access network device, AMF, or NSSF.

In the above embodiments, all or part of the implementation may be realized by software, hardware, firmware, or any combination thereof. When implemented in software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are performed in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer program or instructions may be stored in or transmitted over a computer-readable storage medium. The computer readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server that integrates one or more available media. The usable medium may be a magnetic medium, such as a floppy disk, hard disk, magnetic tape; or an optical medium, such as a DVD; it may also be a semiconductor medium, such as a Solid State Disk (SSD).

In the embodiments of the present application, unless otherwise specified or conflicting with respect to logic, the terms and/or descriptions in different embodiments have consistency and may be mutually cited, and technical features in different embodiments may be combined to form a new embodiment according to their inherent logic relationship.

In the present application, "at least one" means one or more, "a plurality" means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone, wherein A and B can be singular or plural. In the description of the text of the present application, the character "/" generally indicates that the former and latter associated objects are in an "or" relationship; in the formula of the present application, the character "/" indicates that the preceding and following related objects are in a relationship of "division".

It is to be understood that the various numerical references referred to in the embodiments of the present application are merely for convenience of description and distinction and are not intended to limit the scope of the embodiments of the present application. The sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of the processes should be determined by their functions and inherent logic.

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 there may be other divisions when actually implementing, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not implemented. 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 position, or may be distributed on multiple 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: a U-disk, a portable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, an optical disk, or other various media capable of storing program codes.

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 think 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

1. A method of communication, the method comprising:

the method comprises the steps that core network equipment acquires first wireless resource information, wherein the first wireless resource information is used for indicating that terminal equipment located at a first position supports accessed wireless resources;

and the core network device determines, according to the first radio resource information and second radio resource information, an identifier of a first network slice allowing the terminal device to access, where the second radio resource information is used to indicate a radio resource corresponding to a network slice deployed at the first location, and the terminal device supports accessing to the radio resource corresponding to the first network slice at the first location.

2. The method of claim 1, further comprising:

and the core network equipment sends an identifier and/or first information of a second network slice refusing the access of the terminal equipment, wherein the first information is used for indicating that the terminal equipment does not support the access of wireless resources corresponding to the second network slice at the first position.

3. The method according to claim 1 or 2, characterized in that the method further comprises:

and the core network equipment sends third radio resource information, wherein the third radio resource information is used for indicating the radio resource corresponding to the first network slice at the first position.

4. The method according to claim 1 or 2, wherein when the core network device selects a functional network element for network slice NSSF, the core network device obtains the first radio resource information, and the method comprises:

the NSSF receives a first request message from a first access and mobility management function network element, AMF, the first request message including the first radio resource information.

5. The method according to claim 1 or 2, wherein when the core network device is a first access and mobility management function network element AMF, the core network device obtaining first radio resource information includes:

the first AMF sends a second request message to access network equipment, wherein the access network equipment serves the terminal equipment at the first position;

the first AMF receives a second response message from the access network device, the second response message including the first radio resource information.

6. The method of claim 5, further comprising:

and the first AMF triggers and releases a Protocol Data Unit (PDU) session corresponding to a second network slice which rejects the access of the terminal equipment.

7. The method of claim 6, wherein when the set of identifications of the first network slice is an empty set, the method further comprises:

the first AMF sends a registration rejection message to the access network equipment; and/or the presence of a gas in the gas,

and the first AMF triggers a de-registration process, and the de-registration process is used for de-registering the terminal equipment.

8. A method of communication, the method comprising:

a first access and mobility management function network element AMF acquires first radio resource information, wherein the first radio resource information is used for indicating that terminal equipment at a first position supports accessed radio resources;

the first AMF sends the first radio resource information to a network slice selection function network element NSSF;

the first AMF receives an identification of a first network slice allowing the terminal device to access from the NSSF, wherein the terminal device supports accessing the wireless resources corresponding to the first network slice at the first position.

9. The method of claim 8, further comprising:

and the first AMF receives an identifier of a second network slice which is rejected to be accessed by the terminal equipment and/or first information from the NSSF, wherein the first information is used for indicating that the terminal equipment does not support accessing to the wireless resources corresponding to the second network slice at the first position.

10. The method of claim 9, further comprising:

the first AMF receives third radio resource information from the NSSF, where the third radio resource information is used to indicate radio resources corresponding to the first network slice at the first location.

11. The method of claim 10, further comprising:

and the first AMF sends the first information and/or the third wireless resource information to an access network device.

12. The method according to any of claims 8 to 11, wherein the obtaining of the first radio resource information by the first AMF comprises:

13. A method of communication, comprising:

the method comprises the steps that access network equipment acquires first wireless resource information, wherein the first wireless resource information is used for indicating that terminal equipment located at a first position supports accessed wireless resources;

The access network equipment sends the first radio resource information to a first access and mobility management function network element AMF;

the access network device receives an identification of a first network slice allowing the terminal device to access from the first AMF, wherein the terminal device supports access to a radio resource corresponding to the first network slice at the first position.

14. The method of claim 13, further comprising:

and the access network equipment receives an identifier and/or first information of a second network slice rejected by the terminal equipment from the first AMF, wherein the first information is used for indicating that the terminal equipment does not support accessing to the wireless resources corresponding to the second network slice at the first position.

15. The method of claim 14, further comprising:

the access network device receives third radio resource information from the first AMF, wherein the third radio resource information is used for indicating radio resources corresponding to the first network slice at the first position.

16. The method of claim 15, further comprising:

And the access network equipment sends the first information and/or the third wireless resource information to the terminal equipment.

17. A method of communication, comprising:

a terminal device located at a first position sends first wireless resource information to an access network device, wherein the first wireless resource information is used for indicating that the terminal device supports accessed wireless resources;

and the terminal equipment receives the identification of a first network slice allowing the terminal equipment to access from the access network equipment, wherein the terminal equipment supports the access of the wireless resources corresponding to the first network slice at the first position.

18. The method of claim 17, further comprising:

and the terminal equipment receives an identifier of a second network slice refusing the access of the terminal equipment and/or first information from the access network equipment, wherein the first information is used for indicating that the terminal equipment does not support the access of wireless resources corresponding to the second network slice at the first position.

19. The method of claim 17 or 18, further comprising:

and the terminal equipment receives third wireless resource information from the access network equipment, wherein the third wireless resource information is used for indicating the wireless resource corresponding to the first network slice allowed at the first position.

20. A method of communication, the method comprising:

the method comprises the steps that access network equipment acquires first wireless resource information, second wireless resource information and an identifier of a first network slice, wherein the first wireless resource information is used for indicating that terminal equipment located at a first position supports accessed wireless resources, the second wireless resource information is used for indicating wireless resources corresponding to at least one network slice at the first position, and the at least one network slice comprises the first network slice;

the access network device determines an identifier of a second network slice according to the first radio resource information, the second radio resource information and the identifier of the first network slice, wherein the terminal device supports access to the radio resource corresponding to the second network slice at the first position;

and the access network equipment sends the identifier of the second network slice to a first access and mobility management network element.

21. The method of claim 20, wherein the identification of the first network slice comprises an identification of a network slice to which the terminal device requests access.

22. The method of claim 21, wherein obtaining, by the access network device, the identity of the first network slice comprises:

And the access network equipment acquires the identifier of the network slice requested to be accessed by the terminal equipment from the first access and mobility management network element or the terminal equipment.

23. The method according to any of claims 20 to 22, wherein the obtaining, by the access network device, the second radio resource information comprises:

and the access network equipment acquires the second radio resource information from the first access and mobility management network element, the access network equipment or other access network equipment.

24. The method of any one of claims 20 to 22, further comprising:

and the access network equipment sends third indication information to the first access and mobility management network element, where the third indication information is used to indicate whether the terminal equipment supports simultaneous access to part or all of the second network slices.

25. The method of any one of claims 20 to 22, further comprising:

and the access network equipment sends an identifier of a third network slice to the first access and mobility management network element, wherein the terminal equipment does not support access to the radio resource corresponding to the third network slice at the first position.

26. A method of communication, the method comprising:

a first access and mobility management network element sends an identifier of a first network slice to access network equipment located at a first position;

the first access and mobility management network element receives an identifier of a second network slice and third indication information from the access network device, the terminal device supports access to a radio resource corresponding to the second network slice at the first position, and the third indication information is used for indicating whether the terminal device supports simultaneous access to part or all of the second network slices;

the first access and mobility management network element determines an identifier of a network slice allowing the terminal device to access according to the second network slice and the third indication information;

and the first access and mobility management network element sends the identifier of the network slice allowing the terminal equipment to access to the terminal equipment.

27. The method of claim 26, wherein the identification of the first network slice comprises an identification of a network slice that the terminal device requests access to.

28. The method of claim 26 or 27, further comprising:

And the first access and mobility management network element sends second radio resource information to the access network device, where the second radio resource information is used to indicate radio resources corresponding to at least one network slice at the first position, and the at least one network slice includes the first network slice.

29. The method of claim 26 or 27, further comprising:

and the first access and mobility management network element receives an identifier of a third network slice from the access network device, wherein the terminal device does not support access to the radio resource corresponding to the third network slice at the first position.

30. The method of claim 26 or 27, further comprising:

and the first access and mobility management network element receives fourth indication information and a registration request message sent by the access network device, where the fourth indication information is used to indicate, to the first access and mobility management network element, an identifier of a network slice to which the terminal device is allowed to access according to the identifier of the second network slice.

31. The method of claim 26 or 27, further comprising:

And the first access and mobility management network element determines the network slice which rejects the access of the terminal equipment.

32. A method of communication, the method comprising:

a terminal device at a first position receives identification of a network slice deployed at the first position and information of radio resources corresponding to the network slice at the first position from an access network device;

the terminal equipment determines the identifier of a first network slice which is requested to be accessed by the terminal equipment according to the identifier of the network slice and the information of the wireless resource corresponding to the network slice, and the terminal equipment supports the access of the wireless resource corresponding to the first network slice at the first position;

and the terminal equipment sends a registration request message to the access network equipment, wherein the registration request message comprises the identification of the first network slice.

33. The method of claim 32, wherein the terminal device receiving, from an access network device, an identification of the network slice deployed at the first location and information of radio resources corresponding to the network slice at the first location comprises:

and the terminal equipment receives the identification of the network slice deployed at the first position and the information of the wireless resource corresponding to the network slice at the first position from access network equipment through a broadcast message.

34. A method of communication, the method comprising:

the method comprises the steps that access network equipment sends an identifier of a network slice deployed at a first position and information of radio resources corresponding to the network slice at the first position to terminal equipment at the first position;

and the access network equipment receives a registration request message from the terminal equipment, wherein the registration request message comprises an identifier of a first network slice, and the terminal equipment supports access to a wireless resource corresponding to the first network slice at the first position.

35. The method of claim 34, wherein the sending, by the access network device, to the terminal device at the first location, the identification of the network slice deployed at the first location and the information of the radio resources corresponding to the network slice at the first location comprises:

and the access network equipment sends the identification of the network slice deployed at the first position and the information of the wireless resource corresponding to the network slice at the first position to the terminal equipment through a broadcast message.

36. The method according to any of claims 1, 8, 13, 17, 20, 26, 32, 34, wherein the radio resources comprise frequency points and/or frequency bands.

37. A communication apparatus, characterized in that it comprises means or units for implementing the method according to any one of claims 1 to 36.

38. A communications device comprising a processor and interface circuitry for receiving signals from or transmitting signals to or from a communications device other than the communications device, the processor being arranged to implement the method of any of claims 1 to 36 by means of logic circuitry or executing code instructions.

39. A chip comprising a processor coupled to a memory for storing a computer program, the processor being configured to execute the computer program stored in the memory to cause the chip to perform the communication method of any one of claims 1 to 36.

40. A computer-readable storage medium, in which a computer program or instructions is stored which, when executed by a communication apparatus, carries out the method of any one of claims 1 to 36.