WO2022095047A1

WO2022095047A1 - Wireless communication method, terminal device, and network device

Info

Publication number: WO2022095047A1
Application number: PCT/CN2020/127591
Authority: WO
Inventors: 卢飞; 刘建华
Original assignee: Oppo广东移动通信有限公司
Priority date: 2020-11-09
Filing date: 2020-11-09
Publication date: 2022-05-12
Also published as: CN116114315A

Abstract

Embodiments of the present application provide a wireless communication method, a terminal device, and a network device. In a process of accessing an onboarding network, the terminal device can obtain restricted information in time, thereby preventing attempting to perform services other than obtaining a key and a user identifier required for access to an SNPN. The wireless communication method comprises: a terminal device receives first information, the first information comprising indication information or a rejection cause value, wherein the indication information is used for indicating that target registration is only used for the onboarding network, the rejection cause value is used for indicating that establishment of a first PDU session is rejected, and the first PDU session is not used for obtaining configuration service information.

Description

Method, terminal device and network device for wireless communication

technical field

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

Background technique

In some scenarios, such as in the office, home, factory and other scenarios, in order to be able to manage more effectively and safely, there will be local users or managers to deploy local networks or private networks, such as independent non-public networks. , SNPN). In order to obtain the key and user ID for accessing the SNPN network, the terminal device needs to access the fast provisioning (onboarding) network, such as the PLMN network, and then the provisioning server (Provisioning Server) needs to access the SNPN network. and the user ID sent to the terminal device. However, in this process, the terminal device may try to obtain services other than the key and user identity required to access the SNPN network, resulting in unnecessary waste of signaling.

SUMMARY OF THE INVENTION

The embodiments of the present application provide a wireless communication method, a terminal device, and a network device. During the process of accessing the fast configuration network, the terminal device can obtain restricted information in time, and avoid trying to obtain the password required for accessing the SNPN network. Services other than keys and user IDs.

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

The terminal device receives first information, where the first information includes indication information or a rejection reason value; wherein,

The indication information is used to indicate that the target registration is only used to quickly configure the network;

The rejection reason value is used to indicate that the establishment of the first PDU session is rejected, and the first PDU session is not used to obtain configuration service information.

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

The network device sends first information to the terminal device, where the first information includes indication information or a rejection reason value;

in,

In a third aspect, a terminal device is provided for executing the method in the above-mentioned first aspect.

Specifically, the terminal device includes functional modules for executing the method in the first aspect.

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

Specifically, the network device includes functional modules for executing the method in the second aspect above.

In a fifth aspect, a terminal device is provided, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the first aspect.

In a sixth aspect, a network device is provided, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the second aspect.

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

Specifically, the apparatus includes: a processor for invoking and running a computer program from a memory, so that a device on which the apparatus is installed executes the method in any one of the first to second aspects above.

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

In a ninth aspect, a computer program product is provided, comprising computer program instructions, the computer program instructions causing a computer to perform the method in 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 one of the above-mentioned first to second aspects.

Through the above technical solution, the terminal device can learn that the target registration is only used to quickly configure the network based on the indication information, so that after the target registration is completed, repeated attempts to obtain configuration service information (such as the key and user required for accessing the SNPN network) are avoided. service other than the logo), so as to realize the terminal power saving.

Alternatively, the terminal device may establish a PDU session that is only used to obtain configuration service information (such as the key and user ID required to access the SNPN network) based on the rejection reason value, thereby avoiding repeated attempts to obtain the configuration after the target registration is completed. Services other than service information (such as keys and user IDs required to access the SNPN network), so as to achieve terminal power saving.

Description of drawings

FIG. 1 is a schematic diagram of a communication system architecture to which an embodiment of the present application is applied.

FIG. 2 is a schematic diagram of a communication system architecture for acquiring configuration server data through a rapid configuration network provided by an embodiment of the present application.

FIG. 3 is a schematic flowchart of a registration provided by the present application.

FIG. 4 is a schematic flowchart of a method for wireless communication according to an embodiment of the present application.

FIG. 5 is a schematic flowchart of indicating registration restriction provided according to an embodiment of the present application.

