CN116114315A

CN116114315A - Wireless communication method, terminal equipment and network equipment

Info

Publication number: CN116114315A
Application number: CN202080103767.0A
Authority: CN
Inventors: 卢飞; 刘建华
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2020-11-09
Filing date: 2020-11-09
Publication date: 2023-05-12
Anticipated expiration: 2040-11-09
Also published as: CN116114315B; WO2022095047A1

Abstract

The embodiment of the application provides a wireless communication method, terminal equipment and network equipment, wherein in the process of accessing a rapid configuration network, the terminal equipment can acquire limited information in time, and service except a key and a user identifier required by accessing an SNPN (social network service) is prevented from being tried. The method of wireless communication includes: the terminal equipment receives first information, wherein the first information comprises indication information or rejection reason value; wherein the indication information is used for indicating that the target registration is only used for rapidly configuring the network; the reject cause value is used to indicate a rejection to establish a first PDU session that is not used to acquire configuration service information.

Description

Wireless communication method, terminal equipment and network equipment

Technical Field

The embodiment of the application relates to the field of communication, and more particularly, to a wireless communication method, terminal equipment and network equipment.

Background

In some scenarios, such as office, home, factory, etc., local users or administrators may place local or private networks, such as separate non-public networks (Standalone Non public network, SNPN), for more efficient and secure management. In order to obtain the key and the user identifier for accessing the SNPN network, the terminal device needs to access a fast configuration (onboard) network, such as a PLMN network, and then the configuration server (Provisioning Server) sends the key and the user identifier required for accessing the SNPN network to the terminal device. However, in this process, the terminal device may attempt to acquire services other than the key and the user identifier required for accessing the SNPN network, resulting in unnecessary signaling waste.

Disclosure of Invention

The embodiment of the application provides a wireless communication method, terminal equipment and network equipment, wherein in the process of accessing a rapid configuration network, the terminal equipment can acquire limited information in time, and service except a key and a user identifier required by accessing an SNPN (social network service) is prevented from being tried.

In a first aspect, a method of wireless communication is provided, the method comprising:

the terminal equipment receives first information, wherein the first information comprises indication information or rejection reason value; wherein,

the indication information is used for indicating that the target registration is only used for rapidly configuring the network;

the reject cause value is used to indicate a rejection to establish a first PDU session that is not used to acquire configuration service information.

In a second aspect, there is provided a method of wireless communication, the method comprising:

the network equipment sends first information to the terminal equipment, wherein the first information comprises indication information or reject reason value;

wherein,

In a third aspect, a terminal device is provided for performing the method in the first aspect.

Specifically, the terminal device comprises functional modules for performing the method in the first aspect described above.

In a fourth aspect, a network device is provided for performing the method in the second aspect.

In particular, the network device comprises functional modules for performing the method in the second aspect described above.

In a fifth aspect, a terminal device is provided comprising a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory to execute the method in the first aspect.

In a sixth aspect, a network device is provided that includes a processor and a memory. The memory is for storing a computer program and the processor is for calling and running the computer program stored in the memory for performing the method of the second aspect described above.

In a seventh aspect, there is provided an apparatus for implementing the method of any one of the first to second aspects.

Specifically, the device comprises: a processor for calling and running a computer program from a memory, causing a device in which the apparatus is installed to perform the method of any of the first to second aspects as described above.

In an eighth aspect, a computer-readable storage medium is provided for storing a computer program that causes a computer to execute the method of any one of the first to second aspects.

In a ninth aspect, there is provided a computer program product comprising computer program instructions for causing a computer to perform the method of any one of the first to second aspects above.

In a tenth aspect, there is provided a computer program which, when run on a computer, causes the computer to perform the method of any of the first to second aspects described above.

By adopting the technical scheme, the terminal equipment can know that the target registration is only used for rapidly configuring the network based on the indication information, so that repeated attempts to acquire services except configuration service information (such as a key and a user identifier required for accessing the SNPN network) are avoided after the target registration is completed, and the terminal electricity saving is realized.

Alternatively, the terminal device may establish a PDU session only for acquiring configuration service information (e.g., a key and a user identifier required for accessing the SNPN network) based on the reject cause value, thereby avoiding repeated attempts to acquire services other than the configuration service information (e.g., the key and the user identifier required for accessing the SNPN network) after the target registration is completed, and thus achieving power saving of the terminal.

Drawings

Fig. 1 is a schematic diagram of a communication system architecture to which embodiments of the present application apply.

Fig. 2 is a schematic diagram of a communication system architecture for acquiring configuration server data through a fast configuration network according to an embodiment of the present application.

Fig. 3 is a schematic flow chart of a registration provided herein.

Fig. 4 is a schematic flow chart of a method of wireless communication provided in accordance with an embodiment of the present application.

Fig. 5 is a schematic flow chart diagram provided according to an embodiment of the present application indicating that registration is limited.

Fig. 6 is a schematic flow chart diagram of another indication that registration is limited provided in accordance with an embodiment of the present application.

Fig. 7 is a schematic flow chart diagram of yet another indication that registration is limited provided in accordance with an embodiment of the present application.

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

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

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

Fig. 11 is a schematic block diagram of an apparatus provided according to an embodiment of the present application.

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

Detailed Description

The following description of the technical solutions in the embodiments of the present application will be made with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden for the embodiments herein, are intended to be within the scope of the present application.

