Communication method and communication device

Abstract

The invention provides a communication method and a communication device. The communication method comprises the following steps: a first network element determines that a remote terminal accesses a network through an emergency relay service code RSC; and the first network element sends first information to a second network element, wherein the first information is used for indicating the remote terminal to access the network through the emergency RSC. The method provided by the embodiment of the invention is helpful for the network side to perceive the access mode of the far-end terminal.

Description

Communication method and communication device Technical Field

[0001] The present application relates to the field of communication technology, and more specifically, to a communication method and a communication device. Background Art

[0002] In some communication systems, when a remote terminal accesses the network through a relay terminal, core network elements (such as the access and mobility management function (AMF)) cannot perceive whether the remote terminal accesses the network through the relay terminal or directly through the access network equipment, which may cause some problems.

[0003] Summary of the Invention

[0004] The embodiments of the present application provide a communication method and a communication device. The following describes various aspects of the embodiments of the present application.

[0005] In a first aspect, a communication method is provided, including: a first network element determines that a remote terminal accesses a network through an emergency relay service code RSC; the first network element sends first information to a second network element, wherein the first information is used to indicate that the remote terminal accesses the network through the emergency RSC.

[0006] In the second aspect, a communication method is provided, including: a second network element receives first information sent by a first network element, the first information being used to instruct a remote terminal to access the network through an emergency relay service code RSC; the second network element processes a first connection of the remote terminal according to the first information, the first connection being used for non-emergency business communication of the remote terminal.

[0007] According to a third aspect, a communication method is provided, comprising: a remote terminal sending second information to a first network element, wherein the second information is used to determine that the remote terminal accesses a network via an emergency relay service code RSC.

[0008] In a fourth aspect, a communication method is provided, including: a second network element receives third information sent by a remote terminal, the third information being used to instruct the remote terminal to access the network through an emergency RSC; the second network element processes a second connection of the remote terminal according to the third information, the second connection being used for non-emergency business communication of the remote terminal.

[0009] In a fifth aspect, a communication method is provided, comprising: a remote terminal sends third information to a second network element, wherein the third information is used to instruct the remote terminal to access the network through an emergency RSC.

[0010] In the sixth aspect, a communication device is provided, including: a determination unit, used to determine that a remote terminal accesses the network through an emergency relay service code RSC; a sending unit, used to send first information to a second network element, wherein the first information is used to indicate that the remote terminal accesses the network through the emergency RSC.

[0011] In the seventh aspect, a communication device is provided, including: a receiving unit for receiving first information sent by a first network element, wherein the first information is used to instruct a remote terminal to access the network through an emergency relay service code RSC; a processing unit for processing a first connection of the remote terminal according to the first information, wherein the first connection is used for non-emergency business communication of the remote terminal.

[0012] In an eighth aspect, a communication device is provided, comprising: a sending unit, configured to send second information to a first network element, wherein the second information is used to determine whether the device accesses the network via an emergency relay service code RSC.

[0013] In the ninth aspect, a communication device is provided, including: a receiving unit for receiving third information sent by a remote terminal, the third information being used to instruct the remote terminal to access the network through an emergency RSC; a processing unit for processing a second connection of the remote terminal according to the third information, the second connection being used for non-emergency business communication of the remote terminal.

[0014] In a tenth aspect, a communication device is provided, comprising: a sending unit, configured to send third information to a second network element, wherein the third information is used to instruct the device to access a network through an emergency RSC.

[0015] In the eleventh aspect, a communication device is provided, comprising a memory, a transceiver and a processor, wherein the memory is used to store programs, the processor sends and receives data through the transceiver, and the processor is used to call the program in the memory so that the communication device executes the method described in any one of the first to fifth aspects.

[0016] In a twelfth aspect, a chip is provided, comprising a processor for calling a program from a memory so that a device equipped with the chip executes the method described in any one of the first to fifth aspects.

[0017] In a thirteenth aspect, a computer-readable storage medium is provided, on which a program is stored, wherein the program enables a computer to execute the method described in any one of the first to fifth aspects.

[0018] In a fourteenth aspect, a computer program product is provided, comprising a program, wherein the program enables a computer to execute the method described in any one of the first to fifth aspects.

[0019] In a fifteenth aspect, a computer program is provided, wherein the computer program enables a computer to execute the method described in any one of the first to fifth aspects.

[0020] In an embodiment of the present application, the first network element determines that the remote terminal accesses the network through the emergency RSC, and the first network element sends first information to the second network element. The first information is used to indicate that the remote terminal accesses the network through the emergency RSC, which helps the network side perceive the access method of the remote terminal. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] FIG1 is an example diagram of a wireless communication system used in an embodiment of the present application.

[0022] FIG2 is an example diagram of a 5GS architecture in an embodiment of the present application.

[0023] FIG3 is an exemplary diagram of the system architecture of an L2 U2N relay in one embodiment of the present application.

[0024] FIG4 is an example diagram of a protocol stack of an L2 U2N relay in an embodiment of the present application.

[0025] FIG5 is a system block diagram of a UE accessing a network and using IMS services in an embodiment of the present application.

[0026] FIG6 is a schematic flow chart of a UE performing network registration in an embodiment of the present application

[0027] FIG7 is a schematic flowchart of a communication method provided in one embodiment of the present application.

[0028] FIG8 is a schematic flowchart of a communication method provided in another embodiment of the present application.

[0029] FIG9 is a schematic flowchart of a communication method provided in yet another embodiment of the present application.

[0030] FIG10 is a schematic structural diagram of a communication device provided in one embodiment of the present application.

[0031] FIG11 is a schematic structural diagram of a communication device provided in another embodiment of the present application.

[0032] FIG12 is a schematic structural diagram of a communication device provided in yet another embodiment of the present application.

[0033] FIG13 is a schematic structural diagram of a communication device provided in yet another embodiment of the present application.

