CN115314973A - Wireless communication method and communication device - Google Patents

Wireless communication method and communication device Download PDF

Info

Publication number
CN115314973A
CN115314973A CN202110502290.XA CN202110502290A CN115314973A CN 115314973 A CN115314973 A CN 115314973A CN 202110502290 A CN202110502290 A CN 202110502290A CN 115314973 A CN115314973 A CN 115314973A
Authority
CN
China
Prior art keywords
terminal
gin
information
snpn
message
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202110502290.XA
Other languages
Chinese (zh)
Inventor
朱强华
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN202110502290.XA priority Critical patent/CN115314973A/en
Priority to PCT/CN2022/088938 priority patent/WO2022237516A1/en
Publication of CN115314973A publication Critical patent/CN115314973A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/02Access restriction performed under specific conditions
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/16Discovering, processing access restriction or access information

Abstract

The application provides a wireless communication method and a communication device. The method comprises the following steps: receiving a request message from a terminal, wherein the request message is used for requesting registration to the SNPN; acquiring GIN information, wherein the GIN information is a GIN used when the terminal selects the SNPN or a GIN list in cell broadcast information of a cell accessed by the terminal; judging whether the signing information of the terminal supports the GIN information; wherein, the subscription information contains a CH-controlled preferential GIN list with priority; and when the subscription information of the terminal does not support the GIN information, rejecting the terminal to register to the SNPN. According to the scheme, the network side refuses the registration of the terminal to the SNPN under the condition that the network side judges that the subscription information of the terminal does not support the GIN information corresponding to the terminal, so that the terminal can be prevented from being accessed to the SNPN by mistake, and the access control of the terminal is realized based on the GIN information.

Description