The technical solution of the embodiment of the application can be applied to various communication systems, for example: global system for mobile communications (Global System of Mobile communication, GSM), code division multiple access (Code Division Multiple Access, CDMA) system, wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) system, general packet Radio service (General Packet Radio Service, GPRS), long term evolution (Long Term Evolution, LTE) system, long term evolution advanced (Advanced long term evolution, LTE-a) system, new Radio, NR system evolution system, LTE over unlicensed spectrum (LTE-based access to unlicensed spectrum, LTE-U) system, NR over unlicensed spectrum (NR-based access to unlicensed spectrum, NR-U) system, non-terrestrial communication network (Non-Terrestrial Networks, NTN) system, universal mobile telecommunication system (Universal Mobile Telecommunication System, UMTS), wireless local area network (Wireless Local Area Networks, WLAN), wireless fidelity (Wireless Fidelity, wiFi), fifth Generation communication (5 th-Generation, 5G) system, or other communication system, etc.

Generally, the number of connections supported by the conventional communication system is limited and easy to implement, however, with the development of communication technology, the mobile communication system will support not only conventional communication but also, for example, device-to-Device (D2D) communication, machine-to-machine (Machine to Machine, M2M) communication, machine type communication (Machine Type Communication, MTC), inter-vehicle (Vehicle to Vehicle, V2V) communication, or internet of vehicles (Vehicle to everything, V2X) communication, etc., and the embodiments of the present application may also be applied to these communication systems.

Optionally, the communication system in the embodiment of the present application may be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, a dual connectivity (Dual Connectivity, DC) scenario, and a Stand Alone (SA) fabric scenario.

Optionally, the communication system in the embodiments of the present application may be applied to unlicensed spectrum, where unlicensed spectrum may also be considered as shared spectrum; alternatively, the communication system in the embodiments of the present application may also be applied to licensed spectrum, where licensed spectrum may also be considered as non-shared spectrum.

Embodiments of the present application describe various embodiments in connection with network devices and terminal devices, where a terminal device may also be referred to as a User Equipment (UE), access terminal, subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, user Equipment, or the like.