[0034] FIG14 is a schematic structural diagram of a communication device provided in yet another embodiment of the present application.

[0035] FIG15 is a schematic structural diagram of a device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0036] The technical solution in this application will be described below with reference to the accompanying drawings.

[0037] FIG1 illustrates a wireless communication system 100 used in an embodiment of the present application. The wireless communication system 100 may include a network device 110 and a user equipment (UE) 120. The network device 110 may communicate with the UE 120. The network device 110 may provide communication coverage for a specific geographic area and may communicate with the UE 120 within the coverage area. The UE 120 may access a network (e.g., a wireless network) through the network device 110.

[0038] Figure 1 exemplarily shows a network device and two UEs. Optionally, the wireless communication system 100 may include multiple network devices, and each network device may include a different number of terminal devices within its coverage area, which is not limited in this embodiment of the present application. Optionally, the wireless communication system 100 may also include other network entities such as a network controller and a mobility management entity, which is not limited in this embodiment of the present application.

[0039] It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: fifth generation (5G) system or new radio (NR), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), etc. The technical solutions provided in this application can also be applied to future communication systems, such as the sixth generation mobile communication system, satellite communication system, etc.

[0040] The UE in the embodiments of the present application may also be referred to as a terminal device, an access terminal, a user unit, a user station, a mobile station, a mobile station (MS), a mobile terminal (MT), a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user apparatus. The UE in the embodiments of the present application may refer to a device that provides voice and / or data connectivity to a user and can be used to connect people, objects, and machines, such as a handheld device or an in-vehicle device with wireless connection capabilities. The UE in the embodiments of the present application can be a mobile phone, a tablet computer, a laptop computer, a PDA, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc. Optionally, the UE can be used to act as a base station. For example, the UE can act as a scheduling entity that provides sidelink signals between UEs in V2X or D2D, etc. For example, a cellular phone and a car communicate with each other using sidelink signals. The cellular phone and smart home devices communicate without relaying the communication signal through a base station.

[0041] The network device in the embodiments of the present application may be a device for communicating with a UE, and may also be referred to as an access network device or a radio access network device. For example, the network device may be a base station. The network device in the embodiments of the present application may refer to a radio access network (RAN) node (or device) that connects a UE to a wireless network. A base station may broadly cover various names as follows, or be replaced with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitting point (TP), master station MeNB, secondary station SeNB, multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station may be a macro base station, a micro base station, a relay node, a donor node, or the like, or a combination thereof.

[0042] In some embodiments, the network device can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile network device, and one or more cells can move according to the location of the mobile network device. In other examples, the helicopter or drone can be configured to act as a device for communicating with another network device. In some embodiments, the network device can refer to a CU or a DU, or the network device can include a CU and a DU, or the network device can also include an AAU.

[0043] It should be understood that network devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; can also be deployed on water; and can also be deployed in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the network devices and the scenarios in which they are used.

[0044] It should also be understood that all or part of the functions of the network device and UE in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (such as a cloud platform).

[0045] With the continuous development of system applications, network controlled interactive services (NCIS) services are introduced into the standards as a new service form to carry out related standardized services.

[0046] Taking 5G as an example, the NCIS service is primarily targeted at applications such as AR / VR and gaming, which place high demands on service quality, including speed, latency, packet loss rate, and high-speed encoding and decoding. For example, VR gaming requires a 10 Gbps rate with a packet loss rate of no more than 10E-4. Sessions established for NCIS services are called NCIS sessions. UEs in the same NCIS session are considered to form an NCIS group, for example, when forming a team in a game.

[0047] In 3GPP Release 17 (R17), the 5G proximity service (ProSe) project was used to design solutions for proximity service communications. ProSe includes NCIS. One of the key ProSe scenarios is the user equipment to network (UE-to-network, U2N) relay scenario. U2N relay uses a relay UE to relay data for a remote UE, enabling the remote UE to communicate with the network.

[0048] The following describes a system architecture in an embodiment of the present application in conjunction with FIG2 .

[0049] Figure 2 is a diagram of the 5G system (5GS) architecture, which includes: network slice selection function (NSSF), authentication server function (AUSF), unified data management (UDM), access and mobility management function (AMF), session management function (SMF), policy control function (PCF), application function (AF), UE, radio access network (RAN), user plane function (UPF), data network (DN) and other network elements.

[0050] An example diagram of the system architecture of Layer 2 (L2) U2N relay may be shown in FIG3 .

[0051] As shown in Figure 3, in the L2 U2N relay architecture, the L2 remote UE has its own core network elements, such as the remote UE AMF, remote UE SMF, and remote UE UPF.

[0052] To enable relay communication, the relay UE and remote UE must obtain necessary configuration parameters before relay communication can begin. These configuration parameters can come from the PCF or application server, or they can be pre-configured on the terminal device or SIM card. Before transmitting data, the remote UE must first discover a suitable relay UE and establish a PC5 connection with it.

[0053] An example diagram of the protocol stack for the L2 U2N relay can be shown in Figure 4. As shown in Figure 4, in the L2 U2N relay, the adaptation layer (ADAPT) is placed above the radio link control (RLC) sublayer of the control plane and user plane at the Uu interface between the relay UE and the gNB; the Uu service data adaptation protocol (SDAP) layer and the Uu packet data convergence protocol (PDCP) are terminated between the remote terminal and the gNB; and the PC5 RLC, PC5 media access control (MAC), and PC5 physical layer (PHY) are terminated in each link (i.e., the link between the remote terminal and the relay terminal and the link between the relay terminal and the gNB).

[0054] For L2 UE to network relay uplink:

[0055] The Uu Adaptation Layer of the relay terminal supports uplink bearer mapping between incoming PC5 RLC channels for relaying and outgoing Uu RLC channels on the relay UE Uu path. For uplink relay services, different end-to-end bearers (signaling radio bearers (SRBs) and data radio bearers (DRBs)) of the same remote UE and / or different remote UEs can be mapped and data multiplexed on a single Uu RLC channel (N is an integer).