FIG. 6 is another schematic flowchart of indicating registration restriction provided according to an embodiment of the present application.

FIG. 7 is a schematic flowchart of yet another indication of registration restriction provided according to an embodiment of the present application.

FIG. 8 is a schematic block diagram of a terminal device provided 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 ways

The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. With regard to the embodiments in the present application, all other embodiments obtained by persons of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

The technical solutions of the embodiments of the present application can be applied to various communication systems, for example: a Global System of Mobile communication (GSM) system, a Code Division Multiple Access (CDMA) system, a wideband Code Division Multiple Access (CDMA) system (Wideband Code Division Multiple Access, WCDMA) system, General Packet Radio Service (General Packet Radio Service, GPRS), Long Term Evolution (Long Term Evolution, LTE) system, Advanced Long Term Evolution (Advanced long term evolution, LTE-A) system , New Radio (NR) system, evolution system of NR system, LTE (LTE-based access to unlicensed spectrum, LTE-U) system on unlicensed spectrum, NR (NR-based access to unlicensed spectrum) unlicensed spectrum, NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (Wireless Fidelity, WiFi), fifth-generation communication (5th-Generation, 5G) system or other communication systems, etc.

Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communication, but also support, for example, Device to Device (Device to Device, D2D) communication, machine to machine (M2M) communication, machine type communication (MTC), vehicle to vehicle (V2V) communication, or vehicle to everything (V2X) communication, etc. , the embodiments of the present application can also be applied to these communication systems.

Optionally, the communication system in this embodiment of the present application may be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, a dual connectivity (Dual Connectivity, DC) scenario, or a standalone (Standalone, SA) distribution. web scene.

Optionally, the communication system in the embodiment of the present application may be applied to an unlicensed spectrum, where the unlicensed spectrum may also be considered as a shared spectrum; or, the communication system in the embodiment of the present application may also be applied to a licensed spectrum, where, Licensed spectrum can also be considered unshared spectrum.

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

The terminal device may be a station (STATION, ST) in the WLAN, and may be a cellular phone, a cordless phone, a Session Initiation Protocol (Session Initiation Protocol, SIP) phone, a Wireless Local Loop (WLL) station, a personal digital assistant (Personal Digital Assistant, PDA) devices, handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, next-generation communication systems such as end devices in NR networks, or future Terminal equipment in the evolved public land mobile network (Public Land Mobile Network, PLMN) network, etc.

In this embodiment of the present application, the terminal device can be deployed on land, including indoor or outdoor, handheld, wearable, or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons, and satellites) superior).

In this embodiment of the present application, the terminal device may be a mobile phone (Mobile Phone), a tablet computer (Pad), a computer with a wireless transceiver function, a virtual reality (Virtual Reality, VR) terminal device, and an augmented reality (Augmented Reality, AR) terminal Equipment, wireless terminal equipment in industrial control, wireless terminal equipment in self driving, wireless terminal equipment in remote medical, wireless terminal equipment in smart grid , wireless terminal equipment in transportation safety, wireless terminal equipment in smart city or wireless terminal equipment in smart home, etc.

As an example and not a limitation, in this embodiment of the present application, the terminal device may also be a wearable device. Wearable devices can also be called wearable smart devices, which are the general term for the intelligent design of daily wear and the development of wearable devices using wearable technology, such as glasses, gloves, watches, clothing and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction, and cloud interaction. In a broad sense, wearable smart devices include full-featured, large-scale, complete or partial functions without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, which needs to cooperate with other devices such as smart phones. Use, such as all kinds of 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, and the network device may be an access point (Access Point, AP) in WLAN, or a base station (Base Transceiver Station, BTS) in GSM or CDMA , it can also be a base station (NodeB, NB) in WCDMA, it can also be an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or access point, or in-vehicle equipment, wearable devices and NR networks The network equipment or base station (gNB) in the PLMN network or the network equipment in the future evolved PLMN network or the network equipment in the NTN network, etc.

As an example and not a limitation, in this embodiment of the present application, the network device may have a mobile feature, for example, the network device may be a mobile device. Optionally, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a High Elliptical Orbit (HEO) ) satellite etc. Optionally, the network device may also be a base station set in a location such as land or water.

In this embodiment of the present application, a network device may provide services for a cell, and a terminal device communicates with the network device through transmission resources (for example, frequency domain resources, or spectrum resources) used by the cell, and the cell may be a network device ( For example, the cell corresponding to the base station), the cell can belong to the macro base station, or it can belong to the base station corresponding to the small cell (Small cell). Pico cell), Femto cell (Femto cell), etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

Exemplarily, a communication system 100 to which this embodiment of the present application is applied is shown in FIG. 1 . The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal device 120 (or referred to as a communication terminal, a terminal). The 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 exemplarily shows one network device and two terminal devices. Optionally, the communication system 100 may include multiple network devices and the coverage of each network device may include other numbers of terminal devices. This application The embodiment does not limit this.

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

It should be understood that, in the embodiments of the present application, a device having a communication function in the network/system 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 a communication function, and the network device 110 and the terminal device 120 may be the specific devices described above, which will not be repeated here. ; The communication device may also include other devices in the communication system 100, such as other network entities such as a network controller, a mobility management entity, etc., which are not limited in this embodiment of the present application.

It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and/or" in this article is only an association relationship to describe the associated objects, indicating that there can be three kinds of relationships, for example, A and/or B, it can mean that A exists alone, A and B exist at the same time, and A and B exist independently B these three cases. In addition, the character "/" in this document generally indicates that the related objects are an "or" relationship.

The terms used in the embodiments of the present application are only used to explain specific embodiments of the present application, and are not intended to limit the present application. The terms "first", "second", "third" and "fourth" in the description and claims of the present application and the drawings are used to distinguish different objects, rather than to describe a specific order . Furthermore, the terms "comprising" and "having" and any variations thereof are intended to cover non-exclusive inclusion.

It should be understood that the "instruction" mentioned in the embodiments of the present application may be a direct instruction, an indirect instruction, or an associated relationship. For example, if A indicates B, it can indicate that A directly indicates B, for example, B can be obtained through A; it can also indicate that A indicates B indirectly, such as A indicates C, and B can be obtained through C; it can also indicate that there is an association between A and B relation.

In the description of the embodiments of the present application, the term "corresponding" may indicate that there is a direct or indirect corresponding relationship between the two, or may indicate that there is an associated relationship between the two, or indicate and be instructed, configure and be instructed configuration, etc.

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

In this embodiment of the present application, "predefinition" may be implemented by pre-saving corresponding codes, forms, or other means that can be used to indicate relevant information in devices (for example, including terminal devices and network devices). The implementation method is not limited. For example, predefined may refer to the definition in the protocol.

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

For better understanding of the embodiments of the present application, the SNPN network related to the present application is described.

End users will conduct data services through the public network (ie PLMN), but in some scenarios, such as office scenarios, home scenarios, and factories, in order to be able to manage more effectively and safely, there will be local users or managers to deploy local networks. or private network.

The network elements in the non-public network (NPN) network can exist independently of the PLMN network, that is, the NPN network has a Policy Control Function (PCF) entity and a Session Management Function (SMF) entity. , Access and Mobility Management Function (AMF) entity, Unified Data Management (Unified Data Management, UDM) entity and other network elements, and the NPN network has its own root key, security algorithm, contract information, Policy information etc. achieve isolation from the public network (PLMN).

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

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

It should be noted that the above-mentioned AN device may also be a radio access network (Radio Access Network, RAN) device, and the above-mentioned PCF entity may also be a visited PCF (visited PCF, vPCF) entity, which is not limited in this application.

The UDM entity is the subscription database in the core network, which stores the subscription data of users in the 5G network. The AMF entity is the mobility management function in the core network, and the SMF entity is the session management function in the core network. In addition to the mobility management of the UE, the AMF entity is also responsible for sending session management related messages between the UE and the SMF entity. 's forwarding. The PCF entity is a policy management function in the core network, and is responsible for formulating policies related to the mobility management, session management, and charging of the UE. The UPF entity is the user plane function in the core network. It transmits data with the external data network through the N6 interface, and transmits data with the AN device through the N3 interface. After the UE accesses the 5G network through the Uu interface, a protocol data unit (Protocol Data Unit, PDU) session data connection between the UE and 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 obtain user subscription data from the UDM entity through the N8 and N10 interfaces respectively, and obtain policy data from the PCF entity through the N15 and N7 interfaces.

It should be noted that each network element in FIG. 2 may also have other functions, which is not limited in this application.

In order to facilitate a better understanding of the embodiments of the present application, the process of sending configuration service information by a configuration server related to the present application is described, and the specific processes are shown in S0-1 to S0-12 in FIG. 3 .

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

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

S0-3, the UDM entity sends the 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 (onboarding);

S0-4, the AMF entity sends registration acceptance information to the UE, and the registration acceptance information carries the 5G Globally Unique Temporary UE Identity (5G-GUTI) and the registration area allocated by the AMF entity to 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 the process of establishing a PDU session, so that the configuration server can send the configuration service information (the key and user identity required to access the SNPN network) to the UE through the user plane; the configuration server can also send directly through the control plane Configuration service information, if the configuration service information is sent through the control plane, this step may not be performed;

S0-7, the configuration server sends configuration service information to the UDM entity, where the configuration service information carries the key and user identity 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 the AMF entity;

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

S0-11, the UE sends uplink NAS transmission information to the AMF entity, where the uplink NAS transmission information carries the confirmation information of the UE for the configuration service information;

S0-12, the AMF entity returns the confirmation information of the UE for the configuration service information to the UDM entity.

Since the user subscription data sent by the UDM entity to the AMF entity in the above S0-3 is only used for onboarding, but the UE cannot perceive this restricted information, when the UE requests other services, the network side needs to reject it, but the UE will still Retrying other services will cause unnecessary waste of signaling. The network side also needs to process these unnecessary signaling, and the UE side will also cause waste of resources and unnecessary power consumption.

Based on the above problems, this application proposes a registration scheme. During the process of accessing the fast configuration network, the terminal device can obtain the restricted information in time, and avoid trying to obtain the key and user ID required for accessing the SNPN network. Business.

The technical solutions of the present application are described in detail below through specific embodiments.

FIG. 4 is a schematic flowchart of a method 200 for wireless communication according to an embodiment of the present application. As shown in FIG. 4 , the method 200 may include at least part of the following contents:

S210, the network device sends first information to the terminal device, where the first information includes indication information or a rejection reason value; wherein the indication information is used to indicate that the target registration is only used for quick network configuration; the rejection reason value is used to indicate that the establishment is rejected the first PDU session, the first PDU session is not used to obtain configuration service information;

S220, the terminal device receives the first information.

In this embodiment of the present application, the network device can send restricted information (indication information or rejection reason value) for target registration to the terminal device, so that in the target registration, the terminal device can only achieve the purpose of quickly configuring the network, or , the terminal device only establishes a PDU session for acquiring configuration service information. The terminal equipment can be prevented from attempting services other than acquiring the key and user identity required to access the SNPN network.

That is, the network device can notify the terminal device that the target registration is only for quickly configuring the network by rejecting the process of establishing a normal PDU session (the first PDU session).

The network device may be, for example, an AMF entity, and of course, may also be some other network elements, such as access network devices.

Optionally, the network device acquires user subscription data of the terminal device, where the user subscription data is only used to quickly configure network usage. For example, the user subscription data is default data. In this case, the network device sends the first information to the terminal device. That is, before sending the first information, the network device acquires the user subscription data of the terminal device.

Optionally, in some embodiments, where the first information includes the rejection reason value, the rejection reason value is the target registration only for quickly configuring the network.

Optionally, in the case where the first information includes the rejection reason 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 first The second information is used to request the establishment of the first PDU session. Correspondingly, according to the first PDU session, the network device determines that the rejection reason value is the target registration only for quickly configuring the network.

That is, after the target registration is completed, since the terminal device does not know the restricted information in time (the target registration is only used to quickly configure the network), the terminal device initiates the establishment of the first PDU session.

Optionally, the second information may carry at least one of the following:

The PDU session identifier (Identity, ID) allocated by the terminal device for the first PDU session, the single-network slice assistance information (Single-Network Slice Selection Assistance Information, S-NSSAI), the data network name (Data Network Name, DNN) information, and The request type (the request type is set to initial request), and the PDU session establishment request message (used to request the establishment of the first PDU session).

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

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