The terminal device may be a STATION (ST) in a WLAN, may be a cellular telephone, a cordless telephone, a session initiation protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) STATION, a personal digital assistant (Personal Digital Assistant, PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle mounted device, a wearable device, a terminal device in a next generation communication system such as an NR network, or a terminal device in a future evolved public land mobile network (Public Land Mobile Network, PLMN) network, etc.

In embodiments of the present application, the terminal device may be deployed on land, including indoor or outdoor, hand-held, wearable or vehicle-mounted; can also be deployed on the water surface (such as ships, etc.); but may also be deployed in the air (e.g., on aircraft, balloon, satellite, etc.).

In the embodiment of the present application, the terminal device may be a Mobile Phone (Mobile Phone), a tablet computer (Pad), a computer with a wireless transceiving function, a Virtual Reality (VR) terminal device, an augmented Reality (Augmented Reality, AR) terminal device, a wireless terminal device in industrial control (industrial control), a wireless terminal device in unmanned driving (self driving), a wireless terminal device in remote medical (remote medical), a wireless terminal device in smart grid (smart grid), a wireless terminal device in transportation security (transportation safety), a wireless terminal device in smart city (smart city), or a wireless terminal device in smart home (smart home), and the like.

By way of example, and not limitation, in embodiments of the present application, the terminal device may also be a wearable device. The wearable device can also be called as a wearable intelligent device, and is a generic name for intelligently designing daily wear by applying wearable technology and developing wearable devices, such as glasses, gloves, watches, clothes, shoes and the like. The wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also can realize a powerful function through software support, data interaction and cloud interaction. The generalized wearable intelligent device includes full functionality, large size, and may not rely on the smart phone to implement complete or partial functionality, such as: smart watches or smart glasses, etc., and focus on only certain types of application functions, and need to be used in combination with other devices, such as smart phones, for example, various smart bracelets, smart jewelry, etc. for physical sign monitoring.

In this embodiment of the present application, the network device may be a device for communicating with a mobile device, where the network device may be an Access Point (AP) in a WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, a relay station or an Access Point, a vehicle device, a wearable device, a network device or a base station (gNB) in an NR network, a network device in a PLMN network of future evolution, or a network device in an NTN network, etc.

By way of example and not limitation, in embodiments of the present application, a network device may have a mobile nature, e.g., the network device may be a mobile device. Alternatively, the network device may be a satellite, a balloon station. For example, the satellite may be a Low Earth Orbit (LEO) satellite, a medium earth orbit (medium earth orbit, MEO) satellite, a geosynchronous orbit (geostationary earth orbit, GEO) satellite, a high elliptical orbit (High Elliptical Orbit, HEO) satellite, or the like. Alternatively, the network device may be a base station disposed on land, in a water area, or the like.

In this embodiment of the present application, a network device may provide a service for a cell, where a terminal device communicates with the network device through a transmission resource (e.g., a frequency domain resource, or a spectrum resource) used by the cell, where the cell may be a cell corresponding to a network device (e.g., a base station), and the cell may belong to a macro base station, or may belong to a base station corresponding to a Small cell (Small cell), where the Small cell may include: urban cells (Metro cells), micro cells (Micro cells), pico cells (Pico cells), femto cells (Femto cells) and the like, and the small cells have the characteristics of small coverage area and low transmitting power and are suitable for providing high-rate data transmission services.

Exemplary, a communication system 100 to which embodiments of the present application apply is shown in fig. 1. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal device 120 (or referred to as a communication terminal, terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminal devices located within the coverage area.

Fig. 1 illustrates one network device and two terminal devices by way of example, and alternatively, the communication system 100 may include a plurality of network devices and may include other numbers of terminal devices within the coverage area of each network device, which is not limited in this embodiment of the present application.

Optionally, the communication system 100 may further include a network controller, a mobility management entity, and other network entities, which are not limited in this embodiment of the present application.

It should be understood that a device having a communication function in a network/system in an embodiment of the present application may be referred to as a communication device. Taking the communication system 100 shown in fig. 1 as an example, the communication device may include a network device 110 and a terminal device 120 with communication functions, where the network device 110 and the terminal device 120 may be specific devices described above, and are not described herein again; the communication device may also include other devices in the communication system 100, such as a network controller, a mobility management entity, and other network entities, which are not limited in this embodiment of the present application.

It should be understood that the terms "system" and "network" are used interchangeably herein. The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.

The terminology used in the description section of the present application is for the purpose of describing particular embodiments of the present application only and is not intended to be limiting of the present application. The terms "first," "second," "third," and "fourth" and the like in the description and in the claims of this application and in the drawings, are used for distinguishing between different objects and not for describing a particular sequential order. Furthermore, the terms "comprise" and "have," as well as any variations thereof, are intended to cover a non-exclusive inclusion.

It should be understood that, in the embodiments of the present application, the "indication" may be a direct indication, an indirect indication, or an indication having an association relationship. For example, a indicates B, which may mean that a indicates B directly, e.g., B may be obtained by a; it may also indicate that a indicates B indirectly, e.g. a indicates C, B may be obtained by C; it may also be indicated that there is an association between a and B.

In the description of the embodiments of the present application, the term "corresponding" may indicate that there is a direct correspondence or an indirect correspondence between the two, or may indicate that there is an association between the two, or may indicate a relationship between the two and the indicated, configured, or the like.

In the description of embodiments of the present application, the term "information" may have the same meaning as "message" and in some scenarios, the two terms may be interchanged.

In the embodiment of the present application, the "predefining" may be implemented by pre-storing corresponding codes, tables or other manners that may be used to indicate relevant information in devices (including, for example, terminal devices and network devices), and the specific implementation of the present application is not limited. Such as predefined may refer to what is defined in the protocol.

In this embodiment of the present application, the "protocol" may refer to a standard protocol in the communication field, for example, may include an LTE protocol, an NR protocol, and related protocols applied in a future communication system, which is not limited in this application.

For a better understanding of the embodiments of the present application, the SNPN network related to the present application will be described.

End users may conduct data traffic over a public network (i.e., PLMN), but in some scenarios, such as office scenarios, home scenarios, factories, there may be local users or administrators who place local or private networks for more efficient and secure management.

The network elements in the non-public network (Non public network, NPN) network may exist independent of the PLMN network, i.e. the NPN network has a policy control function (Policy Control function, PCF) entity, session management function (Session Management Function, SMF) entity, access and mobility management function (Access and Mobility Management Function, AMF) entity, unified data management (Unified Data Management, UDM) entity, etc., and the NPN network has its own root key, security algorithm, subscription information, policy information, etc. to achieve isolation from the public network (PLMN).

The key of the fast configuration (onboard) network and/or the user identifier of the access fast configuration (onboard) network may be preconfigured on the terminal device, but the terminal device does not have the key and the user identifier of the access SNPN network. In order to obtain the key and the user identifier for accessing the SNPN network, the terminal device needs to access the rapid configuration (onboard) network, and then the configuration server (Provisioning Server) sends the key and the user identifier required for accessing the SNPN network to the terminal device. After the terminal equipment obtains the secret key and the user identifier sent by the configuration server, the terminal equipment can perform normal access of the SNPN network. The onboard network may also be a PLMN network, so that the terminal device directly obtains, through the PLMN network, a key and a user identifier required for accessing the SNPN network sent by the configuration server.

Specifically, as shown in fig. 2, the configuration server is connected to a UDM entity in the PLMN network through a Nps interface, and the default key server (Default Credential Server, DCS) entity is connected to an authentication server function (Authentication Server Function, AUSF) entity in the PLMN network through an Ndcs interface. In addition, AS shown in fig. 2, in the PLMN Network, the UE performs Access Stratum (AS) connection with AN Access Network (AN) device through a Uu interface to exchange Access Stratum messages and wireless data transmission, and performs Non-Access Stratum (NAS) connection with AN AMF entity through AN N1 interface to exchange NAS messages; the AN equipment is connected with the AMF entity through AN N2 interface, and the AN equipment is connected with a user plane function (User Plane Function, UPF) entity through AN N3 interface; the UPF entities are connected through an N9 interface, the UPF entities are connected with a Data Network (DN) through an N6 interface, and meanwhile, the UPF entities are connected with the SMF entities through an N4 interface; the SMF entity is connected with the PCF entity through an N7 interface, the SMF entity is connected with the UDM entity through an N10 interface, the SMF entity controls the UPF entity through an N4 interface, and meanwhile, the SMF entity is connected with the AMF entity through an N11 interface; the AMF entities are connected through an N14 interface, the AMF entity is connected with the UDM entity through an N8 interface, the AMF entity is connected with the AUSF entity through an N12 interface, the AMF entity is connected with a network slice selection function (Network Slice Selection Function, NSSF) entity through an N22 interface, and meanwhile, the AMF entity is connected with the PCF entity through an N15 interface; the PCF entity is connected with an application function (Application Function, AF) entity through an N5 interface; the AUSF entity is connected to the UDM entity through an N13 interface.

The AN device may be a radio access network (Radio Access Network, RAN) device, and the PCF entity may be a visited PCF (vcpcf) entity, which is not limited in this application.

The UDM entity is a subscription database in the core network, storing subscription data of users in the 5G network. The AMF entity is a mobility management function in the core network, the SMF entity is a session management function in the core network, and the AMF entity is responsible for forwarding session management related messages between the UE and the SMF entity in addition to mobility management of the UE. The PCF entity is a policy management function in the core network, and is responsible for formulating policies related to mobility management, session management, charging, etc. for the UE. The UPF entity is a user plane function in the core network, performs data transmission with AN external data network through AN N6 interface, and performs data transmission with AN AN device through AN N3 interface. After the UE accesses the 5G network through the Uu port, a protocol data unit (Protocol Data Unit, PDU) session data connection from the UE to the UPF entity is established under the control of the SMF entity, so as to perform data transmission. The AMF entity and the SMF entity respectively acquire user subscription data from the UDM entity through N8 and N10 interfaces, and acquire policy data from the PCF entity through N15 and N7 interfaces.

It should be noted that, the respective network elements in fig. 2 may also have other specific functions, which are not limited in this application.

For better understanding of the embodiments of the present application, a flow of sending configuration service information by the configuration server related to the present application is described, and a specific flow is S0-1 to S0-12 shown in fig. 3.

S0-1, the UE sends registration request information to an AMF entity in a PLMN network, wherein the registration request information carries a user identifier and a registration type, and the registration type can be set as initial registration;

s0-2, the AMF entity performs an authentication process on the UE and acquires user subscription data of the UE from the UDM entity;

s0-3, the UDM entity sends user subscription data to the AMF entity and indicates that the user subscription data is default data and can only be used for quick configuration (onboard);

s0-4, the AMF entity sends registration acceptance information to the UE, wherein the registration acceptance information carries a 5G global unique temporary terminal identifier (5G Globally Unique Temporary UE Identity,5G-GUTI) and a registration area which are distributed by the AMF entity for the UE;

s0-5, the UE returns registration completion information to the AMF entity to confirm that the allocated 5G-GUTI is valid;

s0-6, the UE initiates a PDU session establishment process, so that the configuration server can send configuration service information (keys and user identifications required by accessing the SNPN network) to the UE through a user plane; the configuration server may also send configuration service information directly through the control plane, and if the configuration service information is sent through the control plane, this step may not be executed;

S0-7, the configuration server sends configuration service information to the UDM entity, wherein the configuration service information carries a key and a user identifier required by the UE to access the SNPN network;

s0-8, the UDM entity returns confirmation information to the configuration server;

s0-9, the UDM entity sends the received configuration service information to an AMF entity;

s0-10, the AMF entity sends downlink NAS transmission information to the UE, wherein the downlink NAS transmission information carries the configuration service information;

s0-11, the UE sends uplink NAS transmission information to the AMF entity, wherein the uplink NAS transmission information carries acknowledgement information of the UE aiming at the configuration service information;

s0-12, the AMF entity returns the confirmation information of the UE aiming at the configuration service information to the UDM entity.

Since the user subscription data sent from the UDM entity to the AMF entity in S0-3 is only used for onboard, but the UE cannot perceive the limited information, when the UE requests to perform other services, the network side needs to reject, but the UE still retries other services, which causes unnecessary signaling waste, the network side needs to process the unnecessary signaling, and the UE side also causes resource waste and unnecessary power consumption.

Based on the above problems, the present application proposes a registration scheme, in which, during the process of accessing a rapid configuration network, a terminal device can timely learn limited information, so as to avoid attempting to acquire services other than a key and a user identifier required for accessing an SNPN network.

The technical scheme of the present application is described in detail below through specific embodiments.

Fig. 4 is a schematic flow chart of a method 200 of wireless communication according to an embodiment of the present application, as shown in fig. 4, the method 200 may include at least some of the following:

s210, the network equipment sends first information to the terminal equipment, wherein the first information comprises indication information or rejection reason value; wherein the indication information is used for indicating that the target registration is only used for rapidly configuring the network; the reject cause value is used for indicating that the establishment of a first PDU session is refused, and the first PDU session is not used for acquiring configuration service information;

s220, the terminal equipment receives the first information.

In the embodiment of the application, the network device may send the limited information (the indication information or the reject cause value) for the target registration to the terminal device, so that in the target registration, the terminal device may only achieve the purpose of rapidly configuring the network, or the terminal device only establishes a PDU session for acquiring the configuration service information. The terminal device can be prevented from attempting to acquire services other than the key and the user identification required for accessing the SNPN network.

That is, the network device may inform the terminal device that the target registration is only for the fast configuration network by rejecting the procedure of normal PDU session (first PDU session) establishment.

The network device may be, for example, an AMF entity, but may also be some other network element, such as an access network device.

Optionally, the network device obtains user subscription data of the terminal device, where the user subscription data is only used for rapidly configuring network usage. For example, the user subscription data is default data. In this case, the network device transmits the first information to the terminal device. That is, the network device acquires the user subscription data of the terminal device before transmitting the first information.

Optionally, in some embodiments, in the case that the first information includes the reject cause value, the reject cause value is targeted for registration only for fast configuration of the network.

Optionally, in case the first information includes the reject cause value, after the target registration is completed and before the terminal device receives the first information, the terminal device sends second information to the network device, the second information being used for requesting to establish the first PDU session. Accordingly, the network device determines, according to the first PDU session, that the reject cause value is targeted for registration only for fast configuration of the network.

That is, after the target registration is completed, the terminal device initiates the establishment of the first PDU session since the terminal device does not learn the limited information in time (the target registration is only used for fast configuration of the network).

Optionally, at least one of the following may be carried in the second information:

the terminal device allocates a PDU session identification (Identity, ID) for the first PDU session, single network slice assistance information (Single-Network Slice Selection Assistance Information, S-NSSAI), data network name (Data Network Name, DNN) information, and request type (request type set as initial request), and a PDU session establishment request message (for requesting establishment of the first PDU session).

Alternatively, in the embodiment of the present application, the terminal device may establish a PDU session for acquiring the configuration service information according to the first information.

Optionally, in some embodiments, the terminal device releases the established at least one PDU session, which is not used for acquiring the configuration service information. That is, since the target registration is only used for configuring the network quickly, the network device cannot meet the traffic requirements of the established at least one PDU session in this case.

Optionally, the configuration service information includes at least a key and a user identification required for accessing the SNPN. That is, the terminal device may obtain the key and the user identifier required for accessing the SNPN from the configuration service information, so that the SNPN may be accessed normally.

Optionally, in some embodiments, in a case where the first information includes the indication information, the first information is registration acceptance information for the target registration, or the first information configures the indication information for a terminal received after the target registration is completed. That is, in the case where the first information includes the indication information, the indication information may be carried in registration acceptance information for the target registration, or the indication information may be carried in terminal configuration indication information received by the terminal device after the target registration is completed.

Registration schemes in the examples of the present application are described in detail below by examples 1 to 3.

In embodiment 1, a network device (such as an AMF entity) may send registration accept information to a terminal device (UE), where the registration accept information includes indication information, where the indication information is used to indicate that target registration is only used for a fast configuration (onboard) network, and may be specifically implemented through flows S1-1 to S1-6 as shown in fig. 5.

S1-1, UE sends registration request information to an AMF entity, wherein the registration request information is used for requesting to realize target registration, the registration request information carries a user identifier and a registration type, and the registration type can be set as initial registration;

S1-2, an AMF entity performs an authentication process on the UE and acquires user subscription data of the UE from a UDM entity;

s1-3, the UDM entity sends user subscription data to the AMF entity and indicates that the user subscription data is default data and can only be used for quick configuration (onboard);

s1-4, an AMF entity sends registration acceptance information to UE, wherein the registration acceptance information carries 5G-GUTI and a registration area distributed by the AMF entity for the UE; in addition, the registration acceptance information also carries indication information, wherein the indication information is used for indicating that the target registration is only used for a quick configuration (onboard) network; the indication information may be carried in the registration result; after receiving the indication information, the UE can only establish PDU session for obtaining configuration service information;

s1-5, the UE returns registration completion information to the AMF entity to confirm that the allocated 5G-GUTI is valid;

s1-6, the UE initiates a process of establishing a PDU session, wherein the PDU session is used for acquiring configuration service information; so that the configuration server can send configuration service information (keys and user identifications required for accessing the SNPN network) to the UE through the user plane; the configuration server may also send configuration service information directly through the control plane, and this step may not be performed if the configuration service information is sent through the control plane.

The subsequent steps may be described with reference to fig. 3, and are not described herein.

In embodiment 2, a network device (such as an AMF entity) may send downlink NAS transport information to a terminal device (UE), where the downlink NAS transport information includes a reject cause value, where the reject cause value is used for target registration only for fast configuration of a network, and the reject cause value is used to indicate that establishment of a first PDU session is rejected, and the first PDU session is not used to acquire configuration service information, which may be specifically implemented through flows S2-1 to S2-7 as shown in fig. 6.

S2-1, the UE sends registration request information to an AMF entity, wherein the registration request information is used for requesting to realize target registration, the registration request information carries a user identifier and a registration type, and the registration type can be set as initial registration;

s2-2, the AMF entity performs an authentication process on the UE and acquires user subscription data of the UE from the UDM entity;

s2-3, the UDM entity sends user subscription data to the AMF entity and indicates that the user subscription data is default data and can only be used for quick configuration (onboard);

s2-4, the AMF entity sends registration acceptance information to the UE, wherein the registration acceptance information carries 5G-GUTI and a registration area distributed by the AMF entity for the UE;

s2-5, the UE returns registration completion information to the AMF entity to confirm that the allocated 5G-GUTI is valid;

S2-6, the UE initiates a PDU session establishment process for establishing a first PDU session, wherein the first PDU session is not used for acquiring configuration service information; specifically, the UE sends uplink NAS transport information to the AMF entity, where the uplink NAS transport information carries a PDU session ID, S-nsai, DNN information, a request type (the request type is set as an initial request), and a PDU session establishment request message allocated by the UE for the first PDU session;

s2-7, the AMF entity verifies whether the first PDU session is used for quick configuration (onboard) and is used for acquiring configuration service information, and after verification, the first PDU session is used for normal service, the AMF entity returns downlink NAS transmission information to the UE, the downlink NAS transmission information carries a rejection reason value, the rejection reason value is used for target registration only for quick configuration network, and the rejection reason value is used for indicating rejection to establish the first PDU session; after the UE receives the reject cause value, it can only establish a PDU session for acquiring configuration service information.

In embodiment 3, the network device (such as the AMF entity) may send, after the target registration is completed, terminal configuration indication information to the terminal device (UE), where the terminal configuration indication information includes indication information, where the indication information is used to indicate that the target registration is only used for configuring the fast configuration (onboard) network, and may be specifically implemented through the flows S3-1 to S3-7 as shown in fig. 7.

S3-1, the UE sends registration request information to an AMF entity, wherein the registration request information is used for requesting to realize target registration, the registration request information carries a user identifier and a registration type, and the registration type can be set as initial registration;

s3-2, the AMF entity performs an authentication process on the UE and acquires user subscription data of the UE from the UDM entity;

s3-3, the UDM entity sends the user subscription data to the AMF entity, and optionally, the UDM entity indicates that the user subscription data is default data and can only be used for quick configuration (onboard);

s3-4, the AMF entity sends registration acceptance information to the UE, wherein the registration acceptance information carries 5G-GUTI and a registration area distributed by the AMF entity for the UE;

s3-5, the UE returns registration completion information to the AMF entity to confirm that the allocated 5G-GUTI is valid;

s3-6, if the UDM entity does not indicate that the user subscription data is default data in S3-3, the method can only be used for quick configuration (onboard), and when the user subscription data is changed, the UDM entity sends updated user subscription data to the AMF entity, and the UDM entity indicates that the updated user subscription data is default data, and the method can only be used for quick configuration (onboard); in this case, the AMF entity transmits terminal configuration indication information to the UE, the terminal configuration indication information including indication information for indicating that the target registration is only for a fast configuration (onboard) network; after receiving the indication information, the UE can only establish PDU session for obtaining configuration service information (key and user identifier required for accessing SNPN network), and release other PDU session locally;

S3-7, the UE returns terminal configuration completion information to the AMF entity.

Therefore, in the embodiment of the application, the terminal device can know that the target registration is only used for rapidly configuring the network based on the indication information, so that repeated attempts to acquire services except for configuration service information (such as a key and a user identifier required for accessing the SNPN network) are avoided after the target registration is completed, and power saving of the terminal is realized.

Alternatively, in the embodiment of the present application, the terminal device may establish a PDU session only for acquiring configuration service information (such as a key and a user identifier required for accessing the SNPN network) based on the reject cause value, so that, after the target registration is completed, repeated attempts to acquire services other than the configuration service information (such as the key and the user identifier required for accessing the SNPN network) are avoided, thereby realizing power saving of the terminal.

The method embodiments of the present application are described in detail above with reference to fig. 4 to 7, and the apparatus embodiments of the present application are described in detail below with reference to fig. 8 to 12, it being understood that the apparatus embodiments and the method embodiments correspond to each other, and similar descriptions may refer to the method embodiments.

Fig. 8 shows a schematic block diagram of a terminal device 300 according to an embodiment of the present application. As shown in fig. 8, the terminal device 300 includes:

A communication unit 310 for receiving first information including indication information or reject cause value; wherein,

the reject cause value is used to indicate a rejection to establish a first protocol data unit, PDU, session that is not used to obtain configuration service information.

Optionally, in case the first information comprises the reject cause value, the reject cause value is registered for the target only for fast configuration of the network.

Optionally, after the target registration is completed and before receiving the first information, the communication unit 310 is further configured to send second information, where the second information is used to request to establish the first PDU session.

Optionally, the terminal device 300 further includes:

a processing unit 320, configured to establish a PDU session for acquiring configuration service information according to the first information.

Optionally, the terminal device 300 further includes:

the processing unit 320 is configured to release the established at least one PDU session, which is not used for acquiring the configuration service information.

Optionally, in the case that the first information includes the indication information, the first information is registration acceptance information for the target registration, or the first information configures the indication information for the terminal received after the target registration is completed.

Optionally, the configuration service information includes at least a key and a user identification required to access the independent non-public network SNPN.

Alternatively, in some embodiments, the communication unit may be a communication interface or transceiver, or an input/output interface of a communication chip or a system on a chip. The processing unit may be one or more processors.

It should be understood that the terminal device 300 according to the embodiment of the present application may correspond to the terminal device in the embodiment of the method of the present application, and the foregoing and other operations and/or functions of each unit in the terminal device 300 are respectively for implementing the corresponding flow of the terminal device in the method 200 shown in fig. 4, which is not described herein for brevity.

Fig. 9 shows a schematic block diagram of a network device 400 according to an embodiment of the present application. As shown in fig. 9, the network device 400 includes:

a communication unit 410 for transmitting first information to the terminal device, the first information including indication information or reject cause value;

wherein,

Optionally, the network device further comprises: a processing unit 420, wherein,

after the target registration is completed and before the first information is sent, the communication unit 410 is further configured to receive second information sent by the terminal device, where the second information is used to request to establish the first PDU session;

the processing unit 420 is configured to determine, based on the first PDU session, that the reject cause value is targeted for registration only for fast configuration of the network.

Optionally, the communication unit 410 is further configured to obtain user subscription data of the terminal device, where the user subscription data is only used for rapidly configuring network usage.

Optionally, the user subscription data is default data.

Optionally, in the case that the first information includes the indication information, the first information is registration acceptance information for the target registration, or the first information is terminal configuration indication information sent after the target registration is completed.

It should be understood that the network device 400 according to the embodiment of the present application may correspond to the network device in the embodiment of the method of the present application, and the foregoing and other operations and/or functions of each unit in the network device 400 are respectively for implementing the corresponding flow of the network device in the method 200 shown in fig. 4, and are not further described herein for brevity.

Fig. 10 is a schematic structural diagram of a communication device 500 provided in an embodiment of the present application. The communication device 500 shown in fig. 10 comprises a processor 510, from which the processor 510 may call and run a computer program to implement the method in the embodiments of the present application.

Optionally, as shown in fig. 10, the communication device 500 may further comprise a memory 520. Wherein the processor 510 may call and run a computer program from the memory 520 to implement the methods in embodiments of the present application.

Wherein the memory 520 may be a separate device from the processor 510 or may be integrated into the processor 510.

Optionally, as shown in fig. 10, the communication device 500 may further include a transceiver 530, and the processor 510 may control the transceiver 530 to communicate with other devices, and in particular, may send information or data to other devices, or receive information or data sent by other devices.

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

Optionally, the communication device 500 may be specifically a network device in the embodiment of the present application, and the communication device 500 may implement a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the communication device 500 may be specifically a mobile terminal/terminal device in the embodiment of the present application, and the communication device 500 may implement a corresponding flow implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein for brevity.

Fig. 11 is a schematic structural view of an apparatus of an embodiment of the present application. The apparatus 600 shown in fig. 11 includes a processor 610, and the processor 610 may call and run a computer program from a memory to implement the methods in the embodiments of the present application.

Optionally, as shown in fig. 11, the apparatus 600 may further comprise a memory 620. Wherein the processor 610 may call and run a computer program from the memory 620 to implement the methods in embodiments of the present application.

The memory 620 may be a separate device from the processor 610 or may be integrated into the processor 610.

Optionally, the apparatus 600 may further comprise an input interface 630. The processor 610 may control the input interface 630 to communicate with other devices or chips, and in particular, may acquire information or data sent by the other devices or chips.

Optionally, the apparatus 600 may further comprise an output interface 640. Wherein the processor 610 may control the output interface 640 to communicate with other devices or chips, and in particular, may output information or data to other devices or chips.

Optionally, the apparatus may be applied to a network device in the embodiments of the present application, and the apparatus may implement a corresponding flow implemented by the network device in each method in the embodiments of the present application, which is not described herein for brevity.

Optionally, the apparatus may be applied to a mobile terminal/terminal device in the embodiment of the present application, and the apparatus may implement a corresponding flow implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein for brevity.

Alternatively, the device mentioned in the embodiments of the present application may also be a chip. For example, a system-on-chip or a system-on-chip, etc.

Fig. 12 is a schematic block diagram of a communication system 700 provided in an embodiment of the present application. As shown in fig. 12, the communication system 700 includes a terminal device 710 and a network device 720.

The terminal device 710 may be configured to implement the corresponding functions implemented by the terminal device in the above method, and the network device 720 may be configured to implement the corresponding functions implemented by the network device in the above method, which are not described herein for brevity.

It should be appreciated that the processor of an embodiment of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The processor may be a general purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in hardware, in a decoded processor, or in a combination of hardware and software modules in a decoded processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.

It will be appreciated that the memory in embodiments of the present application may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (Double Data Rate SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and Direct RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

It should be understood that the above memory is exemplary but not limiting, and for example, the memory in the embodiments of the present application may be Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), direct RAM (DR RAM), and the like. That is, the memory in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

Embodiments of the present application also provide a computer-readable storage medium for storing a computer program.

Optionally, the computer readable storage medium may be applied to a network device in the embodiments of the present application, and the computer program causes a computer to execute a corresponding flow implemented by the network device in each method in the embodiments of the present application, which is not described herein for brevity.

Optionally, the computer readable storage medium may be applied to a mobile terminal/terminal device in the embodiments of the present application, and the computer program causes a computer to execute a corresponding procedure implemented by the mobile terminal/terminal device in each method of the embodiments of the present application, which is not described herein for brevity.

Embodiments of the present application also provide a computer program product comprising computer program instructions.

Optionally, the computer program product may be applied to a network device in the embodiments of the present application, and the computer program instructions cause the computer to execute corresponding flows implemented by the network device in the methods in the embodiments of the present application, which are not described herein for brevity.

Optionally, the computer program product may be applied to a mobile terminal/terminal device in the embodiments of the present application, and the computer program instructions cause a computer to execute corresponding processes implemented by the mobile terminal/terminal device in the methods in the embodiments of the present application, which are not described herein for brevity.

The embodiment of the application also provides a computer program.

Optionally, the computer program may be applied to a network device in the embodiments of the present application, and when the computer program runs on a computer, the computer is caused to execute a corresponding flow implemented by the network device in each method in the embodiments of the present application, which is not described herein for brevity.

Optionally, the computer program may be applied to a mobile terminal/terminal device in the embodiments of the present application, where the computer program when run on a computer causes the computer to execute corresponding processes implemented by the mobile terminal/terminal device in the methods in the embodiments of the present application, and for brevity, will not be described herein.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

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

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. For such understanding, the technical solutions of the present application may be embodied in essence or in a part contributing to the prior art or in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

A method of wireless communication, comprising:

the terminal equipment receives first information, wherein the first information comprises indication information or rejection reason values; wherein,

the indication information is used for indicating that the target registration is only used for rapidly configuring the network;

the reject cause value is used to indicate a rejection to establish a first protocol data unit, PDU, session that is not used to obtain configuration service information.
The method of claim 1, wherein the reject cause value is targeted for registration only for fast configuration of a network in the case that the first information includes the reject cause value.
The method of claim 2, wherein the method further comprises:

after the target registration is completed and before receiving the first information, the terminal device sends second information, where the second information is used to request to establish the first PDU session.
A method according to any one of claims 1 to 3, wherein the method further comprises:

and the terminal equipment establishes a PDU session for acquiring configuration service information according to the first information.
The method of any one of claims 1 to 4, wherein the method further comprises:

the terminal device releases the established at least one PDU session, which is not used for acquiring configuration service information.
The method according to any one of claims 1 to 5, wherein in the case where the first information includes the indication information, the first information is registration acceptance information for the target registration or the first information is terminal configuration indication information received after completion of the target registration.
The method according to any of claims 1 to 6, wherein the configuration service information comprises at least a key and a user identity required for accessing an independent non-public network, SNPN.
A method of wireless communication, comprising:

the network equipment sends first information to the terminal equipment, wherein the first information comprises indication information or rejection reason value;

Wherein,

the indication information is used for indicating that the target registration is only used for rapidly configuring the network;

the reject cause value is used to indicate a rejection to establish a first protocol data unit, PDU, session that is not used to obtain configuration service information.
The method of claim 8, wherein the reject cause value is targeted for registration only for fast configuration of a network if the first information includes the reject cause value.
The method of claim 9, wherein the method further comprises:

after the target registration is completed and before the first information is sent, the network equipment receives second information sent by the terminal equipment, wherein the second information is used for requesting to establish the first PDU session;

the network device determines that the rejection cause value is targeted for registration only for rapidly configuring a network according to the first PDU session.
The method of any one of claims 8 to 10, wherein the method further comprises:

the network device obtains user subscription data of the terminal device, wherein the user subscription data is only used for rapidly configuring network use.
The method of claim 11, wherein the user subscription data is default data.
The method according to any one of claims 8 to 12, wherein in the case where the first information includes the indication information, the first information is registration acceptance information for the target registration, or the first information is terminal configuration indication information transmitted after completion of the target registration.
The method according to any of claims 8 to 13, wherein the configuration service information comprises at least a key and a user identity required for accessing an independent non-public network, SNPN.
A terminal device, comprising:

a communication unit configured to receive first information including indication information or a reject cause value; wherein,

the indication information is used for indicating that the target registration is only used for rapidly configuring the network;

the reject cause value is used to indicate a rejection to establish a first protocol data unit, PDU, session that is not used to obtain configuration service information.
The terminal device of claim 15, wherein the reject cause value is a target registration only for fast configuration of a network in the case that the first information includes the reject cause value.
The terminal device of claim 16, wherein,

after the target registration is completed and before receiving the first information, the communication unit is further configured to send second information, where the second information is used to request establishment of the first PDU session.
The terminal device according to any of the claims 15 to 17, wherein the terminal device further comprises:

and the processing unit is used for establishing a PDU session for acquiring the configuration service information according to the first information.
The terminal device according to any of the claims 15 to 18, wherein the terminal device further comprises:

a processing unit for releasing the established at least one PDU session, which is not used for acquiring the configuration service information.
The terminal device according to any one of claims 15 to 19, wherein in a case where the first information includes the indication information, the first information is registration acceptance information for the target registration or the first information is terminal configuration indication information received after completion of the target registration.
The terminal device according to any of the claims 15 to 20, wherein the configuration service information comprises at least a key and a user identification required for accessing an independent non-public network, SNPN.
A network device, comprising:

a communication unit, configured to send first information to a terminal device, where the first information includes indication information or a reject cause value;

wherein,

the indication information is used for indicating that the target registration is only used for rapidly configuring the network;

the reject cause value is used to indicate a rejection to establish a first protocol data unit, PDU, session that is not used to obtain configuration service information.
The network device of claim 22, wherein the reject cause value is targeted for registration only for fast configuration of the network if the first information includes the reject cause value.
The network device of claim 23, wherein the network device further comprises: the processing unit is further configured to receive second information sent by the terminal device after the target registration is completed and before the first information is sent, where the second information is used to request to establish the first PDU session;

the processing unit is configured to determine, according to the first PDU session, that the reject cause value is targeted for registration only for fast configuration of the network.
The network device according to any of claims 22 to 24, wherein the communication unit is further configured to obtain user subscription data of the terminal device, wherein the user subscription data is only used for fast configuration network usage.
The network device of claim 25, wherein the user subscription data is default data.
The network device according to any one of claims 22 to 26, wherein in a case where the first information includes the indication information, the first information is registration acceptance information for the target registration, or the first information is terminal configuration indication information transmitted after completion of the target registration.
The network device according to any of claims 22 to 27, wherein the configuration service information comprises at least a key and a user identification required for accessing an independent non-public network, SNPN.
A terminal device, comprising: a processor and a memory for storing a computer program, the processor being adapted to invoke and run the computer program stored in the memory for performing the method according to any of claims 1 to 7.
A network device, comprising: a processor and a memory for storing a computer program, the processor being for invoking and running the computer program stored in the memory, performing the method of any of claims 8 to 14.
A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any one of claims 1 to 7.
A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any of claims 8 to 14.
A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 1 to 7.
A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 8 to 14.
A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 7.
A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 8 to 14.
A computer program, characterized in that the computer program causes a computer to perform the method according to any one of claims 1 to 7.
A computer program, characterized in that the computer program causes a computer to perform the method of any one of claims 8 to 14.