Wireless communication method and communication device
Technical Field
The present application relates to the field of wireless communication technologies, and in particular, to a wireless communication method and a communication apparatus.
Background
At present, under the condition that the terminal subscription information stored at the network side is updated, the network selection configuration information on the terminal is overdue. If the terminal selects a stand alone non-public network (SNPN) to deploy for a registration attempt using the expired network selection configuration information, it may cause that the SNPN cannot perform access control on the registration attempt of the terminal.
For example, suppose that china mobile joined federation 1 and federation 2 as a Credential Holder (CH), and some SNPN X had a protocol or connection with federation 1 and no protocol or connection with federation 2. Since the china mobile is a member of federation 1, if the terminals signed by the china mobile sign up to federation 1 and federation 2, the SNPN X can be accessed through the credentials of federation 1. Assuming that the china mobile is updated from supporting alliance 1 and alliance 2 to only supporting alliance 2 because of subscription update, the signed terminal of the china mobile cannot access SNPN X through the certificate of alliance 1 or alliance 2, because the china mobile exits alliance 1, and SNPN X only supports alliance 1 and does not support alliance 2. However, since the network selection configuration information on the china mobile subscription terminal is not updated in time, the terminal may still select SNPN X, and the SNPN X may erroneously accept the registration of the terminal, resulting in a failure of access control on the network side.
Disclosure of Invention
The embodiment of the application provides a wireless communication method and a communication device, which are used for realizing access control of a terminal.
In a first aspect, an embodiment of the present application provides a wireless communication method, which may be performed by a mobility management network element or a module (e.g., a chip) applied in the mobility management network element. The method comprises the following steps: receiving a request message from a terminal, wherein the request message is used for requesting registration to the SNPN; acquiring GIN information, wherein the GIN information is a GIN used when the terminal selects the SNPN or a GIN list in cell broadcast information of a cell accessed by the terminal; judging whether the signing information of the terminal supports the GIN information; wherein, the subscription information contains a CH-controlled preferential GIN list with priority; and when the subscription information of the terminal does not support the GIN information, rejecting the terminal to register to the SNPN.
According to the scheme, under the condition that the network side judges that the subscription information of the terminal does not support the GIN information corresponding to the terminal, the network side refuses the terminal to register to the SNPN, so that the terminal can be prevented from being accessed to the SNPN by mistake, and therefore the access control of the terminal is successfully realized based on the GIN information.
In a possible implementation method, the request message includes a GIN used when the terminal selects the SNPN.
In one possible implementation method, the receiving a request message from a terminal includes: receiving an N2 message from the wireless access network equipment, wherein the N2 message comprises the request message and a GIN used when the terminal selects the SNPN; or receiving an N2 message from the wireless access network equipment, wherein the N2 message comprises the request message and the GIN list in the cell broadcast information.
In one possible implementation, subscription information of the terminal from a unified data management network element is received.
In a possible implementation method, the step of the terminal's subscription information not supporting the GIN information includes: in a case where the GIN information is a GIN used when the terminal selects the SNPN, when the preferred GIN list does not include a GIN used when the terminal selects the SNPN, the subscription information does not support the GIN information; or, in a case where the GIN information is the GIN list in the cell broadcast information, when the preferred GIN list does not include any GIN of the GIN lists in the cell broadcast information, the subscription information does not support the GIN information.
In one possible implementation, the rejecting the registration of the terminal with the SNPN comprises: and sending a rejection message to the terminal, wherein the rejection message comprises a reason value, and the reason value is GIN authorization failure.
In a possible implementation method, network selection configuration information is sent to the terminal; wherein, the network selection configuration information includes a CH-controlled prioritized preferred SNPN list and the preferred GIN list.
According to the scheme, the network selection configuration information of the terminal can be updated, so that the terminal can reselect the network according to the updated network selection configuration information, and the access control of the terminal is facilitated.
In a possible implementation method, the sending network selection configuration information to the terminal includes: and sending a downlink NAS transmission message to the terminal, wherein the downlink NAS transmission message comprises the network selection configuration information.
In one possible implementation, the rejecting the registration of the terminal with the SNPN comprises: sending a refusal message to the terminal, wherein the refusal message comprises a reason value, and the reason value is GIN authorization failure; or sending an acceptance message to the terminal, wherein the acceptance message contains connection state control information (CMCI), and the CMCI is used for indicating the terminal to reselect the network after the terminal is converted from the connection state to the idle state at a specific time. Wherein, reselecting the network refers to reselecting a network other than the SNPN.
In one possible implementation, the rejecting the registration of the terminal with the SNPN comprises: starting a timer;
and after the timer is overtime, starting a deregistration process of the terminal.
In one possible implementation method, the rejecting registration of the terminal to the SNPN includes: and after receiving the notification information from the terminal, starting a deregistration process of the terminal, wherein the notification information indicates that the updating of the network selection configuration information is completed.
In one possible implementation, the unified data management network element is notified: the contract information of the terminal does not support the GIN information; and receiving the network selection configuration information from the unified data management network element. For example, a subscription update notification message from the unified data management network element may be received, where the subscription update notification message includes the network selection configuration information.
In a second aspect, the present application provides a wireless communication method, which may be performed by a unified data management network element or a module (e.g., a chip) applied in the unified data management network element. The method comprises the following steps: receiving a first request from a mobility management network element, wherein the first request comprises information GIN information, and the GIN information is a GIN used when a terminal selects SNPN or a GIN list in cell broadcast information of a cell accessed by the terminal; judging whether the subscription information of the terminal supports the GIN information or not, wherein the subscription information of the terminal comprises a CH-controlled preferential GIN list with priority; and rejecting the first request when the subscription information of the terminal does not support the GIN information.
According to the scheme, under the condition that the network side judges that the subscription information of the terminal does not support the GIN information corresponding to the terminal, the network side refuses the terminal to register to the SNPN, so that the terminal can be prevented from being accessed to the SNPN by mistake, and therefore the access control of the terminal is successfully realized based on the GIN information.
In a possible implementation method, the step of the terminal's subscription information not supporting the GIN information includes: in the case that the GIN information is a GIN used when the terminal selects an SNPN, when the preferred GIN list does not include a GIN used when the terminal selects an SNPN, the subscription information does not support the GIN information; or, in a case where the GIN information is the GIN list in the cell broadcast information, when the preferred GIN list does not include any GIN in the GIN list in the cell broadcast information, the subscription information does not support the GIN information.
In a possible implementation method, the first request is a network function NF registration request, where the NF registration request is used to request to provide a service for the terminal; the rejecting the first request includes: and sending an NF registration response to the mobility management network element, wherein the NF registration response comprises a cause value, and the cause value is GIN authorization failure.
In a possible implementation method, the NF registration response further includes network selection configuration information, where the network selection configuration information includes a CH-controlled prioritized SNPN list and the preferred GIN list.
In a possible implementation method, the first request is a subscription request, and the subscription request is used for requesting to acquire subscription data of the terminal; the rejecting the first request includes: and sending a subscription response to the mobility management network element, wherein the subscription response comprises a cause value, and the cause value is GIN authorization failure.
In a possible implementation method, the subscription response includes network selection configuration information, and the network selection configuration information includes a CH-controlled prioritized preferred SNPN list and the preferred GIN list.
In a possible implementation method, network selection configuration information is sent to the mobility management network element, where the network selection configuration information includes a CH-controlled prioritized preferred SNPN list and the preferred GIN list.
In a possible implementation method, connection state control information CMCI is sent to the mobility management network element, where the CMCI is used to instruct the terminal to reselect the network after the terminal is switched from the connection state to the idle state at a specific time.
In a third aspect, embodiments of the present application provide a wireless communication method, which may be performed by a terminal or a module (e.g., a chip) applied in the terminal. The method comprises the following steps: sending RRC signaling to the wireless access network equipment, wherein the RRC signaling comprises a request message, and the request message is used for requesting registration to the SNPN; the request message contains GIN information or the RRC signaling contains the GIN information; the GIN information is a GIN used when the terminal selects the SNPN; and receiving a response message, wherein the response message is used for refusing the terminal to register to the SNPN.
According to the scheme, the network side refuses the terminal to register to the SNPN under the condition that the network side judges that the subscription information of the terminal does not support the GIN information corresponding to the terminal, so that the terminal can be prevented from being accessed to the SNPN by mistake, and the access control of the terminal is successfully realized on the basis of the GIN information.
In one possible implementation method, network selection configuration information is received, and the network selection configuration information includes a CH-controlled prioritized preferred SNPN list and a CH-controlled prioritized preferred GIN list.
In a possible implementation method, the receiving network selection configuration information includes: and receiving a downlink NAS transmission message, wherein the downlink NAS transmission message comprises the network selection configuration information.
In a possible implementation method, the network selection configuration information is updated according to the network selection configuration information to obtain updated network selection configuration information.
In one possible implementation method, the network is reselected according to the updated network selection configuration information.
In a possible implementation method, the reselecting a network according to the updated network selection configuration information includes: if the response message is a rejection message, triggering to reselect the network according to the updated network selection configuration information according to the rejection message; or, the response message is a reject message, the reject message contains the cause value, and the cause value is GIN authorization failure, and then according to the cause value, the network selection is triggered to be carried out again according to the updated network selection configuration information; or, the response message further includes a CMCI, where the CMCI is used to instruct the terminal to reselect after the terminal is converted from the connected state to the idle state at a specific time, and then reselect after the terminal is converted from the connected state to the idle state at the specific time according to the CMCI; or after deregistration, reselecting the network according to the updated network selection configuration information.
In one possible implementation method, the response message is a reject message, and the reject message includes a cause value, where the cause value is a GIN authorization failure; alternatively, the response message is an accept message.
In a fourth aspect, embodiments of the present application provide a wireless communication method, which may be performed by a radio access network device or a module (e.g., a chip) applied in the radio access network device. The method comprises the following steps: receiving RRC signaling from a terminal, wherein the RRC signaling comprises a request message, and the request message is used for registering to the SNPN; sending GIN information to a mobility management network element; wherein, the GIN information is a GIN used when the terminal selects the SNPN, or a GIN list in cell broadcast information of a cell to which the terminal accesses; and receiving a response message from the mobility management network element, wherein the response message is used for refusing the terminal to register to the SNPN.
According to the scheme, under the condition that the network side judges that the subscription information of the terminal does not support the GIN information corresponding to the terminal, the network side refuses the terminal to register to the SNPN, so that the terminal can be prevented from being accessed to the SNPN by mistake, and therefore the access control of the terminal is successfully realized based on the GIN information.
In a possible implementation method, the RRC signaling includes a GIN used when the terminal selects the SNPN.
In a fifth aspect, the present embodiments provide a wireless communication method, which may be performed by a first network element or a module (e.g., a chip) applied in the first network element. The first network element here may be a unified data management network element or an authentication network element. The method comprises the following steps: receiving an authentication request, wherein the authentication request comprises group identification information GIN information used for network selection, and the GIN information is a GIN used when a terminal selects SNPN or a GIN list in cell broadcast information of a cell accessed by the terminal; judging whether the signing information of the terminal supports the GIN information or not, wherein the signing information of the terminal comprises a preferred GIN list which is controlled by a certificate owner CH and has priority; and when the subscription information of the terminal does not support the GIN information, rejecting the authentication request.
According to the scheme, under the condition that the network side judges that the subscription information of the terminal does not support the GIN information corresponding to the terminal, the network side refuses the terminal to register to the SNPN, so that the terminal can be prevented from being accessed to the SNPN by mistake, and therefore the access control of the terminal is successfully realized based on the GIN information.
In a possible implementation method, in a case that the GIN information is a GIN used when the terminal selects the SNPN, when the preferred GIN list does not include a GIN used when the terminal selects the SNPN, the subscription information does not support the GIN information; or, in a case where the GIN information is the GIN list in the cell broadcast information, when the preferred GIN list does not include any GIN in the GIN list in the cell broadcast information, the subscription information does not support the GIN information.
In one possible implementation, the first network element is a unified data management network element; selecting network configuration information and/or CMCI from a mobile management network element; the updated network selection configuration information comprises a CH-controlled prioritized preferred SNPN list and the preferred GIN list, and the CMCI is used for indicating the terminal to reselect the network after the terminal is switched from a connected state to an idle state at a specific time. Optionally, a subscription update notification is sent to the mobility management network element, where the subscription update notification includes the network selection configuration information and/or the CMCI.
In one possible implementation, the authentication request is received from an authentication network element; and sending an authentication failure message to the authentication network element, wherein the authentication failure message comprises a cause value, and the cause value is GIN authorization failure.
In one possible implementation, the first network element is an authentication network element; and informing the unified data management network element: the subscription information of the terminal does not support the GIN information.
In one possible implementation, the authentication request is received from a mobility management network element; and sending an authentication failure message to the mobility management network element, wherein the authentication failure message comprises a cause value, and the cause value is GIN authorization failure.
In a possible implementation method, subscription information of the terminal from the unified data management network element is received.
In a sixth aspect, an embodiment of the present application provides a communication apparatus, where the apparatus may be a mobility management network element, and may also be a chip for a mobility management network element. The apparatus has the functionality to implement any of the implementation methods of the first aspect described above. The function can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above.
In a seventh aspect, an embodiment of the present application provides a communication device, where the device may be a unified data management network element, and may also be a chip or a module for the unified data management network element. The apparatus has a function of implementing any of the implementation methods of the second aspect described above. The function can be realized by hardware, and can also be realized by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.
In an eighth aspect, embodiments of the present application provide a communication apparatus, which may be a terminal, and may also be a chip or a module for a terminal. The apparatus has a function of implementing any of the implementation methods of the third aspect described above. The function can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above.
In a ninth aspect, an embodiment of the present application provides a communication apparatus, which may be a radio access network device and may also be a chip or a module for a radio access network device. The apparatus has a function of implementing any of the implementation methods of the fourth aspect described above. The function can be realized by hardware, and can also be realized by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.
In a tenth aspect, an embodiment of the present application provides a communication apparatus, which may be a first network element, and may also be a chip or a module for the first network element. The first network element here may be a unified data management network element or an authentication network element. The apparatus has a function of implementing any implementation method of the fifth aspect described above. The function can be realized by hardware, and can also be realized by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.
In an eleventh aspect, an embodiment of the present application provides a communication apparatus, including a processor and a memory; the memory is used for storing computer instructions, and when the apparatus runs, the processor executes the computer instructions stored in the memory, so that the apparatus executes any implementation method in the first aspect to the fifth aspect.
In a twelfth aspect, embodiments of the present application provide a communication apparatus, which includes means or means (means) for performing each step of any implementation method in the first to fifth aspects.
In a thirteenth aspect, an embodiment of the present application provides a communication device, which includes a processor and an interface circuit, where the processor is configured to communicate with another device through the interface circuit, and perform any implementation method in the first to fifth aspects. The processor includes one or more.
In a fourteenth aspect, an embodiment of the present application provides a communication apparatus, including a processor coupled to a memory, where the processor is configured to call a program stored in the memory to execute any implementation method in the first to fifth aspects. The memory may be located within the device or external to the device. And the processor may be one or more.
Fifteenth aspect, embodiments of the present application further provide a computer-readable storage medium, where instructions are stored, and when the computer-readable storage medium is executed on a communication device, the method for implementing any of the first to fifth aspects is performed.
Sixteenth, the present application also provides a computer program product, which includes a computer program or instructions, when the computer program or instructions is executed by a communication device, the method of any of the first to fifth aspects is executed.
In a seventeenth aspect, an embodiment of the present application further provides a chip system, including: a processor configured to perform any of the implementation methods of the first to fifth aspects.
In an eighteenth aspect, an embodiment of the present application further provides a communication system, including: the communication device of the sixth aspect and the communication device of the ninth aspect.
In a nineteenth aspect, an embodiment of the present application further provides a communication system, including: the communication device of the seventh aspect and the communication device of the ninth aspect.
In a twentieth aspect, an embodiment of the present application further provides a communication system, including: the communication device of the tenth aspect and the communication device of the ninth aspect.
Drawings
FIG. 1 (a) is a schematic diagram of a fifth generation (5G) network architecture based on a service architecture;
FIG. 1 (b) is a schematic diagram of a 5G network architecture based on a point-to-point interface;
FIG. 2 is a schematic representation of a federation;
fig. 3 (a) is a schematic diagram of a wireless communication method according to an embodiment of the present application;
fig. 3 (b) is a schematic diagram of a wireless communication method according to an embodiment of the present application;
fig. 3 (c) is a schematic diagram of a wireless communication method according to an embodiment of the present application;
fig. 4 is a schematic diagram of a wireless communication method according to an embodiment of the present application;
fig. 5 is a schematic diagram of a wireless communication method according to an embodiment of the present application;
fig. 6 is a schematic diagram of a wireless communication method according to an embodiment of the present application;
fig. 7 is a schematic diagram of a wireless communication method according to an embodiment of the present application;
fig. 8 is a diagram illustrating a wireless communication method according to an embodiment of the present application;
fig. 9 is a schematic diagram of a wireless communication method according to an embodiment of the present application;
fig. 10 is a schematic diagram of a communication device according to an embodiment of the present application;
fig. 11 is a schematic diagram of a communication device according to an embodiment of the present application;
fig. 12 is a schematic structural diagram of a terminal according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more clear, the present application will be further described in detail with reference to the accompanying drawings. The particular methods of operation in the method embodiments may also be applied to apparatus embodiments or system embodiments.
FIG. 1 (a) is a schematic diagram of a fifth generation (5G) network architecture based on a service architecture. The 5G network architecture shown in fig. 1 (a) may include three parts, namely a terminal, a Data Network (DN) and an operator network. The functions of some of the network elements will be briefly described below.
Wherein the operator network may comprise one or more of the following network elements: an Authentication Server Function (AUSF) Network element, a Network open Function (NEF) Network element, a Policy Control Function (PCF) Network element, a Unified Data Management (UDM) Network element, a Unified Data Repository (UDR), a Network storage Function (Network storage Function, NRF) Network element, an Application Function (AF) Network element, an access and mobility management Function (AMF) Network element, a Session Management Function (SMF) Network element, a Radio Access Network (RAN) device, and a user plane Function (user plane, UPF) Network element, a Network Slice Selection Function (Slice) Network element, a sf Network element, and the like. In the operator network, network elements or devices other than the radio access network device may be referred to as core network elements or core network devices. It should be noted that, in practical applications, AFs are divided into two types, one type belongs to a core network element, and the other type belongs to a third-party application server.
The radio access network device may be a base station (base station), an evolved NodeB (eNodeB), a Transmission Reception Point (TRP), a next generation base station (gNB) in a 5G mobile communication system, a next generation base station in a 6G mobile communication system, a base station in a future mobile communication system, or an access node in a wireless fidelity (WiFi) system, and the like; the present invention may also be a module or a unit that performs part of the functions of the base station, and for example, the module may be a Centralized Unit (CU) or a Distributed Unit (DU). The radio access network device may be a macro base station, a micro base station or an indoor station, or a relay node or a donor node. The embodiments of the present application do not limit the specific technologies and the specific device forms adopted by the radio access network device.
A terminal may also be referred to as a terminal equipment, a User Equipment (UE), a mobile station, a mobile terminal, etc. The terminal can be widely applied to various scenes, for example, device-to-device (D2D), vehicle-to-electrical (V2X) communication, machine-type communication (MTC), internet of things (IOT), virtual reality, augmented reality, industrial control, automatic driving, telemedicine, smart grid, smart furniture, smart office, smart wearing, smart transportation, smart city, and the like. The terminal can be cell-phone, panel computer, take the computer of wireless transceiver function, wearable equipment, vehicle, unmanned aerial vehicle, helicopter, aircraft, steamer, robot, arm, intelligent home equipment etc.. The embodiment of the present application does not limit the specific technology and the specific device form adopted by the terminal.
The radio access network equipment and the terminal may be fixed or mobile. The radio access network equipment and the terminal can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; can also be deployed on the water surface; it may also be deployed on airborne airplanes, balloons, and satellite vehicles. The embodiment of the application does not limit the application scenarios of the wireless access network equipment and the terminal.
And the AMF network element executes functions of mobility management, access authentication/authorization and the like. In addition, it is also responsible for transferring user policy between the terminal and the PCF.
The SMF network element performs functions such as session management, control policy execution issued by PCF, selection of UPF, and Internet Protocol (IP) address allocation of the terminal.
The UPF network element is used as an interface UPF with a data network to complete functions of user plane data forwarding, session/stream level-based charging statistics, bandwidth limitation and the like.
And the UDM network element executes functions of managing subscription data, user access authorization and the like.
And the UDR executes the access function of the type data such as the subscription data, the strategy data, the application data and the like.
And the NEF network element is used for supporting the opening of the capability and the event.
The AF network element transfers requirements of the application side on the network side, such as Quality of Service (QoS) requirements or user status event subscriptions, etc. The AF may be a third party functional entity, or may be an application service deployed by an operator, such as an IP Multimedia Subsystem (IMS) voice call service.
And the PCF network element is responsible for performing policy control functions such as charging, qoS bandwidth guarantee, mobility management, terminal policy decision and the like aiming at the session and service stream levels.
The NRF network element can be used for providing a network element discovery function and providing network element information corresponding to the network element type based on the request of other network elements. NRF also provides network element management services such as network element registration, update, de-registration, and network element status subscription and push.
And the AUSF network element is responsible for authenticating the user so as to determine whether the user or the equipment is allowed to access the network.
And the NSSF network element is used for selecting the network slice, counting the users in the network slice and the like.
The DN is a network outside the operator network, the operator network can access a plurality of DNs, and the DN can deploy a plurality of services and provide services such as data and/or voice for the terminal. For example, the DN is a private network of an intelligent factory, a sensor installed in a workshop of the intelligent factory can be a terminal, a control server of the sensor is deployed in the DN, and the control server can provide services for the sensor. The sensor can communicate with the control server, obtain the instruction of the control server, transmit the sensor data gathered to the control server, etc. according to the instruction. For another example, the DN is an internal office network of a company, the mobile phone or computer of the employee of the company may be a terminal, and the mobile phone or computer of the employee may access information, data resources, and the like on the internal office network of the company.
Nausf, nnef, npcf, nudm, naf, namf, and Nsmf in FIG. 1 (a) are the service interfaces provided by the AUSF, NEF, PCF, UDM, AF, AMF, and SMF, respectively, for invoking the corresponding service operations. N1, N2, N3, N4, and N6 are interface serial numbers. The meaning of these interface serial numbers can be found in the third generation partnership project (3 rd generation partnership project,3 gpp) standard protocol, which is not limited herein.
Fig. 1 (b) is a schematic diagram of a 5G network architecture based on a point-to-point interface, where introduction of functions of a network element in the schematic diagram refers to introduction of functions of a corresponding network element in fig. 1 (a), and details are not described again. The main differences between fig. 1 (b) and fig. 1 (a) are: the interfaces between the control plane network elements in fig. 1 (a) are served interfaces, and the interfaces between the control plane network elements in fig. 1 (b) are point-to-point interfaces.
In the architecture shown in fig. 1 (b), the interface names and functions between the network elements are as follows:
1) And N1: the interface between the AMF and the terminal may be used to deliver QoS control rules, etc. to the terminal.
2) N2: the interface between the AMF and the RAN may be used to transfer radio bearer control information from the core network side to the RAN, and the like.
3) N3: the interface between RAN and UPF is mainly used for transmitting the uplink and downlink user plane data between RAN and UPF.
4) N4: the interface between the SMF and the UPF may be used for transmitting information between the control plane and the user plane, including controlling the sending of forwarding rules, qoS control rules, traffic statistics rules, etc. for the user plane and reporting information for the user plane.
5) N5: the interface between the AF and the PCF may be used for application service request issue and network event report.
6) N6: and the UPF and DN interface is used for transmitting the uplink and downlink user data stream between the UPF and the DN.
7) N7: the interface between the PCF and the SMF may be used to send a Protocol Data Unit (PDU) session granularity and a service data stream granularity control policy.
8) And N8: the interface between the AMF and the UDM may be used for the AMF to obtain subscription data and authentication data related to access and mobility management from the UDM, and for the AMF to register information related to current mobility management of the terminal with the UDM.
9) And N9: and the user interface between the UPF and the UPF is used for transmitting the uplink and downlink user data streams between the UPFs.
10 N10: the interface between the SMF and the UDM may be used for the SMF to acquire the subscription data related to session management from the UDM, and for the SMF to register the information related to the current session of the terminal with the UDM.
11 N11): the interface between the SMF and the AMF may be used to transfer PDU session tunnel information between the RAN and the UPF, to transfer control messages to the terminal, to transfer radio resource control information to the RAN, and so on.
12 N12): the interface between the AMF and the AUSF can be used for initiating an authentication process from the AMF to the AUSF, wherein the interface can carry SUCI as a subscription identifier;
13 N13): the interface between the UDM and the AUSF may be used for the AUSF to obtain the user authentication vector from the UDM to execute the authentication procedure.
14 N15): the interface between PCF and AMF can be used to send down terminal strategy and access control relative strategy.
15 N35), N35: the interface between the UDM and the UDR may be used for the UDM to obtain the user subscription data information from the UDR.
16 N36): the interface between the PCF and the UDR may be used for the PCF to obtain policy-related subscription data and application data-related information from the UDR.
It is to be understood that the network element or the function may be a network element in a hardware device, or may be a software function running on dedicated hardware, or a virtualization function instantiated on a platform (e.g., a cloud platform). Optionally, the network element or the function may be implemented by one device, or may be implemented by multiple devices together, or may be a functional module in one device, which is not specifically limited in this embodiment of the present application.
The session management network element, the unified data management network element, the authentication network element, and the mobility management network element in the embodiment of the present application may be network elements having functions of an SMF, a UDM, an AUSF, and an AMF shown in fig. 1 (a) or fig. 1 (b), respectively. For convenience of description, in the following description of the present application, the session management network element, the unified data management network element, the authentication network element, and the mobility management network element are referred to as SMF, UDM, AUSF, and AMF, respectively. It should be noted that, in future communications, the session management network element, the unified data management network element, the authentication network element, and the mobility management network element may still be referred to as SMF, UDM, AUSF, or AMF, or may also have other names, which is not limited in this application. The SMF, UDM, AUSF, and AMF appearing later in the present application may be replaced with a session management network element, a unified data management network element, an authentication network element, and a mobility management network element, respectively.
Some terms or expressions referred to in the embodiments of the present application will be explained below.
1. Non-public network (NPN)
NPN is a non-public 5G network and can be applied to places such as enterprises and factories. The NPN may implement public network integrated NPN (public network integrated NPN) depending on support of a Public Land Mobile Network (PLMN), or implement SNPN without depending on a network function of the PLMN.
2. SNPN
SNPN is deployed independently and does not depend on PLMN. The SNPN is identified using a PLMN ID + Network Identifier (NID). The PLMN ID may be an inherent value reserved by a third-party operator, or may be a specific value of a PLMN operator deploying the SNPN.
The cell broadcast information sent by the cell in the SNPN comprises PLMN ID + NID, and the terminal selects the accessed SNPN according to the cell broadcast information and the configured network selection configuration information. If the terminal finds that the PLMN ID + NID in the network selection configuration information is different from the PLMN ID + NID broadcast by the network, the terminal does not select the SNPN access. The PLMN ID + NID in the network selection configuration information is different from the PLMN ID + NID sent by the network broadcast, which means that the PLMN in the network selection configuration information is different from the PLMN sent by the network broadcast, and/or the NID in the network selection configuration information is different from the NID sent by the network broadcast.
In release 17 of 3GPP, the standard supports terminals to access SNPN using the credentials of the CH. Wherein, if the CH provides the UDM or the AUSF, the CH may be a PLMN or another SNPN; if the CH provides an Authentication, authorization, accounting (AAA-S) server, the CH may be an industry vendor, such as Alibab, tencent, or manufacturer.
3. Group identification for network selection (GIN)
If different CHs make up a federation, each federation is identified using one GIN.
When there is a connection or protocol between a certain SNPN and one or more federations, the terminal may access the SNPN using the credentials of any CH in the one or more federations. Referring to fig. 2, a schematic diagram of a federation is shown. Where a federation contains one or more CHs, each CH may be a PLMN, SNPN, or industry vendor, among others. In fig. 2, CH is SNPN as an example.
Referring to FIG. 2, SNPN A SNPN E constitutes federation 1, SNPN F SNPN J constitutes federation 2, where federation 1 is identified by GIN1 and federation 2 is identified by GIN 2. Furthermore, SNPN X has a connection or a protocol with federation 1, and cell broadcast information transmitted by radio access network equipment in SNPN X includes GIN1, indicating that SNPN X supports federation 1.SNPN Y has connection or agreement with alliance 1 and alliance 2, and cell broadcast information sent by radio access network equipment in SNPN Y comprises GIN1 and GIN2, which indicates that SNPN X supports alliance 1 and alliance 2.
If any member of federation 1 has an identifier, such as the identifier of SNPN a, configured in a terminal, the terminal may select SNPN X or SNPN Y. If a terminal is configured with the identity of any member of federation 2, such as the identity of SNPN F, but not with the identity of any member of federation 1, then the terminal may select SNPN Y but not SNPN X. In addition, any member of the federation, such as SNPN A or SNPN F, can dynamically update the network selection configuration information on the terminal for the GIN.
Under the framework based on CH, a set of new SNPN selection mechanism is defined, and under the mechanism, the network selection configuration information on the terminal, the cell broadcast information sent by the wireless access network equipment and the SNPN selection mode of the terminal are respectively as follows:
1. the network selection configuration information on the terminal comprises one or more of the following a) to c):
a) A user-controlled prioritized list of preferred SNPN;
the SNPN in the SNPN list may be configured or updated by the user.
b) A CH controlled prioritized list of preferred SNPNs;
the SNPNs in the SNPN list are controlled by the CH and may be configured or updated by a Core Network (CN).
c) CH controlled prioritized list of preferred GINs.
Each GIN in the list of GINs is used to identify a group of multiple CHs, also known as a federation.
The GINs in the GIN list are controlled by the CH, and may be configured or updated by the CN.
2. The cell broadcast information sent by the wireless access network equipment comprises one or more of the following a) to c):
a) The first indication information indicates whether the SNPN where the wireless access network equipment is located supports the terminal to access the SNPN by using the CH certificate;
b) A GIN list supported by the SNPN where the wireless access network equipment is located;
the CH supported by the SNPN is the CH identified by the GIN in the GIN list.
c) Second indication information indicating whether a terminal not explicitly configured to select the SNPN is allowed to perform a registration attempt.
3. The terminal selects the SNPN sequence according to the network selection configuration information of the terminal as follows:
a) Selecting the SNPN where the wireless access network equipment which sends the first indication information is located, wherein the first indication information indicates that the SNPN supporting terminal where the wireless access network equipment is located uses the certificate of the CH to access the SNPN;
if the cell broadcast information sent by a plurality of radio access network devices contains first indication information, selecting one SNPN from the SNPNs of the plurality of radio access network devices according to the following priority order:
priority 1: selecting SNPNs in the user controlled prioritized preferred SNPN list (in the order of priority of SNPNs in the user controlled prioritized preferred SNPN list);
priority 2: selecting SNPNs in the CH controlled prioritized preferred SNPN list (in order of priority of SNPNs in the CH controlled prioritized preferred SNPN list);
priority 3: selecting a GIN of the broadcasted GIN in the CH controlled prioritized GIN list, and then selecting an SNPN (in the priority order of the GINs in the CH controlled prioritized GIN list) in which the radio access network device broadcasting the GIN is located;
if an SNPN is not selected by the above method, the following b) is performed:
b) And selecting the SNPN in which the radio access network equipment which broadcasts the second indication information is positioned, wherein the second indication information indicates that the terminal which does not explicitly configure and select the SNPN is allowed to carry out the registration attempt.
This is explained below with reference to an example.
Example 1:
assume that the network selection configuration information on the terminal 1 includes:
a) User controlled prioritized list of preferred SNPNs: { SNPN 1, SNPN 2, SNPN 3};
b) CH controlled prioritized preferred SNPN list: { SNPN 4, SNPN 5, SNPN 6};
c) CH controlled prioritized list of preferred GINs: { GIN1, GIN2, GIN 3}.
The network selection configuration information on the terminal 2 includes:
a) User controlled prioritized list of preferred SNPNs: { SNPN 7, SNPN 8, SNPN 9};
b) CH controlled prioritized preferred SNPN list: { SNPN 10, SNPN 11, SNPN 12};
c) CH controlled prioritized list of preferred GINs: { GIN4, GIN 5, GIN 6}.
The cell broadcast information transmitted by the radio access network device 1 (corresponding to SNPN 1) includes:
a) First indication information indicating that the SNPN 1 supports the terminal to access the SNPN 1 by using the certificate of the CH;
b) List of GINs supported by SNPN 1: { GIN1, GIN2, GIN3, GIN4, GIN 5, GIN 6};
c) And second indication information indicating that the terminal not explicitly configured to select the SNPN is not allowed to perform a registration attempt.
The cell broadcast information transmitted by the radio access network device 2 (corresponding to SNPN 4) includes:
a) First indication information indicating that the SNPN 4 supports the terminal to access the SNPN 4 by using the certificate of the CH;
b) List of GINs supported by SNPN 4: { GIN1, GIN2, GIN3, GIN 4};
c) Second indication information indicating that a terminal that selects the SNPN is not explicitly configured to be allowed to perform a registration attempt.
The cell broadcast information transmitted by the radio access network device 3 (corresponding to the SNPN 10) includes:
a) First indication information indicating that the SNPN 10 supports the terminal to access the SNPN 10 by using the certificate of the CH;
b) List of GINs supported by SNPN 10: { GIN1, GIN2, GIN3, GIN 4};
c) And second indication information indicating that the terminal which selects the SNPN is not configured explicitly for registration attempt.
It should be noted that, for any list in the network selection configuration information of the terminal or the cell broadcast information sent by the radio access network device, the appearance order of the elements in the list represents the priority level, where the priority level appearing first is higher than the priority level appearing later. For example, { SNPN 1, SNPN 2, SNPN 3}, the priority levels are, in order from high to low: SNPN 1, SNPN 2 and SNPN 3.
According to the above SNPN selection mechanism, the terminal 1 selects SNPN 1 from SNPN 1, SNPN 4, and SNPN 10, and the terminal 2 selects SNPN 10 from SNPN 1, SNPN 4, and SNPN 10.
In order to solve the problem of access control failure on the network side, the present application provides a corresponding wireless communication method, which is used for SNPN access control, and the method is specifically described below with reference to the accompanying drawings.
It is specifically noted herein that the execution subject in the implementation method described below is not limited to the current name, for example, AMF, UDM, AUSF, terminal, radio access network device, etc., and taking AMF as an example, the AMF implementing the method described in this application may be an AMF device in a 5G communication system, or may be a device or entity having the same core concept or function. Similarly, the messages mentioned in the present application are not limited by names, and any messages with the same function and different names are also applicable to the method of the present application, and are not described in detail.
Fig. 3 (a) illustrates a wireless communication method according to an embodiment of the present application. The method may be performed by the AMF or a module (e.g., a chip) for the AMF, and the method performed by the AMF is described below as an example.
The method comprises the following steps:
in step 301a, the amf receives a request message for requesting registration to the SNPN from the terminal.
Optionally, the request message is a registration request message.
In step 302a, the amf acquires GIN information, wherein the GIN information is a GIN used when the terminal selects an SNPN or a GIN list in cell broadcast information of a cell to which the terminal accesses.
It should be noted that, in the present application, the GIN information may be a GIN used when the terminal selects the SNPN, a GIN list in cell broadcast information of a cell to which the terminal accesses, or other identification information or a set, a list, etc. thereof, which may be used when the terminal selects the SNPN. The same reason is not described in detail below.
As an implementation method, a terminal sends Radio Resource Control (RRC) signaling to a radio access network device, where the RRC signaling is taken as an example, or may be any signaling message named by other names with the same essence. The RRC signaling includes the request message, where the request message includes GIN information, and the GIN information is a GIN used when the terminal selects the SNPN. The radio access network equipment sends an N2 message to the AMF, wherein the N2 message comprises the request message. Based on the implementation method, step 301a refers to: the AMF receives an N2 message from the wireless access network equipment, wherein the N2 message comprises a request message sent to the wireless access network equipment by the terminal. The step 302a refers to: the AMF acquires the GIN information from the request message, wherein the GIN information is used by the terminal when the terminal selects the SNPN.
As another implementation method, the terminal sends an RRC signaling to the radio access network device, where the RRC signaling includes the request message and GIN information, and the GIN information is a GIN used when the terminal selects an SNPN. The radio access network equipment sends an N2 message to the AMF, wherein the N2 message comprises the request message and the GIN information. Based on the implementation method, step 301a refers to: the AMF receives the N2 message from the radio access network device, wherein the N2 message includes the request message sent by the terminal to the radio access network device. The step 302a refers to: the AMF acquires the GIN information from the N2 message, the GIN information being a GIN used when the terminal selects the SNPN.
As another implementation method, the terminal sends an RRC signaling to the radio access network device, where the RRC signaling includes the request message. And the wireless access network equipment sends an N2 message to the AMF, wherein the N2 message comprises the request message and GIN information, and the GIN information is a GIN list in cell broadcast information of a cell accessed by the terminal. Based on the implementation method, step 301a refers to: the AMF receives the N2 message from the radio access network equipment, wherein the N2 message comprises a request message sent to the radio access network equipment by the terminal. The step 302a refers to: the AMF acquires the GIN information from the N2 message, and the GIN information is a GIN list in cell broadcast information of a cell to which the terminal accesses.
Step 303a, AMF judges whether the contract signing information of the terminal supports the GIN information; wherein, the subscription information includes a CH-controlled prioritized GIN list.
The subscription information of the terminal includes a CH-controlled prioritized GIN list. Optionally, a CH-controlled prioritized preferred SNPN list is also included.
As an implementation method, the AMF obtains the subscription information of the terminal from the UDM.
In the case that the GIN information is a GIN used when the terminal selects the SNPN, if the GIN used when the terminal selects the SNPN does not belong to a preferred GIN list controlled by a CH in the subscription information of the terminal, that is, the preferred GIN list controlled by the CH in the subscription information of the terminal does not include the GIN used when the terminal selects the SNPN, the subscription information does not support the GIN information. For example, when the GIN included in the CH-controlled prioritized preferred GIN list in the subscription information of the terminal is GIN1, GIN2, and GIN3, and the GIN used when the terminal selects SNPN is GIN4, if the GIN4 is not included in the CH-controlled prioritized preferred GIN list in the subscription information of the terminal, it means that the subscription information does not support the GIN information.
In the case that the GIN information is a GIN list in cell broadcast information of a cell to which the terminal is accessed, when any GIN in the GIN list in the cell broadcast information of the cell to which the terminal is accessed does not belong to a CH-controlled preferred GIN list with a priority in subscription information of the terminal, that is, any GIN in the GIN list in the cell broadcast information of the cell to which the terminal is accessed is not included in the CH-controlled preferred GIN list with the priority in the subscription information of the terminal, the subscription information does not support the GIN information. For example, when the GIN included in the CH-controlled prioritized preferred GIN list in the subscription information of the terminal is GIN1, GIN2, and GIN3, and the GIN included in the GIN list in the cell broadcast information of the cell to which the terminal accesses is GIN7, GIN8, and GIN9, if any of the GIN7, GIN8, or GIN9 is not included in the CH-controlled prioritized preferred GIN list in the subscription information of the terminal, the subscription information does not support the GIN information.
Step 304a, when the subscription information of the terminal does not support the GIN information, the AMF refuses the terminal to register to the SNPN.
For example, the AMF transmits a response message to the terminal, the response message being used to reject the terminal from registering to the SNPN. The response message may be a rejection message or an acceptance message. Four specific implementations are given below, but are not limited to the four methods.
In the first implementation method, the AMF sends a rejection message (for example, a registration rejection message) to the terminal, where the rejection message includes network selection configuration information and/or a cause value, and the cause value is a GIN authorization failure or an illegal GIN request. The reject message is used to reject the terminal registration to the SNPN. When the reject message contains the network selection configuration information, the terminal can update the network selection configuration information on the terminal according to the received network selection configuration information to obtain the updated network selection configuration information. Then, the terminal can trigger to reselect the network according to the updated network selection configuration information according to the rejection message, or trigger to reselect the network according to the updated network selection configuration information according to the cause value in the registration rejection message.
It should be noted that the network reselection in the embodiment of the present application refers to selecting a network other than the SNPN, such as selecting another SNPN, or selecting a PLMN, or selecting a PNI-NPN. When the terminal reselects the network, if an SNPN needs to be reselected, the selection may be performed according to the method described above, "the terminal selects the SNPN in the following sequence according to the network selection configuration information of the terminal," which is described in a unified manner here and is not described in detail later.
It should be noted that, in this embodiment of the application, the method for the terminal to update the network selection configuration information may be, for example: and replacing or modifying the relevant part in the network selection configuration information stored in the terminal according to the received network selection configuration information to obtain updated network selection configuration information. For example, the network selection configuration information stored in the terminal includes three parts, namely network selection configuration information related to China Mobile, network selection configuration information related to China Unicom, and network selection configuration information related to China telecom. If the network selection configuration information received by the terminal is the network selection configuration information related to the china mobile, the terminal only needs to modify or replace the stored network selection configuration information related to the china mobile according to the received network selection configuration information.
In the second implementation method, the AMF sends an acceptance message (for example, a registration acceptance message) to the terminal, where the acceptance message includes network selection configuration information and Connection Mode Control Information (CMCI), and the CMCI is used to instruct the terminal to reselect the network after the terminal changes from the connection state to the idle state at a specific time. Subsequently, the terminal can update the network selection configuration information on the terminal according to the received network selection configuration information to obtain the updated network selection configuration information. Then, the terminal can reselect after the terminal is switched from the connected state to the idle state at a specific time according to the CMCI in the acceptance message.
The third implementation method is that the AMF sends an acceptance message (for example, a registration acceptance message) to the terminal, where the acceptance message includes network selection configuration information, then the AMF starts a timer, and after the timer is overtime, the AMF starts a de-registration process of the terminal. Subsequently, the terminal can update the network selection configuration information on the terminal according to the received network selection configuration information to obtain the updated network selection configuration information. Subsequently, the terminal can reselect the network according to the updated network selection configuration information.
The implementation method is fourth, the AMF sends an acceptance message (for example, a registration acceptance message) to the terminal, where the acceptance message includes the network selection configuration information and the confirmation instruction, and then the terminal may update the network selection configuration information on the terminal according to the received network selection configuration information to obtain the updated network selection configuration information. And then according to the confirmation indication, the terminal sends notification information to the AMF, the notification information indicates that the updating of the network selection configuration information is completed, and the AMF starts a de-registration process of the terminal after receiving the notification information from the terminal. Subsequently, the terminal can reselect the network according to the updated network selection configuration information.
It should be noted that the acceptance message or the rejection message may also send the network selection configuration information to the terminal through an additional message without carrying the network selection configuration information. For example, before or after step 304a, the AMF sends a downlink Non Access Stratum (NAS) transport message to the terminal, where the downlink NAS transport message includes the network selection configuration information.
The network selection configuration information may be obtained by the AMF from the UDM. For example, after step 303a, AMF notifies UDM: and the subscription information of the terminal does not support GIN information, and then the UDM sends a subscription update notification message to the AMF, wherein the subscription update notification message comprises the network selection configuration information. The network selection configuration information may be obtained by the UDM from subscription information of the terminal.
According to the above scheme, when the terminal selects the SNPN through the GIN information but the GIN information is invalid, the network element AMF in the core network determines that the subscription information of the terminal does not support the GIN information, and may successfully implement access control on the terminal by, but not limited to, directly rejecting a registration request of the terminal or triggering the terminal to de-register after accepting the registration request of the terminal in the above scheme, so that the terminal may select the correct SNPN. Specifically, after the AMF determines that the subscription information of the terminal does not support the reported GIN information, the AMF notifies the UDM to update the network selection configuration information on the terminal, so that the terminal can select a correct network according to the updated network selection configuration information in the next network selection, thereby realizing access control on the terminal.
The following embodiments of fig. 6 and 7 are two specific examples of the embodiment of fig. 3 (a), and reference may be made to the following detailed description.
Fig. 3 (b) illustrates a wireless communication method provided by an embodiment of the present application, which may be performed by a UDM or a module (e.g., a chip) for the UDM, and the UDM performs the method as an example.
The method comprises the following steps:
in step 301b, the udm receives a first request from the AMF, where the first request includes information GIN information, where the GIN information is a GIN used by the terminal when selecting SNPN or a list of GIN in cell broadcast information of a cell to which the terminal accesses.
The implementation method for obtaining the GIN information by the AMF may refer to the related description in the method embodiment of fig. 3 (a), which is not described herein again.
Step 302b, the udm determines whether the subscription information of the terminal, which includes the prioritized list of preferred GIN controlled by the credential owner CH, supports GIN information.
The UDM may refer to the description in step 303a, which is not described herein again, for determining whether the subscription information of the terminal supports the GIN information.
Step 303b, when the subscription information of the terminal does not support the GIN information, the UDM rejects the first request.
As an implementation method, the first request is a Network Function (NF) registration request, where the NF registration request is used to request to provide a service for the terminal. The UDM rejecting the first request may be: and the UDM sends a NF registration response to the AMF, wherein the NF registration response comprises a cause value, and the cause value is GIN authorization failure or illegal GIN request. Optionally, the NF registration response further includes a registration failure result.
As another implementation method, the first request is a subscription request, and the subscription request is used for requesting to acquire subscription data of the terminal. The UDM rejecting the first request may be: and the UDM sends a signing response to the AMF, wherein the signing response comprises a reason value, and the reason value is a GIN authorization failure or illegal GIN request. Optionally, the subscription response further includes a subscription failure result.
Optionally, the NF registration response or the subscription response further includes network selection configuration information. Or, the UDM sends a subscription update notification to the AMF, where the subscription update notification includes the network selection configuration information. The network selection configuration information may be obtained by the UDM from subscription information of the terminal.
Optionally, the UDM may also send a CMCI to the AMF, where the CMCI is used to instruct the terminal to reselect after the terminal changes from the connected state to the idle state at a specific time. Therefore, the AMF sends the CMCI to the terminal, so that the terminal can reselect the network after the terminal is changed from the connected state to the idle state at a specific time.
It should be noted that, in the following interaction process between the AMF and the terminal, reference may be made to the description of the embodiment of fig. 3 (a). Such as the AMF, sends a reject message or an accept message to the terminal to reject the registration request of the terminal. And the terminal can update the selection configuration information on the terminal according to the network selection configuration information and reselect the network according to the updated network selection configuration information.
According to the above scheme, when the terminal selects the SNPN through the GIN information but the GIN information is invalid, the network element UDM in the core network determines that the subscription information of the terminal does not support the GIN information, and by a method that, in the above scheme, the first request of the AMF is rejected first, and the subsequent AMF knows that the first request is rejected and then can reject the registration request of the terminal, the access control on the terminal is successfully realized, so that the terminal can select the correct SNPN. Specifically, after the UDM determines that the subscription information of the terminal does not support the reported GIN information, the network selection configuration information on the terminal is updated, so that the terminal can select a correct network according to the updated network selection configuration information in the next network selection, thereby realizing access control on the terminal.
Among them, the following embodiments of fig. 4 and fig. 5 are two specific examples of the embodiment of fig. 3 (b), and reference may be made to the following detailed description.
Fig. 3 (c) illustrates a wireless communication method provided in an embodiment of the present application, where the method may be performed by a first network element or a module (e.g., a chip) for the first network element, and the first network element performs the method as an example. Wherein, the first network element may be a UDM or an AUSF.
The method comprises the following steps:
step 301c, the first network element receives an authentication request, where the authentication request includes GIN information, and the GIN information is a GIN used by the terminal when selecting an SNPN, or a GIN list in cell broadcast information of a cell to which the terminal accesses.
For example, when the first network element is a UDM, the UDM may receive the authentication request from the AUSF.
For another example, when the first network element is an AUSF, the AUSF may receive the authentication request from the AMF.
Step 302c, the first network element determines whether the subscription information of the terminal supports the GIN information, where the subscription information of the terminal includes a preferred GIN list controlled by the CH and having a priority.
The first network element determines whether the subscription information of the terminal supports the GIN information, which may refer to the description in step 303a and is not described herein again.
Step 303c, when the subscription information of the terminal does not support the GIN information, the first network element rejects the authentication request.
For example, when the first network element is the UDM, the UDM sends an authentication failure message to the AUSF, where the authentication failure message includes a cause value, and the cause value is a GIN authorization failure or an illegal GIN request.
For another example, when the first network element is an AUSF, the AUSF sends an authentication failure message to the AMF, where the authentication failure message includes a cause value, and the cause value is a GIN authorization failure or an illegal GIN request.
As an implementation method, when the first network element is a UDM, the UDM may further send a subscription update notification to the AMF, where the subscription update notification includes network selection configuration information and/or CMCI. Wherein, the meaning of the network selection configuration information and the CMCI can refer to the foregoing description.
As an implementation method, when the first network element is an AUSF, the AUSF may further notify the UDM: the subscription information of the terminal does not support the GIN information. Therefore, the UDM can send a subscription update notification to the AMF, where the subscription update notification includes the network selection configuration information. Wherein, the meaning of the network selection configuration information can refer to the foregoing description.
It should be noted that, after rejecting the authentication request, the first network element may subsequently notify the AMF to reject the registration request of the terminal, where the registration request is used to request registration to the SNPN. Namely, the first network element informs the AMF of rejecting the terminal to register to the SNPN.
According to the above scheme, when the terminal selects the SNPN through the GIN information, but the GIN information is invalid, and then the network element UDM or AUSF in the core network determines that the terminal subscription information does not support the GIN information in the authentication process of the terminal, the access control of the terminal can be successfully realized by, but not limited to, rejecting the authentication request by the UDM or AUSF and notifying the AMF of rejecting the registration request by the method in the above scheme, so that the terminal can select the correct SNPN. Specifically, after the subscription information of the terminal does not support the reported GIN information, the UDM may update the network selection configuration information on the terminal, so that the terminal may select a correct network according to the updated network selection configuration information in the next network selection, thereby implementing access control on the terminal.
Among them, the following embodiments of fig. 8 and 9 are specific examples of the embodiment of fig. 3 (c), and reference may be made to the following detailed description.
Fig. 4 is a communication method provided in an embodiment of the present application, where the method includes the following steps:
step 401, the amf obtains GIN information of the terminal.
The implementation method for obtaining the GIN information by the AMF may refer to the description in step 302a, and is not described again.
Step 402, authenticating the terminal.
The procedure for authenticating the terminal may refer to the related description in the prior art, such as the description about the terminal authentication procedure in section 6 of 3gpp TS 33.501.
And step 403, the AMF sends a signing request message or an NF registration request message to the UDM, wherein the signing request message or the NF registration request message carries GIN information. Accordingly, the UDM receives the subscription request message.
This step 403 may refer to the description of the step 301b, and the subscription request message or the NF registration request message is a specific example of the first request.
The subscription Request message may be a numm _ SDM _ Get _ Request message. The NF Registration Request message may be a numm UECM Registration Request message.
In step 404, the udm determines whether the subscription information of the terminal supports the reported GIN information.
This step 404 may be as described above with reference to step 302 b.
The specific implementation method for determining whether the subscription information of the terminal supports the reported GIN information by the UDM may refer to the description in step 303a, and is not described again.
In step 405, the udm sends a subscription response message or NF registration response message to the AMF. Accordingly, the AMF receives the subscription response message or the NF registration response message.
This step 405 may refer to the description of step 303b above, that is, the UDM rejects the subscription request message or the NF registration request message through the subscription response message or the NF registration response message.
It should be noted that, when the UDM receives the subscription request message in step 403, the UDM sends a subscription response message in step 405. When the UDM receives the NF registration request message in step 403, the UDM sends an NF registration response message in step 405.
Alternatively, the subscription Response message may be a numm _ SDM _ Get _ Response message. The NF Registration Response message may be a numm UECM Registration Response message.
The subscription response message or the NF registration response message carries network selection configuration information, and optionally, one or more of CMCI, acknowledgement (ACK), or cause value.
The network selection configuration information includes a CH-controlled prioritized preferred SNPN list in the subscription information of the terminal, and optionally, also includes a CH-controlled prioritized preferred GIN list.
The CMCI is used for indicating the terminal to reselect the network after the terminal is converted from the connected state to the idle state at a specific time.
The confirmation indication is used for indicating the terminal to send the notification information after updating the network selection configuration information.
The cause value may be, for example, a GIN authorization failure or an illegal GIN request.
The amf sends a registration response message to the terminal, step 406. Accordingly, the terminal receives the registration response message.
In this step, the AMF rejects the terminal to register to the SNPN requested to be registered by the registration request message through the registration response message.
The registration response message carries network selection configuration information, and optionally, one or more of a CMCI, an acknowledgement indication, or a cause value.
As an implementation method, when the subscription response message or the NF registration response message carries the CMCI, the CMCI may be carried in the registration response message.
As an implementation method, when the subscription response message or the NF registration response message carries a confirmation indication, the registration response message is a registration acceptance message, and the registration acceptance message carries network selection configuration information and the confirmation indication.
As an implementation method, when the subscription response message or the NF registration response message carries a cause value, the AMF rejects the terminal to register to the SNPN requesting registration, where the registration response message is a registration rejection message, and the registration rejection message carries network selection configuration information and the cause value.
As an implementation method, when the subscription response message or the NF registration response message carries a cause value, the AMF may temporarily accept terminal registration, where the registration response message is a registration acceptance message, and the registration acceptance message carries the network selection configuration information, and when the subscription response message or the NF registration response message carries a confirmation indication, the registration acceptance message may also carry the confirmation indication. And, the AMF starts a de-registration flow immediately after sending the registration acceptance message, or starts the de-registration flow when receiving the notification information from the terminal after sending the registration acceptance message, or starts a local timer after sending the registration acceptance message and starts the de-registration flow after the timer is overtime, according to the cause value.
And step 407, the terminal updates the network selection configuration information on the terminal according to the received network selection configuration information.
In step 408, the terminal sends a registration complete message to the AMF. Accordingly, the AMF receives the registration completion message.
Wherein, when the registration response message carries an acknowledgement indication, the step 408 is executed; when the registration response message does not carry an acknowledgement indication, the step 408 is not executed.
Step 409, AMF informs UDM: and finishing updating the network selection configuration information of the terminal.
For example, the AMF sends a Nudm _ SDM _ Info message to the UDM, where the message carries information indicating that updating of the network selection configuration information of the terminal is completed.
If step 408 is executed, the step is executed, and if step 408 is not executed, the step is not executed.
And step 410, the terminal reselects the network according to the updated network selection configuration information.
The specific implementation process of the terminal reselecting the network according to the updated network selection configuration information may refer to the description in step 304a, which is not described herein again.
In the scheme, the AMF acquires GIN information of the terminal, and then the AMF is matched with the UDM to carry out access control on the terminal according to the GIN information. And the UDM judges whether the subscription information of the terminal supports the reported GIN information. The beneficial effects of this scheme can refer to the beneficial effects of the aforementioned embodiment of fig. 3 (b), and are not described again.
Fig. 5 is a communication method provided in an embodiment of the present application, where the method includes the following steps:
reference is made to the above description for steps 501 to 504, and steps 401 to 404.
Step 505, the udm sends a subscription update notification message to the AMF. Accordingly, the AMF receives the subscription update notification message.
Optionally, the subscription update Notification message is a numm _ SDM _ Notification message.
The subscription update notification message carries network selection configuration information, and optionally, also carries a CMCI and/or a confirmation indication.
Wherein, the meanings of the network selection configuration information, the CMCI and the confirmation indication can refer to the foregoing description.
In step 506, the amf sends a downlink NAS transport (NAS transport) message to the terminal. Accordingly, the AMF receives the downlink NAS transport message.
The downlink NAS transport message carries network selection configuration information, and optionally, also carries a CMCI and/or an acknowledgement indication.
And step 507, the terminal updates the network selection configuration information on the terminal according to the received network selection configuration information.
In step 508, the terminal sends an update completion notification message to the AMF. Accordingly, the AMF receives the update completion notification message.
Wherein, when the downlink NAS transport message carries an acknowledgement indication, the step 508 is executed; if the downlink NAS transport message does not carry an acknowledgement indication, the step 508 is not executed.
Optionally, the update completion notification message is an uplink NAS transport message.
Step 509, AMF informs UDM: and finishing updating the network selection configuration information of the terminal.
For example, the AMF sends a Nudm _ SDM _ Info message to the UDM, where the message carries information indicating that the network selection configuration information of the terminal is updated.
If step 508 is executed, the step is executed, and if step 508 is not executed, the step is not executed.
In step 510, the udm sends a subscription response message or NF registration response message to the AMF. Accordingly, the AMF receives the subscription response message or the NF registration response message.
It should be noted that, when the UDM receives the subscription request message in step 503, the UDM sends a subscription response message in step 510. When the UDM receives the NF registration request message in step 503 above, the UDM sends an NF registration response message in step 510.
Alternatively, the subscription Response message may be a numm _ SDM _ Get _ Response message. The NF Registration Response message may be a numm UECM Registration Response message.
Optionally, the subscription response message or the NF registration response message carries a cause value, such as a GIN authorization failure.
In step 511, the amf sends a registration response message to the terminal. Accordingly, the terminal receives the registration response message.
In this step, the AMF rejects the terminal to register to the SNPN requested to be registered by the registration request message through the registration response message.
Optionally, the registration response message carries a cause value.
As an implementation method, when the subscription response message or the NF registration response message carries a cause value, the AMF rejects the terminal registration, the registration response message is a registration rejection message, and the registration rejection message carries the network selection configuration information and the cause value.
As an implementation method, when the subscription response message or the NF registration response message carries a cause value, the AMF may temporarily accept the terminal registration, and the registration response message is a registration acceptance message. And, the AMF starts a de-registration procedure immediately after sending the registration acceptance message, or starts a local timer after sending the registration acceptance message and starts the de-registration procedure after the timer times out, according to the cause value.
And step 512, the terminal reselects the network according to the updated network selection configuration information.
For example, when the registration response message received by the terminal is a registration rejection message, the terminal may trigger to reselect according to the updated network selection configuration information according to the registration rejection message or a cause value in the registration rejection message. For another example, when the downlink NAS transport message received by the terminal carries the CMCI, the terminal changes from the connected state to the idle state at a specific time according to the CMCI, and triggers to reselect the network according to the updated network selection configuration information. For another example, after the network trigger terminal deregisters, the network reselection may be triggered according to the updated network selection configuration information.
The specific implementation process of the terminal reselecting the network according to the updated network selection configuration information may refer to the description in step 304a, which is not described herein again.
In the scheme, the AMF acquires GIN information of the terminal, and then the AMF is matched with the UDM to carry out access control on the terminal according to the GIN information. The main differences between the embodiment of fig. 5 and the embodiment of fig. 4 are: in the embodiment of fig. 5, the UDM updates the network selection configuration information on the terminal before the AMF sends the registration response message to the terminal. The beneficial effects of this scheme can refer to the beneficial effects of the aforementioned embodiment of fig. 3 (b), and are not described again.
Fig. 6 is a communication method according to an embodiment of the present application, where the method includes the following steps:
reference is made to the above description for steps 601 to 602, and steps 401 to 402.
Step 603, the amf sends a subscription request message or NF registration request message to the UDM. Accordingly, the UDM receives the subscription request message or the NF registration request message.
The subscription Request message may be a numm _ SDM _ Get _ Request message. The NF Registration Request message may be a numm UECM Registration Request message.
Step 604, the udm sends a subscription response message or NF registration response message to the AMF. Accordingly, the AMF receives the subscription response message or the NF registration response message.
It should be noted that, when the UDM receives the subscription request message in step 603, the UDM sends a subscription response message in step 604. When the UDM receives the NF registration request message in step 603, the UDM sends an NF registration response message in step 604.
Alternatively, the subscription Response message may be a numm _ SDM _ Get _ Response message. The NF Registration Response message may be a numm UECM Registration Response message.
The subscription response message carries subscription information of the terminal, and the subscription information of the terminal comprises a CH-controlled preferential SNPN list and a CH-controlled preferential GIN list.
Step 605, the amf determines whether the subscription information of the terminal supports the reported GIN information.
The specific implementation of step 605 may refer to the implementation of step 303a, which is not described in detail.
Step 606, AMF informs UDM: the subscription information of the terminal does not support the reported GIN information.
In step 607, the udm sends a subscription update notification message to the AMF. Accordingly, the AMF receives the subscription update notification message.
Optionally, the subscription update Notification message is a Nudm _ SDM _ Notification message.
The subscription update notification message carries network selection configuration information, and optionally, also carries a CMCI and/or a confirmation indication.
Wherein, the meaning of the network selection configuration information CMCI and the confirmation indication can refer to the foregoing description.
Step 608, the amf sends a registration response message to the terminal. Accordingly, the terminal receives the registration response message.
This step 608 may refer to the description of step 304a, that is, the AMF rejects the terminal from registering to the SNPN requested by the registration request message through the registration response message.
The registration response message carries network selection configuration information, and optionally, one or more of a CMCI, an acknowledgement indication, or a cause value.
As an implementation method, when the subscription response message or the NF registration response message carries the CMCI, the CMCI is carried in the registration response message.
As an implementation method, when the subscription response message or the NF registration response message carries a confirmation indication, the registration response message is a registration acceptance message, and the registration acceptance message carries network selection configuration information and the confirmation indication.
As an implementation method, the AMF rejects the terminal registration, the registration response message is a registration rejection message, and the registration rejection message carries the network selection configuration information and the cause value.
As an implementation method, the AMF may temporarily accept terminal registration, where the registration response message is a registration acceptance message, and the registration acceptance message carries the network selection configuration information, where when the subscription response message or the NF registration response message carries the confirmation indication, the registration acceptance message may also carry the confirmation indication. And the AMF starts a de-registration process when receiving the notification information from the terminal after sending the registration acceptance message, or starts a local timer after sending the registration acceptance message and starts the de-registration process after the timer is overtime.
In steps 609 to 612, as well as steps 407 to 410, reference may be made to the above description.
In the scheme, the AMF acquires GIN information of the terminal, and then the AMF is matched with the UDM to carry out access control on the terminal according to the GIN information. And the AMF judges whether the subscription information of the terminal supports the reported GIN information. The beneficial effects of this scheme can refer to the beneficial effects of the embodiment of fig. 3 (a), and are not described again.
Fig. 7 is a communication method according to an embodiment of the present application, where the method includes the following steps:
in steps 701 to 707, as well as steps 601 to 607, reference may be made to the above description.
In steps 708 to 711, as well as in steps 506 to 509, reference may be made to the above description.
Step 712, the amf sends a registration response message to the terminal. Accordingly, the terminal receives the registration response message.
This step 712 may refer to the description of step 304a, that is, the AMF rejects the terminal to register to the SNPN requested by the registration request message through the registration response message.
Optionally, the registration response message carries a cause value.
As an implementation method, the AMF rejects the terminal registration, and the registration response message is a registration rejection message, and the registration rejection message carries the cause value.
As an implementation method, the AMF may temporarily accept the terminal registration, and the registration response message is a registration acceptance message. And, the AMF starts a de-registration procedure immediately after sending the registration accept message, or starts a local timer after sending the registration accept message and starts the de-registration procedure after the timer times out.
Step 713, synchronization step 512, may refer to the foregoing description.
In the scheme, the AMF acquires GIN information of the terminal, and then the AMF is matched with the UDM to carry out access control on the terminal according to the GIN information. The main differences between the embodiment of fig. 7 and the embodiment of fig. 6 are: in the embodiment of fig. 7, the UDM updates the network selection configuration information on the terminal before the AMF sends the registration response message to the terminal. The beneficial effects of this scheme can refer to the beneficial effects of the embodiment of fig. 3 (a), and are not described again.
Fig. 8 is a communication method according to an embodiment of the present application, where a UDM in the method is a first network element in fig. 3 (c). The method comprises the following steps:
step 801, synchronization step 401, can refer to the foregoing description.
Step 802, the AMF sends an authentication request message to the AUSF, wherein GIN information is carried. Accordingly, the AUSF receives the authentication request message.
Optionally, the authentication Request message is a Nausf _ UEAuthentication _ Request message.
And step 803, the AUSF sends an authentication request message to the UDM, wherein the authentication request message carries the GIN information. Accordingly, the UDM receives the authentication request message.
This step 803 can be referred to as described above for step 301 c.
Optionally, the authentication Request message is a numm _ UEAuthentication _ Get _ Request message.
It should be noted that the authentication request message sent by the AUSF to the UDM is two different messages from the authentication request message sent by the AMF to the AUSF.
And step 804, the UDM judges whether the subscription information of the terminal supports the reported GIN information.
For the specific implementation of this step, reference may be made to the description of step 304a, which is not described in detail.
This step 804 may be as described above with reference to step 302 c.
Step 805, the udm sends an authentication failure message to the AUSF, where the authentication failure message carries an authentication failure result and a cause value. Accordingly, the UDM receives the authentication failure message.
This step 805 may be referred to as described above with reference to step 303 c. That is, the UDM rejects the authentication request message sent by the AUSF through the authentication failure message.
Optionally, the authentication failure message is a numm _ UEAuthentication _ Get _ Response message.
The cause value may be, for example, a GIN authorization failure or an illegitimate GIN request.
In step 806, the ausf sends an authentication failure message to the AMF, where the cause value is carried. Accordingly, the AMF receives the authentication failure message.
Optionally, the authentication failure message is a Nausf _ UEAuthentication _ Response message.
Step 807 udm sends a subscription update notification message to AMF. Accordingly, the AMF receives the subscription update notification message.
Optionally, the subscription update Notification message is a numm _ SDM _ Notification message.
The subscription update notification message carries network selection configuration information, and optionally, also carries a CMCI.
The meaning of the network selection configuration information and the CMCI may refer to the foregoing description.
Step 808, the amf sends a downlink NAS transport (NAS transport) message to the terminal. Accordingly, the AMF receives the downlink NAS transport message.
The downlink NAS transport message carries network selection configuration information, and optionally, also carries a CMCI.
This step is optional.
Step 809, the amf sends a registration reject message to the terminal. Accordingly, the AMF receives the registration reject message.
The registration reject message carries a cause value.
As an implementation method, the step 808 is not executed, and the registration rejection message also carries network selection configuration information.
As another implementation method, the step 808 is executed, and the registration rejection message does not carry the network selection configuration information and the CMCI.
And step 810, the terminal updates the network selection configuration information on the terminal according to the received network selection configuration information.
And step 811, the terminal reselects the network according to the updated network selection configuration information.
For example, when the terminal receives the registration rejection message, the terminal may trigger to reselect the network according to the updated network selection configuration information according to the registration rejection message or a cause value in the registration rejection message. For another example, when the terminal receives the CMCI, the terminal changes from the connected state to the idle state at a specific time according to the CMCI, and triggers to reselect the network according to the updated network selection configuration information.
The specific implementation process of the terminal reselecting the network according to the updated network selection configuration information may refer to the description in step 304a, which is not described herein again.
In the scheme, the AMF acquires GIN information of the terminal, and then the AMF is matched with the UDM and the AUSF to carry out access control on the terminal according to the GIN information. And the UDM judges whether the subscription information of the terminal supports the reported GIN information or not in the authentication process. The beneficial effects of this scheme can refer to the beneficial effects of the embodiment of fig. 3 (c), and are not described again.
Fig. 9 is a communication method according to an embodiment of the present application, where an AUSF in the method is a first network element in fig. 3 (c). The method comprises the following steps:
reference is made to the aforementioned descriptions in steps 901 to 902, and steps 801 to 802.
Step 903, the ausf sends an authentication request message to the UDM. Accordingly, the UDM receives the authentication request message.
Optionally, the authentication Request message is a numm _ UEAuthentication _ Get _ Request message.
It should be noted that the authentication request message sent by the AUSF to the UDM is two different messages from the authentication request message sent by the AMF to the AUSF.
And step 904, the UDM sends an authentication response message to the AUSF, wherein the authentication response message carries the subscription information of the terminal. Accordingly, the UDM receives the authentication response message.
Optionally, the authentication Response message is a numm _ UEAuthentication _ Get _ Response message.
And step 905, AUSF judges whether the subscription information of the terminal supports the reported GIN information.
For the specific implementation of this step, reference may be made to the description of step 304a, which is not described again.
This step 905 may be as described above with reference to step 302 c.
Step 906, the AUSF sends authentication failure message to AMF, which carries the cause value. Accordingly, the AMF receives the authentication failure message.
This step 906 may be as described above with reference to step 303c, i.e., the AUSF rejects the authentication request message of the AMF by sending an authentication failure message to the AMF.
Optionally, the authentication failure message is a Nausf _ ue authentication _ Response message.
The cause value may be, for example, a GIN authorization failure or an illegitimate GIN request.
Step 907, ausf informs UDM: the subscription information of the terminal does not support the reported GIN information.
Steps 908 to 912, as well as steps 807 to 811, can be found in reference to the above description.
In the scheme, the AMF acquires GIN information of the terminal, and then the AMF is matched with the UDM and the AUSF to carry out access control on the terminal according to the GIN information. And the AUSF judges whether the subscription information of the terminal supports the reported GIN information in the authentication process. The beneficial effects of this scheme can refer to the beneficial effects of the embodiment of fig. 3 (c), and are not described again.
It is to be understood that, in order to implement the functions in the foregoing embodiments, each of the foregoing devices or network elements includes a corresponding hardware structure and/or software module for performing each function. 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 in hardware or computer software driven hardware depends on the specific application scenario and design constraints of the solution.
Fig. 10 and 11 are schematic structural diagrams of a possible communication device provided in an embodiment of the present application. The communication devices can be used to implement the functions of the terminal, the radio access network device, the AMF, the UDM, or the AUSF in the above method embodiments, and therefore, the advantageous effects of the above method embodiments can also be achieved. In an embodiment of the present application, the communication apparatus may be a terminal, a radio access network device, an AMF, a UDM, or an AUSF as shown in fig. 1 (a) or fig. 1 (b), and may also be a module (e.g., a chip) applied to the terminal, the radio access network device, the AMF, the UDM, or the AUSF.
As shown in fig. 10, the communication apparatus 1000 includes a processing unit 1010 and a transceiver unit 1020. The communication apparatus 1000 is used to implement the functions of the terminal, the radio access network device, the AMF, the UDM or the AUSF in the method embodiments shown in fig. 3 (a), fig. 3 (b), fig. 3 (c), and fig. 4 to fig. 9.
When communications device 1000 is used to implement the functionality of the AMF: a transceiving unit 1020 for receiving a request message from a terminal, the request message requesting registration to the SNPN; a processing unit 1010, configured to acquire GIN information, where the GIN information is a GIN used by the terminal when selecting the SNPN, or a GIN list in cell broadcast information of a cell to which the terminal accesses; judging whether the signing information of the terminal supports the GIN information or not; wherein, the subscription information contains a CH-controlled preferential GIN list with priority; and when the subscription information of the terminal does not support the GIN information, rejecting the terminal to register to the SNPN.
In a possible implementation method, the request message includes a GIN used when the terminal selects the SNPN.
In a possible implementation method, the transceiver 1020 is specifically configured to receive an N2 message from the radio access network device, where the N2 message includes the request message and a GIN used when the terminal selects the SNPN; or receiving an N2 message from the radio access network device, where the N2 message includes the request message and the GIN list in the cell broadcast information.
In a possible implementation method, the transceiver 1020 is further configured to receive subscription information of the terminal from the unified data management network element.
In a possible implementation method, the subscription information of the terminal does not support the GIN information, including: in the case that the GIN information is a GIN used when the terminal selects the SNPN, when the preferred GIN list does not include a GIN used when the terminal selects the SNPN, the subscription information does not support the GIN information; or, in a case where the GIN information is the GIN list in the cell broadcast information, when the preferred GIN list does not include any GIN of the GIN lists in the cell broadcast information, the subscription information does not support the GIN information.
In a possible implementation method, the processing unit 1010 is specifically configured to send a rejection message to the terminal through the transceiving unit 1020, where the rejection message includes a cause value, and the cause value is a GIN authorization failure.
In a possible implementation method, the transceiver 1020 is further configured to send network selection configuration information to the terminal; wherein, the network selection configuration information includes a CH-controlled prioritized preferred SNPN list and the preferred GIN list.
In a possible implementation method, the transceiver unit 1020 is specifically configured to send a downlink NAS transport message to the terminal, where the downlink NAS transport message includes the network selection configuration information.
In a possible implementation method, the processing unit 1010 is specifically configured to send a rejection message to the terminal through the transceiving unit 1020, where the rejection message includes a cause value, and the cause value is a GIN authorization failure; or sending an acceptance message to the terminal, wherein the acceptance message contains connection state control information CMCI, and the CMCI is used for indicating the terminal to reselect the network after the terminal is switched from the connection state to the idle state at a specific time. Wherein, reselecting the network refers to reselecting a network other than the SNPN.
In a possible implementation method, the processing unit is specifically configured to start a timer; and after the timer is overtime, starting a deregistration process of the terminal.
In a possible implementation method, the processing unit 1010 is specifically configured to start a de-registration procedure of the terminal after the transceiver unit 1020 receives notification information from the terminal, where the notification information indicates that the updating of the network selection configuration information is completed.
In a possible implementation method, the transceiving unit 1020 is further configured to notify the unified data management network element to: the contract information of the terminal does not support the GIN information; and receiving the network selection configuration information from the unified data management network element.
When the communication device 1000 is used to implement the functionality of UDM: a transceiver unit 1020, configured to receive a first request from a mobility management network element, where the first request includes information GIN information, where the GIN information is a GIN used when a terminal selects an SNPN, or a GIN list in cell broadcast information of a cell to which the terminal accesses; a processing unit 1010, configured to determine whether the terminal subscription information supports the GIN information, where the terminal subscription information includes a CH-controlled prioritized GIN list; and rejecting the first request when the subscription information of the terminal does not support the GIN information.
In a possible implementation method, the subscription information of the terminal does not support the GIN information, including: in a case where the GIN information is a GIN used when the terminal selects an SNPN, when the preferred GIN list does not include a GIN used when the terminal selects an SNPN, the subscription information does not support the GIN information; or, in case that the GIN information is the GIN list in the cell broadcast information, when the preferred GIN list does not include any GIN in the GIN list in the cell broadcast information, the subscription information does not support the GIN information.
In a possible implementation method, the first request is a network function NF registration request, and the NF registration request is used for requesting to provide a service for the terminal; the processing unit 1010 is specifically configured to send an NF registration response to the mobility management network element through the transceiver unit 1020, where the NF registration response includes a cause value, and the cause value is a GIN authorization failure.
In a possible implementation method, the NF registration response further includes network selection configuration information, where the network selection configuration information includes a CH-controlled prioritized SNPN list and the preferred GIN list.
In a possible implementation method, the first request is a subscription request, and the subscription request is used for requesting to acquire subscription data of the terminal; the processing unit 1010 is specifically configured to send a subscription response to the mobility management network element through the transceiver unit 1020, where the subscription response includes a cause value, and the cause value is a GIN authorization failure.
In a possible implementation method, the subscription response includes network selection configuration information, and the network selection configuration information includes a CH-controlled prioritized preferred SNPN list and the preferred GIN list.
In a possible implementation method, the transceiver 1020 is further configured to send network selection configuration information to the mobility management element, where the network selection configuration information includes a CH-controlled prioritized preferred SNPN list and the preferred GIN list.
In a possible implementation method, the transceiver 1020 is further configured to send connection state control information CMCI to the mobility management element, where the CMCI is used to instruct the terminal to reselect a network after the terminal changes from a connection state to an idle state at a specific time.
When the communication apparatus 1000 is used to implement the functions of a terminal: a transceiver 1020, configured to send an RRC signaling to the radio access network device, where the RRC signaling includes a request message, and the request message is used to request registration to the SNPN; the request message contains GIN information or the RRC signaling contains the GIN information; the GIN information is a GIN used when the terminal selects the SNPN; receiving a response message for rejecting the terminal to register to the SNPN.
In a possible implementation method, the transceiver unit 1020 is further configured to receive network selection configuration information, where the network selection configuration information includes a CH-controlled prioritized preferred SNPN list and a CH-controlled prioritized preferred GIN list.
In a possible implementation method, the transceiver unit 1020 is specifically configured to receive a downlink NAS transport message, where the downlink NAS transport message includes the network selection configuration information.
In a possible implementation method, the processing unit 1010 is configured to update the network selection configuration information according to the network selection configuration information, so as to obtain updated network selection configuration information.
In a possible implementation method, the processing unit 1010 is configured to reselect a network according to the updated network selection configuration information.
In a possible implementation method, the processing unit 1010 is specifically configured to: if the response message is a rejection message, triggering to reselect the network according to the updated network selection configuration information according to the rejection message; or, the response message is a reject message, the reject message contains the reason value, and the reason value is GIN authorization failure, and then network reselection is triggered according to the reason value and the updated network selection configuration information; or, the response message further includes a CMCI, where the CMCI is used to instruct the terminal to reselect a network after the terminal changes from the connected state to the idle state at a specific time, and reselect a network after the terminal changes from the connected state to the idle state at the specific time according to the CMCI; or after deregistration, re-selecting the network according to the updated network selection configuration information.
In one possible implementation method, the response message is a reject message, and the reject message includes a cause value, where the cause value is a GIN authorization failure; alternatively, the response message is an accept message.
When the communications apparatus 1000 is used to implement the functionality of a radio access network device: a transceiver 1020, configured to receive an RRC signaling from a terminal, where the RRC signaling includes a request message, and the request message is used to register to an SNPN; sending GIN information to a mobility management network element; wherein, the GIN information is a GIN used when the terminal selects the SNPN, or a GIN list in cell broadcast information of a cell to which the terminal accesses; and receiving a response message from the mobility management network element, wherein the response message is used for refusing the terminal to register to the SNPN.
In a possible implementation method, the RRC signaling includes a GIN used when the terminal selects the SNPN.
When the communication device 1000 is used to implement the functionality of a first network element (e.g. AUSF or UDM): a transceiving unit 1020, configured to receive an authentication request, where the authentication request includes group identification information GIN information used for network selection, where the GIN information is a GIN used when a terminal selects an SNPN, or a GIN list in cell broadcast information of a cell to which the terminal accesses; a processing unit 1010, configured to determine whether the terminal subscription information supports the GIN information, where the terminal subscription information includes a preferred GIN list controlled by a credential owner CH and having a priority; and when the subscription information of the terminal does not support the GIN information, rejecting the authentication request.
In a possible implementation method, in a case that the GIN information is a GIN used when the terminal selects the SNPN, when the preferred GIN list does not include a GIN used when the terminal selects the SNPN, the subscription information does not support the GIN information; or, in a case where the GIN information is the GIN list in the cell broadcast information, when the preferred GIN list does not include any GIN in the GIN list in the cell broadcast information, the subscription information does not support the GIN information.
In one possible implementation, the first network element is a unified data management network element; a transceiver unit 1020, further configured to select network configuration information and/or CMCI for a mobility management network element; the updated network selection configuration information comprises a CH-controlled preferred SNPN list with priority and the preferred GIN list, and the CMCI is used for indicating the terminal to reselect the network after the terminal is switched from a connected state to an idle state at a specific time. Optionally, a subscription update notification is sent to the mobility management network element, where the subscription update notification includes the network selection configuration information and/or the CMCI.
In a possible implementation method, the transceiver 1020 is configured to receive the authentication request from the authentication network element; and sending an authentication failure message to the authentication network element, wherein the authentication failure message comprises a reason value, and the reason value is GIN authorization failure.
In one possible implementation, the first network element is an authentication network element; the transceiving unit 1020 is further configured to notify the unified data management network element to: the terminal's subscription information does not support the GIN information.
In a possible implementation method, the transceiver 1020 is configured to receive the authentication request from the mobility management element; and sending an authentication failure message to the mobility management network element, wherein the authentication failure message comprises a cause value, and the cause value is GIN authorization failure.
In a possible implementation method, the transceiving unit 1020 is further configured to receive subscription information of the terminal from the unified data management network element.
The more detailed description of the processing unit 1010 and the transceiver unit 1020 can be directly obtained by referring to fig. 3 (a), fig. 3 (b), fig. 3 (c), and the related description in the method embodiments shown in fig. 4 to fig. 9, which are not repeated herein.
As shown in fig. 11, the communication device 1100 includes a processor 1110 and an interface circuit 1120. The processor 1110 and the interface circuit 1120 are coupled to each other. It is understood that the interface circuit 1120 may be a transceiver or an input-output interface. Optionally, the communication device 1100 may further include a memory 1130 for storing instructions to be executed by the processor 1110 or storing input data required by the processor 1110 to execute the instructions or storing data generated by the processor 1110 after executing the instructions.
When the communication apparatus 1100 is used to implement the methods shown in fig. 3 (a), fig. 3 (b), fig. 3 (c), and fig. 4 to fig. 9, the processor 1110 is configured to implement the functions of the processing unit 1010, and the interface circuit 1120 is configured to implement the functions of the transceiver unit 1020.
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.
Fig. 12 provides a schematic diagram of a terminal structure. The terminal is applicable to any of the method embodiments described above. For convenience of explanation, fig. 12 shows only main components of the terminal. As shown in fig. 12, the terminal 1200 includes a processor, a memory, a control circuit, an antenna, and an input-output device. The processor is mainly used for processing communication protocols and communication data, controlling the whole terminal, executing software programs and processing data of the software programs. The memory is primarily used for storing software programs and data. The control circuit is mainly used for converting baseband signals and radio frequency signals and processing the radio frequency signals. The antenna is mainly used for receiving and transmitting radio frequency signals in the form of electromagnetic waves. Input and output devices, such as touch screens, display screens, keyboards, etc., are used primarily for receiving data input by a user and for outputting data to the user.
When the terminal is started, the processor can read the software program in the memory, analyze and execute the instruction of the software program, and process the data of the software program. When data needs to be sent in a wireless mode, the processor carries out baseband processing on the data to be sent and outputs baseband signals to the control circuit, and the control circuit processes the baseband signals to obtain radio frequency signals and sends the radio frequency signals to the outside in the form of electromagnetic waves through the antenna. When data is transmitted to the terminal, the control circuit receives a radio frequency signal through the antenna, the radio frequency signal is further converted into a baseband signal, the baseband signal is output to the processor, and the processor converts the baseband signal into the data and processes the data.
For ease of illustration, fig. 12 shows only one memory and processor. In an actual terminal, there may be multiple processors and memories. The memory may also be referred to as a storage medium or a storage device, and the like, which is not limited in this application.
As an alternative implementation manner, the processor may include a baseband processor and a central processing unit, where the baseband processor is mainly used to process a communication protocol and communication data, and the central processing unit is mainly used to control the whole terminal, execute a software program, and process data of the software program. The processor in fig. 12 integrates the functions of the baseband processor and the central processing unit, and those skilled in the art will understand that the baseband processor and the central processing unit may also be independent processors, and are interconnected through a bus or the like. Those skilled in the art will appreciate that the terminal may include a plurality of baseband processors to accommodate different network formats, the terminal may include a plurality of central processors to enhance its processing capability, and various components of the terminal may be connected by various buses. The baseband processor may also be expressed as a baseband processing circuit or a baseband processing chip. The central processing unit may also be expressed as a central processing circuit or a central processing chip. The function of processing the communication protocol and the communication data may be built in the processor, or may be stored in the memory in the form of a software program, and the processor executes the software program to realize the baseband processing function.
In one example, an antenna and a control circuit having a transceiving function can be considered as the transceiving unit 1211 of the terminal 1200, and a processor having a processing function can be considered as the processing unit 1212 of the terminal 1200. As shown in fig. 12, the terminal 1200 includes a transceiving unit 1211 and a processing unit 1212. A transceiver unit may also be referred to as a transceiver, a transceiving device, etc. Alternatively, a device for implementing a receiving function in the transceiving unit 1211 may be regarded as a receiving unit, and a device for implementing a transmitting function in the transceiving unit 1211 may be regarded as a transmitting unit, that is, the transceiving unit 1211 includes a receiving unit and a transmitting unit. For example, the receiving unit may also be referred to as a receiver, a receiving circuit, etc., and the sending unit may be referred to as a transmitter, a transmitting circuit, etc. Optionally, the receiving unit and the sending unit may be an integrated unit, or may be multiple units independent of each other. The receiving unit and the transmitting unit can be in one geographical position or can be dispersed in a plurality of geographical positions.
Those of ordinary skill in the art will understand that: the various numbers of the first, second, etc. mentioned in this application are only used for the convenience of description and are not used to limit the scope of the embodiments of this application, nor to indicate the order of precedence. "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. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one" means one or more. At least two means two or more. "at least one of, or the like, refers to any combination of these items, including any combination of the singular or plural items. For example, at least one (one ) of a, b, or c, may represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c may be single or multiple. "plurality" means two or more, and other terms are analogous.
It should be understood that, in the various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.
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 above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, 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 instructions. The procedures or functions described in accordance with the embodiments of the application are all or partially generated when the computer program instructions are loaded and executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device including one or more available media integrated servers, data centers, and the like. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a Solid State Disk (SSD)), among others.
The various illustrative logical units and circuits described in this application may be implemented or operated upon by design of a general purpose processor, a digital signal processor, an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other similar configuration.
The steps of a method or algorithm described in the embodiments herein may be embodied directly in hardware, in a software element executed by a processor, or in a combination of the two. The software cells may be stored in Random Access Memory (RAM), flash Memory, read-Only Memory (ROM), EPROM Memory, EEPROM Memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. For example, a storage medium may be coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC.
In one or more exemplary designs, the functions described herein may be implemented in hardware, software, firmware, or any combination of the three. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media that facilitate transfer of a computer program from one place to another. Storage media may be any available media that can be accessed by a general purpose or special purpose computer. For example, such computer-readable media can include, but is not limited to, RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store program code in the form of instructions or data structures and which can be read by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Additionally, any connection is properly termed a computer-readable medium, and, thus, is included if the software is transmitted from a website, server, or other remote source over a coaxial cable, fiber optic computer, twisted pair, digital Subscriber Line (DSL), or wirelessly, e.g., infrared, radio, and microwave. Such discs (disk) and disks (Disc) include compact disks, laser disks, optical disks, digital Versatile Disks (DVD), floppy disks and blu-ray disks, where disks usually reproduce data magnetically, while disks usually reproduce data optically with lasers. Combinations of the above may also be included in the computer-readable medium.