Optionally, the configuration service information includes at least a secret key and a user identity required for accessing the SNPN. That is, the terminal device can obtain the secret key and user identity required for accessing the SNPN from the configuration service information, so that it can normally access the SNPN.

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

The registration scheme in the examples of the present application will be described in detail below through Examples 1 to 3.

In Embodiment 1, a network device (such as an AMF entity) may send registration acceptance information to a terminal device (UE), where the registration acceptance information includes indication information, and the indication information is used to indicate that the target registration is only used for fast configuration (onboarding) the network, specifically. This can be achieved through the processes S1-1 to S1-6 shown in FIG. 5 .

S1-1, the UE sends registration request information to the AMF entity, where the registration request information is used to request the realization of the target registration, and the registration request information carries the user ID and the registration type, and the registration type can be set as initial registration;

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

S1-3, the UDM entity sends the 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 (onboarding);

S1-4, the AMF entity sends registration acceptance information to the UE, where the registration acceptance information carries the 5G-GUTI and the registration area allocated by the AMF entity for the UE; in addition, the registration acceptance information also carries indication information, which is used to indicate The target registration is only used to quickly configure (onboarding) the network; the indication information can be carried in the registration result; after receiving the indication information, the UE can only establish a 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 the process of establishing a PDU session, and the PDU session is used to obtain configuration service information; so that the configuration server can send the configuration service information (the key and user ID required to access the SNPN network) to the user plane through the user plane. The UE; the configuration server may also directly send the configuration service information through the control plane. If the configuration service information is sent through the control plane, this step may not be performed.

Subsequent steps can be referred to as described in FIG. 3 , which will not be repeated here.

In Embodiment 2, a network device (such as an AMF entity) may send downlink NAS transmission information to a terminal device (UE), where the downlink NAS transmission information includes a rejection reason value, and the rejection reason value is only used for the target registration to quickly configure the network, and the The rejection reason value is used to indicate that the establishment of the first PDU session is rejected, and the first PDU session is not used to obtain configuration service information, which can be specifically implemented through the processes S2-1 to S2-7 shown in FIG. 6 .

S2-1, the UE sends registration request information to the AMF entity, the registration request information is used to request the realization of the target registration, the registration request information carries the user identifier and the 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 obtains the user subscription data of the UE from the UDM entity;

S2-3, the UDM entity sends the 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 (onboarding);

S2-4, the AMF entity sends registration acceptance information to the UE, and the registration acceptance information carries the 5G-GUTI and the registration area allocated 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 process of establishing a PDU session, which is used to establish a first PDU session, and the first PDU session is not used to obtain configuration service information; specifically, the UE sends uplink NAS transmission information to the AMF entity, and the uplink NAS transmission information contains Carry the PDU session ID, S-NSSAI, DNN information, and request type (the request type is set as initial request) allocated by the UE for the first PDU session, and the PDU session establishment request message;

S2-7, the AMF entity verifies whether the first PDU session is used for fast configuration (onboarding) and whether it is used to obtain configuration service information. After verifying that the first PDU session is used for normal services, the AMF entity returns downlink NAS transmission information to the UE , the downlink NAS transmission information carries a refusal cause value, the refusal cause value is only used for the target registration to quickly configure the network, and the refusal cause value is used to indicate refusal to establish the first PDU session; after the UE receives the refusal cause value , can only establish a PDU session for obtaining configuration service information.

In Embodiment 3, a network device (such as an AMF entity) may send terminal configuration indication information to a terminal device (UE) after the target registration is completed, where the terminal configuration indication information includes indication information, and the indication information is used to indicate that the target registration is only used for fast The configuration (onboarding) of the network can be specifically implemented through the processes S3-1 to S3-7 shown in FIG. 7 .

S3-1, the UE sends registration request information to the AMF entity, the registration request information is used to request the realization of the target registration, the registration request information carries the user identifier and the registration type, and the registration type can be set as the initial registration;

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

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

S3-4, the AMF entity sends registration acceptance information to the UE, and the registration acceptance information carries the 5G-GUTI and the registration area allocated by the AMF entity to 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 in S3-3 that the user subscription data is the default data, it can only be used for quick configuration (onboarding), and when the user subscription data changes, the UDM entity will update the user subscription data. The data is sent to the AMF entity, and the UDM entity indicates that the updated user subscription data is default data and can only be used for fast configuration (onboarding); in this case, the AMF entity sends the terminal configuration indication information to the UE, and the terminal The configuration indication information includes indication information, and the indication information is used to indicate that the target registration is only used for fast configuration (onboarding) the network; after the UE receives the indication information, it can only establish a configuration service information (needed for accessing the SNPN network) for obtaining the configuration service information. key and user identity), and release other PDU sessions locally;

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

Therefore, in this embodiment of the present application, the terminal device can learn that the target registration is only used to quickly configure the network based on the indication information. Therefore, after the target registration is completed, repeated attempts are avoided except for obtaining configuration service information (such as required for accessing the SNPN network). services other than keys and user IDs), so as to achieve terminal power saving.

Alternatively, in this embodiment of the present application, the terminal device may establish a PDU session that is only used to obtain configuration service information (such as the key and user ID required to access the SNPN network) based on the rejection reason value, so that after the target registration is completed, , to avoid repeated attempts for services other than obtaining configuration service information (such as the key and user ID required to access the SNPN network), thereby realizing power saving of the terminal.

The method embodiments of the present application are described in detail above with reference to FIGS. 4 to 7 , and the apparatus embodiments of the present application are described in detail below with reference to FIGS. 8 to 12 . It should be understood that the apparatus embodiments and the method embodiments correspond to each other, and are similar to For the description, refer to the method embodiment.

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

The communication unit 310 is configured to receive first information, where the first information includes indication information or a rejection reason value; wherein,

The rejection reason value is used to indicate that the establishment of the first protocol data unit PDU session is rejected, and the first PDU session is not used for acquiring configuration service information.

Optionally, in the case where the first information includes the rejection reason value, the rejection reason value is only used for the target registration to quickly configure 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:

The processing unit 320 is 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, where the at least one PDU session is not used for acquiring configuration service information.

Optionally, when 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 the target registration is completed.

Optionally, the configuration service information includes at least a secret key and a user identity required for accessing the independent non-public network SNPN.

Optionally, in some embodiments, the above-mentioned communication unit may be a communication interface or a transceiver, or an input/output interface of a communication chip or a system-on-chip. The aforementioned 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 method embodiment of the present application, and the above-mentioned and other operations and/or functions of the various units in the terminal device 300 are respectively for realizing the method shown in FIG. 4 . The corresponding process of the terminal device in 200 is not repeated here 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, configured to send first information to the terminal device, where the first information includes indication information or a rejection reason value;

in,

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

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

The processing unit 420 is configured to determine, according to the first PDU session, that the rejection reason value is the target registration only for quickly configuring the network.

Optionally, the communication unit 410 is further configured to acquire user subscription data of the terminal device, where the user subscription data is only used to quickly configure network usage.

Optionally, the user subscription data is default data.

Optionally, when 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 method embodiment of the present application, and the above-mentioned and other operations and/or functions of each unit in the network device 400 are respectively for realizing the method shown in FIG. 4 . The corresponding process of the network device in 200 is not repeated here for brevity.

FIG. 10 is a schematic structural diagram of a communication device 500 provided by an embodiment of the present application. The communication device 500 shown in FIG. 10 includes a processor 510, and the processor 510 can call and run a computer program from a memory, so as to implement the method in the embodiment of the present application.

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

The memory 520 may be a separate device independent of the processor 510 , or may be integrated in 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, specifically, may send information or data to other devices, or receive other Information or data sent by a device.

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

Optionally, the communication device 500 may specifically be a network device in this embodiment of the present application, and the communication device 500 may implement the corresponding processes implemented by the network device in each method in the embodiment of the present application. For brevity, details are not repeated here. .

Optionally, the communication device 500 may specifically be the mobile terminal/terminal device of the embodiments of the present application, and the communication device 500 may implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application. , and will not be repeated here.

FIG. 11 is a schematic structural diagram of an apparatus according to an embodiment of the present application. The apparatus 600 shown in FIG. 11 includes a processor 610, and the processor 610 can call and run a computer program from a memory, so as to implement the method in the embodiment of the present application.

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

The memory 620 may be a separate device independent of the processor 610 , or may be integrated in the processor 610 .

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

Optionally, the apparatus 600 may further include an output interface 640 . The processor 610 can control the output interface 640 to communicate with other devices or chips, and specifically, can output information or data to other devices or chips.

Optionally, the apparatus can be applied to the network equipment in the embodiments of the present application, and the apparatus can implement the corresponding processes implemented by the network equipment in the various methods of the embodiments of the present application, which are not repeated here for brevity.

Optionally, the apparatus can be applied to the mobile terminal/terminal equipment in the embodiments of the present application, and the apparatus can implement the corresponding processes implemented by the mobile terminal/terminal equipment in each method of the embodiments of the present application. For brevity, here No longer.

Optionally, the device mentioned in the embodiment of the present application may also be a chip. For example, it can be a system-on-chip, a system-on-a-chip, a system-on-a-chip, or a system-on-a-chip.

FIG. 12 is a schematic block diagram of a communication system 700 provided by 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 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 720 can be used to implement the corresponding functions implemented by the network device in the above method. For brevity, details are not repeated here. .

It should be understood that the processor in this embodiment of the present application may be an integrated circuit chip, which has a signal processing capability. In the implementation process, each step of the above method embodiments may be completed by a hardware integrated logic circuit in a processor or an instruction in the form of software. The above-mentioned processor can 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 available Programming logic devices, discrete gate or transistor logic devices, discrete hardware components. The methods, steps, and logic block diagrams disclosed in the embodiments of this application can be implemented or executed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art. The storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware.

It can be understood that the memory in this embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. Wherein, the non-volatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically programmable read-only memory (Erasable PROM, EPROM). Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory. Volatile memory may be 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 synchronous dynamic random access memory (Double Data Rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (Synchlink DRAM, SLDRAM) ) and direct memory bus random access memory (Direct Rambus RAM, DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but not be limited to, these and any other suitable types of memory.

It should be understood that the above memory is an example but not a limitative description, for example, the memory in the embodiment of the present application may also be a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.

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

Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For brevity, here No longer.

Optionally, the computer-readable storage medium can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application. , and are not repeated here for brevity.

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

Optionally, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the network device in each method of the embodiments of the present application. Repeat.

Optionally, the computer program product can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application, For brevity, details are not repeated here.

The embodiments of the present application also provide a computer program.

Optionally, the computer program can be applied to the network device in the embodiments of the present application. When the computer program is run on the computer, it causes the computer to execute the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity. , and will not be repeated here.

Optionally, the computer program may be applied to the mobile terminal/terminal device in the embodiments of the present application, and when the computer program is run on the computer, the mobile terminal/terminal device implements the various methods of the computer program in the embodiments of the present application. The corresponding process, for the sake of brevity, will not be repeated here.

Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the above-described systems, devices and units may refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

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

The functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium. For such understanding, the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution. The computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program codes .

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited to this. should be covered within the scope of protection of this application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

A method of wireless communication, comprising:

The terminal device receives first information, where the first information includes indication information or a rejection reason value; wherein,

The indication information is used to indicate that the target registration is only used to quickly configure the network;

The rejection reason value is used to indicate that the establishment of the first protocol data unit PDU session is rejected, and the first PDU session is not used to obtain configuration service information.
The method of claim 1, wherein, in the case that the first information includes the rejection reason value, the rejection reason value is only used for fast network configuration for target registration.
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 the establishment of the first PDU session.
The method according to any one of claims 1 to 3, wherein the method further comprises:

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

The terminal device releases the established at least one PDU session, and the at least one PDU session is not used for acquiring configuration service information.
The method according to any one of claims 1 to 5, wherein, when 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 the target registration is completed.
The method according to any one of claims 1 to 6, wherein the configuration service information at least includes a key and a user identity required for accessing an independent non-public network SNPN.
A method of wireless communication, comprising:

The network device sends first information to the terminal device, where the first information includes indication information or a rejection reason value;

in,

The indication information is used to indicate that the target registration is only used to quickly configure the network;

The rejection reason value is used to indicate that the establishment of the first protocol data unit PDU session is rejected, and the first PDU session is not used to obtain configuration service information.
8. The method of claim 8, wherein, in the case that the first information includes the rejection reason value, the rejection reason value is only used for the purpose of quickly configuring the network for target registration.
The method of claim 9, wherein the method further comprises:

After the target registration is completed and before sending the first information, the network device receives second information sent by the terminal device, where the second information is used to request the establishment of the first PDU session;

According to the first PDU session, the network device determines that the rejection reason value is the target registration only for quickly configuring the network.
The method according to any one of claims 8 to 10, wherein the method further comprises:

The network device acquires user subscription data of the terminal device, wherein the user subscription data is only used to quickly configure network usage.
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, when 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.
The method according to any one of claims 8 to 13, wherein the configuration service information at least includes a secret key and a user identity required for accessing an independent non-public network SNPN.
A terminal device, characterized in that it includes:

a communication unit, configured to receive first information, where the first information includes indication information or a rejection reason value; wherein,

The indication information is used to indicate that the target registration is only used to quickly configure the network;

The rejection reason value is used to indicate that the establishment of the first protocol data unit PDU session is rejected, and the first PDU session is not used to obtain configuration service information.
The terminal device according to claim 15, wherein, in the case that the first information includes the rejection reason value, the rejection reason value is only used for target registration to quickly configure the network.
The terminal device according to 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 the establishment of the first PDU session.
The terminal device according to any one of claims 15 to 17, wherein the terminal device further comprises:

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

The processing unit is configured to release the established at least one PDU session, where the at least one PDU session is not used for acquiring configuration service information.
The terminal device according to any one of claims 15 to 19, wherein, when 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 the target registration is completed.
The terminal device according to any one of claims 15 to 20, wherein the configuration service information at least includes a secret key and a user identity required for accessing an independent non-public network SNPN.
A network device, characterized in that it includes:

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

in,

The indication information is used to indicate that the target registration is only used to quickly configure the network;

The rejection reason value is used to indicate that the establishment of the first protocol data unit PDU session is rejected, and the first PDU session is not used to obtain configuration service information.
The network device according to claim 22, wherein, in a case where the first information includes the rejection reason value, the rejection reason value is only used for target registration to quickly configure the network.
The network device according to claim 23, wherein the network device further comprises: a processing unit, after the target registration is completed and before the first information is sent, the communication unit is further configured to receive the second information sent by the terminal device, where the second information is used to request the establishment of the first PDU session;

The processing unit is configured to determine, according to the first PDU session, that the rejection reason value is target registration only for quickly configuring the network.
The network device according to any one of claims 22 to 24, wherein the communication unit is further configured to acquire user subscription data of the terminal device, wherein the user subscription data is only used to quickly configure the network use.
The network device according to claim 25, wherein the user subscription data is default data.
The network device according to any one of claims 22 to 26, wherein when 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.
The network device according to any one of claims 22 to 27, wherein the configuration service information at least includes a secret key and a user identity required for accessing an independent non-public network SNPN.
A terminal device, characterized in that it comprises: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and execute any one of claims 1 to 7. one of the methods described.
A network device, characterized in that it comprises: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and execute any one of claims 8 to 14. one of the methods described.
A chip, characterized by comprising: a processor for invoking and running a computer program from a memory, so that a device installed with the chip executes the method according to any one of claims 1 to 7 .
A chip, characterized by comprising: a processor for calling and running a computer program from a memory, so that a device installed with the chip executes the method according to any one of claims 8 to 14 .
A computer-readable storage medium, characterized by being used for storing a computer program, the computer program causing a computer to execute the method according to any one of claims 1 to 7.
A computer-readable storage medium, characterized by being used for storing a computer program, the computer program causing a computer to execute the method according to any one of claims 8 to 14.
A computer program product comprising computer program instructions, the computer program instructions causing a computer to perform the method of any one of claims 1 to 7.
A computer program product comprising computer program instructions, the computer program instructions 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 according to any one of claims 8 to 14.