[0056] The Uu Adaptation Layer supports remote terminal identification for uplink services (multiplexing data from multiple remote terminals). The remote terminal Uu radio bearer and remote terminal identification information are included in the uplink Uu Adaptation Layer so that the gNB can correlate received data packets for a specific PDCP entity associated with the right remote terminal Uu radio bearer of the remote terminal.

[0057] For L2 UE to network relay downlink:

[0058] The Uu Adaptation Layer may be used to support downlink bearer mapping at the gNB to map the remote terminal's end-to-end radio bearers (SRBs, DRBs) to Uu RLC channels over the relay UE-Uu path. The Uu Adaptation Layer may be used to support downlink N:1 bearer mapping and data multiplexing between a remote terminal and / or multiple end-to-end radio bearers (SRBs, DRBs) of different remote terminals and a Uu RLC channel over the relay UE Uu path.

[0059] The Uu adaptation layer needs to support remote terminal identification for downlink services. The remote terminal Uu radio bearer identity information and remote terminal identification information need to be placed in the Uu adaptation layer by the gNB in ​​the downlink, so that the relay UE can map data packets received from the remote terminal Uu radio bearer to its associated PC5 RLC channel.

[0060] Figure 5 is a system block diagram for a UE accessing a network and using IP multimedia subsystem (IMS) services. Figure 5 includes the terminal device, access network equipment, AMF, SMF, UPF, unified data management (UDM) / home subscriber server (HSS), policy control function (PCF), proxy call session control function (P-CSCF), serving call session control function (S-CSCF), technology-related RFS (TAS), interconnection border control function (IBCF) / border gateway control function (BGCF) / media gateway control function (MGCF) + media plane functions, and part B.

[0061] For example, the UDM / HSS can be connected to the TAS via the Sh interface, the TAS can be connected to the S-CSCF via the ISC interface, the UDM / HSS can be connected to the S-CSCF via the Cx interface, the H-PCF can be connected to the P-CSCF via the Rx or N5 interface, the P-CSCF can be connected to the S-CSCF via the Mw interface, and the UOF of the home network can be connected to the Interconnect Border Control Function (IBCF) / Border Gateway Control Function (BGCF) / Media Gateway Control Function (MGCF) + Media Plane Function via the N6 interface. In addition, in Figure 5, the control plane can be the dotted line passing through the P-CSCF and S-CSCF as shown in Figure 5, and the media plane can be the dotted line that does not pass through the P-CSCF and S-CSCF.

[0062] Figure 6 is a schematic flow chart of UE performing network registration. The details are as follows:

[0063] Step 1: The UE performs a registration process. The registration type can be initial registration or emergency registration.

[0064] Step 2: The UE sends an uplink non-access stratum transport (UL NAS transport) message to the AMF. The message may include the request type (such as initial emergency request), packet data unit (PDU) session identifier (session ID), and PDU session establishment request message.

[0065] In step 3, the AMF obtains the UE identifier from the UDM, for example, the generic public subscription identifier (GPSI) (GPSI here is the mobile station ISDN (MSISDN)). If the AMF has not yet obtained the UE's permanent equipment identifier (PEI), the AMF also needs to obtain the PEI from the UE.

[0066] Step 4: AMF sends Nsmf_PDUSession_CreateSMContextRequest message to SMF. This message carries PDU session ID, data network name (DNN), single network slice selection assistance information (S-NSSAI), request type, subscription permanent identifier (SUPI), PEI, and GPSI.

[0067] Step 5: The SMF sends an Npcf_SMPolicyControl_Create message to the PCF. At the same time, the UE's SUPI, PEI, and GPSI may be sent to the PCF.

[0068] Step 6: SMF sends a Namf_Communication_N1N2MessageTransfer message to AMF. SMF can receive a PDU session establishment request message and send a Namf_Communication_N1N2MessageTransfer message to AMF. The message includes a PDU session establishment accept message. The PDU session establishment accept message includes a QoS rule, a QoS flow parameter, a DNN, an S-NSSAI, and a protocol configuration option (PCO). The PCO can carry the address or fully qualified domain name (FQDN) of the proxy call session control function (P-CSCF). If the PCO does not carry the address of the P-CSCF, the UE can use the pre-configured P-CSCF address or use the dynamic host configuration protocol (DHCP) to obtain the P-CSCF address.

[0069] Step 7: The AMF sends a DL NAS transport message to the UE. This message may include a PDU session establishment accept message and the PDU session ID.

[0070] Step 8: The UE sends a Session Initiation Protocol (SIP) registration message to the P-CSCF. The message includes the user ID, which is the IMS private user identity (IMPI).

[0071] Step 9: The P-CSCF sends an Npcf_PolicyAuthorization_Create Request message to the PCF. This message may include the UE IP address.

[0072] Step 10: The PCF sends an Npcf_PolicyAuthorization_Create Response message to the P-CSCF. This message may include the SUPI, IMEI, and GPSI.

[0073] Step 11: The P-CSCF returns a SIP registration response message to the UE.

[0074] When a remote UE accesses the AMF of the remote UE through L2 relay, the AMF cannot perceive that the remote UE is accessed through the relay UE, which results in the AMF being unable to distinguish whether the remote UE is accessed from the relay UE or directly through the access network device (such as gNB).

[0075] However, the latest 3GPP standardization progress has put forward different requirements for emergency services. For example, emergency services cannot communicate with non-emergency services using the same logical connection of the relay device (but can be connected through different PC5s of the same relay or connections of different relays). Therefore, the AMF needs to be aware of the different service types of the remote UE.

[0076] In order to solve one or more of the above technical problems, the present application proposes a communication method and a communication device. The embodiments of the present application are described in detail below with reference to Figures 7 to 9.

[0077] FIG7 is a schematic flow chart of a communication method according to an embodiment of the present application. The method 700 shown in FIG7 may include steps S710 and S720, which are as follows:

[0078] S710: A first network element determines that a remote terminal accesses the network through an emergency relay service code (RSC).

[0079] The remote terminal may access the network through one or more relay terminals. The first network element may be an access network device, such as a RAN or NG-RAN.

[0080] In some embodiments, the first network element may obtain a radio resource control (RRC) establishment cause value of the remote terminal, and determine, based on the RRC establishment cause value, that the remote terminal accesses the network through an emergency RSC.

[0081] In some embodiments, the first network element may receive second information sent by the remote terminal; the first network element may determine, based on the second information, that the remote terminal accesses the network via the emergency RSC. Optionally, the second information may be used to determine whether the remote terminal accesses the network via the emergency RSC. For example, the second information indicates whether the remote terminal accesses the network via the emergency RSC; if the second information indicates that the remote terminal accesses the network via the emergency RSC, the first network element may determine, based on the second information, that the remote terminal accesses the network via the emergency RSC.

[0082] In some embodiments, the first network element can receive second information sent by the remote terminal, and the second information can include a source layer 2 identifier (Layer-2 ID) or a destination layer 2 identifier corresponding to the PC5 connection between the remote terminal and the relay terminal; the first network element can determine that the remote terminal accesses the network through the emergency RSC based on the mapping relationship between the source layer 2 identifier or the destination layer 2 identifier and the emergency RSC.

[0083] Optionally, the source layer 2 identifier may be the layer 2 identifier corresponding to the party establishing (or initiating) the PC5 connection, for example, the source layer 2 identifier may be the layer 2 identifier corresponding to the remote terminal. The destination layer 2 identifier may be the layer 2 identifier corresponding to the other party in the PC5 connection, for example, the destination layer 2 identifier may be the layer 2 identifier corresponding to the relay terminal.

[0084] Optionally, the mapping relationship between the source layer 2 identifier or the destination layer 2 identifier and the emergency RSC may be pre-configured in the access network device.

[0085] Optionally, the first network element may receive a connection establishment complete (RRC setup complete) message sent by the remote terminal, and the connection establishment complete message may include the second information.

[0086] Optionally, the first network element may receive a registration request message sent by the remote terminal, and the registration request message may include the second information.

[0087] S720. The first network element sends first information to the second network element.

[0088] The second network element may be AMF.

[0089] Optionally, the first information may be used to indicate whether the remote terminal accesses the network via an emergency RSC. For example, the first information may include: an emergency RSC and / or emergency RSC access indication information. Optionally, the emergency RSC access indication information may indicate whether the remote terminal accesses the network via an emergency RSC. For example, the emergency RSC access indication information may be represented by 0 or 1, where 1 may indicate access via an emergency RSC.

[0090] In some embodiments, the first network element may send a connection message to the second network element, and the connection message may include the first information. Optionally, the connection message may be an initial UE information establishment N2-AP connection (initial UE message establishment N2-AP connection) message.

[0091] In some embodiments, the first network element sends a non-access stratum transport message to the second network element, and the non-access stratum transport message may include the first information. Optionally, the non-access stratum transport message may include a downlink non-access stratum transport (DL NAS transport) message and / or an uplink non-access stratum transport (UL NAS transport) message.

[0092] Optionally, the method 700 may further include step S730, which is as follows:

[0093] S730: The second network element processes the first connection of the remote terminal according to the first information.

[0094] The first connection may be used for non-emergency service communications of the remote terminal. For example, the first connection is a non-emergency packet data unit (PDU) session.

[0095] Optionally, if the remote terminal has established a non-emergency PDU session, the second network element may release the non-emergency PDU session.

[0096] Optionally, if the second network element receives a non-emergency PDU session establishment request message sent by the remote terminal, the second network element may not establish the non-emergency PDU session corresponding to the remote terminal.

[0097] In an embodiment of the present application, the first network element determines that the remote terminal accesses the network through the emergency RSC, and the first network element sends first information to the second network element. The first information is used to indicate that the remote terminal accesses the network through the emergency RSC, which helps the network side perceive the access method of the remote terminal.

[0098] FIG8 is a schematic flow chart of a communication method according to an embodiment of the present application. The method 800 shown in FIG8 may include steps S810 and S820, which are as follows:

[0099] S810: The remote terminal sends third information to the second network element.

[0100] The second network element may be AMF.

[0101] The third information may be used to instruct the remote terminal to access the network via the emergency RSC. For example, the third information may include: emergency RSC and / or emergency RSC access indication information.

[0102] Optionally, the second network element may receive a registration request message sent by the remote terminal, and the registration request message may include third information.

[0103] S820: The second network element processes the second connection of the remote terminal according to the third information.

[0104] Optionally, the second connection may be used for non-emergency service communications of the remote terminal. For example, the second connection is a non-emergency PDU session.

[0105] Optionally, if the remote terminal has established a non-emergency PDU session, the second network element may release the non-emergency PDU session.

[0106] Optionally, if the second network element receives a non-emergency PDU session establishment request message sent by the remote terminal, the second network element may not establish the non-emergency PDU session corresponding to the remote terminal.

[0107] In an embodiment of the present application, the remote terminal sends third information to the second network element, where the third information is used to instruct the remote terminal to access the network through the emergency RSC, which helps the network side to perceive the access method of the remote terminal.

[0108] The method in the embodiment of the present application is described below with reference to FIG9 . FIG9 is a schematic flow chart of the communication method in the embodiment of the present application. The method 900 shown in FIG9 may include steps S910 and S980 , which are as follows:

[0109] S910: The remote UE sends a PC5 connection establishment request message to the relay UE.

[0110] The relay service code in the PC5 connection establishment request can be emergency RSC.

[0111] S920: The relay UE sends a PC5 connection establishment accept message to the remote UE.

[0112] S930: The remote UE sends an RRC setup request message to the gNB.

[0113] The remote UE may send an RRC setup request message to the gNB through the relay UE. The RRC setup request message may carry a temporary mobile subscriber identity (S-TMSI) and an RRC setup cause value.

[0114] At step S940, the gNB returns an RRC setup message to the remote UE.

[0115] S950: The remote UE sends an RRC setup complete message to the gNB.

[0116] The RRC setup complete message can carry a non-access stratum (NAS) container, which can carry a registration request message. The registration request message can carry a registration type. The registration type can be one of the following:

[0117] If the remote UE has initiated initial registration or emergency registration before S910 , the registration type may be mobility registration update.

[0118] If the remote UE has not initiated registration, the registration type can be emergency registration (because the remote UE has accessed the gNB via emergency RSC).

[0119] Optionally, in order to enable the network to distinguish whether the remote UE accesses the network via an emergency RSC, the remote UE may carry second information (or third information) in a registration request message. The second information (or third information) may include: emergency RSC and / or emergency RSC access indication information. Optionally, the emergency RSC access indication information may indicate whether the remote terminal accesses the network via an emergency RSC. For example, the emergency RSC access indication information may be represented by 0 or 1, where 1 may indicate access via an emergency RSC.

[0120] If an RRC connection already exists between the remote UE and the gNB, the UL information transfer message can be used to send the NAS container.

[0121] S960: The gNB sends an initial UE information establishment N2-AP connection message to the AMF.

[0122] This message may carry an RRC establishment cause value and a NAS container. The NAS container may include the registration request message sent in S950.

[0123] If an N2-AP connection already exists between the gNB and the AMF, the gNB may send an uplink non-access stratum transport (UL NAS transport) message to the AMF. This message may carry a NAS container. The NAS container may include the registration request message sent in S950.

[0124] Optionally, to enable the AMF to distinguish whether the remote UE accesses the network via an emergency RSC, the gNB may carry first information in an N2 message (Initial UE Information Establishment N2-AP Connection message or an uplink NAS Transport message). The first information may include: emergency RSC and / or emergency RSC access indication information. For example, the emergency RSC access indication information may be represented by 0 or 1, where 1 may indicate access via emergency RSC.

[0125] Emergency RSC can be sent by remote UE or relay UE to gNB.

[0126] In some embodiments, in addition to the remote UE sending the second information (or third information) to the gNB in ​​S950, the gNB can also learn that the remote UE establishes the RRC connection through the emergency RSC based on the RRC establishment cause value and the remote UE accessing through the relay UE.

[0127] In some embodiments, the remote UE may also send the source layer-2 ID or the destination layer-2 ID in the connection establishment request to the gNB. The gNB may learn from the mapping relationship between the source layer 2 ID or the destination layer-2 ID and the RSC that the remote UE is establishing the RRC connection through the emergency RSC.

[0128] Furthermore, if a non-emergency PDU session has been established previously, the AMF may release the non-emergency PDU session based on the second information (or third information) in the registration request message (this corresponds to step S950) or the first information carried in the N2 message (this corresponds to step S960); or, if the remote UE subsequently initiates a request to establish a non-emergency PDU session, the network side may reject the remote UE's non-emergency PDU session establishment request.

[0129] S970: The AMF returns a registration accept message to the remote UE.

[0130] This message may carry information such as the 5G globally unique temporary UE identity (5G-GUTI) and the tracking area identity (TAI) list.

[0131] The release of the non-urgent PDU session in S960 may be performed after the message sending in S970 is completed.

[0132] S980: The remote UE returns a registration complete message to the AMF.

[0133] In some embodiments, in S950 of the method 900, the remote UE may also directly send third information to the AMF. The third information may include: an emergency RSC and / or an emergency RSC access indication. For example, the emergency RSC access indication information may be represented by 0 or 1, where 1 may indicate access via emergency RSC.

[0134] For example, the remote UE may send a registration request message to the AMF, and the registration request message may include the third information.

[0135] The method embodiment of the present application is described in detail above in conjunction with Figures 1 to 9 . The device embodiment of the present application is described in detail below in conjunction with Figures 10 to 15 . It should be understood that the description of the method embodiment corresponds to the description of the device embodiment. Therefore, for parts not described in detail, reference can be made to the above method embodiment.

[0136] Figure 10 is a schematic structural diagram of a communication device provided in an embodiment of the present application. The communication device 1000 in Figure 10 includes a determining unit 1010 and a sending unit 1020, as follows:

[0137] A determining unit 1010 is configured to determine whether the remote terminal accesses the network via an emergency relay service code RSC;

[0138] The sending unit 1020 is configured to send first information to the second network element, where the first information is used to instruct the remote terminal to access the network through the emergency RSC.

[0139] Optionally, the determining unit 1010 is specifically configured to: determine, according to a radio resource control (RRC) establishment cause value of the remote terminal, that the remote terminal accesses the network through an emergency RSC.

[0140] Optionally, the determining unit 1010 is specifically configured to: receive second information sent by the remote terminal through a relay terminal, the second information being used to determine whether the remote terminal accesses the network through an emergency RSC; and determine whether the remote terminal accesses the network through an emergency RSC according to the second information.

[0141] Optionally, the determination unit 1010 is specifically used to: receive second information sent by the remote terminal, the second information including a source layer 2 identifier or a destination layer 2 identifier corresponding to the PC5 connection between the remote terminal and the relay terminal; and determine that the remote terminal accesses the network through the emergency RSC based on a mapping relationship between the source layer 2 identifier or the destination layer 2 identifier and the emergency RSC.

[0142] Optionally, the determining unit 1010 is specifically configured to: receive a connection establishment completion message sent by the remote terminal, where the connection establishment completion message includes the second information.

[0143] Optionally, the sending unit 1020 is specifically configured to: send a connection message to the second network element, where the connection message includes the first information.

[0144] Optionally, the sending unit 1020 is specifically configured to: send a non-access layer transmission message to the second network element, where the non-access layer transmission message includes the first information.

[0145] Optionally, the first information includes: the emergency RSC and / or emergency RSC access indication information.

[0146] Optionally, the device is an access network device, and the second network element is an access and mobility management function AMF.

[0147] FIG11 is a schematic structural diagram of a communication device provided in an embodiment of the present application. The communication device 1100 in FIG11 includes a receiving unit 1110 and a processing unit 1120, as follows:

[0148] The receiving unit 1110 is configured to receive first information sent by a first network element, where the first information is used to instruct a remote terminal to access the network via an emergency relay service code RSC;

[0149] The processing unit 1120 is configured to process a first connection of the remote terminal according to the first information, where the first connection is used for non-emergency service communication of the remote terminal.

[0150] Optionally, the receiving unit 1110 is specifically configured to: receive a connection message or a non-access layer transmission message sent by the first network element, where the connection message or the non-access layer transmission message includes the first information.

[0151] Optionally, the first connection is a non-emergency packet data unit (PDU) session.

[0152] Optionally, the processing unit 1120 is specifically configured to: release a non-emergency PDU session if the remote terminal has established a non-emergency PDU session.

[0153] Optionally, the processing unit 1120 is specifically configured to: if the apparatus receives a non-emergency PDU session establishment request message sent by the remote terminal, not establish the non-emergency PDU session corresponding to the remote terminal.

[0154] Optionally, the first information includes: the emergency RSC and / or emergency RSC access indication information.

[0155] Optionally, the first network element is an access network device, and the device is an access and mobility management function AMF.

[0156] FIG12 is a schematic structural diagram of a communication device provided in an embodiment of the present application. The communication device 1200 in FIG12 includes a sending unit 1210, which is specifically as follows:

[0157] The sending unit 1210 is configured to send second information to the first network element, where the second information is used to determine whether the device accesses the network through an emergency relay service code RSC.

[0158] Optionally, the second information includes a source layer 2 identifier or a destination layer 2 identifier corresponding to the PC5 connection between the device and the relay terminal.

[0159] Optionally, the sending unit 1210 is specifically configured to: send a connection establishment completion message to the first network element, where the connection establishment completion message includes the second information.

[0160] Optionally, the first network element is an access network device.

[0161] FIG13 is a schematic structural diagram of a communication device provided in an embodiment of the present application. The communication device 1300 in FIG13 includes a receiving unit 1310 and a processing unit 1320, as follows:

[0162] The receiving unit 1310 is configured to receive third information sent by a remote terminal, where the third information is used to instruct the remote terminal to access a network via an emergency RSC;

[0163] The processing unit 1320 is configured to process a second connection of the remote terminal according to the third information, where the second connection is used for non-emergency service communication of the remote terminal.

[0164] Optionally, the receiving unit 1310 is specifically configured to: receive a registration request message sent by the remote terminal, where the registration request message includes the third information.

[0165] Optionally, the third information includes: the emergency RSC and / or emergency RSC access indication information.

[0166] Optionally, the second connection is a non-emergency packet data unit (PDU) session.

[0167] Optionally, the processing unit 1320 is specifically configured to: if the remote terminal has established a non-emergency PDU session, release the non-emergency PDU session.

[0168] Optionally, the processing unit 1320 is specifically configured to: if the apparatus receives a non-emergency PDU session establishment request message sent by the remote terminal, not establish a non-emergency PDU session corresponding to the remote terminal.

[0169] FIG14 is a schematic structural diagram of a communication device provided in an embodiment of the present application. The communication device 1400 in FIG14 includes a sending unit 1410, which is specifically as follows:

[0170] The sending unit 1410 is configured to send third information to the second network element, where the third information is used to instruct the device to access the network through the emergency RSC.

[0171] Optionally, the sending unit 1410 is specifically configured to: send a registration request message to the second network element, where the registration request message includes the third information.

[0172] Optionally, the third information includes: the emergency RSC and / or emergency RSC access indication information.

[0173] Optionally, the second network element is an access and mobility management function AMF.

[0174] FIG15 is a schematic diagram of the structure of an apparatus provided in one embodiment of the present application. The dotted lines in FIG15 indicate that the unit or module is optional. Apparatus 1500 may be used to implement the method described in the above method embodiment. Apparatus 1500 may be a chip or a communication device.

[0175] The device 1500 may include one or more processors 1510. The processor 1510 may support the device 1500 to implement the method described in the method embodiment above. The processor 1510 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

[0176] The apparatus 1500 may further include one or more memories 1520. The memories 1520 store programs that can be executed by the processor 1510, causing the processor 1510 to perform the methods described in the above method embodiments. The memories 1520 may be independent of the processor 1510 or integrated into the processor 1510.

[0177] The apparatus 1500 may further include a transceiver 1530. The processor 1510 may communicate with other devices or chips via the transceiver 1530. For example, the processor 1510 may transmit and receive data with other devices or chips via the transceiver 1530.

[0178] The present invention also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to the communication device provided in the present invention, and the program enables a computer to execute the method performed by the communication device in each embodiment of the present invention.

[0179] The present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to the communication device provided in the present application, and the program causes a computer to execute the method performed by the communication device in each embodiment of the present application.

[0180] The embodiments of the present application also provide a computer program. The computer program can be applied to the communication device provided in the embodiments of the present application, and the computer program enables a computer to execute the method performed by the communication device in each embodiment of the present application.

[0181] It should be understood that in the embodiments of the present application, "B corresponding to A" means that B is associated with A and B can be determined based on A. However, it should also be understood that determining B based on A does not mean determining B based solely on A, but B can also be determined based on A and / or other information.

[0182] It should be understood that the term "and / or" in this document simply describes a relationship between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

[0183] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0184] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0185] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0186] 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 separately, or two or more units may be integrated into one unit.

[0187] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0188] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A communication method, characterized in that: include: The first network element determines that the remote terminal accesses the network via the emergency relay service code RSC; The first network element sends first information to the second network element, where the first information is used to instruct the remote terminal to access the network through the emergency RSC.

2. The method according to claim 1, characterized in that The first network element determines that the remote terminal accesses the network through the emergency RSC, including: The first network element determines, according to a radio resource control (RRC) establishment cause value of the remote terminal, that the remote terminal accesses the network through an emergency RSC.

3. The method according to claim 1, characterized in that The first network element determines that the remote terminal accesses the network through the emergency RSC, including: The first network element receives second information sent by the remote terminal through the relay terminal, where the second information is used to determine that the remote terminal accesses the network through the emergency RSC; The first network element determines, based on the second information, that the remote terminal accesses the network through the emergency RSC.

4. The method according to claim 1, wherein The first network element determines that the remote terminal accesses the network through the emergency RSC, including: The first network element receives second information sent by the remote terminal, where the second information includes a source layer 2 identifier or a destination layer 2 identifier corresponding to the PC5 connection between the remote terminal and the relay terminal; The first network element determines, based on a mapping relationship between the source layer 2 identifier or the destination layer 2 identifier and the emergency RSC, that the remote terminal accesses the network through the emergency RSC.

5. The method according to claim 4, characterized in that The first network element receiving the second information sent by the remote terminal includes: The first network element receives a connection establishment completion message sent by the remote terminal, where the connection establishment completion message includes the second information.

6. The method according to any one of claims 1 to 5, characterized in that The first network element sending first information to the second network element includes: The first network element sends a connection message to the second network element, where the connection message includes the first information.

7. The method according to any one of claims 1 to 5, characterized in that The first network element sending first information to the second network element includes: The first network element sends a non-access layer transmission message to the second network element, where the non-access layer transmission message includes the first information.

8. The method according to any one of claims 1 to 7, characterized in that The first information includes: the emergency RSC and / or emergency RSC access indication information.

9. The method according to any one of claims 1 to 8, characterized in that The first network element is an access network device, and the second network element is an access and mobility management function AMF.

10. A communication method, characterized in that: include: The second network element receives first information sent by the first network element, where the first information is used to instruct the remote terminal to access the network through the emergency relay service code RSC; The second network element processes a first connection of the remote terminal according to the first information, where the first connection is used for non-emergency service communication of the remote terminal.

11. The method according to claim 10, characterized in that The second network element receiving the first information sent by the first network element includes: The second network element receives a connection message or a non-access layer transmission message sent by the first network element, where the connection message or the non-access layer transmission message includes the first information.

12. The method according to claim 10 or 11, characterized in that The first connection is a non-emergency packet data unit (PDU) session.

13. The method according to claim 12, characterized in that The second network element processes the first connection of the remote terminal according to the first information, including: If the remote terminal has established a non-emergency PDU session, the second network element releases the non-emergency PDU session.

14. The method according to claim 12 or 13, characterized in that The second network element processes the first connection of the remote terminal according to the first information, including: If the second network element receives the non-emergency PDU session establishment request message sent by the remote terminal, the second network element does not establish the non-emergency PDU session corresponding to the remote terminal.

15. The method according to any one of claims 10 to 14, characterized in that The first information includes: the emergency RSC and / or emergency RSC access indication information.

16. The method according to any one of claims 10 to 15, characterized in that The first network element is an access network device, and the second network element is an access and mobility management function AMF.

17. A communication method, characterized in that: include: The remote terminal sends second information to the first network element, where the second information is used to determine that the remote terminal accesses the network through the emergency relay service code RSC.

18. The method according to claim 17, characterized in that The second information includes a source layer 2 identifier or a destination layer 2 identifier corresponding to the PC5 connection between the remote terminal and the relay terminal.

19. The method according to claim 18, characterized in that The remote terminal sending second information to the first network element includes: The remote terminal sends a connection establishment completion message to the first network element, where the connection establishment completion message includes the second information.

20. The method according to any one of claims 17 to 19, characterized in that The first network element is an access network device.

21. A communication method, characterized in that: include: The second network element receives third information sent by the remote terminal, where the third information is used to instruct the remote terminal to access the network through the emergency RSC; The second network element processes a second connection of the remote terminal according to the third information, where the second connection is used for non-emergency service communication of the remote terminal.

22. The method according to claim 21, characterized in that The second network element receives third information sent by the remote terminal, including: The second network element receives a registration request message sent by the remote terminal, where the registration request message includes the third information.

23. The method according to claim 21 or 22, characterized in that The third information includes: the emergency RSC and / or emergency RSC access indication information.

24. The method according to any one of claims 21 to 23, characterized in that The second connection is a non-emergency packet data unit (PDU) session.

25. The method according to claim 24, characterized in that The second network element processes the second connection of the remote terminal according to the third information, including: If the remote terminal has established a non-emergency PDU session, the second network element releases the non-emergency PDU session.

26. The method according to claim 24 or 25, characterized in that The second network element processes the second connection of the remote terminal according to the third information, including: If the second network element receives the non-emergency PDU session establishment request message sent by the remote terminal, the second network element does not establish the non-emergency PDU session corresponding to the remote terminal.

27. A communication method, characterized in that: include: The remote terminal sends third information to the second network element, where the third information is used to instruct the remote terminal to access the network through the emergency RSC.

28. The method according to claim 27, characterized in that The remote terminal sending third information to the second network element includes: The remote terminal sends a registration request message to the second network element, where the registration request message includes the third information.

29. The method according to claim 27 or 28, characterized in that The third information includes: the emergency RSC and / or emergency RSC access indication information.

30. The method according to any one of claims 27 to 29, characterized in that The second network element is the access and mobility management function AMF.

31. A communication device, characterized in that: include: A determination unit, configured to determine that the remote terminal accesses the network via an emergency relay service code RSC; The sending unit is used to send first information to the second network element, where the first information is used to instruct the remote terminal to access the network through the emergency RSC.

32. The device according to claim 31, characterized in that The determining unit is specifically configured to determine, according to a radio resource control (RRC) establishment cause value of the remote terminal, that the remote terminal accesses the network through an emergency RSC.

33. The device according to claim 31, characterized in that The determining unit is specifically configured to: receive second information sent by the remote terminal through a relay terminal, where the second information is used to determine that the remote terminal accesses the network through an emergency RSC; and determine that the remote terminal accesses the network through an emergency RSC according to the second information.

34. The device according to claim 31, characterized in that The determination unit is specifically used to: receive the second information sent by the remote terminal, the second information including the source layer 2 identifier or the destination layer 2 identifier corresponding to the PC5 connection between the remote terminal and the relay terminal; determine that the remote terminal accesses the network through the emergency RSC based on the mapping relationship between the source layer 2 identifier or the destination layer 2 identifier and the emergency RSC.

35. The device according to claim 34, characterized in that The determining unit is specifically configured to: receive a connection establishment completion message sent by the remote terminal, where the connection establishment completion message includes the second information.

36. The device according to any one of claims 31 to 35, characterized in that The sending unit is specifically configured to send a connection message to the second network element, where the connection message includes the first information.

37. The device according to any one of claims 31 to 35, characterized in that The sending unit is specifically configured to send a non-access layer transmission message to the second network element, where the non-access layer transmission message includes the first information.

38. The device according to any one of claims 31 to 37, characterized in that The first information includes: the emergency RSC and / or emergency RSC access indication information.

39. The device according to any one of claims 31 to 38, characterized in that The device is an access network device, and the second network element is an access and mobility management function AMF.

40. A communication device, characterized in that: include: a receiving unit, configured to receive first information sent by a first network element, wherein the first information is used to instruct a remote terminal to access a network via an emergency relay service code RSC; A processing unit is configured to process a first connection of the remote terminal according to the first information, where the first connection is used for non-emergency service communication of the remote terminal.

41. The device according to claim 43, characterized in that The receiving unit is specifically configured to receive a connection message or a non-access layer transmission message sent by the first network element, where the connection message or the non-access layer transmission message includes the first information.

42. The device according to claim 43 or 44, characterized in that The first connection is a non-emergency packet data unit (PDU) session.

43. The device according to claim 45, characterized in that The processing unit is specifically configured to release a non-emergency PDU session if the remote terminal has established the non-emergency PDU session.

44. The device according to claim 45 or 46, characterized in that The processing unit is specifically configured to: if the device receives a non-emergency PDU session establishment request message sent by the remote terminal, not establish the non-emergency PDU session corresponding to the remote terminal.

45. The device according to any one of claims 43 to 47, characterized in that The first information includes: the emergency RSC and / or emergency RSC access indication information.

46. ​​The device according to any one of claims 43 to 48, characterized in that The first network element is an access network device, and the device is an access and mobility management function AMF.

47. A communication device, characterized in that include: The sending unit is used to send second information to the first network element, where the second information is used to determine whether the device accesses the network through the emergency relay service code RSC.

48. The device according to claim 47, characterized in that The second information includes a source layer 2 identifier or a destination layer 2 identifier corresponding to the PC5 connection between the device and the relay terminal.

49. The device according to claim 48, characterized in that The sending unit is specifically configured to send a connection establishment completion message to the first network element, where the connection establishment completion message includes the second information.

50. The device according to any one of claims 47 to 49, characterized in that The first network element is an access network device.

51. A communication device, characterized in that include: a receiving unit, configured to receive third information sent by a remote terminal, wherein the third information is used to instruct the remote terminal to access a network through an emergency RSC; The processing unit is configured to process a second connection of the remote terminal according to the third information, where the second connection is used for non-emergency service communication of the remote terminal.

52. The device according to claim 51, characterized in that The receiving unit is specifically configured to receive a registration request message sent by the remote terminal, where the registration request message includes the third information.

53. The device according to claim 51 or 52, characterized in that The third information includes: the emergency RSC and / or emergency RSC access indication information.

54. The device according to any one of claims 51 to 53, characterized in that The second connection is a non-emergency packet data unit (PDU) session.

55. The device according to claim 54, characterized in that The processing unit is specifically configured to release a non-emergency PDU session if the remote terminal has established the non-emergency PDU session.

56. The device according to claim 54 or 55, characterized in that The processing unit is specifically configured to: if the device receives a non-emergency PDU session establishment request message sent by the remote terminal, not establish the non-emergency PDU session corresponding to the remote terminal.

57. A communication device, characterized in that include: The sending unit is used to send third information to the second network element, where the third information is used to instruct the device to access the network through the emergency RSC.

58. The device according to claim 57, characterized in that The sending unit is specifically configured to send a registration request message to the second network element, where the registration request message includes the third information.

59. The device according to claim 57 or 58, characterized in that The third information includes: the emergency RSC and / or emergency RSC access indication information.

60. The device according to any one of claims 57 to 59, characterized in that The second network element is the access and mobility management function AMF.

61. A communication device, characterized in that The communication device comprises a memory, a transceiver and a processor, wherein the memory is used to store programs, the processor transmits and receives data through the transceiver, and the processor is used to call the program in the memory so that the communication device executes the method as described in any one of claims 1 to 30.

62. A chip, characterized in that: The device comprises a processor configured to call a program from a memory so that a device equipped with the chip executes the method according to any one of claims 1 to 30.

63. A computer-readable storage medium, characterized in that A program is stored thereon, the program causing a computer to execute the method according to any one of claims 1 to 30.

64. A computer program product, characterized in that A program is included, the program causing a computer to execute the method according to any one of claims 1 to 30.

65. A computer program, characterized in that The computer program causes a computer to execute the method according to any one of claims 1 to 30.

Images