Claims (32)

1. A wireless communication method applied to a mobility management network element, comprising:
receiving a request message from a terminal, wherein the request message is used for requesting registration to an independent deployment non-public network (SNPN);
acquiring group identity GIN information for network selection, wherein the GIN information is a GIN used when the terminal selects the SNPN or a GIN list in cell broadcast information of a cell accessed by the terminal;
judging whether the signing information of the terminal supports the GIN information or not; wherein, the subscription information comprises a preferred GIN list controlled by a certificate owner CH and having priority;
and when the subscription information of the terminal does not support the GIN information, refusing the registration of the terminal to the SNPN.
2. The method of claim 1, wherein the request message comprises a GIN used by the terminal in selecting the SNPN.
3. The method of claim 1, wherein receiving the request message from the terminal comprises:
receiving an N2 message from a wireless access network device, wherein the N2 message comprises the request message and a GIN used by the terminal when the terminal selects the SNPN; alternatively, the first and second liquid crystal display panels may be,
and receiving an N2 message from the wireless access network equipment, wherein the N2 message comprises the request message and the GIN list in the cell broadcast information.
4. The method of any of claims 1 to 3, further comprising:
and receiving subscription information of the terminal from the unified data management network element.
5. The method according to any of claims 1 to 4, wherein the terminal's subscription information does not support the GIN information, comprising:
in a case where the GIN information is a GIN used when the terminal selects the SNPN, when the preferred GIN list does not include a GIN used when the terminal selects the SNPN, the sign information does not support the GIN information; alternatively, the first and second electrodes may be,
in a case where the GIN information is the GIN list in the cell broadcast information, when the preferred GIN list does not include any GIN of the GIN lists in the cell broadcast information, the subscription information does not support the GIN information.
6. The method of any one of claims 1 to 5, wherein said rejecting the terminal to register with the SNPN comprises:
and sending a rejection message to the terminal, wherein the rejection message comprises a reason value, and the reason value is GIN authorization failure.
7. The method of any of claims 1 to 5, further comprising:
sending network selection configuration information to the terminal;
wherein, the network selection configuration information includes a preferred SNPN list and the preferred GIN list controlled by CH and having priority.
8. The method of claim 7, wherein the sending network selection configuration information to the terminal comprises:
and sending a downlink NAS transmission message to the terminal, wherein the downlink NAS transmission message comprises the network selection configuration information.
9. The method of claim 7 or 8, wherein said denying the terminal to register with the SNPN comprises:
sending a rejection message to the terminal, wherein the rejection message comprises a reason value, and the reason value is GIN authorization failure; alternatively, the first and second electrodes may be,
and sending an acceptance message to the terminal, wherein the acceptance message comprises connection state control information CMCI, and the CMCI is used for indicating the terminal to reselect the network after the terminal is converted from the connection state to the idle state at a specific time.
10. The method of claim 7 or 8, wherein said denying the terminal to register with the SNPN comprises:
starting a timer;
and after the timer is overtime, starting a deregistration process of the terminal.
11. The method of claim 7 or 8, wherein said denying the terminal to register with the SNPN comprises:
and after receiving the notification information from the terminal, starting a de-registration process of the terminal, wherein the notification information indicates that the updating of the network selection configuration information is completed.
12. The method of any of claims 7 to 11, further comprising:
and informing the unified data management network element: the contract signing information of the terminal does not support the GIN information;
and receiving the network selection configuration information from the unified data management network element.
13. A wireless communication method applied to a unified data management network element is characterized by comprising the following steps:
receiving a first request from a mobility management network element, wherein the first request comprises group identification information (GIN) information used for network selection, and the GIN information is a GIN used when a terminal selects an SNPN (selective noise network) or a GIN list in cell broadcast information of a cell accessed by the terminal;
judging whether the subscription information of the terminal supports the GIN information or not, wherein the subscription information of the terminal comprises a preferred GIN list with priority controlled by a certificate owner CH;
and when the subscription information of the terminal does not support the GIN information, rejecting the first request.
14. The method of claim 13, wherein the sign-up information of the terminal does not support the GIN information, comprising:
in the case that the GIN information is a GIN used when the terminal selects an SNPN, when the preferred GIN list does not include a GIN used when the terminal selects an SNPN, the subscription information does not support the GIN information; alternatively, the first and second electrodes may be,
in a case where the GIN information is a GIN list in the cell broadcast information, when the preferred GIN list does not include any GIN in the GIN list in the cell broadcast information, the subscription information does not support the GIN information.
15. The method of claim 13 or 14,
the first request is a Network Function (NF) registration request which is used for requesting to provide service for the terminal;
the rejecting the first request comprises:
and sending an NF registration response to the mobility management network element, wherein the NF registration response comprises a cause value, and the cause value is GIN authorization failure.
16. The method of claim 15, further comprising:
the NF registration response also comprises network selection configuration information, and the network selection configuration information comprises a CH-controlled preferential SNPN list and the preferential GIN list.
17. The method of claim 13 or 14,
the first request is a signing request, and the signing request is used for requesting to acquire signing data of the terminal;
said rejecting said first request comprises:
and sending a subscription response to the mobility management network element, wherein the subscription response comprises a reason value, and the reason value is GIN authorization failure.
18. The method of claim 17, wherein said subscription response includes network selection configuration information, said network selection configuration information including a CH controlled prioritized list of preferred SNPNs and said preferred GIN list.
19. The method of any of claims 13 to 15, 17, further comprising:
and sending network selection configuration information to the mobility management network element, wherein the network selection configuration information comprises a CH-controlled preferential SNPN list with priority and the preferential GIN list.
20. The method of any of claims 13 to 19, further comprising:
and sending connection state control information CMCI to the mobility management network element, wherein the CMCI is used for indicating the terminal to reselect the network after the terminal is converted from a connection state to an idle state at a specific time.
21. A wireless communication method applied to a terminal is characterized by comprising the following steps:
sending Radio Resource Control (RRC) signaling to radio access network equipment, wherein the RRC signaling comprises a request message, and the request message is used for requesting registration to an independent deployment non-public network (SNPN); the request message contains Group Identification (GIN) information for network selection or the RRC signaling contains the GIN information; the GIN information is a GIN used when the terminal selects the SNPN;
and receiving a response message, wherein the response message is used for refusing the terminal to register to the SNPN.
22. The method of claim 21, wherein the method further comprises:
receiving network selection configuration information, wherein the network selection configuration information comprises a CH-controlled preferential SNPN list and a CH-controlled preferential GIN list.
23. The method of claim 22, wherein receiving network selection configuration information comprises:
and receiving a downlink NAS transmission message, wherein the downlink NAS transmission message comprises the network selection configuration information.
24. The method of claim 22 or 23, wherein the method further comprises:
and updating the network selection configuration information according to the network selection configuration information to obtain the updated network selection configuration information.
25. The method of claim 24, wherein the method further comprises:
and reselecting the network according to the updated network selection configuration information.
26. The method of claim 25, wherein said reselecting based on said updated network selection configuration information comprises:
if the response message is a rejection message, triggering to reselect the network according to the updated network selection configuration information according to the rejection message; alternatively, the first and second liquid crystal display panels may be,
if the response message is a reject message, and the reject message contains the reason value, and if the reason value is GIN authorization failure, the response message triggers to reselect the network according to the updated network selection configuration information according to the reason value; alternatively, the first and second electrodes may be,
the response message also comprises a CMCI (China Mobile communications interface), and the CMCI is used for indicating the terminal to reselect the network after the terminal is converted from the connection state to the idle state at a specific time, and reselecting the network after the terminal is converted from the connection state to the idle state at the specific time according to the CMCI; alternatively, the first and second liquid crystal display panels may be,
after deregistering, reselecting the network according to the updated network selection configuration information.
27. The method according to one of claims 21 to 25, wherein the response message is a reject message comprising a cause value, the cause value being a GIN authorization failure; alternatively, the first and second electrodes may be,
the response message is an accept message.
28. A wireless communication method applied to a wireless access network device is characterized by comprising the following steps:
receiving Radio Resource Control (RRC) signaling from a terminal, wherein the RRC signaling comprises a request message, and the request message is used for registering to an independent deployment non-public network (SNPN);
sending GIN information to a mobility management network element; wherein the GIN information is a GIN used when the terminal selects the SNPN, or a GIN list in cell broadcast information of a cell to which the terminal accesses;
and receiving a response message from the mobility management network element, wherein the response message is used for refusing the terminal to register to the SNPN.
29. The method of claim 28, further comprising:
the RRC signaling comprises a GIN used when the terminal selects the SNPN.
30. A communications device comprising means for performing a method according to any one of claims 1 to 12, or means for performing a method according to any one of claims 13 to 20, or means for performing a method according to any one of claims 21 to 27, or means for performing a method according to claim 28 or 29.
31. A communications device comprising a processor and interface circuitry for receiving and transmitting signals from or sending signals to other communications devices than the communications device, the processor being configured to implement the method of any one of claims 1 to 12, or to implement the method of any one of claims 13 to 20, or to implement the method of any one of claims 21 to 27, or to implement the method of claim 28 or 29, by logic circuitry or executing code instructions.
32. 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 29.
CN202110502290.XA 2021-05-08 2021-05-08 Wireless communication method and communication device Pending CN115314973A (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202110502290.XA CN115314973A (en) 2021-05-08 2021-05-08 Wireless communication method and communication device
PCT/CN2022/088938 WO2022237516A1 (en) 2021-05-08 2022-04-25 Wireless communication method and communication apparatus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110502290.XA CN115314973A (en) 2021-05-08 2021-05-08 Wireless communication method and communication device

Publications (1)

Publication Number Publication Date
CN115314973A true CN115314973A (en) 2022-11-08

Family

ID=83853828

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110502290.XA Pending CN115314973A (en) 2021-05-08 2021-05-08 Wireless communication method and communication device

Country Status (2)

Country Link
CN (1) CN115314973A (en)
WO (1) WO2022237516A1 (en)

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11006274B2 (en) * 2015-11-30 2021-05-11 Qualcomm Incorporated Service-based network selection
CN109327883B (en) * 2017-07-31 2023-07-14 华为技术有限公司 Method and device for transmitting information

Also Published As

Publication number Publication date
WO2022237516A1 (en) 2022-11-17

Similar Documents

Publication Publication Date Title
US11778044B2 (en) Session establishment method and device
CN116602016A (en) Cell selection method, paging method and device
EP4061024A1 (en) D2d communication method, apparatus and system
CN114007204A (en) Communication selection method and device based on relay communication and direct communication
CN112954768B (en) Communication method, device and system
CN113746649A (en) Network slice control method and communication device
US20240080787A1 (en) Redirection and retry of registration
US20230104162A1 (en) Using dnai to identify a smf supporting connection to a local dn
CN116868603A (en) New method for external parameter provisioning for AF sessions
WO2021088061A1 (en) Communication method and apparatus
CN115314973A (en) Wireless communication method and communication device
CN115244991A (en) Communication method, device and system
CN114642079B (en) Communication method and device
US20240023182A1 (en) Handling the unknown rrc establishment cause value in nr
EP4087316A1 (en) Communication method and apparatus
US20240080651A1 (en) Rvas network function for hplmn
WO2023082858A1 (en) Method for determining mobility management policy, communication apparatus, and communication system
US20240031929A1 (en) Connection Establishment
WO2021088060A1 (en) Communication method and apparatus
GB2621184A (en) Apparatus, method and computer program
CN115988473A (en) Communication method, communication device and communication system
KR20220163439A (en) Initiate network request registration process
CN116249073A (en) Method for multicast/broadcast communication and related device
CN116420427A (en) System and method for UE context management in a side link relay scenario
CN117641472A (en) Communication method and device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination